Nice work, Ahmet. Really.. well done (and Otoy chaps !!)
ten
Version 2.12.2 - final (updated on 18.11.14)
Moderators: ChrisHekman, aoktar
- solidworkattack
- Posts: 18
- Joined: Sun Oct 05, 2014 8:37 am
still getting these weird colortransformations at the beginning of liveviewing..
https://www.youtube.com/watch?v=PiSX3UE ... e=youtu.be
happens since 2.1 - haven't had any issues with 2.06
tested several HDRIs and also scenery without HDRI
updated nvidia drivers and display drivers - but that doesn't fix it.
I mean it's kind of useless to use directlighting or pathtracing since I always have to wait a certain time to see the "final" color of the object.
pmc works
just recorded a demo to show what I mean.
I would be really grateful if anybody could help me.
philipp
https://www.youtube.com/watch?v=PiSX3UE ... e=youtu.be
happens since 2.1 - haven't had any issues with 2.06
tested several HDRIs and also scenery without HDRI
updated nvidia drivers and display drivers - but that doesn't fix it.
I mean it's kind of useless to use directlighting or pathtracing since I always have to wait a certain time to see the "final" color of the object.
pmc works
just recorded a demo to show what I mean.
I would be really grateful if anybody could help me.
philipp
Cinema R16 | Win 8.1 Pro | 2x Geforce GTX780 6GB | i7-4960X Extreme Edition | 16GB
COOL, have you notified how much faster and much better on cleaning the noises in 2.10?solidworkattack wrote:still getting these weird colortransformations at the beginning of liveviewing..
https://www.youtube.com/watch?v=PiSX3UE ... e=youtu.be
happens since 2.1 - haven't had any issues with 2.06
tested several HDRIs and also scenery without HDRI
updated nvidia drivers and display drivers - but that doesn't fix it.
I mean it's kind of useless to use directlighting or pathtracing since I always have to wait a certain time to see the "final" color of the object.
pmc works
just recorded a demo to show what I mean.
I would be really grateful if anybody could help me.
philipp
i think we should give more info what's that. Then i'm sure you will thanks to Otoy guys.
It's coherent mode, read please related section from Standalone threads:
http://render.otoy.com/forum/viewtopic.php?f=33&t=42564
http://render.otoy.com/forum/viewtopic.php?f=33&t=42854
you can disable coherent, and loose the power.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
- solidworkattack
- Posts: 18
- Joined: Sun Oct 05, 2014 8:37 am
aoktar wrote:COOL, have you notified how much faster and much better on cleaning the noises in 2.10?solidworkattack wrote:still getting these weird colortransformations at the beginning of liveviewing..
https://www.youtube.com/watch?v=PiSX3UE ... e=youtu.be
happens since 2.1 - haven't had any issues with 2.06
tested several HDRIs and also scenery without HDRI
updated nvidia drivers and display drivers - but that doesn't fix it.
I mean it's kind of useless to use directlighting or pathtracing since I always have to wait a certain time to see the "final" color of the object.
pmc works
just recorded a demo to show what I mean.
I would be really grateful if anybody could help me.
philipp
i think we should give more info what's that. Then i'm sure you will thanks to Otoy guys.
It's coherent mode, read please related section from Standalone threads:
http://render.otoy.com/forum/viewtopic.php?f=33&t=42564
http://render.otoy.com/forum/viewtopic.php?f=33&t=42854
you can disable coherent, and loose the power.
read about it on the standalone thread. cool feature, indeed. going to keep it activated for rendering for sure - just going to disable it while playing with the colorsliders.
thanks for your fast reply
Cinema R16 | Win 8.1 Pro | 2x Geforce GTX780 6GB | i7-4960X Extreme Edition | 16GB
Hey Ahmed,
thank you for this great update - lots of improvements to discover! You are doing such a great job like the otoy team does and I want to say thank you all for that.
Two issues with this release:
- In NG editor the button 'get active material' is doing nothing
- terminating render in PV via ESC freezes Cinema
Best
Ron
thank you for this great update - lots of improvements to discover! You are doing such a great job like the otoy team does and I want to say thank you all for that.
Two issues with this release:
- In NG editor the button 'get active material' is doing nothing
- terminating render in PV via ESC freezes Cinema
Best
Ron
Master: WIN 10 64bit, i7 4930 4,5 Ghz, 64 GB RAM, 1600 W PSU, 1 TB SSD, 14 TB RAID, 2 x RTX 3090
Thanks Ron,Ron wrote:Hey Ahmed,
thank you for this great update - lots of improvements to discover! You are doing such a great job like the otoy team does and I want to say thank you all for that.
Two issues with this release:
- In NG editor the button 'get active material' is doing nothing
- terminating render in PV via ESC freezes Cinema
Best
Ron
1) Which version? R15? try it LV while LV is open. It may occurs sometimes as i see but not common.
2) This is not expected behaviour. Do you have hairs on scene or something others as passes?
Regards,
Ahmet
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
rgd 1) It's R16 and it happened a couple of times while rendering in PV. After finishing the render it worked as expectedaoktar wrote:Thanks Ron,Ron wrote:Hey Ahmed,
thank you for this great update - lots of improvements to discover! You are doing such a great job like the otoy team does and I want to say thank you all for that.
Two issues with this release:
- In NG editor the button 'get active material' is doing nothing
- terminating render in PV via ESC freezes Cinema
Best
Ron
1) Which version? R15? try it LV while LV is open. It may occurs sometimes as i see but not common.
2) This is not expected behaviour. Do you have hairs on scene or something others as passes?
Regards,
Ahmet
rgd 2) No hair nor anything complex in scene - just simple objects. Happening only in stills, if rendering animation I can terminate rendering
Regards
Ron
Master: WIN 10 64bit, i7 4930 4,5 Ghz, 64 GB RAM, 1600 W PSU, 1 TB SSD, 14 TB RAID, 2 x RTX 3090
i don't think R16 version is much stabile. I see some strange behaviour, will test it moreRon wrote: rgd 1) It's R16 and it happened a couple of times while rendering in PV. After finishing the render it worked as expected
rgd 2) No hair nor anything complex in scene - just simple objects. Happening only in stills, if rendering animation I can terminate rendering
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Hi aoktar,
looks good!
one question...:
is ist possible to work with Vertexmap Shading in the near Future..?
...i wish to do something like that with octane...
http://larsnaglerworks.com/EspressoTest ... -Small.mp4
thank you..!
looks good!
one question...:
is ist possible to work with Vertexmap Shading in the near Future..?
...i wish to do something like that with octane...

