add a button to unassign vrm model

[lamystere]

Currently there is no way to remove a vrm model once one is loaded.

[Erimelowo]

Why do you want a way to unassign VRM models? There should not be any advantage to not having one loaded.

[lamystere]

Why do you want a way to unassign VRM models? There should not be any advantage to not having one loaded.

I was not able to switch to a different VRM model once one was loaded. It turned out slime was rejecting the vrm but this wasn't apparent since no error was shown in the gui or logs. Later I made updates to a VRM but slime doesn't seem to reload a file if the same path is submitted. Also when loading files with the same title (many are "untitled" or could be different revisions) it was not apparent whether the file had updated since the title flashes regardless if there's an error or not. Being able to clear the model would bring clarity to all of these minor annoyances. Editing the YML directly was the only way I could be sure a new VRM model was being loaded. One final very insignificant benefit is that the model json can take up a disproportionate amount of space in the settings YML, which might make sharing and troubleshooting it easier.

Side thought: If there's truly no reason to have a model unassigned, then why not have a default VRM model loaded from the start?

Another side thought: Sorry I thought I had linting set up correctly in vscode. I'll update that so the lint check passes soon.

[Erimelowo]

if your problem is that you somehow can’t assign a new model normally, that should be fixed directly. Not by having this workaround of removing a model before reassigning a new one.

and there’s no default VRM model assigned because VRM models don’t all have the same bone lengths :p

[lamystere]

if your problem is that you somehow can’t assign a new model normally, that should be fixed directly. Not by having this workaround of removing a model before reassigning a new one.

My point wasn't VRM issues, that was just an example story to highlight that it can be confusing, even for technical users, because the GUI is not informative. A button provides additional insight. The gui currently does not signal the success or failure of loading a new model. This can't always be inferred by the title changing. The CSS flash of the title provides a false sense of success since it happens regardless.

[Erimelowo]

So the issue is that there's no validation of the VRM model to decide if the title should flash or not?
Why not just do that, and show an error message if the validation fails?

[lamystere]

So the issue is that there's no validation of the VRM model to decide if the title should flash or not? Why not just do that, and show an error message if the validation fails?

That makes sense also. It just seems strange to me as a workflow to be able to add something but not remove it.