Search the Community
Showing results for tags 'errors'.
Found 4 results
-
Several users have reported various errors with devices not connecting to LINDA. Some of these errors are related to newer USB devices such as touch screens and the wireless mice/keyboards. To help you to get LINDA working, it is useful to know what device is causing the problem. Please follow the following guidelines when reporting the error: 1. Unplug the USB for all your devices (joysticks, throttles, touch screen), reboot your system and open LINDA. 2. Plug in each device one-at-a-time and ensure that LINDA shows the device on the Summary and Setup Joysticks pages and that buttons are highlighted on the Joysticks page. 3. If an error message is displayed, either as a pop up dialog or on the LINDA Console, note or take a screen shot of the full error message. 4. Find and note the Vendor and Product IDs (VID and PID) as described below. 5. Report your problem on the Support forum quoting the LINDA version you are using. I will do my best answer your problem. PID & VID The PID and VID can be viewed by opening the Device Manager and looking under Human Interface Devices. Find the device that is not being recognised by LINDA and open the properties (double click or right click and select properties). Then under Details, select Hardware Ids from the Property dropdown. The Vendor and Product IDs (VID/PID) appear in the first and second line as a 4 character hexadecimal number. The VID and PID are used by LINDA to work out the type of device and whether it should be included in the list of devices. UPDATE Further investigation and testing by affected users has identified that the ‘Device cannot be opened’ errors are being generated by the third-party library routines used by LINDA to interface with HID devices. Even updating to the latest version of the library has not resolved the problem with certain devices. There is nothing more I can do a this time with the LINDA code until the library is updated. The only way forward I can suggest is for affected users to isolate the USB device that is stopping the others working and leave it disconnected. Not a satisfactory situation I know.
-
Hey guys! Well.... i've just about had it with MFSX . When I built a new computer mostly for FSX I installed windows 8 on it (I know.... bad move), and sure enough i was getting all kinds of joystick problems, so yes i tried FSUIPC registered, disabling this and that blah blah blah.. And recently i took part in the cross the pond westbound just yesterday, and right when i got my oceanic clearence... BAM! Fatal error! So i was sick of it and uninstalled windows 8 and installed windows 7. I just got FSX up and running, Installed FSUIPC, REX and applied all the tweaks, and now when i try to run.... "Flight simulator was unable to load some program files and will now exit. Pleae reinstall FS....". That was the final strike. I checked for fixes and there are none and even if there are i dont really want to go back to it, i want to try something new. So prepar3d, which has support, developers, communities ect. However I have some questions about it before i buy. Most addon software now give the option for prepar3d which is great, however do PMDG aaircraft work fine? I know you can make them work but is it a hassle? I really enjoy playing on VATSIM so i was wondering if squawkbox works fine. Also, do you get random errors in game like in FSX? Are there a bunch of tweaks to add to the config file? Do you recomend i make the change? If you want my specs just for info there on my profile, and a list of addons i use(ed) in FSX: (in case you want to tell me something on compatibility). PMDG aircraft, looking to get the 777 Catpain sim 777 aerosoft airports and scenery REX ( I know they have prepar3d support) FSUIPC(Not sure if you use it in P3D?) SweetFX P.S. Did any of you use the "FSX to prepar3d migration tool" on the simmarket? Thanks a lot and hope to hear back from you soon!
-
Since the latest update I am unable to extinguish the caution light. and I have two faults showing , 1. Body gear steering error message 2. fuel transfer x4 I am unable to find the source of the error messages. Furthermore the autopilot disconnects itself and after recycling everything for about 10 minutes I am able to get it to function . That happens occasionally and not every time. I'm am using FSX steam edition. Another issue is the 737 ngx 600 update from the operation center keeps appearing after I start the ops center. I do the update but at the next start it reappears. Anyone having similar issues? Shannon Loder
-
important! System Update Status - Reporting Funkalities
Tom Allensworth posted a topic in Hangar Chat
We successfully updated all modules of the forum system earlier today, completing the process at 1700 EST. I ask that you keep your eyes open for things that appear to be broken. If you find anything amiss (we haven't seen anything yet), please report them in this topic. Thanks.
