Still got malware only in this thread,

http://sdavid.missioniron.com/images/3.gif
http://sdavid.missioniron.com/images/4.gif

last time it was 2.gif

Devicelink has access to only 1 set of instruments that is supposed to be for simulating the real instruments in flight which did lag by known measured amounts. There is also some things not linked right yet and work bad or not at all, Those are not part of the simulation.

Get UDPSpeed, run SP and display a few guages then every so often pause the game with the view on the instruments being graphed. If you've got multi-core then maybe a space core will take it up, I've run it with 46 on single core 2.5Gz AMD's and not gotten low FPS. You could have had guages in the screen corners all this time except maybe some online.

Yep, in Yaks where you have to apply a lot of rudder and aileron trim to make the plane fly straight (according to the compass), the ball is considerably offset to the right. In the Italian MC.20X series the ball is slightly off-centered to the right even with neutral trim and flying straight and level. I wonder whether it's realistic.

So quiet these few days in the forum. So time to beat an old dead horse lol. Is there any way that DT can correct these instrumental inaccuracies in the next patch. I understand all the talks about realism or relative advantage etc. Why can't we just correct ALL the inaccuracies on ALL planes, so that everybody is on an equal footing.

Also in terms of light stick force on P-51, would changes ingame stick reponse curves help with this issue? Or is it more inherent modeling issue and CoG related that it can't be addressed by simply altering response curves?

We? I had no idea that you're on Daidalos. Good job!

Was already addressed in this thread. It's not a problem.

It would be a lot of work, I guess, and it wouldn't address the problem that some instruments are hardly legible anyway. I would vote for a quicker solution, an optional extension of the speed bar with flight data available to the pilot of that particular plane type in that particular cockpit. Could be something like an in-game UDPSpeed. Just a wishful idea, don't shoot me... :rolleyes:

That'll work, too. As long as it's accurate.

What I suggest is a new (easier) difficulty setting with direct access to the flight data the game engine uses for computations. So far it would/could be accurate, and 'everybody [in every plane] could be on an equal footing' in this respect.

Where in the wonder woman view can I see the vector ball? I just see TAS, Alt etc.

Aren't there two wonder woman views? One without the vector ball? Try switching trough all modes.

I've attached a couple of grabs I took back in August during the acceleration testing from a Mustang III; the first is the 'pit' view, and the second is the first Wonder Woman view you get by cycling CTL+F1. Note the little circle offset a bit low and to the right relative to the gunsight's center pipper; that is the Vector Ball.

cheers

horseback