SP3: vrayfastSSS2 inside of vrayBlend crash

[gimiky]

nesting a vrayfastSSS2 inside of a vrayBlend material and then rendering seems to cause this error:

"UNHANDLED EXCEPTION: Scanning scene Last marker is at .\src\vrenderlight.cpp, line 152: Exiting VRenderLightObj::init()"

everything will work if the file is saved and reloaded first, but rendering initially after will cause the crash. can anyone else confirm?

edit: seems to be triggered whenever the blend material has been accessed.. ie as i said reloading the file and rendering without any editting of the material will work, but adjusting the material at all will trigger the exception on the next render.

greg

[vlado]

Works fine for me on a simple test; if you can send me your scene to vlado@chaosgroup.com I'll be able to check what's going on.

Best regards,
Vlado

[chipnuts]

Same error different reason

I'm getting that exact error "Last marker is at .\src\vrenderlight.cpp, line 152: Exitting VRenderLightObj::init()" materials nested in RPM Materials. I've sent an email to the RP Manager developer, but figured I'd post it on here as well as there could be a connection with vray and nested materials. There's a couple weird things however. The first is, it only crashed with the RPM Material was applied to Dreamscape objects. If I put a standard mat it renders fine. If I put a vray Mat it renders fine. But if I put a RPM Material with stanard mats nested, vray crashes. I'm not pointing fingers at any plugin in particular, it just seems to be a bug. It could be with the way RPM Mat gets parsed or could be with how vray handles nested materials (which is why I'm posting here instead of starting a new thread). I just wanted to bring it to everyone's attention so a solution could be worked out for the good of the community.
The second thing is, this scene was rendered all last week many many times with no issues. But I'm going to try downgrading to the previous version of RP Man and see if that ‘fixes’ it.

RP Man version 4.212
Vray SP3a
Dreamscape 2.5e
Max 2009 SP1 Creativity Extension 64 bit

-Chip

[chipnuts]

Fyi

Downgrading to RP Manager 4.171 also generates the error.

[chipnuts]

another update

Well, it seems to be RPM Material specific. I opened a fresh scene, created a sea object, put an RPM Material on it hit render (with scanline) and it generates the error below:
"Error allocating mesh. Insufficient memory available for:

Sea Suface01

Reduce the face count to render this scene."

I'm on an 8 core xeon 3ghz, with 16 GB Ram, so that's got to be a serious problem. Just figured I'd pass it on.

[jacksc02]

You might want to let grant from RPManager know about this.

[SnipeyX]

Grant has been working with Chip on the issue, but interestingly, same thing happens if you render with a composite material on a dreamscape surface, so it's probably more of a dreamscape issue than vray or RPM.