2024.11 compatibility hacks

[Dobby233Liu]

Description

• GM 2024.11 introduced "Automatically remove unused assets when compiling". If this is enabled (but as I observed, SDF shaders and filter assets will receive the same treatment even if it isn't enabled), the spots for unused assets in the UTObject pointer lists are written with null, which makes UMT freak out.
• In addition, a currently always zero property was added to UTFont in GM 2024.11.

This horribly hacks around ModLib code not written with the null entires in mind to carry on if it ever hits them, and the ModTool is touched up to represent/hide the null entries. The unknown property in UTFont is now also accounted for. It should now be possible to load and save unless there are edge cases.

Depends on #1937.

Fixes #1996, fixes #2006, fixes #2011

Caveats

---

Notes

[github-actions]

Download the artifacts for this pull request here:

GUI:

• GUI-windows-latest-isBundled-false-isSingleFile-false
• GUI-windows-latest-isBundled-false-isSingleFile-true

CLI:

• CLI-ubuntu-latest-isBundled-false
• CLI-macOS-latest-isBundled-false
• CLI-windows-latest-isBundled-false

[Dobby233Liu]

Note that there's currently a bug, where if you leave null entries exposed on the asset tree for too long and move around too much, maybe click into one of the nulls (the true conditions are uncertain), it could cause a hang or even crash. I'm consistently getting the crash as descripted by the incomplete stacktrace below:

System.ArgumentNullException: Value cannot be null. (Parameter 'key')
   at System.ArgumentNullException.Throw(String paramName)
   at System.Collections.Hashtable.ContainsKey(Object key)
   at MS.Internal.WeakDictionary`2.TryGetValue(TKey key, TValue& value)
   at MS.Internal.Helper.SetItemValuesOnContainer(DependencyObject owner, DependencyObject container, Object item)
   at System.Windows.Controls.VirtualizingStackPanel.InsertContainer(Int32 childIndex, UIElement container, Boolean isRecycled)

Might be a WPF bug, if inquired I will try to grab a full crash dump.

[Dobby233Liu]

Note that there's currently a bug [...] (the true conditions are uncertain) [...]

Ok now I see, you have to very specifically click into the null entries first

What's even funnier is, if I run ModTool through VSCode, it hangs instead of crashing

[CoolModder]

Sorry to bother you, but it appears there are two issues:

1. Shaders are improperly imported creating null entries that cause shaders not to be visible in editor and create errors when saving code (Seen in the Mindwave Demo)
2. Structs and/or variable set to functions are improperly handled, and not being properly recompiled. This can been seen by trying to import modified minigames from Mindwave Demo into their data.win.

[Bloxxel64]

oh thank goodness

[MichaelEpicA]

Code does not work for me, Decompiling just gives me this. /* EXCEPTION!
Underanalyzer.Decompiler.DecompilerException: Decompiler error during AST building: Data left over on VM stack at end of fragment.

[colinator27]

Code does not work for me, Decompiling just gives me this. /* EXCEPTION! Underanalyzer.Decompiler.DecompilerException: Decompiler error during AST building: Data left over on VM stack at end of fragment.

@MichaelEpicA Unsure if this is fixed in upstream Underanalyzer (this PR may need to be updated), but does this happen on ALL code entries, or just some? If it's just some, if you could send a small code entry's disassembly, that would be helpful for debugging (but report it over here: https://github.com/UnderminersTeam/Underanalyzer/issues). Also, you may be able to turn that specific error into a warning in the UTMT settings.

[MichaelEpicA]

Can confirm this can be turned into a warning in the UTMT settings, and saving appears to work, however I'm doubtful it will load correctly due to UMT reporting a object miscount. It is every single code entry.

[colinator27]

Can confirm this can be turned into a warning in the UTMT settings, and saving appears to work, however I'm doubtful it will load correctly due to UMT reporting a object miscount. It is every single code entry.

@MichaelEpicA Hmm... if there's a small code entry sample, I guess I'm still curious to look at its disassembly to see if it has to do with actual decompilation, or if there's some other problem at play here.

[MichaelEpicA]

If so, should I just move this over to https://github.com/UnderminersTeam/Underanalyzer/issues then?

[colinator27]

If so, should I just move this over to https://github.com/UnderminersTeam/Underanalyzer/issues then?

Sure, I'll probably just close it if it ends up being irrelevant.

[CoolModder]

Note: the editor (on Mindwave's Demo) shows shaders now
However, when AddAssetsFromList(Data.Shaders, RefType.Shader); is called, it still crashes when compiling.
Also, when attempting to compile code like this:
define_boop("boop", { init: init, fleas: fleas })
It causes an error at 1499 of AssemblyWriter.CS.