MonoBehaviour template info failed to load. MonoBehaviour assets will not be fully deserialized.

[dgyst]

Describe the bug
When I try to read or export MonoBehaviour, i get only part of the file. Sometimes an error pops up in the window "MonoBehaviour template info failed to load. MonoBehaviour assets will not be fully deserialized."

Game detective pikachu returns.

resources.zip

[nesrak1]

Use the command line il2cppdumper or cpp2il programs to dump the dummy dlls, put them in managed, and disable cpp2il integration in UABEA by Options > Enable/Disable Cpp2Il in the main window.

[dgyst]

Thanks for the answer! This is the first time I've encountered a unity game. I got the dummy dll, but I don't quite understand where to put them. To the folder with the file you want to open?

[nesrak1]

In the game's Managed folder (which is in GameName_Data)

[dgyst]

Thx! It's works!

[dgyst]

After importing MonoBehaviour, I can't read the file.

[nesrak1]

Does your dump have a managed registry by any chance? There is a bug involving those that was reported recently.

[dgyst]

How it should look like managed registry? My dump is made from a game for Nintendo Switch.

[nesrak1]

There is a field in the dump called ManagedReferencesRegistry or something like that. If you don't see that, then something else is the issue.

[dgyst]

I didn't find it in my dump ManagedReferencesRegistry. What else can I try?

[nesrak1]

First, make sure you're on nightly. Then double check if reimporting the original works. If it does, you may have made a mistake during the edit and broke the format (I think this can also happen if you add an array item but don't increment the length as well.)

If you have issues reimporting the original, I think the best thing at this point would be to send a minimum example of a dump not importing correctly. You could send the raw and dump before and the raw after reimporting the original dump without changes.

[dgyst]

Thanks for the hint with importing the original dump! By trial and error, I found out that the problem was in the section "m_Enabled": 1,
"m_Script": {
"m_FileID": 1,
It was necessary to change "m_FileID": 0 to 1.
Thanks again for the help!

[lanboone]

Thanks for the hint with importing the original dump! By trial and error, I found out that the problem was in the section "m_Enabled": 1, "m_Script": { "m_FileID": 1, It was necessary to change "m_FileID": 0 to 1. Thanks again for the help!

I have exactly the same problem as you, but I don't quite understand what you mean by m_FileID. Where is it set?

[nesrak1]

@lanboone You should probably open a new issue for this. Deserialization issues occur when anything goes wrong reading an asset, so it could be many things causing it in your situation.

[albass]

I have the same problem. I tried the solution above (dump the dummy dlls, put them in managed, and disable cpp2il integration in UABEA by Options > Enable/Disable Cpp2Il in the main window) - it doesn't work...
What other options might there be?
The most interesting thing is that i can view the same bundles in AssetStudio