Texture Loading Error

[7enith]

Hi,

I have a very dense scene (over 100Million Polys no Instances and 60GB of RAM Usage) which I cannot share yet. After starting Modo and Rendering with RT, or Progressive, or Adaptive I get an "unhandled exception" error for the Textures.
To solve the problem I had to go into the "images" palette and wait for every texture to be loaded. After that waiting as long as Modo was running Rendering was no Problem, even distributed Rendering works fine.

Now these waiting times get longer even after I moved the files from server to local. I often don?t know how long I need to wait, so if I hit the render button to early Modo freezes and I can restart the app and try again.
My setup is Modo 11.2 with Vray 3.5 production build. I have 64gb of Ram. I tried 10.2 as well. I never experienced this issue before.

all the best
Christian

[vladimir.nedev]

Have you enabled the Update Image When Painting option by any chance ?

Greetings,
Vladimir Nedev

[7enith]

Its deactivated

thanks
Christian

[vladimir.nedev]

What if you start rendering through V-Ray Standalone ?
Does it crash then ?

Greetings,
Vladimir Nedev

[7enith]

I will test that this evening. A workaround solution I use now is : Going into the images palette, reload all images, then I hide the whole scene and revealing it in 4 chunks one after another and start RT which each chunk introduced. Basically chunk1 -> start rt, then adding chunk2 -> start rt, chunk3 -> start rt and so on. It seems to work for now, even on the server. The scene eats around 60gb of my 64gb, that issue has been around when I was in the 45gb realm, although you only had to go into the images palette back then and it solved the issue.

[7enith]

Hello Vladimir, Vray Standalone seems to work just fine. Immediately after opening I?m able to render with it, which is not possible inside Modo without my strange workaround.
Best Christian

[7enith]

This issue really is annoying inside Modo! Don?t know how many times I had to restart the app, even with my workaround technique the error seems to happen if I don?t wait long enough!
Man I really hope this is fixed with the next production build! Unfortunately I cannot share the scene, so that it would be easier for you guys to get rid of this error

[vladimir.nedev]

I can't fix this unless I can reproduce it. So I need the scene.

Also, it seems that the issue is somehow being caused by Modo, since Standalone renders just fine.
Can you try disabling textures for the Modo OpenGL viewport ?

Greetings,
Vladimir Nedev