Forum Mod Bakery Docs

Blender 2.8+ Weasel's Collision Editor

Please login to contribute to the conversation.
Aka "That collision blender add-on thingy Weasel made". Import/Edit/Export all types of collisions with blender


My very first add-on went under its third rewrite and had to be rebranded. Old version - SPG was very narrow and limited - only cuboids and only StaticPhys chunks. This version, however, supports all types of vanilla SHAR collision volumes and I plan to add rigged collision support (mainly for cars and miscellaneous animated level entities like trains and trapdoors)
SPG is not gonna be supported from now on.
(P.S My install of blender 2.79 crashes for no reason now and I can't even test my add-on there. So use the legacy version if you're still stuck on 2.79)

Download Collision Editor here (2.8+)

SPG - Legacy download


And it really works!
Is there a way to get it to work with 2.79?
I'll look into backwards compatibility sometime later today as I don't even have 2.79 installed. (Although I stongly suggest you use 2.8 if possible)
This is AWESOME. I can't wait for 2.79 compatability, as I mainly use that.
I only did the easy part of writing a P3D file, credit to yourself for the annoying maths required.
[deleted user]
4 yrs ago (Statistics)
Finally, the lives of modders are gonna be 20% more easier
Спасибо товарищ! :)
I like how users are now going ahead and creating custom collision (and mods that use it/tools that help create it) as opposed to what the situation was a while ago where mainly people just waited for the Model Builder.
  • Added 2.79 version
  • Added import functionality
I like how users are now going ahead and creating custom collision (and mods that use it/tools that help create it) as opposed to what the situation was a while ago where mainly people just waited for the Model Builder.
DeepFriedBurger
WOAS approached me with an idea based on the fact I had some experience with P3D files. It just kinda worked out that he could get the info out of Blender and I could write the file. In a perfect world I'd know Python enough to write the file from Python rather than writing JSON then using an external app to read the data out of JSON into a P3D file. If there's other things that could be automated in a similar way I'm happy to help out.
Completely rewrote the tool to use .p3dxml files instead of JSON workaround. Now it only requires the SPG_P3DXML_28/279.py script file to function. I highly recommend you use the 0.2.0 version as it's also been internally optimized