Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

morso484

Members
  • Joined

  • Last visited

  1. Thanks for all the info, I was kinda thinking that was the case, not really cheaper nor worth the effort.
  2. I'm thinking about abandoning my older tower desk top and going with these new mini pc's. Mainly to do simple things and internet access, but I would love to devote a large block of hard drive to my FS2020, (not ready to make the switch). Prices are coming down and Amazon has some interesting sales. Any thoughts on what does and doesn't work with this setup and what to look for. My current machine Has a Ryzen 7, my system is a little better than the minimums for 2020. Thanks
  3. Thanks, good to know, my NVIDIA card is an RTX3070, unsure of the ram but I believe it to be at least 8.
  4. I am about ready to pull the trigger on the MD-11, one of my favorite aircraft, TFDi recommends at least a Ryzen 7 3700 and 16g ram. I have a Ryzen 5 3600 and 32g ram. Would this be doable? Does anyone have this combo? Thanks in advance
  5. Thanks for the response, I believe the 64 bit is the way I will go, I will put the new O/S on a new drive and boot from that, using my old drive as the backup source. I did manage to get the FSX running again, careful uninstalling of SP1 and reinstalling got everything back to a working state, I would appreciate advise on running with the memory resources that I do have until the 64 bit upgrade. Last night while giving it a test run, a QW 757 was only able to taxi to the active runway before it crapped out, but I did have IE open at the time. Mike
  6. I am turning here because the forum was of great help with past issues I had, (missing landing gear on CS aircraft), anyway, my latest issue is this; My FSX seemed pretty stable under Windows 7 Professional 32 bit. I had just purchased PMDG 737 NGX and the 600 series add on a few days later and it seemed to install and run well, but I got part of the way through the first tutorial and the sim locked up. Probably out of memory due to the 32 bit limits, (I have 8 gig on board). I did some preliminary checking of the fsx.cfg and other things, but did not change anything, (99 % sure, but may have inadvertently mouse clicked on something), The program wouldn't work after that, initially, it ran and opened, but you could not see the twirling aircraft that you selected, just a black screen, then FSX wouldn't open at all, opening FSX screen, stop with fatal error, closing fsx. Haven't been able to get past it. I used my FSX disks to attempt a reinstall, but only the repair feature, no joy, today I did a windows restore back to when the 737 600 was installed, ( I know it worked then), but again no joy. I am pretty feed up but really want to get this fixed, In the near future, I am looking to install a faster hard drive, maybe SSD or SSHD and go with Win 7 64 bit. I assume that should help the memory issues. Now as an aside in case it helps any diagnosis, I also have Train Simulator 2014 that CTD as well, but it is a notoriously buggy program and that is a battle for another time. Mike
  7. Oops, should have read more carefully, maybe it will help give some direction in his case. Mike
  8. I had very similar problems re-installing my CS aircraft. The short version is nothing worked with all the re-installs and such, but check your fsx.cfg file, in the "trusted" section, a lot of the lines end with a number, such as "=2". I found a bunch that said "=-2", somewhere, someone suggested changing those to the positive number and it worked. Others said delete the fsx.cfg file and let FSX rebuild it, but that didn't work for me. I just went in the fsx.cfg file trusted section and changed every instance of the line ending with a negative number back to it's positive counter part and it worked. I'm still trying to figure out what it all means or why they changed, but that seemed to fix every aircraft that I had trouble with, add on or default. Mike
  9. Jim, Thanks for the reply, actually, I did try that initially but it never asked if you wanted to use those or trusted it, just like after the reinstall, FSX never asked to re- activate the program. I'm wondering what the numbers in the fsx.cfg file mean. The lines end with "=0,1or 2" or the negative version, but what does 0 or 1 or 2 mean to FSX? This might be the issue I'm having now with the seemingly random changes of those numbers. I do believe this fix will help a lot of people with gauges problems or whatever, mainly the large number of people who can't get their Captain Sim aircraft to have landing gear. If I can hammer out a solid solution, I will be spending the word. Mike
  10. Hi, To make a long story short, I have just spent weeks fixing my FSX after a hardware upgrade, first my Captain Sim aircraft wouldn't work, then the PMDG aircraft. After fixing those, my FSX quit after 30 minutes and couldnt' be reactivated. Well I muddled through all of it and seem to have fixed everything. For those interested, my FSX was it's own directory, but wouldn't reactivate until I made a new user account on my computer, then accessed FSX and it asked for the key code. The aircraft all had problems that were traced to the fsx.cfg file. For some reason, every place there was to be a number, "0,1 or 2" it had a negative sign in front of it. On some forum, someone mentioned this fix. So, changing all the numbers from the negative version to the positive seemed to fix the aircraft. ( I have added an example). Now tonight after the first time of flying after the fix, I flew a Carenado 182Q and it work fine. Then I switched to a Captain Sim 727-100 and it did not work, no working switches and such. I know I changed all the numbers, but I suspect that after flying one aircraft, something in the fsx.cfg file changed others to the negative version. I stopped FSX, opened the fsx.cfg and found the 727-100 numbers had changed to a -2. The question is what can I do to prevent this or somehow lock this file so it can't be changed? This is what I mean about the fsx.cfg file, this seems to make the aircraft work properly: C:\FSX\SimObjects\Airplanes\CS_B777-200ER_GE\panel\Captain_Sim.x777.sys.GAU.abhtzzaokchluweqkccwkiunhcbawnirqqhoozuw=2 C:\FSX\SimObjects\Airplanes\CS_B777-200ER_GE\panel\Captain_Sim.x777.sound.GAU.qeqiwhqkolezuiwzrzbbtrtzbrcabkltuhqbzebb=2 C:\FSX\SimObjects\Airplanes\CS_B777-200ER_GE\panel\Captain_Sim.x777.update.GAU.rooqwnuuciwoaaiwrwhlowzqcciehltteruorilb=2 Maybe someone will recognize the problem that is changing these numbers in the first place and I can fix that. As an aside, Captain Sim support was worse than useless, but forum members were of great help and went above and beyond to help. PMDG support was much more receptive, but were unable to diagnose the problem, probably not their fault. Lastly Microsoft support, what can I say? They did however offer to fix the problem for $99.00 Thanks in advance and maybe this will help someone else. Mike
  11. After a hardware update, I had problems with my FSX, Captain Sim aircraft would not work or reinstall, well after weeks of work, and a fresh FSX install, they're fixed. My Level D 767 works fine as well. Now my PMDG MD11 and 747 won't work right, nothing seems to respond to mouse clicks on the panels or pedestals. Also the PMDG line on the add on tab on the FSX menu bar is gone. I've reinstalled twice with no luck. I have the boxed versions distributed by aerosoft and a downloaded LCF upgrade for the 747. Thank, Mike

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.