Issue with Loading Assembly-CSharp.dll (Dump MonoBehaviour)
I encountered an issue while trying to open or save a MonoBehaviour in the game "The Silver Case." It seems that the program is not attempting to read the Assembly-CSharp.dll file as it should. I conducted further investigation using Process Monitor and observed that the program never attempts to locate the Assembly-CSharp.dll file during these actions(only global-metadata.dat search). This problem persists even after attempting to use the latest Nightly build of the game.
I've never heard of this issue before. Does it dump without fields or with an error that it failed to deserialize? Since you know how to use process monitor, maybe try debugging the parts of the code that involve reading those dlls? This is where the code looks to open the folder: https://github.com/nesrak1/UABEA/blob/a1b55db413e0591ba2cff30466a9f905683c8c8b/UABEAvalonia/Workspace/AssetWorkspace.cs#L413 This is where the code that tries to figure out what fields an asset has (including a monobehaviour): https://github.com/nesrak1/UABEA/blob/a1b55db413e0591ba2cff30466a9f905683c8c8b/UABEAvalonia/Workspace/AssetWorkspace.cs#L240 Besides doing that, I don't know what the problem could be. I don't have the game so I can't debug myself. (I'm also assuming you meant nightly build of uabea, not the game)
dump without fields. Yes, I can see the code. If I figure something out, I'll post it.
(I'm also assuming you meant nightly build of uabea, not the game)
yes, nightly build of uabea
works in uabe, but with errors
If the problem seems to be in AssetsTools.NET (in GetTemplateBaseField for example), build the UABEA specific branch of AssetsTools.NET and copy the dll and pdb into the Libs folder so that you can debug into AssetsTools.NET functions without the debugger jumping over them.