Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Engine Assets Before Unity 5 #1327

Open
SNBeast opened this issue May 2, 2024 · 8 comments
Open

[Bug]: Engine Assets Before Unity 5 #1327

SNBeast opened this issue May 2, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@SNBeast
Copy link

SNBeast commented May 2, 2024

Are you on the latest version of AssetRipper?

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

Which release are you using?

Windows x64

Which game did this occur on?

Project Exonaut

Which Unity version did this occur on?

3.5.4f1

Is the game Mono or IL2Cpp?

Mono

Describe the issue.

Many of the shaders in material files, and a material in a prefab, fail to resolve, leaving 0000000deadbeef15deadf00d0000000 GUIDs. Investigating in other explorers reveals that those files are commonly not found, but the shaders linked to are definitely present somewhere and used in the original game because there are pink shader errors in the rebuilt game not present in the original. Unity 3.5.4f1 is installed and the only installed version.

(Spun off unrelated note into separate issues.)

Relevant log output

AssetRipper.log

@SNBeast SNBeast added the bug Something isn't working label May 2, 2024
Copy link

github-actions bot commented May 2, 2024

Thank you for submitting your first issue here. Please be sure you have uploaded your AssetRipper.log file. It is in the same folder as the exe file. :)

@ds5678
Copy link
Collaborator

ds5678 commented May 3, 2024

It sounds like you have multiple problems. I would prefer you separate them into individual issues.

@SNBeast
Copy link
Author

SNBeast commented May 3, 2024

The unrelated note is something I didn't want to bother with making a separate issue for, since it's easy enough to fix in the exported project.
I have gone ahead and spun them off into separate issues though.

@ds5678
Copy link
Collaborator

ds5678 commented May 3, 2024

Are the missing materials and shaders provided by Unity?

@SNBeast
Copy link
Author

SNBeast commented May 3, 2024

Are the missing materials and shaders provided by Unity?

It's pretty hard to tell, espsecially with me being so novice. Unless I'm interpreting wrong or haven't looked at enough, the properties passed from the materials I've looked at don't match any of the built-in shaders provided on Unity's download page for any of the versions in the file structure (ex: Assets/Material/armorUpEffect.mat using a deadbeef shader and passing the properties _MainTex, _InvFade, _Color, _TintColor). That being said, some built-in shaders do resolve correctly, like Assets/Material/Font Material.mat correctly linking to GUI/Text Shader. The one failed material link, which is in the Renderer in Assets/Resources/projectiles/plane.prefab, I have no idea how to investigate, since other tools I've tried so far go nowhere.

@ds5678
Copy link
Collaborator

ds5678 commented May 3, 2024

It's probably a safe assumption that these are engine assets. I'm currently only able to datamine Unity 5 and later for those.

@ds5678 ds5678 changed the title [Bug]: Failure to find shaders and a material in a 3.5.4f1 project [Bug]: Engine Assets Before Unity 5 May 3, 2024
@SNBeast
Copy link
Author

SNBeast commented May 3, 2024

Managed to find these assets: they're in unity_builtin_extra, which is built-in.

@ds5678
Copy link
Collaborator

ds5678 commented May 4, 2024

Managed to find these assets: they're in unity_builtin_extra, which is built-in.

My assumption was correct 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants