Search the Community

Hi,I have been running Flight without problems, but the Marketplace always crashes on start - that is quite unfortunate, because it seems that it is the only way to install additional content (am I wrong?). I am running Win XP SP3, updated. Is there any help?

Hey everyone, I believe I have solved the joystick woes with Windows 8 and Windows 8.1. I have done 2 days of stress testing FSX and P3D with multiple installs of the program and OS, and I haven't had a disconnect yet. Before I go further - I want to give my thanks to certain individuals who have helped me and inspired me to solve this joystick annoyance. 1) Word Not Allowed for having his awesome guides 2) AVSIM's staff/team for creating the amazing Hardware/Software Guide to FSX/P3D 3) Peter Dowson's FSUIPC utility (it got me through the periods when no joystick fix was avialable) 4) Orbx Team - Thank you Global and your Tips and Tricks Forum section 5) NickN's - FSX Computer System Guide 6) Ranak Jones of "Rogue's Guide to Acquisition: Principles of Final Frontier" for sending me a spare XFX 6970 for my system and pointing me to Windows 8 Registry to search for USB Device GUIDs potential errors 7) Microsoft MSDN for having Windows 8.1 Pro for testing/evaluation purposes only. 8) LM Prepar3d Developer Network Testing: 1) FullScreen FSX in Eyefinity Mode (5760x1200) for 3 hours+ 2) Windowed FSX in triple screen mode and 1920x1200 for 4 hours+ 3) Multiple active windows on top of FSX Windowed in background for 4 hours+ 4) Testing was done with USB 3.0 and USB 2.0 ports FSX testing was in Win 8.1 and 8, and P3D 1.4 was in Win 8. My System Cpu: i5-750 (intel 1156 cpu) overclocked to 4.1Ghz Memory: 8GB DDR3 Storage: 1xSamsung 830 SSD at Sata III (Main drive), Intel 80GB SSD at Sata II speeds, 1 TB hitachi mechanical HDD at sata II <- all connected to PCIEx4 Sata III controller) Motherboard: MSI Fuzion p55A - has native usb 2.0 and Renesas USB 3.0 controller Video: New XFX 6970 2GB with latest ATI drivers OS - Windows 8 Pro Clean install / Windows 8.1 Clean Install Joystick: Thurstmaster Hotas X Windows 8 Solution - (FSX / Prepar3d 1.4) 1) Make sure power management features are off or set to high 2) Most important setting is USB Selective Suspend Setting is Disabled (we all knew this) Honestly, that setting does not disable USB selective suspend in Windows 8 (this is for Windows 8 only), like it promises. The power management on USB devices is set to Selective Suspend Please see your HID Devices, USB Input Device and USB Root Hub Devices - They are STILL set to Suspend. You have to turn OFF the manual power savings one by one to all USB Devices/Compositive Devices and the all the USB Root Hubs (this is v.important). If it says "Allow the computer to turn off this device to save power" and is checked then please UNCHECK it For example like this This was discovered when I was searching for Joystick UID's in Windows 8 based on Ranak's suggestion. This is where stuff gets weird for both Windows 8 and Windows 8.1. I am no registry expert, but GUID's for my joystick is half correct and half backwards as compared to one listed in FSUIPC's ini file See Pic - Windows Registry And my Joystick GUID in FSUIPC So for some reason half of the GUID is backwards in Registry - I do not know if that is normal or not but that led me to search all the usb devices/ports in Device Manager. Here I found all the power saving features were somehow enabled when Windows Power Management is explicitly set to disable. Recap So for Windows 8 Pro ONLY - Uncheck Allow the computer to turn off this device to save power and make sure Windows Power management also has Selective Suspend set to Disabled. Prepar3d 1.4 - Please have JOYSTICKS=1 in [CONTROLS] in P3D.cfg (more on this later) Windows 8.1 Pro (RTM Version) - FSX TEST No joystick disconnects with 1 Setting change Only - Joystick works in Windows 8.1 Pro I am seeing that all devices still have the USB Power Management check in windows 8.1 but in FSX with PNW, and Bowerman addon, Carenado B200 - Joystick did not disconnect. The only crash I got was from latest FSUIPC 4.92. If in Windows 8.1 you have joystick disconnects, then just turn off all those power management features as listed in for Windows 8. Miscellaneous Info FSUIPC I have it installed but it Zero Joystick Configuration in all tests. I hope this helps everyone - as Windows 8.1 Pro definitely works fantastic with no joysticks issues so far. And Windows 8 works with all power management features individually turned off in all those sections listed. Have a great day, Skywolf

