Beta 0.68 (SDK 1.18 ) obsolete

[aoktar]

hi ChrisVis,
Live viewer takes geometry from viewport data. But Picture viewer getting scene data of C4D renderer.
So it's normal not a bug. Live vewer shows geometry tesellation(Hypernurbs) as opengl viewport, but Picture viewer uses render settings of objects. Also Spheres which is checked "Render Perfect" which are not generating polygons.

[ChrisVis]

hi ChrisVis,
Live viewer takes geometry from viewport data. But Picture viewer getting scene data of C4D renderer.
So it's normal not a bug. Live vewer shows geometry tesellation(Hypernurbs) as opengl viewport, but Picture viewer uses render settings of objects. Also Spheres which is checked "Render Perfect" which are not generating polygons.

Hi aoktar,

thank you for this reply and the detailed inside of the renderer differences... I wasn`t aware of the "render perfect" checked mark, that a sphere will not be rendered, if it is checked. That solved some of my problems with the differences of preview and picture manager renderer! Is this only with spheres or does this affect other objects / geometries, too?

Also I had some new problems now that didn`t happen before, and I don`t know if it is related to octane or just the Nvidia driver or if my hardware is getting weak.
Got 2 times within minutes a bluescreen just while working in a scene, not final rendering... with a message I couldn`t completely read but was related to a nvlddmdm.sys file.... some display driver error.

And I got random unavailabilites of my GTX590s the last few days... 2 different cards (only 1 at a time) sometimes just dissapear in octane and even in my GPU obsever gadget, while sometimes still being shown in the windows device manager, sometimes also disappearing there.
Then I have to restart and while that windows hangs until I turn of my turbobox, then it goes down and reastarts and the GPUs are there again.

All these problems just started the last few days... I had 2 bluescreens with 0.6.8a and 1 bluescreen with 0.6.7c today.

Do I get into NVIDIA 320.18 driver stability problems with GTX 5xx series as reported in some forums more and more? I think I will go back to 314.22 for more tests... these issues are getting me nuts somehow, not blaming you at all aoktar (you are doing awesome work here! ), but I don`t know why I suddenly have so much stability issues... and I have to finish some work.

Also updated my Intel chipset drivers to Intel Chipset 9.4.0.1017, but didn`t solve anything.
Do you have any ideas about the bluescreen? You also mentioned that some of your GTX590 sometimes disappear in octane, right? Did this happen before or just since 320.18? I never had this issue before and I think I am using 320.18 for 1 month now... these disappearing problems just happen since last week I think.

Hope to get all back to rock stable system and work again soon,
Greetings,
ChrisVis

[aoktar]

hi ChrisVis,
i suppose that ungenerated geometry problem is on Spheres only.
For Blue screen, i'm using driver 314.22 and have never any problems. This seems like a driver-hardware problem. But i don't have much more technical info about it. General forum section can be more helpful for you.

[cfrank78]

Hi!

0.6.8a works pretty stable. Only a view crashes and allways with update geometry but only with more complex szenes and only if i use all gpus, even the display gpu.

But one thing i found out was - not any material of the live database works. only a veeeeeeeeery view. But, no leather, no wood, no curtain....nothing. Why is that? In max they work well, in c4d they just look glossy or diffuse......completely strange.

Another point. How can i adjust target lights to be visible in the render view? I tried a view sliders but in the renderview the target and area lights are not visible, just their light.

Kind regards Chris!

[aoktar]

Hi!

0.6.8a works pretty stable. Only a view crashes and allways with update geometry but only with more complex szenes and only if i use all gpus, even the display gpu.

But one thing i found out was - not any material of the live database works. only a veeeeeeeeery view. But, no leather, no wood, no curtain....nothing. Why is that? In max they work well, in c4d they just look glossy or diffuse......completely strange.

Another point. How can i adjust target lights to be visible in the render view? I tried a view sliders but in the renderview the target and area lights are not visible, just their light.

Kind regards Chris!

dblive manager is working good for me as in picture. Can be a character problem with directories?
For visible lights, you must put octanelighttag and adjust visibility

[miroof]

0.68a is unstable for me
with basic scene setup

[aoktar]

0.68a is unstable for me
with basic scene setup

are you sure that you did a clean install? Can you give me more info about setup, files?

[miroof]

21h25:i delete the c4doctane folder in my pluging then unzip the last version
( except for one version who needed old files )
I had oct.dat inside cinema 4d folder

21h26:I just to delete this .dat, let's see if it was my problem
21:27: I crashed launching a preview in the live render, i just order to convert my material to octane during this time.
windows report : AppHangB1

[cfrank78]

Ok found my Problems. Had an issue with the directorys!

Now everything works!

But i have another question. When i use max and use movable proxies, i can do realtime animation preview, but when i do the same thing in cinema4d, give the octane object tag and start to play the szene, it is allways much, much, much slower than max. In Cinema it is writing voxelizing image, voxelizing finised, render, voxelizing image, voxelizing finished, render. ando so on. i have a pretty fast cpu but there is absolutely no way to playback the szene smothly with updating geometry so a realtime preview is not possible, or am i doing something wrong again? I also tried it with the lowest settings possible, its allways lagging behind and "laggy" cause of this voxelization. Why is that so much more complicated than with the Max Plugin?

Hope i do something wrong!

Kind regards Chris!

[aoktar]

Ok found my Problems. Had an issue with the directorys!

Now everything works!

But i have another question. When i use max and use movable proxies, i can do realtime animation preview, but when i do the same thing in cinema4d, give the octane object tag and start to play the szene, it is allways much, much, much slower than max. In Cinema it is writing voxelizing image, voxelizing finised, render, voxelizing image, voxelizing finished, render. ando so on. i have a pretty fast cpu but there is absolutely no way to playback the szene smothly with updating geometry so a realtime preview is not possible, or am i doing something wrong again? I also tried it with the lowest settings possible, its allways lagging behind and "laggy" cause of this voxelization. Why is that so much more complicated than with the Max Plugin?

Hope i do something wrong!

Kind regards Chris!

What kind of problem with directories? If it's a bug still need fixing.
Voxelling speed each program must be similar. Are you sure movable meshes has similar polygon counts as Max? Voxeling messages is not a matter because also max plugin does same way but not display message. Another note that's we are not yet compiling speed tag. This can give some speed but not for voxelling.