| 01:09.55 | macsforme | what are "smart variations?" |
| 01:15.35 | Zehra | a bit of bad wording on my part, I basically mean that the format and the world generated from the said format is a bit overly simplistic and results in some inconsistencies and counter-intuitive behavior. |
| 01:16.30 | Zehra | so instead of bzw = (1.x objects + 2.x + mesh), we'd have it run instead in the following form.... |
| 01:17.45 | Zehra | 1.x objects -> converted to mesh + 2.x objects -> converted to mesh.. bzw = (mesh + bzdb vars and settings) |
| 01:19.14 | blast007 | changes to map objects aren't on my radar at the moment (pun not intended) |
| 01:20.21 | macsforme | mesh physics are by their nature less robust and more expensive than using more primitive shapes |
| 01:22.30 | macsforme | it would be hard to make them work with the way map makers tend to overlap objects to combine them into more complex shapes... meshes would probably need to be manifold at the very least to make that work well |
| 01:27.15 | macsforme | the way we do collisions is fairly distinctive... I tried a few years ago to replicate our physics behavior in an external physics engine, but it did not work well (even using box physics, not even mesh physics, although I think mesh physics were worse): https://youtu.be/7_qCwILE7fE |
| 01:33.06 | macsforme | so basically, mixing meshes and primitive shapes does not work well... but if we are going mesh-only, we are probably looking at building all maps with a modeling application going forward |
| 01:37.02 | blast007 | if we go mesh only, I would think we may also drop the BZW format |
| 01:42.19 | Zehra | I think I mostly understand what is being said, I'll have to look more closely into meshes to better grasp some of the finer details. |
| 01:44.43 | blast007 | zoom, enhance! |
| 01:46.09 | Zehra | lol |
| 01:48.53 | blast007 | glTF is the format I'd look at |
| 01:49.20 | blast007 | could be used to replace our map format and used for tank models |
| 01:49.52 | blast007 | and this extension could be used to provide author/license/etc information for maps: https://github.com/KhronosGroup/glTF/blob/master/extensions/2.0/Khronos/KHR_xmp/README.md |
| 01:53.14 | Zehra | I'd imagine it coming in as relatively useful for assets such as textures and custom map objects. |
| 01:54.30 | Zehra | "evergreen trees" objects licensed under CC0, textures public domain..etc |
| 01:57.45 | blast007 | possibly |
| 01:58.49 | macsforme | does it support anything similar to our current "inside" and "outside" points for physics? |
| 01:59.24 | blast007 | I'm not sure |
| 02:02.50 | blast007 | my thought was that we'd have a custom extension for things like teleporter links and other BZFlag specific data |
| 13:30.55 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 15:02.46 | *** join/#bzflag Sgeo (~Sgeo@ool-18b98aa4.dyn.optonline.net) |
| 20:02.46 | *** join/#bzflag Zehra (~Keiki_Han@unaffiliated/zehra) |