WideFS 6101 and latest

[ewg550]

Hi Pete

since i am using the latest WideFS 6.220 i have problems with my PM.

he did every 20 seconds a 1 second brake.

using IPX (someone told me it is faster) with network timing 0,0 (works best) and other values.

But that never happens with 6101. Can i download it anywhere?

regards

Marcus

[Pete Dowson]

since i am using the latest WideFS 6.220 i have problems with my PM. he did every 20 seconds a 1 second brake.

using IPX (someone told me it is faster) with network timing 0,0 (works best) and other values.

Such a regular pause sounds like the work of either an anti-virus program, or a memory optimiser, or, possibly, the TCP/IP protocol being installed on the Network (even if not used by WideFS) and IP addresses not being fixed on each PC.

Since as long ago as version 5.50 WideFs has been tuned to work smoothest (not necessarily fastest) with TCP/IP. This is because IPX/SPX is problematic with Windows XP, which most folk are moving to (quite sensible in my opinion). Smoother operation is preferable to fast but jerky.

Anyway, try leaving the parameters to default, I think they'll work better that way even with IPX/SPX.

But that never happens with 6101.

I assure you there is absolutely no difference in the handling of the Network between versions 6.101 and 6.22. Going back to 6.101 will not help at all, and I certainly cannot supply it or support it.

The only changes between the two were the addition of joystick scanning and a speed up on initial loading. The change in version numbers was more to do with Beta test trials and matching changes in FSUIPC.

If you like, you can try cutting out the joystick scanning -- maybe you have some strange USB or other joystick driver on the client which causes delays when queried by WideClient. To switch it off merely set "ButtonScanInterval=0" in the [Config] section of WideClient's INI file.

Regards,

Pete

[ewg550]

Hi Pete

thx for your answer

Which settings i need for TCPIP

TCPIP=YES

;PORT

;networktiming

?

[Pete Dowson]

Which settings i need for TCPIP

TCPIP=YES

Just "UseTCPIP=Yes" (it will default to this in any case if you delete the one saying "No"), and, in the WideClient.ini files, "ServerName=". Let everything else default.

Pete

[ewg550]

Which settings i need for TCPIP

TCPIP=YES

Just "UseTCPIP=Yes" (it will default to this in any case if you delete the one saying "No"), and, in the WideClient.ini files, "ServerName=". Let everything else default.

Pete

