Wizball

I dont know if my findings is related to the issue other have. But it was the solution for me.

When this registry entry existed my p3d was just hanging at 30% cpu and nothing more happend, no errors. I dident get the P3D dialog/startup screen. No FSUIPC.log was created. And your right, when I reinstalled FSUIPC things was working again, but I dident know why just reinstalling FSUIPC was fixing my issue. So it had to be something. But if your installer are removing all the FSUIPC entries from registry it will explain why it worked after a reinstall.

Hello I Also had issues lately with P3D not starting because of FSUIPC. It happend after a crash I had with P3D. I think I found the reason it dident start. I searched the registry for FSUIPC and found this. [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers] "F:\\Games\\Lockheed Martin\\Prepar3D v3\\Prepar3D.exe"="$ IgnoreFreeLibrary<FSUIPC4.dll>" When I deleted the "F:\\Games\\Lockheed Martin\\Prepar3D v3\\Prepar3D.exe"="$ IgnoreFreeLibrary<FSUIPC4.dll>" P3D started as normal. I dont know why fsuipc4.dll is "flagged", but maybe this can give you some hints. Tom Stian

I have locked my framerate to 25 FPS. And also usaly have 25 FPS in Fs2004.. My computer that is running PMSystems is a P4 1.4 GHz with 256MB RAM. The videocard is a Geforce 2 card. But I dont think that should slow down the performance to pmsystem!? Best Regards Tom Stian Bjerk

My PM-system may be a littlebit slow.. the logic cycle is set to 50ms .. And the hardware is a P4.. So I dont know why it is so slow.. PMsystems is not a CPU friendly software ..

Now I tried the both 0BCA and 32F9 offset.. The Autobrake is trigging the 0BCA offset, so can not use that one. But the 32F9 is working almost fine :) .. The only problem is that the offset is only trigging when my toe brakes are "on the move" If I hold the brakes steady at 50%, the offset is "0". PMsystems can have some problem to get the time to read the offset if I dont push the brakes "slowly". Best Regards Tom Stian Bjerk

Hi.. I have made an logic on PMSystems for automaticly disconnects autobrake when using the toe brake. For that I have used this offsets for detecting the toe brake use. 0C00 1 Right toe brake control: 0 – 200, proportional braking with timed decay 0C01 1 Left toe brake control: 0 –200, proportional braking with timed decay When monitoring the two offsets I got normal values from 0C01 (left toe brake) , 0-200 as described. But from the 0C00 (right toe brake) I got some very strange values. I dont remeber the values right now (at job) but it is not between the 0-200. And the right toe brake also "infect" the values for the left toe brake. Is it a bug ? :) Using FS2004 with FSUIPC 3.71 Well.. hope you understand. :) Best Regards Tom Stian Bjerk

Thanks... Its works now.. Thank you for the support :)

Hi.. Im using Project Magenta software. I want to assign two axis on my CH TQ for the Fuel Cutoff to the PMSystem. the Offsets are 561A .0 CutoffL 561A .1 CutoffR ON = Cutoff OFF = IDLE But I dont understand how to do it.. Im using a other axis for gear up and down. but I dont use any offset for that.. using the "buildt in" values. Can anybody help me with this issue ? Best Regards Tom Stian Bjerk

Hi.. Is it possible to preorder the FSUIPC4 ?.. So that I have the key when its ready for release? Best Regards Tom Stian Bjerk

My netbt.sys is also version 5.1.2600.2180

WideFS has worked perfecly for me until this problem with the mailslot/broadcast case. I dident now that the recommandation was to have all to computers in the same workgroup to get the WideFS to work two-way interaction. That is something I have missed. well well.. but I will check all my computers now and change them all to the same workgroup.. Anyway.. I am happy now.. :) .. Tnx again for the great support Pete.. Best Regards Tom Stian Bjerk

YES YES YES YES YES YES YES :) I SOLVED IT :) .. (sorry for caps :=) I am really happy now.. All the computers have to be in the same workgroup for the mailslot to work correctly .. :) I have not tested it very much yet, but as I said it worked :) There is a known bug for microsoft, you can read about it here http://support.microsoft.com/?kbid=822345 Microsoft says that the resolution is to obtain the latest servicepack. But I have all updates from windowsupdate. But MS also says that it is possible to get an HOTFIX for this problem. Best Regards Tom Stian Bjerk

What I could do is supply a WideClient with both the interval (3 seconds at present) and the timeout (1 second at present) configurable. Then you could experiment, from the daft (timeout of 10 seconds, every 11, or similar) to the fast (timeout of 100 mSecs every 150 mSecs) -- assuming I set the values in mSecs. What do you think? Is it worth a try? Let me know. I sohuld be able to fit that in tomorrow some time. Regards, Pete If you feel you have the time it had been very kind of you to do that.. :) until you have made that new version I will still test here to get it to work. I dont going to cry even if we dont find out what the problem is. The wideserve/client is still working good with the wideclient defined setup :=) .. But it had been nice to find it what the problem is. Isent there anyone else that have tested this ? Tnx for the great support Best Regards Tom Stian

