OTOY Forums

mrom wrote:Thank you, starezloto texture works now.

But what is strange: I made a new custom workspace (including a live viewer window), and it takes quite long (xx secs) to load.

without the live viewer window, there's no delay.


EDIT: now it takes less than 30 secs, around 10.

The change on activation pattern was because of this topic: http://forums.cgsociety.org/showthread. ... &t=1426863

Installed this build and the 3.05 Test 4 standalone.

I can login into standalone and everything is fine. But in cinema, as soon as I want to open the octane settings cinema freezes....the first time it happened it said that I'm not logged in correctly or something. Second time no popup, just freeze.

Win10
C4D R18
GTX1080 Hybrid
32GB RAM

I second that material previews don't work, thumbnails are not generated. Otherwise good so far

Thank you

DinoMuhic wrote:Installed this build and the 3.05 Test 4 standalone.

I can login into standalone and everything is fine. But in cinema, as soon as I want to open the octane settings cinema freezes....the first time it happened it said that I'm not logged in correctly or something. Second time no popup, just freeze.

Win10
C4D R18
GTX1080 Hybrid
32GB RAM

Can you make a capture to show this? What happens if you open Live Viewer before settings?

What happens with latest test4? If all good i'll make a release today or monday.

aoktar wrote:What happens with latest test4? If all good i'll make a release today or monday.

unfortunately i can't tell you, if this issue Is new or always has been there.
since i am new to the workflow of saving material compositions as orbx into the localdb (trying it today for the first time) to then import them again in any other project.
but still i wanted you to know:

when i export a material-composition, that once had been created in a c4d-file, as orbx and then import it into c4d again, there is some things missing.
importing the same file into standalone though, this issue does not appear, everything is as expected.
i need to mentioned that i tried to isolate the material, that looses it's inputs and then went through the same export/import procedure, but this way nothing gets lost. so, i only experience that in the context of the "bigger" material-comp.

please see this screenshots for explanations, additionally the orbx-file is attached:
http://www.mesutcapkin.com/temp/testmaterial.orbx
(almost forgot the original c4d-file): http://www.mesutcapkin.com/temp/orbx_mat.c4d

Hi Aoktar,

thx for the great update but....i have a Problem with the activation.
I use Win7 64bit, Cinema4D R17 and this octane version...

Cinma4D R17 dont close correctly...if i close Cinema4D, Cinema4D runs still in the background und dont close. So i cant use Octane on another machine because its still activated on the other machine.
If i start and close the standalone alone, all works perfect.....(if i close, standalone tells otoy that is not in use)
If i start Cinema4D R15 with Octane-Plugin 3.04 and i close it, all would be fine (Plugin+Standalone close correctly)

so it must be a problem with the new plugin

Do you know what kind of problem this be could?

I also have the exact problem on two PC's win10 and win7. C4D just hungs in the background and it's tested with only Octane in the plugins folder on both. Octane standalone closes just fine. If I remove the Octane plugin from the C4D folder and put back all my other plugins, C4D works and closes as expected. It is like it is not signing out for some reason, I'm just thinking here, no actual knowledge. this is on C4D 17.053, Latest standalone and latest plugin and Nvidia drivers on both PC's. Also can anyone verify that the material previews don't work anymore in that release? Here when I update a material it just turns grey.
Update: Actually just tested and the C4D not closing right only happens because I have the Live preview window docked on my interface, if I undock it and close it, C4D closes as expected with Octane, maybe that helps?
Thanks,

KonstantinosD wrote:I also have the exact problem on two PC's win10 and win7. C4D just hungs in the background and it's tested with only Octane in the plugins folder on both. Octane standalone closes just fine. If I remove the Octane plugin from the C4D folder and put back all my other plugins, C4D works and closes as expected. It is like it is not signing out for some reason, I'm just thinking here, no actual knowledge. this is on C4D 17.053, Latest standalone and latest plugin and Nvidia drivers on both PC's. Also can anyone verify that the material previews don't work anymore in that release? Here when I update a material it just turns grey.
Update: Actually just tested and the C4D not closing right only happens because I have the Live preview window docked on my interface, if I undock it and close it, C4D closes as expected with Octane, maybe that helps?
Thanks,

thx, but doesn't work.
Octane live viewer is not integrate in my interface....

NVN wrote: Cinma4D R17 dont close correctly...if i close Cinema4D, Cinema4D runs still in the background und dont close. So i cant use Octane on another machine because its still activated on the other machine.
Do you know what kind of problem this be could?

I'm aware of that. But i don't know how much often happens on users. This happens randomly as i can understand. But i'm still not sure about reason.
Could you try with disabling "Allow to send renderstarts to Otoy"?