P-51D Dogfight - Stalls and Spins

[Der_Fred]

Redo the Pic

https://www.dropbox.com/s/os22jhe0nfn1655/Long127.jpg

[msalama]

Rgr that Sir.

[Der_Fred]

Try this track...

It'll be interesting to see if there's a problem with track between different types of PCs. Maybe a track is hardware dependent ?

 

:-)

FW190AI.trk

[msalama]

Nope. Shows you shooting thin air some 7.8 NM away from the FW. I wonder if they ever get this fixed?

[Der_Fred]

I thought maybe the track might be corrupted with the up/download, so downloaded both and tried them... with no problems.

 

It seems to point towards track PC hardware dependencies.. maybe they need to try another recording format ?

[Echo38]

Fred, what's your frame rate like in DCS? High, low? Is it steady or does it fluctuate greatly?

 

My own tracks consistently get corrupted (more than half the time), even when just playing them myself. Now that you mention hardware, I'm wondering if it might be due to the fact that the sim struggles on my system, with low, unsteady frame rates.

[Der_Fred]

How do you see your Frame Rate ?

Mine must be fairly high, as I don't see any stuttering, and when I accelerate time, the results are the same and there's no difference, except what the brain can keep up this.. :-)

 

Don't know how much difference the 'Box' would make ?

The Box:

Win7 Pro

Intel Core I7-2600 @ 3.4Ghz

Ram = 16GB

GCard = NVidia GeForce GTX 560 4GB Vram

Resolution = 1920x1080

[Echo38]

I don't remember the default key. Shift+Pause, maybe? Look in the General tab of the key commands.

[Blaze]

RCtrl+Pause

[Der_Fred]

Ah.. Ok

 

FPS: Mostly above 60 (vsync not selected), averaging around 100, max'ing at 140'ish (blue sky) and high 50's when lot's of ground details.

 

An occasional quick low spike when events happen (FW canopy ejecting = 20), or start of fires and smoke (= 45'ish), but climbs again.

 

I'm running with Med-High settings for graphics on 1920x1080 resolution.

[ZaltysZ]

Maybe a track is hardware dependent ?

 

The problem is that track doesn't record object states at discrete time intervals. It records initial state and deltas (like player input) only, and then game resimulates everything on track playback. Such playback relies on determinism of calculations. Once different enough result is calculated, track playback begins to deviate.

 

The scary thing is that there is not so much guarantee in determinism of floating point calculations once you begin comparing results even on CPUs of the same platform. There are instructions which gives different results depending on manufacturer of CPU or even model. Basically, program runs on different CPUs, but it can give tiny bit different result in same cases, and if you rely on getting exactly the same results independent of CPU, things begin to break.

[Der_Fred]

FYI:

Another point of interest, is with recording with Fraps (latest) - that latest movie.

 

The only way I can get a smooth recording flow, at full resolution is to run the playback at half-speed, with VSync locked.

 

Any other DCS setting and I get erratic jerky recordings even missing 1 second of detail ??

[NineLine]

FYI:

Another point of interest, is with recording with Fraps (latest) - that latest movie.

 

The only way I can get a smooth recording flow, at full resolution is to run the playback at half-speed, with VSync locked.

 

Any other DCS setting and I get erratic jerky recordings even missing 1 second of detail ??

 

Have you tried using the avi convertor built into the sim? You can view the track as you want it to be convert it, save a new track, then convert that one to an avi with the sim.

[Der_Fred]

That's an idea.. :-)

 

I'll look at that - thanks