Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: designbarros on 2014-12-15, 22:58:35

Title: Corrupted Scene - Corona a7.1
Post by: designbarros on 2014-12-15, 22:58:35

Hello everyone,
i had some problems with the new corona version, my scene is corrupted and all those autobackups too.
Does anyone have this problem?!

I solved the problem partly merge the scene in a new document and import only the geometry without any light source or camera.

Title: Re: Corrupted Scene - Corona a7.1
Post by: Stan_But on 2014-12-15, 23:37:48

It's normal
With some new versions recommended to do reset of renders setup or even merge old scene to new. For example when Coronalights was changed to target Coronalights

Title: Re: Corrupted Scene - Corona a7.1
Post by: marioteodoru on 2014-12-16, 16:47:48

I keep having this problem too. Never had this error before. 

Title: Re: Corrupted Scene - Corona a7.1
Post by: Ondra on 2014-12-16, 20:10:55

marioteodoru: are you really using a7.1? Or daily build? Some older one had this problem, it is fixed now

Title: Re: Corrupted Scene - Corona a7.1
Post by: Utroll on 2014-12-17, 00:23:14

Quote from: marioteodoru on 2014-12-16, 16:47:48

I keep having this problem too. Never had this error before.

I had that once, but it was not corona related, just max corrupted the file, and autosave just trashed over 50/all files.
Hope for you it's not the case because they was nothing to do but cry (and add a incremental save button on main toolbar)

Title: Re: Corrupted Scene - Corona a7.1
Post by: marioteodoru on 2014-12-17, 13:26:43

@Keymaster  I'm using

Build timestamp: Dec  5 2014 23:12:31
Corona version: Daily build post-A7  in 3dsmax 2015

I also get a "WTF Error in listbox " error when i open rendersetup.

Title: Re: Corrupted Scene - Corona a7.1
Post by: maru on 2015-01-19, 14:32:36

Does it still happen with newer versions?

Title: Re: Corrupted Scene - Corona a7.1
Post by: Ondra on 2015-02-02, 13:43:20

Quote from: marioteodoru on 2014-12-16, 16:47:48

I keep having this problem too. Never had this error before.

I assume this was daily build? There was shortly a bug that caused these problems, it is fixed by now