OTOY Forums

neonZorglub wrote:

ramone163 wrote:
Confirm.
My time is:
Standalone RC7 - loads in 5 seconds
3ds Max 2019 RC7 - loads in 6 MINUTES!
3ds Max 2017 3.07-4.43 - loads in 7 second (and viewport performance much better than RC7)

And if I rotate some object, I see a duplicate.

Hi ramone, coilbook,
Thanks for your scene.
I could reproduce your slow loading time; it seems to come from the 'Enable Animated material update in Viewport' option, in Material tab of global preferences ..
Turning it off brings me back to < 5sec load time ..
Sorry about that, it seems to recreate / update materials for every instances.. This will be fixed in the next version.

I 'll investigate the rotation /duplicate issue, I couldn't reproduce it yet.
Thanks,

Thank you! Also please look into forest pack has no motion blur. We can now replace any reference object with forest pack and it evaluates very fast but we have no motion blur. . THnaks Link to post viewtopic.php?f=81&t=69509

rc7 can crash during octane viewport open while adjusting sun volume texture or just textures max must be restarted

CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to download symbol(stats data)
device 2: direct light kernel failed
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to download symbol(stats data)
device 1: direct light kernel failed
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to create link
device 1: failed to create OSL compile context:

device 1: failed to compile module 1
CUDA error 700 on device 1: an illegal memory access was encountered
-> could not get memory info
CUDA error 700 on device 1: an illegal memory access was encountered
-> could not get memory info
CUDA error 700 on device 1: an illegal memory access was encountered
-> could not get memory info

-> failed to unload module
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to bind device to current thread
device 1: failed to initialize context
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to bind device to current thread
device 2: failed to initialize context
denoiserThread1 : Initialization failed. Restart required
CUDA error 201 on device 1: invalid device context
-> failed to create link
device 1: failed to create OSL compile context:

device 1: failed to compile module 0
CUDA error 201 on device 2: invalid device context
-> failed to create link
device 2: failed to create OSL compile context:

device 2: failed to compile module 0

EDIT: Deleted. Flipped normals...

coilbook wrote:rc7 can crash during octane viewport open while adjusting sun volume texture or just textures max must be restarted

CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to download symbol(stats data)
device 2: direct light kernel failed
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to download symbol(stats data)
device 1: direct light kernel failed
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to create link
device 1: failed to create OSL compile context:

device 1: failed to compile module 1
CUDA error 700 on device 1: an illegal memory access was encountered
-> could not get memory info
CUDA error 700 on device 1: an illegal memory access was encountered
-> could not get memory info
CUDA error 700 on device 1: an illegal memory access was encountered
-> could not get memory info

-> failed to unload module
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to bind device to current thread
device 1: failed to initialize context
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to bind device to current thread
device 2: failed to initialize context
denoiserThread1 : Initialization failed. Restart required
CUDA error 201 on device 1: invalid device context
-> failed to create link
device 1: failed to create OSL compile context:

device 1: failed to compile module 0
CUDA error 201 on device 2: invalid device context
-> failed to create link
device 2: failed to create OSL compile context:

device 2: failed to compile module 0

Hi coilbook,
it would
I think it depends on a Vram issue, it should already be solved in the final V4 SDK.
Regards
Paride

Well RC7 is giving the same error of exceeding 20 devices even though I am using exactly 20

"OctaneRender 4.00 RC7 (4000017)

the total count of GPUs used locally and over the network exceeds 20. ignoring slave ..... with 5 device(s).
"

paride4331 wrote:

coilbook wrote:rc7 can crash during octane viewport open while adjusting sun volume texture or just textures max must be restarted

CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to download symbol(stats data)
device 2: direct light kernel failed
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to download symbol(stats data)
device 1: direct light kernel failed
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to create link
device 1: failed to create OSL compile context:

device 1: failed to compile module 1
CUDA error 700 on device 1: an illegal memory access was encountered
-> could not get memory info
CUDA error 700 on device 1: an illegal memory access was encountered
-> could not get memory info
CUDA error 700 on device 1: an illegal memory access was encountered
-> could not get memory info

-> failed to unload module
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to bind device to current thread
device 1: failed to initialize context
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to bind device to current thread
device 2: failed to initialize context
denoiserThread1 : Initialization failed. Restart required
CUDA error 201 on device 1: invalid device context
-> failed to create link
device 1: failed to create OSL compile context:

device 1: failed to compile module 0
CUDA error 201 on device 2: invalid device context
-> failed to create link
device 2: failed to create OSL compile context:

device 2: failed to compile module 0

Hi coilbook,
it would
I think it depends on a Vram issue, it should already be solved in the final V4 SDK.
Regards
Paride

Hi Paride,
were you able to tell otoy about no motion blur for moving itoo forest objects? Thanks

coilbook wrote:

neonZorglub wrote:

ramone163 wrote:
Confirm.
My time is:
Standalone RC7 - loads in 5 seconds
3ds Max 2019 RC7 - loads in 6 MINUTES!
3ds Max 2017 3.07-4.43 - loads in 7 second (and viewport performance much better than RC7)

And if I rotate some object, I see a duplicate.

Hi ramone, coilbook,
Thanks for your scene.
I could reproduce your slow loading time; it seems to come from the 'Enable Animated material update in Viewport' option, in Material tab of global preferences ..
Turning it off brings me back to < 5sec load time ..
Sorry about that, it seems to recreate / update materials for every instances.. This will be fixed in the next version.

I 'll investigate the rotation /duplicate issue, I couldn't reproduce it yet.
Thanks,

Thank you! Also please look into forest pack has no motion blur. We can now replace any reference object with forest pack and it evaluates very fast but we have no motion blur. . THnaks Link to post viewtopic.php?f=81&t=69509

Hi coilbook,
For the rotation / duplicate issue, it could be caused by same object instances with different properties (eg motion blur steps) used in the same scatter node.
It might be fixed by turning off 'Use same scatter node for compatible instances' in Global settings / troubleshooting ..
For forest pack motion blur, could you post a small sample scene ?
Thanks

I get regular 3ds max crashes after I render in inteactive viewport, saved the image to file, closed viewport, load new scene. During the file opening process 3ds max crashes. Not depending on a certain scene.

Its a shame that its not possible to view this 3ds max error files in any way. Maybe there could be a hint inside.

mbetke wrote:I get regular 3ds max crashes after I render in inteactive viewport, saved the image to file, closed viewport, load new scene. During the file opening process 3ds max crashes. Not depending on a certain scene.

Its a shame that its not possible to view this 3ds max error files in any way. Maybe there could be a hint inside.

Hi mbetke,
thanks for your report.
Regards
Paride.

Converting a textured cube to an editable poly while viewport is open, crashes 3dsmax.
Made a video with the steps.

Video: https://youtu.be/Xbn1U88x65E