in-process RT

[super gnu]

ok, i get there are some benefits to in-process vray RT, but so far its causing me problems.

since most of my testing with RT gpu seems to be trying to render things and having it fail (im always trying really complex scenes in the hope they will work)

its often that id have to restart the render server.


now its in-process, i have to restart max every time my render fails. is there any way to avoid this? its really annoying.

on a related note, my current testing was to see if the new forest beta works better with the new beta RT than the old one.


lumpy landscape with a modest forest scattered on tip.


seems not so far, i get a "threadproc" error, and it then refuses to render again until i restart max.

[super gnu]

i tried moving back to the old render server using the DR method.


also didnt work, i got errors "applying changes to scene"


so i hid the forest object, and just kept the original source trees visible. ive used these before with RT.

i get loads of errors regarding transferring of the maps, then it crashes.



i then went back to the in-process RT, and get the same "threadproc" error as before. so it seems forestpack isnt the issue.

link to dump and log files:


http://we.tl/khypDTUgtx

[super gnu]

tracked that issue down to one specific tree... no idea what is different about that one in particular.

anyway, deleted it, it starts rendering.. whole scene is bright yellow green, and log shows "invalid lightcache samples" among various warnings. cancelled render, now max is locked up.

nice!

[vlado]

It would be best to get us a scene to support@chaosgroup.com then, so that we can fix it before the official release.

Best regards,
Vlado

[matanov]

There was a empty Output in that problematic tree's material. That was causing the crash, although this scene is using massive amount of RAM and I get another crash when trying to render with CUDA with an "out of mem" message (I have 32 GB). RT CPU renders fine, but on the edge of the machines memory capabilities (28/32 GB).

[savage309]

The crash with the problematic material will be fixed for the 3.30.01 stable, so thanks for the report.

[super gnu]

great to hear ive found a fixable bug.

any thoughts on the multicoloured rendering though? its happened a couple of times, once bright green, the next a psychedelic purple and red. seems to happen when using forestpack beta, so i cant say where the issue is. probably betatesting with 2 betas simultaneously isnt the best idea!