Vechicle model problem

[VeTaL]

First problem: this model loads without warnings, but i cant see textures.

 

Second problem: i load this car with

AddVehicleTire(_car,Vec3(-1,0,1.7),0.5,-0.4);
AddVehicleTire(_car,Vec3(1,0,1.7),0.5,-0.4);
AddVehicleTire(_car,Vec3(-1,0,-1.4),0.5,-0.4);
AddVehicleTire(_car,Vec3(1,0,-1.4),0.5,-0.4);

car is jumping like swiming on the sea

[macklebee]

not sure exactly if this is the problem, but you have some mat files that do not have a texture associated at all in them... you also have several mat files that are using the diffuse_bumpmap frag shader but just using the diffuse vert shader with them... and you have some mat files that using mesh.vert and mesh.frag... with no diffuse texture being assigned... And this might not be a problem at all, but I have had trouble in the past with other applications using special characters in file names... you have several mat files using the number sign, #, and parenthesis, (), in the names...

 

with this many surface materials, its hard to say what is screwing them up... you might have better luck just exporting a small section of the model that only has a couple of materials/textures associated with them and attempting the material files that way... I would strongly suggest you try using Icare's ADN material editor so you can see the proper way to create material files for your model.

[VeTaL]

Okay, maybe we would take another car... but what about "swiming"? Can you recomend something?

[macklebee]

look at the parameters for the AddVehicleTire()... you are possibly just using the defaults for the spring constant and damping... or perhaps a zero is being written to them... i would try to set it up like the the example vehicle in the editor, the viperscout, where the spring constant and damping is set at 20 and 150, respectively... then make changes from there to get something you like...

 

also... it looks like the suspension length is being set to a -0.4? I would have thought this needed to be a positive number... i dunno... B)

 

and one thing i see different is that the viperscout is using TFormPoint for the position of the tires...

[VeTaL]

Can anybody offer the simplest car physic demo?

[Marleys Ghost]

What about the viperscout scripts?

[VeTaL]

It is floating in the air... Looking like it have old phy-files, and i cant generate new one, because i haven't obj-file (gmf2obj dont work properly: it just generates 47 bytes of code)

[VeTaL]

I just need to setup those tires parameters: in my case OR car jumps like boat in the storm on the ressources (between wheel and body, so wheels are on the ground) , OR jumps in the same way, but wheels are sometimes got underground.

[VeTaL]

What a strange: when engine generates phy-files for static buildings (like tower: i just deleted phy-file of the tower, so engine generates new one) - its okay.

But when i delete vehicle_monstertruck.phy so engine would generate new one - car is just floating in the air.(http://leadwerks.com/werkspace/index.php?/topic/2653-vechicle-model-problem/page__p__24495__fromsearch__1#entry24495)

[macklebee]

The PHY file auto created by the engine is for static objects. You would have to use phygen or obj2phy. Now the viperscout is working just fine. If its not for you, then I suspect you have done something strange. What version are you using? When you download a new version, do you overwrite or do you do a fresh install? You didn't delete the PHy file for the viperscout did you?

[VeTaL]

Emm.. maybe i'm mising something, but looking like viperscout is in Private folder, so i cant use it?

 

I'm using 2.4, for now i'm making clean install to be sure i make everything right.

[VeTaL]

Zip data error... nothing good

[VeTaL]

Just downloaded vehicle_monstertruck, tested it - it is still floating in the air and dont want to fall down.

[VeTaL]

btw, as for me, vehicle_monstertruck dont load properly even in clear 2.4 version

[macklebee]

I wasn't suggesting that you try to use the viperscout in your own project, but rather you look at the viperscout's lua file to see how the vehicle commands were used.

[Canardia]

You must set the entitytype of the car's model body to something which doesn't collide with the vehicle body. The flying is caused by a overlapping collision of two physics bodies.

[VeTaL]

//You must set the entitytype of the car's model body to something which doesn't collide with the vehicle body

 

Car's model body to vechicle body? .. em.. maybe... wheels?