HammerPlusPlus-Issue-Tracker icon indicating copy to clipboard operation
HammerPlusPlus-Issue-Tracker copied to clipboard

[Feature Request] [BUILD 8860] Preventing Hammer++ from crashing by not rendering corrupted models in the Model Browser

Open mathieu12 opened this issue 2 years ago • 1 comments

Hammer++ crashes when it tries to load a corrupted model in the Model Browser. The error message it gives is the following : Model "blahblah" is corrupt and Hammer++ cannot proceed. This model is incompatible with this version of Hammer++. You must remove this model or convert it to a native format by recompiling.

While I understand the workaround you are suggesting us, I have a lot of these "corrupted" models and I don't wanna lose time figuring out which one is broken or not. I think it would be cool to find a way to force these corrupted models to not render, so that it prevents Hammer++ from crashing and we would continue browsing without any problem. Also why not automatically adding a label "Corrupted" on these corrupted models?

Thanks in advance :3

mathieu12 avatar May 02 '22 19:05 mathieu12

This is very problematic for anyone who mounts content from older games like HL2 or TF2 onto newer games like Portal 2 or CS:GO. The older human models will crash newer branches of Source unless you recompile them, which isn't a problem in normal Hammer because you can just avoid selecting the models you know will crash, but in Hammer++ it will crash immediately trying to render the previews. Either there should be something in place to prevent the previews from crashing, or an option to revert to the old model browser layout - maybe there is the latter and I just missed it?

vrad-exe avatar Sep 23 '22 01:09 vrad-exe