Pretty sure I have mentioned this issue before, but to explain, Mario 64 Movie Maker does a simple check to see if the ROM loaded in Project64 is using a vanilla player model.

If it returns as a modded ROM, access to Appearance Settings is disabled by showing an error message instead of the expected window.

However, this does not check if the Appearance Settings window is even open. In this case, you could just launch a vanilla ROM, open the Appearance Settings then switch to a modded ROM. As it doesn't double-check for any instances of the Appearance Settings form, you can use the settings along with all its features (and of course break the model).

I think a solution to this would just be disabling every feature of the Appearance Settings rather than just deny access to it completely. The user would still access it but won't be able to do anything. Then again, that depends on what you might think works out for this.

https://youtu.be/dQw4w9WgXcQ

After some time I've realized most of the things I have done have been incredibly bad when coming to coding, especially because when I started in this project, and 64Filmmaker, I was tremendously nooby to VB.NET, and, well, more like .NET and or programming in general.

So after some time, and having worked with Unity, so I have some experience, decided to take the challenge to rewrite M64MM2 in C#, from the already existent code.

This was a thing proposed by James back in 2016, I believe? but because I wasn't ready for C# he could not start rewriting M64MM2 in C#, which meant that 64FM would have not, either.

All changes will go in a new branch.

stupid

Replica of this one.