Can't open old file with Corona 3

[patrick.testa]

Hello,
I have installed Corona 3 and I can't open a file that was created with Max 2016 and Corona 2; I've tried both with Max 2016 and Max 2019 but both remain stuck with the pop-up asking about the new displacement mode. Other files, even with displacement applied, are opened correctly...
Any idea?
Thank you,

Patrick

(I've tried to import everything in a new scene but it doesn't work; same behaviour...)

[TomG]

Any chance you could send us the offending scene, since it is specific to that scene and others are working fine? Cheers!

[Ink Visual]

Not sure if that's Corona related but I've noticed it too. I have the last month project done on Corona 2 and since upgrading to Corona 3 I cannot open any files related to that project.
Some other project done 4 months ago (also on Corona 2) opened fine though. I will do some more tests later today (reverting back to Corona 2, opening some other project files) in order to confirm whether it has something to do with an upgrade or not.

[patrick.testa]

I've just uploaded the scene (1543928115_Montaldo-Ristorante-011.max)
It's only the max file, without textures and proxies; please let me know if you need those files too.
Thanks!

Patrick

[patrick.testa]

An update…
I've temporarily reinstalled Corona 2 and the file opens correctly. I'll make a quick render and go back to Corona 3!
Before this final solution I tried to merge everything in a new scene disabling displacement before the import, but it didn't work...

[Romas Noreika]

Maybe its your scene or proxys or something in it. Thats causing the file not to open.

I am opening corona 2 scenes on Corona 3 just fine.

Win 10 64 PRO
Max 2018
Corona 3

[Otuama]

Is anyone else having this issue?

We can't update in the office if this is actually a problem.

Thanks

[patrick.testa]

My biggest concern about going back to Corona 2 is the fact that I use almost exclusively Rebusfarm for rendering and they have updated to Corona 3
I'm afraid that renders could have issues or artifacts with the new displacement mode if I upload the scenes with Corona 2...

[maru]

Sorry for the delay here!

I checked Patrick's scene, and I can confirm there is a problem opening it with Corona 3. I'll forward it to the devs.
It also froze for me when I tried merging the scene and selected "all", but I managed to merge it successfully when just selecting groups of objects few times.

As to autobump (new displacement) - it can be disabled. See the note at the very bottom here https://coronarenderer.freshdesk.com/support/solutions/articles/12000050158

[Otuama]

Do you know approx when this might be fixed?

Is it a case of it just happening to a random people or everyone.

[romullus]

Can't speak for everyone, but i personally had never encountered this.

[patrick.testa]

At present it only happened to me on one of my older works, done with Max2016 and Corona2. I reinstalled Corona2 to work on that scene and than returned to version 3 without further problems on other files… (the scene with that issue still doesn't work)

[Ink Visual]

Same for me. I only have this problem on one of the projects I worked on. Whole project folder is affected, none of the multiple max files can be opened. It must have something to do with some sort of scene asset that was used along all of the affected files I believe.

[maru]

Same for me. I only have this problem on one of the projects I worked on. Whole project folder is affected, none of the multiple max files can be opened. It must have something to do with some sort of scene asset that was used along all of the affected files I believe.

Can you share any scene like this with us? Here is the uploader: https://corona-renderer.com/upload

(internal note id=300952759)

[Ink Visual]

Hi I uploaded the file. It's named 1547116941_afected-scene.zip.
If you need any additional assets like proxies etc please let me know.
Thanks,
Michal
__________________________________________
EDIT
Sorry guys. Please ignore the file I mentioned above. This is not the project I was referring to earlier, it's another one that I discovered not being able to open today, but after some tests I don't think it has anything to do with Corona version anymore, more likely with forest pack I guess....

I will send you another one in couple minutes which is definitely crashing because of Corona version (checked that couple of times, everything opens fine with Corona 2, and doesn't open after switching back to 3.0 though).

EDIT 2
We've been trying to locate the problem (merging files partially, eliminating scatters, proxies etc) and find out what causes files to crash. Unfortunately it most likely goes back to the Corona version issue. Could you guys please check the scene and dump files I sent and help us solve this? Thanks

[mh]

Hi guys

any progress on this? We are having the same issues, some of the files on some of the workstations can't be opened — it seems to be pretty random, some files are fine at first opening but then crash and it's gone. It doesn't happen on all workstations running the same version of corona though, not sure if that helps. Having said that a colleague of mine seems to be affected the most as she's been having issues on half of the projects we've worked on.

any help on this would be much appreciated. thanks!

[Ink Visual]

If I were to specify what is most likely an issue I'd say it has something to do with corona scatter. I can merge proxies/objects of the scatters from the affected files fine, I can merge scatters on their own without their influences (scattered objects) but when I try to merge both scatters with all their influences 3DS max crashes. Hope it helps, really looking forward to seeing it resolved soon as it causes at a lot of troubles atm.

[mh]

it's definitely not a scatter issue on our end as we don't use it, we are forest pack peeps

[Ink Visual]

Hi Maru,
Did you guys have a chance to look at the scene I sent? Can you replicate the problems I mentioned and see any potential cause of the issues?
I'd appreciate any response on it.
Thanks!

[maru]

We have managed to reproduce the issue in the 2 scenes that we received.
We do not yet know what is causing it.
It is marked as a "dealbreaker", meaning highest priority.

We'll be sure to update you here once any findings are made.
Currently the only workaround is to use Corona 2.

[Ink Visual]

Hi Maru, thanks a lot for the info.
Great to hear someone is working on it. Looking forward to seeing solution soon!
Cheers ;)

[mh]

thanks maru!

[patrick.testa]

An update…
I tried opening with Max 2020 the same scene that didn't work on Max 2019 and it opened correctly, than I saved it for 2019 and now it works there too… (I couldn't keep working on it in 2020 because of missing plugins, like multitexture...)
Sorry, it was a different scene… Still not working!

[Ink Visual]

Hi guys,
Are there any news on this issue? Our team has to go back to one of our old projects and we are having huge troubles opening the files. It's very important that we can use the stuff we produced at earlier stages, we cannot afford rebuilding things from scratch. It's quite urgent.
As mentioned in my previous posts, the issue is most likely associeted with proxies.
Any help will be much appreciated, thanks!

[maru]

Sorry, no news at this time, but hopefully it will be resolved before v4 release.

[maru]

Hi all,

According to our tests with the newest daily (22.05) and 3ds Max 2019, both reported scenes now open and render fine.
This is most probably thanks to the "scatter in wire box mode kills performance" fix.

I am moving this to resolved, but please do let us know if some issues remain.

[Ink Visual]

Hi Maru,
Great to hear that, thanks for your help on this!
We will download the latest daily later this week and test affected files.
I'll let you know if there's anything wrong.
Cheers!

[mike288]

Hi Maru,
Great to hear that, thanks for your help on this!
We will download the latest daily later this week and test affected files.
I'll let you know if there's anything wrong.
Cheers!

Thank you. Please, let us know.

[mh]

thanks maru!