just tested it with TCPIP and its unfly able only stutters without end ;-((

[Pete Dowson]

just tested it with TCPIP and its unfly able only stutters without end ;-

It does sound like you do have something wrong with the network then. Have you removed/uninstalled IPX/SPX throughout? I don't think it's good to have more than one protocol enabled. Also, for TCP/IP you should ensure that you define fixed IP addresses for each of your PCs -- don't let Windows assign them automatically.

There's a lot of expertise on this stuff in the PM newsgroup. You may want to talk to the folks there about it, see what suggestions they come up with. Whenever I get network problems it's a matter of trial and error changing this, that, or the other, till it works nice. Then don't touch it ever again. :wink:

Leave the performance-related WideFS parameters to default though. You can get into a real mess changing those. It took several beta testers and I several months of fiddling about with them until we arrived at good defaults, back when I first changed over to TCP/IP.

BTW, did you first try cutting out the joystick scanning as I suggested? That would have been the only difference from 6.101 to 6.22.

Regards,

Pete

[ewg550]

just tested it with TCPIP and its unfly able only stutters without end ;-

You do have something wrong with the network somewhere then.

There's a lot of expertise on this stuff in the PM newsgroup. You may want to talk to the folks there about it, see what suggestions they come up with. whenever I get netwrok problems it's a matter of trial and error changing this tat or the other till it works nice. Then don't touch it ever again. :wink:

Leave the WideFS parameters to default though. You can get into a realy mess changing those. It took several beta testers and I several months of fidlling about with them until we arrived at good defaults, back when I first changed over to TCP/IP.

Regards,

Pete

pete

indeed you are right PM NG is ok, but all things i testet.

Now iam back to IPX and it works better but i get now every 10 seconds stutters for 2 seconds...

timeout=5

networktiming=0,0 (anyhting higher as 0 makes stutters again alive.

i really dont know what i can test further.

i did all network teawks at PM Page i read nearly all PM NG topics..

really strange

btw: nothing without FS and PM runs on the 2 computers, nothing more (check Task Manager and checked with program "ENDITALL")

:-((

[Pete Dowson]

Now iam back to IPX and it works better but i get now every 10 seconds stutters for 2 seconds...

That sounds EXACTLY like the stutters caused by Windows (expecially Windows 98/95/Me) when you have TCP/IP installed on the network, but have not assigned fixed IP addresses for each PC. (What Windows version(s) are you using?).

Other possibilities for regular stutters like that are memory managers/tweakers and anti-virus activities. I am pretty sure that you have some process, nothing to do with FS or WideFs, causing this. It may not be one closed automatically or easily with EndItAll.

Check also with Katy Pluta on the FS2004 forum, or in the PM Newsgroup.

BTW you responded to (quotes) and earlier draft reply from me, which I sent unintentionally -- I edited it afterwards. You might want to reread it, just in case.

Regards,

Pete

[ewg550]

That sounds EXACTLY like the stutters caused by Windows (expecially Windows 98/95/Me) when you have TCP/IP installed on the network, but have not assigned fixed IP addresses for each PC. (What Windows version(s) are you using?).

Other possibilities for regular stutters like that are memory managers/tweakers and anti-virus activities. I am pretty sure that you have some process, nothing to do with FS or WideFs, causing this. It may not be one closed automatically or easily with EndItAll.

Check also with Katy Pluta on the FS2004 forum, or in the PM Newsgroup.

BTW you responded to (quotes) and earlier draft reply from me, which I sent unintentionally -- I edited it afterwards. You might want to reread it, just in case.

Regards,

Pete

ok pete

i am using WIN XP prof.

Every Client PC have a manually assigend IP adress

cant disable TCPIP cause i using it for the network conections with the other computers (switch)

192.168.0.1 and 192.168.0.2

but one thing i need to know.

in which window i need to copy the IP?

Pic1 (now) or Pic2, too?

http://www.files.ivao-de.net/1.JPG

http://www.files.ivao-de.net/2.JPG

and i am pretty sure that no tweaker or Virus program is running, cause i did a format C: and only installed windows XP FS and PM Software.

i really dont know which proccess interacting and disturb.

And i am also no network spezialst, sorry :-(

[Pete Dowson]

i am using WIN XP prof.

And you got IPX/SPX working? Phew! It was mainly because I could never get any satisfactory results with IPX/SPX with WinXP that I spent so much time getting TCP/IP operation up to scratch. Now it is much smoother.

Every Client PC have a manually assigend IP adress

In that case it must be something else causing the stutters. Check the list of processes running, ask Katy or others in the PM group.

cant disable TCPIP cause i using it for the network conections with the other computers (switch)

Of course, do not disable TCP/IP on an XP network (though Win98 worked fine with only IPX/SPX installed). Best if you ONLY have TCP/IP, though, if possible.

in which window i need to copy the IP?

Pic1 (now) or Pic2, too?

I don't know Pic2. I only ever set the address in the place you have, in Pic1.

And i am also no network spezialst, sorry :-(

Nor I! :? I am out of ideas. Sorry.

BTW, did you try, as I suggested twice now, disabling the joystick scanning in WideClient? You've not answered that one yet.

Also, do you have "UseTimer=On" in the PFD.INI of PM? If so, change it to "Off". I don't think that is good unless you need to run more than one copy on the same PC.

Regards,

Pete

[ewg550]

BTW, did you try, as I suggested twice now, disabling the joystick scanning in WideClient? You've not answered that one yet.

Also, do you have "UseTimer=On" in the PFD.INI of PM? If so, change it to "Off". I don't think that is good unless you need to run more than one copy on the same PC.

Regards,

Pete

i dont have any line in wideclint.ini called joystick scanning or anything else so i guess that shouldnt be the problem.

i am running the GC twice on the client, and usetimer i just checked is set in both configs to OFF

[Pete Dowson]

i dont have any line in wideclint.ini called joystick scanning or anything else so i guess that shouldnt be the problem.

Please check the WideFS documentation! That parameter defaults ON. You need to add the line I suggested to try switching the joystick scanning off. That's why I suggested it! It defaults on because on all systems I know of it does no harm whatsoever.

i am running the GC twice on the client, and usetimer i just checked is set in both configs to OFF

Ah! I have the GC running three times on one client, and it stutters very badly UNLESS I set UseTimer=On on two of them. They compete for WideClient's attention and this causes havoc. If one is the PFD/ND and the other is EICAS, set UseTimer=On in the EICAS.

Really it is MUCH smoother if you only run one copy. Try one stretched window with both PFC and EICAS. I am waiting for a version of the PFD.EXE which provided PFD/ND for both pilot and copilot, plus EICAS, all in one wide window.

Also try TCP/IP again (with default WideClient settings) when you've done this.

If you posted these things in the PM Newsgroup I'm sure several folks will advise you about all this.

Regards,

Pete

[ewg550]

pete

i will now try all this ideas some of them i dont know till now :D

will report in a hour or so :shock:

[ewg550]

short status:

config:

IPX

one GC

buttonscaninterval=0

all smooth no problems.

i dont like to test now TCPIP cause "never touch a running system" you know ;-))))

but it seems that the scan thing and the 2 applications of GC causes this badly stutters

M.

[Pete Dowson]

it seems that the scan thing and the 2 applications of GC causes this badly stutters

Yes, it does, unless one uses Timer to limit its access. Best to use a stretched window with all the gauges you need.

Regards,

Pete

[ewg550]

ok i´v finished my tests

config:

TCPIP

2 GC (EICAS with Usetime=on)

buttonscaninterval=0

its unflyable getting so many stutters

switching back to IPX and all work fine.

really dont understand it

[Pete Dowson]

really dont understand it

Nor I, sorry.

Have you no access to the PM newsgroup?

Pete

[ewg550]

yes i have access since a long time ;-)

and i already asked there about TCPIP/IPX but only one answer.

Now i tested again with IPX and only with one GC it works ok, at least when i start second GC it stutters again :cry: :cry: :cry:

when i only run one GC have it set then usetimer to on or off, or makes that no change when i only run one GC?

[Pete Dowson]

Now i tested again with IPX and only with one GC it works ok, at least when i start second GC it stutters again :cry: :cry: :cry:

Since both GCs are basically reading the same small amount of data from FS, through WideClient, the problem can only be that they do not like competing. Perhaps it is your video card -- many cards (or drivers) do not support OpenGL acceleration on more than one window. I use a Parhelia which certainly does not have that problem. I know Ray Proudfoot tried two GC windows on one nVidia based card and also had stutters.

This is really a question for Enrico, the author of PM, but my advice is to display all your instruments in one window, not two, using one copy of GC. If your video driver does not allow you to stretch the one window over two monitors, you either need a newer driver, or maybe you have chosen the wrong mode.

Regards,

Pete