I'm doing some basic testing with muti-dae... and the object is't following the car correctly. It also isn't taking damage according to the jbeam that it is grouped with.. /= - - - Updated - - - any and all help would be appreciated.
Re: Multi-Dae issue. Please Help. I have absolutely no qualificaiton on this, but it could be that the mesh isnt assigned to the jbeam. Ive seen a lot of this stuff in the past where the mesh is fixed in one direction while the jbeam acts normally (i.e. the specific mesh will just rotate around the jbeam as it is driving in circles) I base this on what Gabester said in this thread http://www.beamng.com/threads/11411...-Issue?p=174446&highlight=rotation#post174446
Re: Multi-Dae issue. Please Help. Reset transformations in the new .dae and make sure origin is 0 0 0
Re: Multi-Dae issue. Please Help. Also, check the console command for errors, I suffered many times from "Flexbody: VY node not found" errors which produced the same problems. Where the mesh doesn't get assigned to the jBeam.
Re: Multi-Dae issue. Please Help. I already tried that... it still does what ever this is... just slightly different and what you're seeing is the aftereffect.. before it was even worse.. - - - Updated - - - I havn't dealt with this issue and won before... VY Node Failure How do I troubleshoot this issue.
Re: Multi-Dae issue. Please Help. The VY node error means it can't find enough nodes to bind to for direction, etc. It needs to be bound to more nodes.
Re: Multi-Dae issue. Please Help. I've found the VY node failure to happen more frequently than it should. I would think 3 nodes should be enough to constrain a mesh, though it might deform badly, but I'm pretty sure I've had VY node failure happen with many more. I had trouble with my rear axle on the Corolla and ended up changing the node groupings around and messing with that until it worked.
Re: Multi-Dae issue. Please Help. You're a life saver... I just realized that the mesh is connected to just 5 nodes that are in a horizontal line. After I fixed the error it wans't working fully correctly so I had to do the 0,0,0 origin on the mesh another time.. now after fiddiling with Pos, Rot, and Scale it's perfect, aside from my horrible alpha quality modeling. But thanks alot for everyone who helped me out here. works very well now.