<t>All SimObjects are drivable, to the extent their simulations support user input. P3D looks for the existence of a panel.cfg file to know whether it is "controllable" or not. Additionally, the object category found in the aircraft.cfg/sim.cfg should be listed in the Prepar3d.cfg line for "User Obj...

It looks like you're simulating a piston engine, right? Digging a little more, try adding this additional one: "GENERAL ENG COMBUSTION SOUND PERCENT" (double). This value (0 - 100%) essentially should reflect the magnitude of the sound.



Mike

<t>I haven’t tried this myself, but in theory I think it should be possible. To give it a try, your implementation will need to provide the relevant data for the type of engine you want using the variables in the Simulation Variables document. For starters, you’ll need to add engine type and number ...

<t>WRT the objects in MP issue... In your Prepar3D.cfg, try adding the "Boat" to the list of user selectable object categories. For example:<br/> <br/> <br/> <br/> [Main]<br/> <br/> User Objects=Airplane, Helicopter, Boat<br/> <br/> <br/> <br/> Please report back if that fixes your carrier scenario ...

<t>If you just want to control it manually, set it up as a selectable object:<br/> <br/> <br/> <br/> - First give the object a panel\panel.cfg file. It can be empty. This indicates to Prepar3D that it's user controllable.<br/> <br/> - Add "boats" to the Prepar3D.cfg. e.g. User Objects=Airplane, Heli...

<t>Hi Thad,<br/> <br/> The general flow of the TP model is:<br/> <br/> throttle -> commanded engine speed (Ne) -> commanded fuel flow -> Ne - > shaft torque (used by the prop)<br/> <br/> You should see lookup tables in the SDK turboprop sample on how to tune these.<br/> <br/> <br/> <br/> It is corre...

<t>Any FSX-compatible aircraft should work in Prepar3D. The content layout is essentially the same as in FSX. Some content may require a the developer's installer, however, which may be specifically for FSX or Prepar3D. So you'll have to work with the developer if you run into those issues.<br/> <br...

I suppose it depends on how in-sync you want to be with the host simulation. If you don't sync everytime your version changes you may still get the bumpiness.

TOTAL WORLD VELOCITY is not simply set, as a vector (x,y,z) cannot be defined by a simple scalar. That's why we need to set the "..X/Y/Z" values.



Try setting the corresponding body relative values as well: VELOCITY BODY X/Y/Z.

<t>You are correct, the ground bumpiness is a function of world relative velocity and time. We don't bother generating bumps when you're up in the air.<br/> <br/> <br/> <br/> I assume that since you're freezing position you are updating lat/lon/alt from your own simulation via SimConnect. I think if...

Do you have "backup" software installing that could be doing this? Prepar3d wouldn't do this automatically.

Try using ACCELERATION BODY Y, which will give you the vertical acceleration relative to the aircraft. VELOCITY WORLD Y will give you the vertical velocity relative to the earth.