Crash after invalid geometric normal warnings

[pietervanstee]

Hi,

I've updated to vray 3.6 recently.
The scene that I started in the previous build is now causing problems while rendering.

I've read this thread: https://forums.chaosgroup.com/forum/...-instance-name
And recreating the proxies could fix this, but as I've got many proxies I was wondering if there is another solution, or is there a script to automate this?

I've uploaded a part of the log where the errors/warnings start to show.
The objects with errors are itoo forest objects, populated with proxies containing trees etc...

Thank you in advance

[vlado]

Do you have any other errors or warnings (f.e. about "Normal bump" textures)? What kind of textures are you using for bump mapping?

Best regards,
Vlado

[pietervanstee]

Hi vlado,

No there are no other errors or warnings before these.
As I always fix these normal bumps right away.
Haven't checked them all manually but they should all be VrayNormalMaps.
The errors are just showing up after the update to 3.6

If I cancel the render in time, I can still continue in max, otherwise max crashes quite quickly.
I've had the same problem with another project earlier this week.

If I can share some files please let me know.
Thank you

[pietervanstee]

Hi,

Can someone have a look at this please?
After some testing the problem seems to be with the proxies created in 3.5
If I render the single proxy isolated, the same error still shows.
As mentioned in this thread: https://forums.chaosgroup.com/forum/...-instance-name
the problem is resolved by recreating the proxies, but as I've got lots of proxies this would take me very long to do.
Is there any other way to fox this problem, or alternativly easily recreate/regenerate the proxies so this warning is removed.

I can't get my render to finish as these warnings cause max to crash.

Thanks

[matanov]

Hi Pieter,

Please send us the original geometry that you're using for creating those proxies.

[pietervanstee]

Thank you Peter,

I've sent you an email.