VRCW-Recovery 1.5.0 is here. Your recovered worlds now come back closer to how they were made: more scripts you can actually edit, lighting you can bake again, and more of the original shaders.
This release also fixes a number of small mistakes that could slip into a recovered world without any warning. Recoveries are steadier too, and the app feels quicker.
Editable scripts for far more of your world
Before 1.5.0, a world's scripts came back as editable UdonSharp only when they came from a known public package. Most worlds are full of scripts their creators wrote themselves, and those stayed locked: they worked, but you couldn't open and change them.
1.5.0 turns those scripts back into UdonSharp code you can read and edit. You'll find them in Assets/Recovered/UdonSource/.
Each rebuilt script is checked against the original before it's used:
Verified: it behaves the same as the original, so your world now runs from the editable script.
Compiled: it works, but we couldn't prove it's identical. You get the code to look at, and the world keeps running the original, so nothing breaks.
Failed: it couldn't be rebuilt. The original stays in place and the report says why.
This check is deliberately strict, so a script is only swapped in when we're confident it's right.
VRCW-Recovery also finds more public packages than before, so more scripts come back exactly as their authors published them.
The Guide now explains clearly which of your scripts are editable and which still run from the original.
Lighting you can bake again
Recovered worlds have always kept their baked lighting. But if you edited the world and pressed Bake, most of it went dark, because the published world no longer contains what Unity needs to bake.
1.5.0 fills those gaps for you:
Objects are marked for baking again, based on how they were lit in the original world.
Bake settings are estimated from the original lightmaps, so a new bake comes out at a similar quality.
Stand-in lights are added where the original lights can be worked out. They start switched off, so you decide when to use them.
Nothing about the world's look changes until you bake. The Guide has step-by-step instructions for re-baking.
More original shaders
More of your materials now use the real shader the world was built with, not a stand-in:
More shaders are recognised, including the popular Lit shader family.
More places to get them from: several well-known free shaders are now downloaded straight from their public pages.
Know where to find the rest: when a shader can't be included, the recovery report tells you who makes it and where to get it.
Fewer mix-ups: two different shaders with the same name no longer overwrite each other.
Offline recoveries keep their shaders even when a download isn't available.
Small mistakes, fixed
These bugs didn't stop a recovery, but they could leave a world slightly different from the original. All are fixed in 1.5.0:
A see-through texture could be replaced by a solid one with the same colours.
Two similar-looking models could be merged, giving one of them the wrong materials.
Some models had a broken second set of texture coordinates, which could spoil their lighting.
Players joining late could see an outdated state for some synced objects, and timed triggers fired too early.
A texture could be deleted even though a material still used it.
A package's scripts could be removed when only some of them belonged to the world.
Some animations could fail to load or lose their targets.
Some package versions could clash because a version requirement was missed.
Steadier recoveries and a snappier app
Running a recovery again is safer. It reuses earlier work only when that work is still complete, and redoes anything that's missing.
No more endless waiting. A recovery could hang forever if a helper tool got stuck. It now moves on, and stuck downloads time out after a minute.
Better VRChat SDK choice. The newest stable SDK is preferred over a preview version.
No overwriting. A new recovery never lands in an existing project folder.
A quicker window. Settings save once you stop typing, and the log scrolls smoothly during long recoveries.