But a huge amount of work went into performance enhancements and content improvements. Naturally, I just wrote above about the work that went into patching and setup, because that’s what I worked on. The entire ACES Studio can be justifiably proud of the tremendous effort that went into FSX SP1 and SDK SP1A. By dropping the auto-generation, I had more work to keep the setup current but we’ll be in a great position for future patches. The self-extractor is the WiX v3 setup.exe chainer. So I created a new SDK product using WiX v3. Both issues combined, a patch wasn’t something I could pull off in a reasonable timeframe. Another complication was the release of SDK SP1 (without the “A” suffix) it also shipped as a product but with custom code that manually updated and deleted files in the RTM SDK. I investigated delivering a patch for the SDK too, but ran into the same issues with changing IDs as with the game. Unlike the game itself, the SDK update is delivered as a new product, not a patch. It’s available only in English and only for users of the Deluxe editions, so we needed to deliver only one package. FSX SDK SP1A is delivered in one self-extractor.The story of building custom upgrade packages deserves its own series of posts. It also meant that I couldn’t follow the typical approach of rebuilding the upgrade MSI packages – the GUIDs and IDs kept changing. That’s why I needed to build 13 distinct patches (two each for English, French, German, Italian, Polish, and Spanish and one for Japanese). However, it wasn’t otherwise a “typical” patch build the RTM setup auto-generated most of its 42,000 files so file IDs and component GUIDs and IDs weren’t stable. I built the patch-creation packages (.pcp files) in WiX v3 and built the patches using MsiMsp and PatchWiz 3.1. Of the approximately 42,000 files(!) in RTM, only a couple of hundred were patched or added in SP1.Because of how the FSX RTM setup was built, it wasn’t feasible to ship one patch for all the editions and languages. FSX SP1 is delivered in multiple per-language self-extractors, each of which contains two patches, one for each of the two editions Flight Simulator X is available in (Standard and Deluxe). FUNCTIONS AND SUBJECTIVE TESTS QPS Requirements Simulator level Entry No.I’ll be discussing both projects in more detail in future posts, but for now, here’s a quick summary: Also available is Flight Simulator X Software Development Kit SP1A. Windows 7 is a newer, better OS and thus should not be affected by this at all.The project that has kept me busy since moving to the ACES Studio at the beginning of the year is finally out the door! Flight Simulator X Service Pack 1 is now available from. When they announced that you had to have Vista for it, people FREAKED OUT! So they made it backwards compatible for XP. Install SP1 by itself, from the link Pat posted above.įYI, FSX was designed, specifically, to run on Vista 64-Bit, with DirectX 10. Once that is complete, reinstall SP1, and then Acceleration. Now locate Microsoft Flight Simulator X, BUT this time left click it ONE time and in the top click "Repair". ![]() If it is not listed there, click "View installed updates" in the top left, and locate it there. ![]() ![]() Once again locate, Microsoft Flight Simulator X: SP1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |