=rk=
Resource contributor
- Messages
- 4,702
- Country
There is an odd new glitch with FSPackagetool.exe, one that promotes itself. I think it has to do with the new forbidden files and of course, my funky way of doing things. I do most of my model "tuning," before project build, in MCX. I can make keyframe animations in 3ds Max, but understanding materials, is like learning Cyrillic, I like to think I'm getting there. So a problem with anything with MCX, is that it strips many animations and also <Behaviors> from the XML. So a solution has, or had been to just keep a copy of the XML, called "whatever.XML - copy" in that same folder, I'd edit the XML after MCX export, FSPackagetool would ignore it and all was well.
Now, FSPackagetool red warning flags the competing XML and refuses the build. If I remove it from the folder, FSPackagetool refuses to build over the missing XML copy. Deleting the temp folders didn't work. If I just renamed the model, it would probably work, but there are many placements that would be lost. My solution was to change the GUID on the copy XML. I can still use it for copy/pasting, FSPackagetool accepts it for the build and since there are no bin and gltf files, the glitch ends there, apparently.
Also, the "new" Scenery Editor is much more robust, imo. Clicky and responsive and so robust, in fact, it refused to release the cursor after checking "one click placement." Every click to exit placement, including off screen, resulted in another placement, until I finally tried the drop down to uncheck the Scenery Editor. Asking for confirmation to close freed the cursor to dismiss the dialog and continue editing. So in case anyone else experiences odd behavior from the editors, maybe try that.
Now, FSPackagetool red warning flags the competing XML and refuses the build. If I remove it from the folder, FSPackagetool refuses to build over the missing XML copy. Deleting the temp folders didn't work. If I just renamed the model, it would probably work, but there are many placements that would be lost. My solution was to change the GUID on the copy XML. I can still use it for copy/pasting, FSPackagetool accepts it for the build and since there are no bin and gltf files, the glitch ends there, apparently.
Also, the "new" Scenery Editor is much more robust, imo. Clicky and responsive and so robust, in fact, it refused to release the cursor after checking "one click placement." Every click to exit placement, including off screen, resulted in another placement, until I finally tried the drop down to uncheck the Scenery Editor. Asking for confirmation to close freed the cursor to dismiss the dialog and continue editing. So in case anyone else experiences odd behavior from the editors, maybe try that.