Simon853

You also did a lot of work in trying to sync all the simconnect transfers between frame syncs, to prevent graphic jittering, which you might recall, but not to worry. I'll do some tests and get the logs to you next week. Amazingly, this is my day job.. :) Si

No Pete. If you recall, you helped me out a while ago with my UAV simulator, interfacing to a control system that tells my interfacing application what the lat/long, alt, pitch and roll of the simulated aircraft is, as well as onboard camera pan orientation) and then I send that to FSX which generates the 3D display and virtual cockpit view (for the simulated camera view.) The lat/long, alt and virtual cockpit pan functions work fine still, but the pitch and roll have developed a "stepped" function since SP1 and FSUIPC 4.10, so setting pitch and bank with 0x578 and 0x57C no longer has the same immediate effect. I have to call them several times again for the aircraft to rotate to the desired attitude. Regards, Si

I've just installed FSUIPC 4.10 after installing FSX SP1. I notice that if I command the aircraft pitch and roll to a set value (degrees) then it only moves part of the way. Subsequent repeats of the process function move it incrementally in steps until the aircraft stops at the commanded settings. It used to go straight to the commanded settings. Can anyone confirm this behaviour for me? Is it something that can be fixed? Thanks, Si

Sorry, UAV is Unmanned Aerial Vehicle. (Think autonomous spy-planes..) Since the movement of the aircraft is being controlled by a separate simulator, FSX is put into slew mode, and the aircraft's position is updated via FSUIPC4. It doesn't really matter how frequenty I update the data. Running it anywhere between 2 and 20 Hz still gives an occasional flicker on the graphics. But if the actual update of the variables within FSX is down to MS's programming, rather than FSUIPC poking values in - which I had assumed, then I guess there's probably nothing I can do about it. Thanks, Si

I'm using FSUIPC4 to slave FSX to a UAV control system, where FSX is being used to generate the camera view. It works really well apart from that I get regular graphic jitters. I'm updating the aircraft position and virtual cockpit direction 20 times a second, and using the zoom function to zoom the "camera"'s field of view. When zoomed in to about FS's zoom level of 30 I regularly see the view jump for a frame before it snaps back. I've logged the values I'm setting and they're smooth. The problem is also noticeably worse if FSX is not the focused application, which indicates it's not a problem in the data. What I'm wondering is whether FSX could be reading from the values as they're being written, and sporadically reading out invalid values as this occurs? The bad frames are only a fraction of a degree out though, so its probably a least-significant byte that's getting temorarily corrupted. (i.e. I never go from a stable view of the ground to a single frame of sky, it only jumps a small amount, but enough to be an annoyance when zoomed in looking at a building or vehicle.) Any ideas? Thanks, Si