You got mail :)

Great.. I will take a look at it to night.. :D do you wont the logs here or email? Best Regards Tom Stian

Well.. Yesterday I reinstalled my fs2004 computer.. Installed Windows XP with SP2 and all windows updates. Installed fs2004 with the patch 9.1 Installed wideserve on it. But the broadcast still not works. Amazing. I have tried almost everything. But... The weakness of my testing was that I almost only was testing from one client. I tried a another client yesterday, and the broadcast worked.. hmm.. strange.. Why doesnt the 4 other clients works? .. The clients that are not working are compaq computers. Different models. Have tried to upgrade the network card driver. Even tried different settings on the NIC. with no luck. And now the very scary part. Why did the broadcast worked for my client when I was running fs2004 on my Media Center Edition PC ? Im going crazy soon :)

Hi again.. I have tested much here now. And I found a solution on the broadcast, but not exaclty the problem. I installed FS2004 on another computer (this computer is a Media Center Edition w/SP2). also installed fsuipc and widefs on it. On that computer the wideserve broadcast works as a dream. So the problem that I have with the broadcast on my other computer is a local problem I think. It is very strange. The easiest solution is to reinstall the computer to fixes it. But will try to find out what is wrong with it first so that I can locate the bug on it :) I will post it here if I find the problem. Best Regards Tom Stian Bjerk

My server is WinXP Pro with SP2 , my clients are 4 WinXP Pro with SP2 and 1 Win2K SP4. Hmm.. Now I get confussed.. The reconnect with UDP Protocol works now. I have tested it many times that the result was that is was not working. But I tried now and it worked. But the diffrent now was that I only tested 1 client with UDP, the others client is using TCP. So I dont have any log for you at the moment :)

I have not tested the 6598 yet, but have tested the 6597. I still have problems to get the Broadcast to work.. The client wont connect if I dont define the servername and Protocol in the wideclient.ini. And another problem.. If I use UDP on the clients and I restarting the FS2004, the clients wont reconnect. I have to restart wideclient.exe on every client. But with TCP it works great.. Here is my sample of my wideserve.ini [Config] AdvertiseService=1 AutoRestart=0 AutoUpdateTime=13 MaximumBlock=8192 NoStoppedRestarts=Yes Port=8002 RestartTime=10 SendTimeout=15 TCPcoalesce=No ProtocolPreferred=UDP [ClientNames] 1=WHITESTAR 2=ZAGREB 3=TSBFLIGHT2 4=TSBFLIGHT3 5=TSBFLIGHT4 And my wideclient.ini [Config] ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 PollInterval=2000 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 Window=75,81,593,489 Port=8002 ServerName=Hanibal Protocol=TCP This is now my working config. If I remove the servername and protocol from the wideclient.ini it wont work. Best Regards Tom STian Bjerk

Great .. will try the new version tomorrow .. :) .. I have to sleep now :) So long.. Tom Stian

The server is running WinXP.. To get it to work I hade to set the ProtocolPreferred=TCP on the server and Protocol=TCP on the clients .. without this the clients dident work.. When I defined UDP on the clients and the server I did get som errors in wideserver.log. I will test a littlebit more tomorrow and will report it here.. So long Best Regards Tom Stian Bjerk

standby on this.. Mabye I found some out here.

Hi.. I trying to test the latest beta WideFS version.. I have some troubles with it.. I have 5 client computers and 1 server with fs2004.. I have upgraded wideclient on all the clients and the wideserver on the server. After the upgrade I can only connect one of the client computers to the server. The other clients wideclient.log says: ********* WideClient Log [version 6.596] Class=FS98MAIN ********* Date (dmy): 17/04/06, Time 00:14:39.425: Client name is xxxxxx 631 Attempting to connect now 1632 Trying to locate server: Need details from Server Broadcast 1632 Failed to connect: waiting to try again 2674 Attempting to connect now 35281 Trying to locate server: Need details from Server Broadcast I have tried the both ProtocolPreferred= UDP and TCP on the server I have tried to telnet from a client that not working to the server. Ill get a repons from the server on port 8002. There is no firewall on my system. But there is very strange that there is one computer that get connected to the server. (it is the same client every time) .. Also using the same client config on all clients. My clients are 4 WinXP and one Win2k.. The wideserver.log dosent say anything about any connection from the computers that I have problems with. It only logs the computer that works. What is wrong ? :) Best Regards Tom Stian Bjerk