Custom Models - Collision?
Dalin Seivewright
0x0000221E Join Date: 2007-10-20 Member: 62685Members, Constellation
in Mapping
<div class="IPBDescription">i haz cowwizion?</div>I just realized that my compiled models have no collision. Is it an issue with the tool I use to export into the COLLADA format or does the Engine Test just not support custom model collisions yet? I was thinking that it simply required another entry in the "model_compiled" file, ie. 'collision "myModel.dae"', but after a couple attempts at being clever I gave up.
Comments
I been trying to figure out and asking around on how to impliment a physics mesh for months but had no luck or response.
I have just tried the following in my model_compile file:
geometry "refinery_arch_beam.dae"
physics "refinery_arch_beam_phys.dae" - Made a wire mesh only.
Compiled but still not solid, I tried a few different words: collide, collision.
;( Cries
I too have tried collision and collisionhull so far. I'm sure we'll figure it out... before they tell us though. Maybe.
With no Phys Engine at the moment the current test build does the calculations on the CPU but at some point that will shift over to those who have a Phys Enabled GPU or Phys Card.
I tried other things like having the mesh in the same model file as a seperate object of course with a different name like collision hull etc and so on.
I also have pressed every button I can find to do with physics in blender to try and set some values.
Without knowing where to start its difficult.
so I gussed right lol, gotta figure out why
geometry "refinery_arch_beam.dae"
physics "refinery_arch_beam_phys.dae" didnt work for me, I shall suss it out!
Thank youuuuu
Thanks for doing an epic confirm.
<!--quoteo(post=0:date=:name=SgtBarlow)--><div class='quotetop'>QUOTE (SgtBarlow)</div><div class='quotemain'><!--quotec-->geometry "refinery_arch_beam.dae"
physics "refinery_arch_beam_phys.dae"
didnt work for me, I shall suss it out!<!--QuoteEnd--></div><!--QuoteEEnd-->
Thats interesting. I just tried that myself and it worked perfectly. Does the file size of the model without the physics line differ from the model file with it? The Physics added about 300KB to my terrain model, which is 4096x4096x512. Try using the same model for both geometry and physics first.
I am having such trouble getting this to work. When you build you model, are you getting two green bars for the same model like in the video or just one?
Even though I specified the physics entry I am getting 1 progress bar not two and the file size of the .model is not getting bigger :(
I'm using program X to export into Obj or 3DS (the different apps I've used so far have either or but do not export to COLLADA directly. In this case I'm using Tree[d], an AMAZING Tree model generator, and I used a program called L3DT to create a terrain model.) Wings3D has a COLLADA exporter so I import the OBJ or 3DS file and simply export immediate to COLLADA.
Perhaps they're getting two different bars because the file is processing two different files? I've only done it with one single file for both Geometry and Physics, so I don't think they'd have to do any extra processing if they hold the model in memory.