NOTE: If you own other GoFlight hardware and have already installed the same or more recent version of GoFlight software than that was included with your MCP-Pro, you do not need to install the software again. Get on line and go to www.goflightinc.com. On the GoFlight home page click Support. Click on “GF Config x.xx” to download the latest module drivers and configuration software. MYGOFLIGHT is driven to make flying and travel safer and simpler. We solve the problems that enhance airplanes and avionics technology as well as the journey itself.
I’ve posted a number of times on the transition to 64-bit, we have release notes and a FAQ, as well as a number of technotes for plugin developers, but in this post I want to cover how I see the community moving over to 64-bit.
Goflight For Macbook Air
![Goflight Goflight](https://www.x-aviation.com/catalog/images/M2016.jpg)
64-bit is a fundamentally confusing issue – it’s one of those things that should be totally transparent to computer users, but due to the nature of code and plugins, 64-bit is not transparent. Japji sahib path lyrics in punjabi download. So more explanation will hopefully at least not confuse the issue even more. Maybe.
Is a Transition to 64-bit Even Necessary? Does it Have to be Now?
The short answer is yes. 32-bit applications simply cannot take advantage of more than 4 GB of physical memory (among other limitations). Every year CPUs get faster, people get more cores, GPUs get faster, GPUs ship with more VRAM, and every now and then we even get a faster PCIe bus. During this time hard drive, SSD and RAM prices continue to fall. You can bring your computer up to 8 GB of memory (Crucial memory – good stuff!) for $34. But what’s the point if the app you are feeding is 32-bit?
In other words, the march of hardware is unrelenting, and if we want X-Plane to be able to use the full power of our computers, we have to go to 64-bit.
Goflight For Mac
How soon do we need to go to 64-bit? Menace ii society mp3 download. Mac users who like add-ons have been crammed up against that 32-bit ceiling for a while now, while Win 7/64 users mostly still have some headroom. But the real question is: could we finish out a major version run in 32-bit? Could we wait years to go 64-bit? I think the answer is no. Even if we didn’t care about the RAM limit on Mac and Linux* 64-bit will become a Windows issue too; it’s only a matter of time, and I suspect not that much time.
The Phases of Adoption
This is how I see the migration from 32-bits to a 32/64-bit world going:
- Beta. That’s where we are now. In this phase, 64-bit technology is unproven even in the sim itself. Plugin developers are hopefully trying the 64-bit betas and looking for major critical bugs, but 64-bit isn’t useful for actually flying. (Well, the sim is beta, and I never recommend flying on the beta.) I don’t expect anyone to ship a 64-bit add-on during this phase.
- Crossover. Once X-Plane 10.20 goes final and we have a stable 64-bit build that third party developers can actually test against, we’ll have a phase where some add-ons come out in 32/64-bit formats and others are not yet ported. The length of this phase will be the difference between the fast and slow add-on developers; different plugins will take different time to port, have different levels of complexity, etc. During this phase, users will have to pick 32-bit for compatibility or 64-bit for memory use.
- Acceptance. Eventually we’ll arrive at a point where so many add-ons have been made 64-bit compatible that the norm and expectation is that all add-ons are 64-bit, and the community will mostly have to abandon add-ons that are not migrated forward.
Note that “acceptance” is not only after 10.20 goes final but there is an entire phase between 10.20 going final and being able to “just run all add-ons in 64 bit”. This is because it is going to take time for people to move their plugins forward.
32-bit Still Works!
Goflight For Mac Pro
I cannot emphasize this enough: there is a 32-bit build of X-Plane in the 10.20 betas, and it should just work! The switch from 32 to 64 bits is not a binary transition where we pull the rug out from under everyone in one swoosh and everyone scrambles. It is the beginning of a migration that can happen over time, while 32 and 64-bit apps areboth available to everyone.
* I have heard people tell us that we don’t care about the Mac just when it is surging, that we should drop everything but Windows, and that Linux is, in fact, the wave of the future. We’re going to hedge our bets and keep supporting all three. Having done the work to be cross-platform it doesn’t make sense to drop multi-OS support.
Goflight For Mac Pro
About Ben Supnik
Ben is a software engineer who works on X-Plane; he spends most of his days drinking coffee and swearing at the computer -- sometimes at the same time.Got it working, mostly stable now! Not sure if people are still having problems, but thought I'd share this since some might have given up. My hardware, gf166 (2), rp46 and 48. I need to say this hardware has always been finicky, and they will be times when a display freezes, happened a few times even in win7.
The backstory, I just upgraded my gaming machine from win 7 to 10. I was about to give up, even considered buying a Saitek radio module, but I prefer Goflights' amber colored displays, easier on the eyes.
Some things need consideration that no one might have mentioned before:
1) if possible, use a USB 1 extension hub plugged into USB 2 port. (Make sure you NEVER plug this hub into a USB 3 port, it damaged one of my hubs, (it was working perfectly in win 7) and didn't even know it caused me plenty of confusion! These older hubs are pretty rare, if not even available. And they can be damaged when plugged into usb3. I checked the hubs' power supply with volt meter, still good, but the USB hub itself cannot be powered anymore, and without power, the connection does not always work consistently with different low-powered USB devices. This problem took me down the wrong track, and I am certain others have suffered from it.
2) after all GF modules are confirmed up and running, (after lots of trial and error), make sure to turn off power to USB hub after computer is shutdown. Better yet, leave all extension hubs on power strip for easy access.
3) when you are ready to turn on your machine, turn on your USB hubs first, then power up on your machine.
4) do not run GFconfig while FSX is running. (It only needs GFdev.exe, which loads automatically with FSX). GFconfig should run outside of FSX for configuration only. (Related: GFdev.exe cannot be running if assigning keystrokes to rp48).
5) if you exit FSX, leave your machine turned on, and decide to restart FSX, then you will need to kill and restart GFdev.exe while in-game. (You will find no buttons are responsive). Solution is to switch FSX to windowed mode, then task manager to kill GFdev.exe. Helpful to have a shortcut to GFDev.exe for restarts. Then task back into FSX, the buttons should be responsive.
The best option is to turn off your machine and your USB ports until next gaming session. There is still a chance one of the high powered LED displays (gf46/166) will be lost if you have too many sessions with FSX without a re-boot. In that case, only a re-boot works.
I have repeated this these many times, and believe my goflight hardware setup in win 10 is as stable as it can be. Hope his helps someone