Wow, indeed, it's a big issue...
I never used and I'm not sure if I'll ever see such instance.
Of course, some recommended Editor add-ons weren't done. Is this an End of World ? No, it's not. They did what they could and we can be happy for new features, compiling some RX mods using 469 was showing a lot of USELESS TRASH which those mods are having + naming variables as functions from Core, perhaps to mock mods in a stupid coding style trying to use similar named assets... UT469 was really helpful for getting rid of nasty bytes. If it has a NEW "ScriptWarning" but without showing "NOTAWarningScript" then... I won't use it in that case... Is this even a problem for me ? No, I'll hack that bugger some day, not today... no one has asked a native to work out of an array - that can be stopped at C++ Level, it's more polite to spit a log as long as you didn't gave me any replacement for that "Warning". But... I'm assuming that I was talking to the wind and then this is not a big issue.
Could any of you did figure in Editor.log if a brush has borked vertexes which model is about for being fixed ? No ? No problem then we are used already with trash maps, it's place for more... I bugged a brush on purpose and Editor did not show any "Warning" and this is definitely Garbage Brush.
I've been expecting a log:
Code: Select all
Warning: Brush4 has a non-coplanar surface !
I'm not disturbed then, I'll use only quality maps not just UNR files. I'm grateful for goodies solved/added at UT469 after all...