http://larsnaglerworks.com/EspressoTest ... -Small.mp4
thank you..!
.
.
.
http://www.larsnaglerworks.com
http://www.behance.net/LarsNagler
http://cargocollective.com/larsnaglerworks
Mac Pro 5.1 :: 3,33 GHz 6-Core Intel Xeon :: Mac Pro Nvidia GTX680 4 Gig :: 32GB :: C4D 13 Studio :: Octane Renderer
OP-1
.
.
http://www.larsnaglerworks.com
http://www.behance.net/LarsNagler
http://cargocollective.com/larsnaglerworks
Mac Pro 5.1 :: 3,33 GHz 6-Core Intel Xeon :: Mac Pro Nvidia GTX680 4 Gig :: 32GB :: C4D 13 Studio :: Octane Renderer
OP-1
I'm seeing a strange gama-shading behavior. Using R16. Have not tested in R15 yet.
When I first open a scene and it renders in the Live Viewer, I get one result (see Octane-Spiders_1).
Then if I navigate the scene or just select some object in the scene, the Live Viewer renders
the image different (see Octane-Spiders_2). I get the same result with Direct Lighting and Path Tracing.
Am I doing something wrong with my scene set-up or is this some other issue?
When I first open a scene and it renders in the Live Viewer, I get one result (see Octane-Spiders_1).
Then if I navigate the scene or just select some object in the scene, the Live Viewer renders
the image different (see Octane-Spiders_2). I get the same result with Direct Lighting and Path Tracing.
Am I doing something wrong with my scene set-up or is this some other issue?
i7 4930K_Asus_RampageIV-Extreme_64GB_3-Titan_NVIDIA-337.88_Win7-64