Describe the new feature or enhancement

AudioMixerController, AudioMixerGroupController, AudioMixerEffectController, AudioMixerSnapshotController.
These assets have complex pre-processing when unity builds them. As a result, the editor and release data won't be mapped to each other, so reversing the data is not a trivial task. The current exported AudioMixerGroups lose all audio effect stacks, exposed parameters, snapshot values, transition overrides...

Describe the new feature or enhancement

Scene assets should be exported into the scene file. Currently, only GameObjects and Components are considered "IsSceneCompatible". However, a scene file can contain, say, meshes. Such a mesh should not be exported as an asset on its own. Instead, it should be exported into the scene YAML file.

But what would happen if such a mesh is exported as a separate asset, which is how AssetRipper does?
I'll take tk2d-tilemap running in UnityEditor as an example. As tk2d-tilemap creates meshes and saves them directly in the scene, the PlayMode logic can safely "Object.DestroyImmediate()" them to free memory when finished using them. And the exported mesh assets will thus be literally "destroyed", and the scene gets invalid references to its meshes afterward, which results in a broken scene.

To be more precise, a call to Object.DestroyImmediate() on a mesh asset during PlayMode will not take effect. Instead, an error message is printed into the console. However, tk2d-tilemap does something more to solve this. It actually destroys the mesh by using AssetDatabase APIs if it finds out that the mesh is a separated asset.

Describe the new feature or enhancement

A shader exported as a YAML asset can be assigned to and used by a material as a regular .shader asset, but it does not work with Shader.Find() unless we explicitly register it.

Shader.Find() is essential for exporting a playable Unity project, especially regarding rendering image effects.

Describe the new feature or enhancement

Having deterministic GUIDs, exportIDs, and timestamps across multiple exports of the same game is essential so that any manually-added reference in the exported project won't be lost after a re-export. Also, massive art assets won't have to be re-imported if we keep the Library folder or use a cache server.

Describe the new feature or enhancement

Texture import settings - Max size should be at least equal to the exported texture size,
since textures in the release build can't be larger than the original project's max size setting.

Describe the new feature or enhancement

Sprites from different textures can have different texture importer settings like PixelsToUnits.

When these sprites are packed into a SpriteAtlas in the game build, the exported game project will have all these sprites under one large Texture2D. As PixelsToUnits is a property of texture importer, all sprites will have the same property values, which is incorrect compared to the original game project.

To preserve the render data of sprites, we should export sprites as YAML assets, one .asset file for each sprite, so that each can have its own properties. I've tested this idea in Unity Editor by creating multiple sprites from textures in code, assigning different properties to them, saving them as .asset files, building the game, and finally running the game... All things are as expected.

Textures and SpriteAtlas

Texture import settings - Max size should be no smaller than the exported texture size since textures in the release build can't be larger than the original project's max size setting.

SpriteAtlas - Should not be exported! The corresponding texture of a SpriteAtlas is not an asset in the original project but an artifact of a release build. Now that the texture has been exported, the SpriteAtlas is not necessary for the exported project. Beyond that, exporting the SpriteAtlas will instead crash Unity if SpritePackerMode is enabled in the editor settings, which happens during the packing process when entering PlayMode.

data viewing support .PDB like in dotPeek

Describe the new feature or enhancement

Currently, all exported scenes are located in the "Assets/Scene/" folder. It does not match the scene file locations serialized in EditorBuildSettings.asset. SceneManager.LoadScene series functions will fail to load such scenes.
Thus, scene files should be exported to their original locations.

Are you on the latest version of AssetRipper?

Yes, I'm on the latest release of AssetRipper.

Which release are you using?

GUI Version Windows x64

Which game did this occur on?

N/A

Which Unity version did this occur on?

N/A

Is the game Mono or IL2Cpp?

Not Applicable

Describe the issue.

A sprite that is packed into a SpriteAtlas may have an incorrect pivot when exported as a YAML asset.
This leads to incorrect bounds for frustum culling, thus missing sprites in the rendered image.
The pivot value should be recalculated with information from the atlas.

Relevant log output

No response