Hello Nico Thanks for your quick respons and sorry for putting my problem in the wrong forum. I uninstalled FLAI and intalled it again on my C:\ disk. I did not manipulate anything and now everything is running 100%. 😄 Thanks for your excellent program: it really enhances the flight experience! Best regards Wim Mens

Hello, I'd consider myself a competent amateur so I may be missing something here, but here's my problem. I'm flying the RealAir Turbine Duke and deciding to add a challenge to an already difficult scenario I've created, I opted to have the left engine completely fail mid flight. Unfortunately, when it does fail at my specified time, the flaps and landing gear stop operating due to the left generator no longer working. I've tried simply starting one engine, whilst parked, and operating the flaps and nothing; unless both engines/gens are running the flaps/landing gear don't operate. I've tested the same conditions in the B60 Duke and the stock FSX Beechcraft twin engine aircraft and, as expected, no problems. Am I missing something, or is this a bug that needs reporting to RealAir? Thank you for any help.

I want to ask, how to mark a thread as "Problem solved" or something like that? In many communities it is a feature, to mark threads in that way, that helps members with one view, whether thy can find fast solutions in the thread. If it is not possible, you should think about it. It is a very useful and timesaving feature. Thanks for answering.

Dear collegue virtual aviators. In this post I would like to share with you my successful troubleshooting session while having problems exchanging flightdata from one PC to another PC using simPlugins Panel Builder and simPluginsPrepar3D40.exe interface for Prepar3Dv4. For the impatient reader: the problem I faced was caused by an active "Virtualbox Host-Only Network" ethernet adapter by Oracle Corporation (version: 5.1.26.0, date: 2017-07-27). De-activating this adapter brought the flightinstruments on PC2 immediately to "life". I saw a post from GauthierH from February 15, 2016 here on Vatsim forums. He mentioned also have a PC with a "Virtualbox Host-Only Network" adapter, but he reported that it was not in use. As far as I know until now, the source of the problem I encountered has not yet been published. This is the reason I feel free to share my experience with you. My PC setup: PC1 and PC2 operating under Microsoft Windows 10 Pro. PC1 is has a 64-bit i7 processor. PC2 a 64-bit Intel Atom Z3735F processor. Both PC's via ethernet cable connected in a local area network. PC1 running a flightsimulator Prepar3Dv4 (bought recently) and a SimPlugins interface app: simPluginsPrepar3D40.exe. PC2 running SimPlugins Panel Builder v 2.99. My problem: The flightsim data from PC1 is not arriving in PC2. The standard 6 flightinstruments of the Panel Builder application in PC2 are not moving. I checked / tried: a1) When I run Panel Builder on the flightsimulator PC (PC1) then it works O.K. Panel Builder receives and shows correctly the flightdata from the Prepar3Dv4 flightsimulator; a2) The "Comms Checker" program from simPlugins, installed on PC2. did not show reception of flightdata; b) all the problem solutions I found on internet and in this forum, like: setting same language; setting decimal point as the decimal indicator; c) MS Windows Homegroup and filesharing working O.K.; d) stopped (temporarily) the Firewall of an Antivirus program running on PC1 and PC2; e) created portforwaring for all the Panel Builder and interface ports on the router (from my ISP) in the LAN towards PC2; f) checked the Windows 10 Firewall that it was not blocking traffic from Panel Builder and the interface app; g) on PC1 I had the Wireshark app installed. For those readers that are not familiar with this application: Wireshark is a Network Analyzing Tool. With this tool I analyzed the UDP traffic that was seen by Wireshark. I saw that many UDP packets were sent from an IP address: 192.168.56.1 to the multicast address 224.11.5.62, to UDP ports in the ranges: 41001 to 41010, and so on. These are ports in a range used by the simPluginsPrepar3D40.exe. The address 192.168.56.1 is an address that is used with a local area network (LAN), but none of my PC's has this address. But in the beginning of seeing all this: no bells rang in my mind. With Wireshark I was able to see the content of the UDP packets sent. They contained data that I recognized as data of flightinstruments, radio frequencies of radios and navaids, etcetera. The information presented by Wireshark helped me to build up my knowledge of how flightdata and data of radios, navaids, settings of switches was being communicated to a Panel Builder app, it did not bring me (yet) a solution to my problem: the data is not arriving in PC2. What I further discovered through Wireshark was that it was seeing a "Virtualbox Host-only Network" (in the list of network adapters like "Ethernet1, Ethernet2" and so on). I know Oracle's Virtualbox application. I used it a while ago on my PC1. It is still installed in this PC. h) Because I came not much further in this troubleshooting session, I decided to install Wireshark also on PC2. When running Wireshark on PC2 I saw that on PC2 Wireshark did not report the existance of a "Virtualbox Host-only Network" adapter. i) I googled on internet for an explanation of what is a "Virtualbox Host-only Network". I found a useful instruction on YouTube, address: "https://www.youtube.com/watch?v=1k6u8bFKGHA". According to this instruction video a Virtualbox Host-only Network blocks traffic to the LAN. Next I checked the status of my "Virtualbox Host-Only Network" adapter. I saw that it was Activated. j) For the sake of this troubleshooting session, I de-activated the "Virtualbox Host-Only Network" adapter (Microsoft Windows 10 Control Panel -> Network and Sharing center -> Network connections). As soon as the "Virtualbox Host-Only Network" adapter was de-activated, I saw that the "standard six" flightinstruments panel of the Panel Builder application running in PC2 were working. In PC1 I turned the flying aircraft to another heading. I saw the Heading indicator on PC2 was changing according to the heading indicator in the cockpit of the aircraft in Prepar3Dv4. I also experienced that pushing the "Start" and "Stop" buttons on the interface app simPluginsPrepar3D40.exe had the intended result of starting and stopping the flightinstruments in the running Panel Builder application on PC2. A test with the "Comms Checker" application on PC2 was now successful. For the moment I have no necessity to have the "Virtualbox Host-Only Network" adapter to be activated so I leave it de-activated. Sofar this troubleshooting report. Paulsk

