FS data rata, crazy !

[stag]

Hi all,

I'm getting a strange thing with PM's software, take a look :

UserTime=off

UserTime=on

Why such a low Data rate ?

I thought FS data rate was linked to flightsim FPS, how does it work ?

(In this example I'm using FS98).

Thanks,

Seb

[Pete Dowson]

I'm getting a strange thing with PM's software, take a look

Looks like the FS frame rate counter is out of range. That 32768 value just means an overflow I think.

Why such a low Data rate ?

I thought FS data rate was linked to flightsim FPS, how does it work ?

(In this example I'm using FS98).

FS98? Does my stuff still work on FS98? What version of FSUIPC are you using? The first FS version it was actually designed for was FS2000. I only made it run on FS98 in its first few months in order to compare the offset results to ensure ongoing compatibility.

The WideFS data rate is regulated by all sorts of loops, priorities and so on, to ensure smooth operation. You should be limiting the frame rate in FS to suit the instrumentation and you flights, to get things nice and smooth.

For PM support, and to find out exactly what PM's displays mean, you really need to talk to PM.

Regards

Pete

[stag]

Thanks!

Yes it works! FS98 rocks ! (joke)

I can't tell about FSUIPC because I've just removed FS98.

But it was around 2007.

I gave up, PM doesn't worth the trouble, TOO expensive for me !

Here is the answer from PM :

These settings are to protect your processor and any other applications. Not in a physical ‘harm’ way but to allow time for other processes on your system, and they are put there because every system is different:

Example, if you have them all off, and you have a target frame rate of 100, then you might create problems for your system, the GC program will start to use all your system resources to maintain (try) to gain your FPS. Typical side effects are no processor time left for critical system tasks like network traffic, then it can result in stutters across your GC displays.

The human eye is conformable at perceiving fluid motion 24 / 25fps (in the US it is 30fps) Cinema is always 24pfs. This is a progressive frame though, to get a interlaced frame rate feel perhaps 40 to 50fps will give you extremely smooth displays – 25fps is however very acceptable. 12fps you will notice a slight jitter. But even this is user perceptible.

Summary, a very fast modern computer will typically give between 30 to 90fps, without side effects. A lesser computer (2 to 4yrs old) if you left the frame rate open, you might start to see side effects / stutters or system problems.

This is entirely system dependent, the options are there for the customer – we have customers going back ten years – a lot has happened with processors and OS since then.

Have a good day.

[Pete Dowson]

I gave up, PM doesn't worth the trouble, TOO expensive for me !

So that output was from the Demo, all on one PC? In that case I am not surprised at the figures -- PM is meant to be run on a Network. And the demo is quite restricted, simply to show you the instrumentation. Those figures are by no means representative.

Pete

[stag]

I also tried it on a network (wifi) but the data rate was even worse ! (5FPS)

[Pete Dowson]

I also tried it on a network (wifi) but the data rate was even worse ! (5FPS)

Possibly the PCs you were using didn't have the right OpenGL drivers installed. This makes the PM modules resort to emulation, which hogs the processor and starves WideClient of time. On all of the Networks I've ever had for PM, starting over 10 years ago, the data rate has always been able to remain close to the throttled (limited) FS frame rate and provide smooth gauge operation.

Either way, all this is probably irrelevant for the demo suite and as you aren't going to spend the money there's no point in investigating further! ;-)

Pete

[stag]

Interesting, but I'm using latest ATI drivers.

Maybe my computers ain't fast enough ? (about 4-5 years old)

Thanks for helping me anyway !