FSUIPC and Plane Position.

[cwhelchel]

I have a question that has probably been answered here before....

I'm using a seperate sim and want to move a plane in MSFS. Currently I do all the conversions and write latitude, longitude, alt, pitch, bank, etc. in a timer at 25ms.

This way is exceptionally jerky. I've seen a post in this forum about this problem but it seems like the solution was to use two computers talking with WideFS. I am currently trying to use threads, but they don't seem to work much better.

Does anyone know a way to get the jerkiness out of Flight Sim.

Thanks,

Cainan

[Pete Dowson]

I'm using a seperate sim and want to move a plane in MSFS. Currently I do all the conversions and write latitude, longitude, alt, pitch, bank, etc. in a timer at 25ms. This way is exceptionally jerky.

Is the sim restricted to running at the same frame rate? 25 mSecs, if consistently achieved (is it?) would be 40 fps. It maybe better to aim at a lower rate so that both can sync more reliably -- eg, 40 mSecs for a 25 fps limit.

It may also be better if run on a PC with dual cores or hyperthreading, where your program and FS are running in separate 'processors'.

Finally, there are several modes in which FS can be when doing this. Before FS2004 you actually had to put it into Slew. In FS2004 you can try Slew, Pause, Zero simrate, or normal flight modes. Experimentation may be needed.

Regards

Pete

[cwhelchel]

Thanks for the advice. I'll try it. But I have a feeling the problem stems from my end of things. The lat/long only gets updated at an 8 Hz rate and I write out the position much faster than that. Anyway I'm looking somewhere else for a lat/long with a higher update rate.

Thanks Again!

Cainan

[Pete Dowson]

Thanks for the advice. I'll try it. But I have a feeling the problem stems from my end of things. The lat/long only gets updated at an 8 Hz rate and I write out the position much faster than that. Anyway I'm looking somewhere else for a lat/long with a higher update rate.

Aha, yes, 8Hz would be jerky. Maybe you could try interpolating intermediate positions if you cannot get something better?

Pete