Jump to content

tnbriggs

Registered Users
  • Posts

    12
  • Joined

tnbriggs's Achievements

Advanced  Simmer

Advanced Simmer (2/7)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later

Recent Badges

10

Reputation

  1. Here are a couple. There are many more. 1. As I read it the brake toggle command on the full keyboard list is Num Decimal, which is the equivalent of Numpad Period or "numpad ." 2. The parking brake toggle is Ctrl + Num. No numerical keypad on a 85 key keyboard so can't execute those. I did a spreadsheet which lists them, attached. And instead of redoing all of them for the 85 key keyboard I thought if there were a list for the short keyboard commands I'd have a look at those first and see if they would work. It looks like no one has such a list so I may add another column to the spreadsheet with them. FS2020keybdcommands.zip
  2. I can't find a list of the FS2020 short keyboard key bindings anywhere on the web. Plenty of lists for the default keyboard (101 keys or more, with a numpad and navpad) but nothing for the short keyboard (85 keys) my laptop has. Anyone seen such a list or will I have to create it myself? And is there anyway to export it from FS2020, perhaps using the developer menu? Thanks for any help.
  3. Hello all, After a bit of forum searching with no results I'm posting this question. Odd display issue here. The ATI 5570 graphics card (1 gb vram) in my computer failed and until I either do an oven-based reflow on it or buy a replacement I installed the machine's original Geforce 7300 GT (256 mb vram) back into the computer. But now when I try to run FSX, I get no gauges on any aircraft and the gauge locations on the panels (2d & 3d) are transparent. See screenshots attached. I also reset all the display settings to their minimums, no change. The 7300 GT worked ok in FSX years ago in both XP & Win7 and seems to work ok in most other applications (except that on Flightradar24 I can no longer see anything in 3d mode). Any ideas what the problem is with the gauges now? Machine is dual boot MacPro 1,1 (bootcamp) running Windows 10 Pro 32 bit. 15 GB memory. Win10 is running DirectX 12. Thanks for any help.
  4. I was able to download and install FS2020 through the Xbox Game Pass. Installed the update, too. Install was to a external drive connected through IEEE1394 (Firewire 800). Program will not load fully. Loads about 50%, to the shot of the Cessna 172 heading into the mountains, and then crashes to desktop. Deleted and reinstalled, and also did a reset which also required another download and reinstall. Same result, CTD at 50% load. Not sure if the CTD is because of system not meeting minimum requirements or not. I have noticed others seem to have the the 50% load and CTD issues and imagine some of them are on compliant systems. Will likely delete once the $1 Xbox game pass time limit expires.
  5. Thanks for the response. My question was to try to determine if it would run at all or if I would get an incompatible system prompt and it would fail to run, even poorly. Good suggestion about the download and trial. I've got an old (2012) MacBook Pro w/ 10g ram that also boots to Win10 & on which I run FSX occasionally & I may give that a try. More curious than committed right now and would like to avoid wasting $70 if possible. Thanks again.
  6. Searched the forum and couldn't find anything on this so I'm asking. I am aware of what MS has published as the hardware minimums (https://flightsimulator.zendesk.com/hc/en-us/articles/360013463459-Minimum-Recommended-and-Ideal-PC-Specifications-for-Microsoft-Flight-Simulator). The question is: Will FS2020 fail to run without those hardware minimums or will it just run poorly? For instance; 1 With a 1 GB vram graphics card will it fail to run? 2 With anything less than an Intel or AMD CPUs & GPUs listed will it fail to run? Thanks.
  7. Running FSX on D drive, as admin. Thanks.
  8. Thanks for the response. I'd already been through all the Google searches and have been changing settings during flights for quite a while; it's just sort of a nuisance. Thought maybe someone on the forum had a clever solution to it, but apparently not. Thanks again.
  9. Thanks for the response. Yes Win10 from Win7, sort of surprised it worked at all. Mechanical hard drives are fully defragged. I'd considered SSD but not sure it's worth spending any money on them. Something perversely ironic about spending a couple hundred $ on problems that were created by a free(?) upgrade(?). Plus the computer is a 2006 Mac Pro that I can boot into 2 versions of OSX, Win 10 & XP (so I can run some old 16 bit apps). Guess I could always put in a spare HD I've got and install Win7 & FSX on it alone; but seems like a lot of work. Thanks again.
  10. I just upgraded (?) to Windows 10 32 bit from Windows 7 32 bit. FSX Gold worked acceptably in Win7, but in Win10 there is a lot more disk access delay, in particular when ATC (FSX native) communications occur, & I can't fly for very long before I get OOM errors. Didn't happen in Win 7. I tried the 3 gb switch (fcdedit /set IncreaseUserVA 30272) but it didn't solve anything and made FSX startup & loading of add-ins impossible). FSX is on my D drive in its own directory, not on C. I increased the virtual memory (swapfiles) on both disks, too. Still no joy. I know I can reduce all the display settings to less than I have now, which are moderately intense, but I'd rather not if something else works. While the computer it's on is 64 bit, the bootup (EFI) is 32 bit, so I can't run 64bit Win10 on it. Any ideas of what might help? Thanks.
  11. Jim Thanks for the response. I'll give it a try.
  12. June 23, 2017 The latest I can find on FlightSim.com are these threads, which are over a year old. I last played MS Flight late in 2016 but now when I try it appears all the servers and logins are dead. I still know all my login information (UserID, password, etc.) but none of it seems to work. I had both Alaska and Hawaii and enjoyed both. I'm guessing all of Microsoft Flight's access is now dead. Is this right? Seems a shame since I know the software is still on my computer and probably playable. Thanks.
×
×
  • Create New...