Page 7 of 12
Re: OctaneRender® for 3ds max® v4.00-RC7 - 6.09 [TEST]
Posted: Wed Nov 07, 2018 11:49 am
by paride4331
Hi mbtke and kcpr-raffaEl,
could you try a quick test:
install Octane standalone (using installer, not .zip), then restart windows.
Have you still CUDA 700 error working with 3dsMax?
Let me hear from you.
Regards
Paride
Re: OctaneRender® for 3ds max® v4.00-RC7 - 6.09 [TEST]
Posted: Wed Nov 07, 2018 11:59 am
by paride4331
paride4331 wrote:Hi mbtke and kcpr-raffaEl,
could you try a quick test:
install Octane standalone (using installer, not .zip), then restart windows.
Have you still CUDA 700 error working with 3dsMax?
Let me hear from you.
Regards
Paride
@mbekte
could you try uncheck Active on Device 2, does 3dsMax lag?
Regards
Paride
Re: OctaneRender® for 3ds max® v4.00-RC7 - 6.09 [TEST]
Posted: Thu Nov 08, 2018 8:44 am
by HHbomb
"I get a lot of crashes of max when opening "environnement and effects" ( 8 ) in 6.09 and 6.08 especially when having a hdr map in environnement texture."
I'm the only one ?
Re: OctaneRender® for 3ds max® v4.00-RC7 - 6.09 [TEST]
Posted: Thu Nov 08, 2018 10:26 am
by mbetke
I installed Stand-Alone and browsing my Environment-Textures and UI is faster now. No lags or errors so far. Will keep an eye on it during wok with large scenes.
Re: OctaneRender® for 3ds max® v4.00-RC7 - 6.09 [TEST]
Posted: Thu Nov 08, 2018 11:46 am
by mbetke
Okay I again got the CUDA700 error with the scene I sent you and disables Device 2 plus installed stand-alone.
You have the scene already.
This time I was able to produce the error while working in material editor (again) with open viewport.
I clicked several times around and changed values of the rock materials' displacement, then jumped back to environment map slot, changed some stuff like gamma and rotation there, then back to the displacement material.
Render stopped, pop up window appeared.
Maybe the error comes up more often with larger textures? No idea...
Code: Select all
CUDA error 700 on device 3: an illegal memory access was encountered
-> failed to deallocate device memory
CUDA error 700 on device 3: an illegal memory access was encountered
-> could not get memory info
CUDA error 700 on device 3: an illegal memory access was encountered
-> failed to deallocate device memory
CUDA error 700 on device 3: an illegal memory access was encountered
-> could not get memory info
CUDA error 700 on device 3: an illegal memory access was encountered
-> failed to deallocate device memory
CUDA error 700 on device 3: an illegal memory access was encountered
-> could not get memory info
CUDA error 700 on device 3: an illegal memory access was encountered
-> failed to deallocate device memory
CUDA error 700 on device 3: an illegal memory access was encountered
-> could not get memory info
CUDA error 700 on device 3: an illegal memory access was encountered
-> failed to deallocate device memory
CUDA error 700 on device 3: an illegal memory access was encountered
-> could not get memory info
CUDA error 700 on device 3: an illegal memory access was encountered
-> failed to deallocate device memory
CUDA error 700 on device 3: an illegal memory access was encountered
.
.
.
.
.
.
.
Re: OctaneRender® for 3ds max® v4.00-RC7 - 6.09 [TEST]
Posted: Thu Nov 08, 2018 12:22 pm
by paride4331
Hi mbetke,
could try this:
viewtopic.php?f=27&t=69413
and uncheck (if you checked) "enable repeated viewport update" in Octane global setting > trouble shooting.
Let me hear from you.
Regards
Paride
Re: OctaneRender® for 3ds max® v4.00-RC7 - 6.09 [TEST]
Posted: Fri Nov 09, 2018 8:50 am
by mbetke
I did. Will observe and report back.
I got news about my overbright images issue. maybe you remember.
It seems to appear if HDRI Gamma is greater 1 and Exposure in Imager also with an higher value.
For example I had to change HDRI Gamma from 1.1 to 1.0 and Imager Exposure from 4 to 0.3 to get the same look than in Octane 3. I hope it helps a bit to nail down the source?
Re: OctaneRender® for 3ds max® v4.00-RC7 - 6.09 [TEST]
Posted: Fri Nov 09, 2018 11:53 am
by paride4331
mbetke wrote:I did. Will observe and report back.
I got news about my overbright images issue. maybe you remember.
It seems to appear if HDRI Gamma is greater 1 and Exposure in Imager also with an higher value.
For example I had to change HDRI Gamma from 1.1 to 1.0 and Imager Exposure from 4 to 0.3 to get the same look than in Octane 3. I hope it helps a bit to nail down the source?
Hi mbetke,
could you check if opening that scene with V3 and V4 response curve or order was changed?
Regards
Paride
Re: OctaneRender® for 3ds max® v4.00-RC7 - 6.09 [TEST]
Posted: Fri Nov 09, 2018 4:45 pm
by coilbook
Hi Why when I try to increase transmission instead of glass effect it starts glowing Thanks
my goal is red hot melted glass. ANd i thought in the uber material you can have clear and light emission at the same time
Re: OctaneRender® for 3ds max® v4.00-RC7 - 6.09 [TEST]
Posted: Mon Nov 12, 2018 10:03 am
by mbetke
Hi mbetke,
could you check if opening that scene with V3 and V4 response curve or order was changed?
Regards
Paride
Win 7 / i7 5
I got a very nice example this morning while re-using a 3.07 scene.
With 3.07 all is fine. A bit bright but that was my setting. HDR Gamme is 1.3, You can see orange tones of wood and green gras looking good.
Then I installed latest 3.08. Response curve in default "Response/Gamma/LUT" order. Image totally blown out. After that I set HDR Gamma down to 1.0. Brightness looking normal, but wood and gras looking a bit blown out.
On version 4 (latest), same look and behavior like in 3.08. Response curve in default "Response/Gamma/LUT" order and not changed. Same Gamma behavior.
Must really be a combination of envionment texture, and imager. Because like I wrote before, as soon as i rebuilt the same environment textue HDR setup from scratch all looks like it should. Just copy/pasting doesn't work. I need to rebuilt it.