OTOY Forums

aoktar wrote:

SVITAdmin wrote:ok. Back to testing. 99f seems to lock up C4D whenever i open an octane file on our PCs

why? It's very great for everyone

I wish i knew. C4D just locks up before showing anything. I can't get a report or anything. Going back to 99e fixed the issue.

SVITAdmin wrote:

aoktar wrote:

SVITAdmin wrote:ok. Back to testing. 99f seems to lock up C4D whenever i open an octane file on our PCs

why? It's very great for everyone

I wish i knew. C4D just locks up before showing anything. I can't get a report or anything. Going back to 99e fixed the issue.

do you have vnapi.dll in plugin?

aoktar wrote: do you have vnapi.dll in plugin?

i see nvapi.dll and nvapi64.dll, but no vnapi.dll

99f introduced an offset in the rendered image. It's a 2d offset which can be fixed by moving the layer in aftereffects/photoshop to match the position of the old render (you're missing the edge pixels of course).

Render of 99e looks as it should and matches cinemas viewport, 99f moves the framing to the left and down.

aoktar, I'm loving the Team Render support and all the other work you have done.

Most of my work is for still images, so that's why I was asking about it.

I think at this point I need to look at the hardware side of things. Water-cooling my next build will happen for sure.
My Titan temps right now are about 70C - 80C. Makes me a little nervous.....

When the cloud render service happens, I will try that as well.

Thanks again for all your hard work!

Augustronic: there is no different in codes to cause this. Only dll loading function is updated. Can you be sure there is no user mistake?

Artdude12: I'm looking forward this native support. But now i have to fix current features to go ahead

Any other reply for last version? I'm curious about is it working or has problems on startup or others?

aoktar wrote:Any other reply for last version? I'm curious about is it working or has problems on startup or others?

I'm finishing up a render, but will try the full install of 99f when that is done. Curious as to why it's only locking up my C4D and no one else's.

Hi - sorry to report this - but I get a crash on activating plugin in the settings window - Cinema just stops work. I'm booting into windows 8 on a Mac Pro 12 core and running Cinema4d R15

I have tried =>
deleting prefs from Maxon Appdata folder - restarting - reactivate = crash
running the uninstall package in the cinema folder - reinstalling - reactivating = crash
deleting all aspects of octane altogether and re-installing from fresh (1.2 and 99f) - reactivate = crash
And other various ways ie not entering activation info for 1.20 so it asks from within cinema, reverting back to an earlier version (.82) = this doesn't crash - just refuses to activate
Tried running C4D as administrator, deleting all other plugins..

Still end result is crash on activation..

I have read elsewhere a clean install of windows fixes this - but I really dont want to do that.

Has anyone had any luck with a similar setup?

Octane 1.20 runs like a dream BTW

Regards
Stuart

pulsegorup: have you a win7 system to check it? Maybe a problem on some win8.1 systems during activation. Some people worked on W8.1's