What they mean by multiple DAE support: Multiple separate .DAE files that make up one vehicle, I.E. separate wheel models from the main car model, etc
Well then I should be able to the take the dually wheels off of the box truck and put them on the van effortlessly. Correct? Or the exhaust? Or am I still on the wrong path?
well, if when multiple .dae support comes, gabester splits the h45 in multiple .dae's, then kind of yes, kind of no, yes, because yeah(lol, yes because yes), you could, but no, because you'd still have to update the jbeam, if he just leaves it as is (which i imagine he would, because you'd probably still have to update the jbeam to load from the different files) then no, because then you'd have to update the jbeams to allow the box truck wheels to show up in the part selector for the cargo van
It may be the perspective, but I think you need to line up these panels so they are perfectly in line with each other.
Then choosing the body between the van and box truck switches everything over. So the 'body' pull down will say for example, "van, box, super duty" correct? But even back to what I said, if it is in the same .DAE, it is one vehicle. If they are separate, it is a separate vehicle in one clump of similar .DAE files. and I do notice that what gabester said what not what I thought he said. I was confused.
no, incorrect, if they are seperate, its still one vehicle, it just allows modding easier, because they can just model everything in seperate files, and having the jbeam code place the models apropiatly (unless of course jbeam can only choose where the node/beams go, in which case, no idea, gabester, if you could shed some light on this, that would be awesome )
Well honestly idk lol. I do wish that Gabe would give a explanation for dummies (me). Lol. I'll just have to wait and see what this means for myself. Lol. But thanks logoster, for your help!
For those who didn't understand what "multiple DAE support" means exactly I'll try to make it simple with the way I think it's gonna be: One folder = On vehicle One folder = Multiple DAE files One folder = Multiple JBeam files Let's say the vehicle is 'van' and we have this structure: vehicles\van\van.jbeam vehicles\van\van_wheels.jbeam vehicles\van\van_default.dae vehicles\van\van_custom.dae The van_default.dae would contain different 3D models that make up the original van. The van_custom.dae would contain different 3D models that make up this custom van. The van.jbeam would contain physics data for all the parts that can use the same nodes / beams for both configurations of the vehicle. The van.jbeam file could define 2 engines (lets say V6 and V8) which you could choose from the Ctrl+E menu. The van_wheels.jbeam would contain the parts related to the wheels. Let's say a model inside van_default.dae contains a mesh called defaultWheelF. The van_default_wheel_F part would point to that mesh and define nodes / beams etc for the default front wheel. Let's say a model inside van_custom.dae contains a mesh called customWheelF. The van_custom_wheel_F part would point to that mesh and define nodes / beams etc for the custom front wheel. Now consider models and jbeam as only 2 separate groups. Imagine that all the meshes from all the DAE files in the van folder are in a same bucket. And imagine all the parts from all the jbeam files from the van folder and in a separate bucket. That's how it works in the end. If you use the Ctrl+E menu and select a part it finds the appropriate jbeam code in the appropriate jbeam file. Then it reads the linked mesh and finds it in the appropriate DAE file. So you could separate things in any number of dae files just like you can with jbeam parts. If this works like I just explained the only drawback I see would be all meshes would have to be named differently. Which means 2 dae files from the same vehicle (folder) could not have a mesh named wheel_F but would have to define a separate name. So there maybe the engine will allow this using a "path" for a mesh like if you say default.wheel_F it would point to the wheel_F mesh in the default_van.dae file. Gabester please correct me if I'm wrong soemwhere here. But I think it's mostly gonna be like this.
This is exactly what he said to me about a month ago in a PM "I will finish it one day.. I'm just waiting for more stable releases for adding new content. And I need a new GPU to cope better with modern games." Not dead
Sorry to bump this thread, but I think this is a great idea for a mod, and I would hate to see it die
