Printable View
Frames are ok and there's no error in the log file. I understand that you
don't purposely lagging it.
It works flawless as soon as I close the gc and start in a different mode
than F6.
Regards Anders Eriksson
http://www.gavle.to/~anders.eriksson/airplane.gif
http://www.gavle.to/~anders.eriksson/sva_logga.gif
Now this was quite time consuming... expanded F6 page I tried it on a slower
PC, with 737, 747, 777 selected, with and without usetimer and can't see any
"lag" going on when the program runs for a while. I am running pmSystems,
FMC and MCP, but on other computers.
What other programs are running on that PC? Is UseTimer=On on that PC? Is
pmSystems running? FS Framerate is limited?
"Anders Eriksson" wrote in message
news:388865.77938@wb.onvix.com...
> Frames are ok and there's no error in the log file. I understand that you
> don't purposely lagging it.
> It works flawless as soon as I close the gc and start in a different mode
> than F6.
>
>
> Regards Anders Eriksson
>
> http://www.gavle.to/~anders.eriksson/airplane.gif
> http://www.gavle.to/~anders.eriksson/sva_logga.gif
>
> Frames are ok and there's no error in the log file. I understand that you
> don't purposely lagging it.
What is astonishing to me ... how can all frames be OK and information in
response to throttle movement be 10 seconds late???
What are you monitoring? Speed? Bank? N1?
All I am doing is displaying what comes through from FS.
If the frames weren't ok then the response from , let's say the trottle when
it spools up, on the N1 meter would be quite jerky. That is not happening.
It all moves very smooth, just 10-15 sec late.
I'm not quite sure what u mean by "What are you monitoring". It doesn't
matter what I change. Baro, nd range, nd mode, or altitude preset it all
responds late. timings are off and FS fps locked to 20.
I'm running nothing but XP, GC and WideFs on this pc. Its an AMD sempron
2600+, 512 MB ram and an ATI 9600 Pro 128MB.
Strangely it hasn't occur on the last 3 flights now. Hope it was a temp
hickup. But I'm about to buy the first officer side so that's why Im abit
concerned.
Since I havn't been able to reproduce it,her's from an earlier post:
""Pressing F gives following result: FPS 54 DATA RATE 19
FS FPS 19,9 (Locked to 20)""
Regards Anders Eriksson
http://www.gavle.to/~anders.eriksson/airplane.gif
http://www.gavle.to/~anders.eriksson/sva_logga.gif
> I'm not quite sure what u mean by "What are you monitoring". It doesn't
> matter what I change. Baro, nd range, nd mode, or altitude preset it all
> responds late. timings are off and FS fps locked to 20.
So all values are delayed...
> Strangely it hasn't occur on the last 3 flights now. Hope it was a temp
> hickup. But I'm about to buy the first officer side so that's why Im abit
> concerned.
It sounds like there is some data buffering going on on your network... all
is smooth but delayed points into that direction.
Here is a list of tips to make sure your network runs as fast as possible...
this mostly applies to XP systems because they seem to be the most popular
ones:
a.. avoid any "Auto" settings in the network "LAN Settings" for the Link
Speed / Duplex, e.g. use "100 Full Duplex" rather than "Auto"
b.. Set the "receive Buffer" of your network card as high as possible
c.. Disable the "Allow Indexing Service to index this disk..." in your
"Local Disk Properties", as it really slows down network file transfer
d.. Limit your FS frame rate, avoid "unlimited" 30 FPS should be enough
for most, use 50 fps if you must and your hardware can handle it. High or
Unlimited settings will leave WideServer very little time to process network
traffic and will result in pauses in the connected programs.
e.. turn off automatic updates
f.. assign an IP address for every machine, do not use automatic settings
for that
g.. disable network authentication IEEE 802
h.. if you have control, turn off system restore disable automatic
syncronize internet time
Ciao
Enrico