by wlbragg » Wed Jul 06, 2016 5:42 pm
I'm getting a bit confused. I worked on adding the new FDM first to the bombable version then the regular version, I had the same issues with both. A minor issue I haven't sorted out was the prop animation, old version uses engines/engine[0]/n2 and the new FDM only provides engines/engine[0]/n1. After making the change to the prop spin and blur animations it still didn't work and I ended up with a PropBlur object not found. I still need to track that down.
The other issue I am not entirely sure how to debug is 100% n1 prop thrust is barely moving the UAV. I really don't know where to look for that issue as it appears to be in the FDM itself?
Erik, if you get a chance, maybe you could double check this?
My confusion is why the two versions, bombable vs not bombable? Why not make it all inclusive and give a choice to arm or not?
And @ pjedvaj, your comments about adding the two bombable systems two the new FDM don't really apply if I am adding the new FDM to the current bombable version, right?
One other issue is I can't import the ac file into Blender. Is there a .blend available or a pointer to the correct ac import script?
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q