Hello, I just purchased the RealityXP GTN750 using my F1 login. After installation I started Prepar3d V4.1 and loaded the Carenado 337 Skymaster. I installed the popup 750. On startup I get a message that says INVALID LICENSE:CONTACT VENDOR. I can then select continue below and the GPS will go to the next page. What should I do to resolve this issue. Thank You

Hi. Newbie and so apologies for wrong forum, question already asked/solved etc. :mellow: I recently had a problem with a fairly new FSX install (few weeks old, dodgy addon) on a newly built computer that required me to remove it and start again. However, reinstalling it is proving to be more trouble than any reasonable individual has a right to expect. For "some" reason whenever I run the installer all I am offered is the Remove or Repair option. Now, I have removed it. I have scoured my registry, my hard drive for files and fragments and got rid of them. I have followed numerous Googled ideas about how to resolve this problem without success. I have used Revo Uninstaller (always do), I have tried Windows Install Cleanup (it was no help). I have manually looked though my registry using regedit and Registrar Registry Manager. I have, in short, done everything I and apparently, other people, can think of and it still will not install. Please can anyone offer anything further before what is left of my hair is torn from my already weary head. Two things I feel might have bearing on this. My first attempt at reinstalling was working but I realised I had selected the wrong HD and cancelled the procedure. It was literally seconds into the job and only 2 obvious files had been copied to the new (incorrect) folder. This was to my system drive and I do not install FSX on but a seperate one. Secondly, I read elsewhere and thus cannot vouch for the accuracy of the information, that it is possible that the WinSxS folder is corrupted and this will prevent FSX installing. I have no idea if this is true or has happened to me. Everything else is working fine and glance at said folder shows nothing to suggest there is a problem with it. Of course it may not be that obvious assuming this is a possibility. Does anyone have any ideas, anything. I'm at a loss and although I'm no computer expert I am by no means inexperienced and without a modicum of skill. Anything at all would be gratefully received. I want to fly my planes again. I do miss them so. Many thanks for taking the time to read my rather pathetic plea. Best Wishes. Windows 7 x64 btw.

Hi, Recently, I've decided that it is within my best interest to make the investment to add another large disk drive in my system specifically for backups. Although I will have a backup drive, I have no backup software. What do you guys recommend for backing up my system and all of my files?

