Acess Violation - no RTTI data!

[finalimage]

Hello i got this message in a scene, this scene i merge in a new max file than i use the Corona material converter, than i just add a Corona sky and press render, i got this MESSAGE:  Acess Violation - no RTTI data!
I am sending a image attached.

[Ondra]

Hi,
could you send me the scene that causes this? (http://corona-renderer.com/upload)

[finalimage]

Sure, you need also the textures? is quite big, how i do to upload, can be using wetransfer.com? or FTP.

[Ondra]

you can try it, and if the problem persists even when the scene is loaded without textures, then upload a version without textures.

You can use the link I posted earlier - if the scene is bigger than maximum limit, you can split the archive into multiple parts

[finalimage]

Hi Ondra, is there any missing file for the textures? maybe i miss some rar when i upload.

[Ondra]

so your upload is done? I will take a look ;)

[naikku]

Hey Ondra.
I did a small animation for one company with MentalRay and 3dsmax2012, back in ~2012.
They wanted to use the same clip again, this time I wanted to render it again with Corona v1 (I didn't have the original .jpeg sequence anymore).
Corona V1 and 3dsmax2015 gave this same RTTI violation error and max crashed.

The due-date is today Friday 8th of May - So during last night, my comps re rendered it with 3dsmax2012 and Corona a6.
Nothing special about it - it is done now, but would you like I send you the .max file?

[Ondra]

yes please, more data I have, the bigger the chance that I will solve this

[naikku]

sent just now (autobackup01.zip) with private uploader.

I tried with my desktop comp and my laptop, both give RTTI randomly. Computers might render a frame or two
but then crashes. Both comps have 3dsmax2015 + Corona v1.
Original file was made with max2012+MR. Opened in 2015 and used Corona Converter script, sorry don't remember version right now / did it from home.

[Ondra]

hm, in 2016, the scene is crashing for me even without rendering in Corona. It seems that rapidly selecting/deselecting the particle array object is the cause. This means even clicking in the frozen viewport while Corona is rendering

[Ondra]

so crashes in 2016 are unrelated to this this (autodesk problem, lets hope they fix it in SP1).

As for this scene, I recommend testing it with 1.1 - there were a lot of bugfixes that could help here. Please create a new bug report and post fresh scene/minidump if you encounter any further problem