VaM 1.x VaM crashing on specific scene load

[Geraldo]

Hey everyone,

I have a habit of constantly making changes to a scene and then saving it right after, overwriting the previous version. I've never had an issue until now.

I was working on an update for my Judy scene, which differs greatly from the current Hub version since I made tons of changes (like two weeks of accumulated changes). Now, VaM crashes immediately after the scene finishes loading; just a black screen and followed by a crash. Not only does it crash VaM, but my whole PC freezes for like ten seconds before coming back to normal, which is very unusual even for other VaM crashes I've experienced. I tried the usual PC reboot, repairing the core, I also tried loading the scene with lower performance settings (fewer pixel lights, lower physics update cap) in case it was a performance issue, but that didn't help. Now I can't even open the scene to find out what's happening in the first place.

My question is whether I can somehow edit the scene file externally to fix it; like editing the .json to disable every atom in the scene, or disabling atom collision, or anything else that could help really, maybe some weird collision is happening during scene start. I think the last things I was editing involved adding physics-based objects to the environment, so that could be the culprit.

Thanks in advance, any support is appreciated.

 

[hazmhox]

What's the file size? (the json file, uncompressed)

 

[Geraldo]

What's the file size? (the json file, uncompressed)

It's 1.92 MB.

 

[coinstacc]

My question is whether I can somehow edit the scene file externally to fix it; like editing the .json to disable every atom in the scene, or disabling atom collision, or anything else that could help really

Yeah you can, most basic text editors like Notepad (I use Notepad++ since it's better for scripting) should be able to open the json files and (hopefully) format them correctly. You'll have to dig through all the atom data in it but this will be the kind of line to look out for:

Switching the "true" to "false" will disable the atom it applies to. You can also get real spicy and just fully delete atoms from the scene if needed.

(I've done a couple of these kinds of json hacks to force-update plugin versions in scenes without having to reload them and lose existing data.)

 

[Geraldo]

Yeah you can, most basic text editors like Notepad (I use Notepad++ since it's better for scripting) should be able to open the json files and (hopefully) format them correctly. You'll have to dig through all the atom data in it but this will be the kind of line to look out for:
View attachment 629798

Switching the "true" to "false" will disable the atom it applies to. You can also get real spicy and just fully delete atoms from the scene if needed.

(I've done a couple of these kinds of json hacks to force-update plugin versions in scenes without having to reload them and lose existing data.)

Interesting, I'll give it a try! It's 50000+ lines of code so searching for "on" : "true" already narrows it down a bit.
Also, thanks for the heads-up with the plugin update thing, it'll be needed.

 

[coinstacc]

Interesting, I'll give it a try! It's 50000+ lines of code so searching for "on" : "true" already narrows it down a bit.
Also, thanks for the heads-up with the plugin update thing, it'll be needed.

The "id" line above it is also whatever you named the atom, or the default name if you hadn't renamed it. So if you gave things descriptive names, or at least know what kind of name to look for, that'll narrow it down even more. (Mine in the screenshot was just a UIButton I'd left unchanged, but if I'd named it something like "PlayButton" the id in the file would also be "PlayButton".)