Hello, Well, this is nothing new really, but today I'm elated because for me at least, I've finally gotten fsx and a lot of orbx scenery stuff working beautifully....smooth 30-70 fps without jitters or tearing or anything weird over SeaTac with autogen on dense. It's been a long, tedious waste of time trying to get things to work on my system. i7 3.5 ghz, gtx 560ti windows 7. one SSD drive for Windows, one SSD drive for FSX....near instant texture loading and menu loading. Nice to have but $$$$ and limited storage. The issues I've had are numerous crashes to desk-top, fatal error messages, bizarre graphics meltdowns (black skies, smearing weirdness etc, blurries, stuttering, you name it. This stuff doesn't happen all the time, but definitely once in every flying session. Fatal error 2-3 times per session : ( I've tried everything under the sun and have reinstalled fsx and all the add ons four times (my wife is ready to leave me). For me at least I've 'learned' what works on my system and I can repeat it now every time on my computer to ensure great results. I just thought I'd share what I've done that's worked so well. I realize that all systems are different yaddayadda yadda. Some of this might work for you, some of it might not. Posts like this sure helped me sort things out, so I thought I'd give back. So here's my story: -I've tried many tweaks to the config, usually with the Bohote fsx tweaker tool. Bufferpools, max texture load, reject threshold, etc. etc. etc. After hours of trial and error using a saved flight for consistency, I only found the tweaks to cause instability and noticed little to no difference to frame rates or visual performance. I've concluded that for better or worse, the stock config is the most stable. I run the sim at stock config except for the swarmcloud fix which solved flashing clouds for me and the ForceFullScreenVsync=1 which solved the screen tearing. I run my card on default settings with vsync enabled. Nothing else is different. (I've experimented with external AA, vsync settings, external frame limiter, and have noticed no differences to the sim in performance or quality..only instability and unpredictable performance. I'm running fsx acceleration btw. -I also run all the Orbx North America sceneries. I LOVE these addons but have found them to cause a lot of instability to FSX on my machine (crashing, errors, artifacts etc.). I run REX, but have never had any issues with it anywhere and the fsx default scenery flies like a dream and has never crashed or erred. So for me, Orbx FTX was the issue. Now here's the game changer: What really solved MY problems was the UIAutomationCore-1.dll vista file 'fix'. I downloaded this Vista file and simply dropped it into the FSX main folder. I can now fly FSX problem free. I can switch menus over and over, change settings, start and stop, fly in complex areas in addon aircraft and never have a crash or error. If you're having issues on a Widows 7 setup and haven't tried this, I highly recommend it. http://www.mediafire.../?mik2mlqdz1w�� It might not work...hope it does because for me it was like Christmas. It could be wishful thinking, but I'm pretty sure I've gained 10 frames per second from this as well. I'm no computer expert though so don't know if that's even possible. As for settings: Filtering-Bilinear AA-On All boat traffic 100% Cars 25% Water low 2.0 Private traffic 100% Airline traffic-off Autogen Dense / Auto gen complexity maximum Mesh Complexity 50% Mesh Resolution 100% Detail radius 100% Texture res 100% No ground shadows, NO BLOOM!!, no aircraft shadows, cloud distance 80K, Also, I tried using the Grand theft auto ENBseries mod, but only found it to cause issues for me and maybe even instability. I don't know though, people seem to use it and works for them. Thoughts on Frame limiter: If you have a fast machine and you're getting a wide range of fps in a single flight it can cause stutters (as you know). I found that by simply setting the fsx frame limiter to 100, it stops the stutters, but still allows high fps. It's as if by simply having it on, it irons out the issues for a fast machine. So in busy areas, things drop to 20-40 fps, but can fly up to 70 fps without jitters as well in simple areas. By setting to 100, I never fiddle with the slider anymore no matter where I'm flying. Definitely advice for fast systems only though I suspect. This nice little program will allow you to slow down the AI vehicles from 1000 mph to something more realistic like 25 mph. Looks great in towns. http://www.wolfgang-...ng-picheta.de�� Also fixes lots of little details. For me, the brakes release/hold control would never repeat. I'd set the slider to max repeat but it would revert. I tried many joystick assignments for it but the problem persisted. I discovered that by setting it to medium, it now behaves like a true car brake and never reverts in the assignments. On an aesthetic note, I love the Water configurator from http://www.strikings...om/fswc.shtml�� combined with REX, the water can look beautifully real ('black' lakes, rich dark oceans etc.) Well, that's all....sorry for the novel. I just wish that I would have found this post 3 months ago, so I'm just writing it to put it all down in one place. Maybe it can help someone out there with similar issues/setup to me. I realize that it's all nothing new. It just hard to find it all in one place! Hope some of it makes your fsx experience a little more friendly.

prior to updating using older version LNM and LVC all was working well. on my network, updated both LittleNavMap (LNM) and LittleNavConnect (LNC) TO V1.8.3, now LNC window shows connected to both the sim and to my networked computer running LNM, But my aircraft is not showing up in the map. Also can run LNM on my main computer and all scenery loads with no errors, but load scenery on my networked computer thru network and get several errors, can I load scenery on main computer then copy the files generated to my networked computer to have it use? if so where and what type would I look for?

So had a weird one in 5.3 yesterday, Did KEWR-LLBG in real time which was spectacular. Landed at LLBG but as soon as I departed the runway the QW787 started rocking uncontrollably. Made it to the gate and the plane started hopping until the point it rolled on it's side. This was sitting completely still trying to set the parking brake. Eventually I got so ill to my stomach from the screen jumping all over the place I just Alt-F4 and shut down P3D. Has anyone else seen this? Does anyone know of a fix? Thank you in advance as always for the time and any assistance.