Erikviktor1

Pete, I fully understand your point but even the most thourough and best of us cannot remember everything. I work on a very complex project where my "hard-drive" (Brain) is actually full and there is little space left for extras. I need memos.Even pilots need check-lists not because they are dumb but because they need them to memorise things for safety reasons. May I suggest the following; when Installing FSUIPC create a shortcut on the desktop or any other site where it can be found easily that reads "FSUIPC DOCS". You have created a great product but one of the major flaws of Software designers is that they tend to forget who buys their product and that these people DO NOT spend day and night on that same product.

Hello fellow simmers, I have a problem when I switch my USB mouse and keyboard and monitor from the client Pc to the Server running P3D V2. WideFs on client pC runs well and very stable and connects SAITEK panels. Interesting: I connect the panels using the SAITEK FS2004 PANEL PLUGIN and NOT the FSX plugin! The Saitek panels /WideFS work well until I use the USB switch to see the Server screen / connect the mouse and keyboard. When I switch back to the client WideFS crashed and I get the following message "FS ELIMINATOR FOR FSUIPC CLIENT application has stopped working" Note; for pratical purposes and development my rig is set up like a server with 2 client PC and a USB switch that allows me to view and control each PC as required. I use this during development, not in the regular home cockpit. It took me a while to find out that the problem seemed to be related to the USB switching. Fsuipc log clearly shows the USB/HID disconnect and reconnect.. " ++++ HID USB DEVICE RECONNECTED; REINITIALISING FSUIPC CONNECTIONS" A few observations:; WIdeFS and SAITEK panels run well on client when not switching USB mouse or when using a separate mouse connected to PC. Crash is WIDEFS/FSUIPC related. saitek Panels plugin 2004 does NOT crash. I installed the panels and WideFS on the 2d Client and the same problem comes up, so it doesn't seem to be related to any client hardware or software issue. I use a network (ethernet) switch. When using this switch instead of a regular router, the server PC HOMEGROUP settings are lost everytime I reboot and have to be readjusted. As it seems to be FSUIPC related, is there anything I can change in the logging settings that might avert this? Could the crash be related to a dataflow issue caused by the USB disconnect/connect logged by FSUIPC5 (as shown by the log) and maybe an unstable or damaged ethernet switch? But then why is no other interface affected?. Other software that use client interfaces such as Simplugins and Flight1 GTN running on clients are not affected by this problem and run very stable. Reinstalling FSUIPC4, P3D, add-ons did NOT solve the probem. Updating hardware drivers on server and clients did not solve the problem. No hardware problems. I hope someone can help explain how to solve this. Happy landings! Erik

Hi Pete, Thanks for the quick reply- I ignored that Widefs didn't control joystick axis inputs over a client PC. Must have missed that in the docs. I expect that I got confused as many users use FSUIPC to overcome such glitches with their controls running directly on FS (server). I learned something here. Cheers! Erik

Hello, I have the same problem with a SAITEK pro flight yoke installed on a networked PC running updated WIDEFS (registered). I can asign buttons and keys on FSUIPC4 installed on server PC but no axis. FSUIPC and WIDEFS are up to date. I had an older version but installed the latest version from Shiratti.com (version 4.954). This did not solve the problem, nor did "Joyids" software. It did asign an ID nr. and "saw" the yoke but this did not help FSUIP in registering my yoke on the client PC. I tried also to connect the yoke to the server and FSUIPC was able to register the yoke's ID and axis. I hope this might help recognize the yoke on the client PC but no luck there. As I am running out of ideas I think I need your help. Erik

Hello Pete, I have a similar problem as the one described in this forum topic. My saitek yoke is not recognized in FSUIPC4 on a networked PC running widefs. Symptoms; NO ID nr. or joystick ID appears in FSUIPC on networked pc running with updated WIDEFS. I tried creating a Joystick ID nr- with the "Joyids" software as you suggested and my device appears as "SAITEK ID nr.#1" on this software table, but it doesn't change anything. Still no joystick or axis control in FSUIPC4 on network PC. I tried the same procedure connecting the Yoke to the Server PC running FS and yes it does registrer on FSUIPC when activating the yoke axis. On the network PC I can program button functions in the "Buttons and keys" window but no axis control, Moving the yoke produces no signal at all nor any ID. I also reviewed my FSUIPC4 and WIDEFS versions and upgraded both as they weren't up to date and rebooted the system twice but this did not solve the problem. I am running out of options on my side. Your expert advise is required. Erik