Jump to content

Bob Scott

Root Admin
  • Content Count

  • Donations

  • Joined

  • Last visited

Everything posted by Bob Scott

  1. Generally speaking, you're way ahead to rebuild Rome from the ground up when moving P3D to a new build. As mentioned above, you'll need to deactivate and/or uninstall any add-ons that require it to preserve licensing, and make sure to do that before uninstalling P3D itself, as some of the add-ons are deactivated from within P3D (e.g. PMDG acft, FSDreamteam sceneries and utilities). I have found that cloning my P3D drive prior to starting the uninstall process allows me to install add-ons on the new build using the installer (which activates licensing on the new computer), and then I have the option of copying the old configuration over the fresh install with all my customizations intact (and there are literally thousands of those on my machine). MSFS is a bit simpler--at least with the Steam version. Backup your entire MSFS drive (or folders), and turn off and delete your rolling cache. When you install MSFS in Steam on the new box, it'll install the Steam front end and then start MSFS and ask you for the install directory. Once it starts to do the big download from the Azure servers, escape out, quit the sim, and then copy over your old MSFS directory into that location. Ideally, you want to set the MSFS base folder path to be the same as in the old installation so that the paths stored in the cloud still work the same. When you restart MSFS, it'll find and recognize the packages directory and won't re-download all 100+ GB again. As for MSFS add-ons, I'd imagine they'll need to be reinstalled using the installer. Might take some research ahead of time to see if any require deactivation before taking down the old machine.
  2. Sensitivity is not an issue here--calibration is. Have you checked that your rudder is calibrated and centered?
  3. And even mo' faster better is a PCIe 5.0 M.2 NVME. 😉
  4. 🤬 Moderators manage and maintain order in the forums. Don't know where you got the idea that it's a moderator's job to answer everyone's questions...in fact *nobody* has a duty or responsibility to answer questions. There just aren't a lot of people doing GMAX development (or any other kind of development) for the 17-year-old FSX platform these days. I'd interpret the lack of response as an indicator that few to no users that might be able to help are perusing the FSX scenery design subforum because development for a generations-old legacy platform has long since fallen out of their range of interests.
  5. I've found that often you can bump up the DIMM voltage by one or two hundredths of a volt to get it running stable at the memory's advertised XMP settings--I've had quite a few DIMMs that wouldn't run stable even right out of the box at their rated speed/timing/voltages, most likely due to differences between the BIOS setting and the actual voltage applied by the mobo (they're not generally tightly calibrated, where the factory testing equipment is).
  6. The CPU will be downclocked from the max o/c freq based on a number of factors--temps, number of loaded cores, and power. Depending on your motherboard/BIOS options, you can usually override them, but you'll need to keep the heat under control. You can approach the heat issue by disabling HT (not really needed with 16 hardware cores at work), shutting down unneeded blocks of E-cores, manual voltage tweaking, and of course use of a very good CPU cooling solution. That said, I'd not drive myself too crazy trying to squeeze out an extra 3.7% of CPU clock speed, especially if you're not running exceptionally fast RAM.
  7. I'd start by running a memory test, e.g. MemTest 86+ to see if you've got some RAM going south on you. Also, run dism and sfc to check for corrupted WIndows system files.
  8. Some addons don't play well with FSUIPC's calibration features. Try assigning the hardware axes to the throttles in FSUIPC as "normal" axes rather than sending them direct to calibration.
  9. That usually means the sim found the scenery's xml file in the Prepar3D Add-on Files folder but there is no corresponding entry in either of the two add-ons.cfg files. The entry is written by the sim (not the installer) when the sim closes--if P3D is not completing an orderly program shutdown the file may not be written out with the new entry. I have had problems for years with P3D doing a silent crash at shutdown when the shutdown is done at an Orbx add-on airport. You can check to see if that's happening by looking in the Windows event log for red trouble triangles flagging abnormal terminations of P3D. A normal termination won't cause entries in the events log. If you're shutting down at KEGE or another Orbx add-on field, try opening the sim at a default field somewhere, activate the Orbx scenery, then shut P3D down. You should also have your default flight set up with a default aircraft on a default airfield rather than starting with add-ons so that the default environment variables are all properly initialized during startup. You don't have to start the flight there--P3D loads the default flight before it shows the scenario editor where you can select your startup particulars (location, time, acft etc).
  10. I've only ever run MSFS on my backup machine with the 10900K, but I have a portable rig I take when travelling in our motor home that runs a 9900K @ 5.0 GHz cooled by a Noctua NH-D15 (the full 2-fan version). The NH-D15 struggles a bit with heavy loads on the 9900K--it's keeping up, but barely, with temps hitting the mid-70s running P3D. I generally prefer water cooling, but I went with the NH-D15 on that machine because I didn't relish the idea of water connections getting jostled around for hours at a time in a moving vehicle. I also see much heavier multi-core CPU usage on the 10900K in MSFS (running WIndows 10) than you're describing--enough so that I really do think air cooling is a pretty iffy proposition at best on a massively multi-core processor like the 13900K.
  11. As a minimum, a good quality AIO liquid cooler like the Corsair H110i/150i or NZXT Kraken X63/73 or equivalent. 2x140mm or 3x120mm radiators.
  12. I believe they're stored in the cloud. I use FSUIPC for all of my control assignments, which keeps them in a local file under my control, safe from unruly updates, and transportable.
  13. I doubt it. The 13900K has a lot more silicon producing heat--8 performance and 16 efficiency cores versus the 9900K's 8, and at much higher clock speeds. With a very aggressive water cooling system (two 360mm deep radiators in series external to the CPU case, 0.5" ID tubing, Laing D5 pump) temps spike rapidly into throttling territory under an all-core load. It might be possible with some of the E-cores shut down and careful load management, but I wouldn't even think to try it.
  14. First, to be clear, you can't overclock a 13900. You need a K-suffix CPU for that. I found that overclocking my 13900KS (a 13900K that's top-binned from the factory) was mostly a drill involving maintaining turbo speeds on the cores that matter while keeping the cores from throttling back due to thermal limits. The 13900K/KF/KS has a lot of flexibility w/r/t performance--the ability to independently clock cores and the ability to shut down unneeded CPU cores to minimize unnecessary heat production. The 13900K has to move a lot of heat through a fairly small IHS footprint, so a very good quality cooling solution is a real necessity. I don't use my primary sim rig for MSFS...I run that on my secondary system (10900K @ 5.3GHz/RTX3090), but keeping P3D's main thread running at 6.0 GHz was worth the effort. The 13900K is a beast of a CPU...it'll do a good job stock out of the box (when paired with a high-quality cooling solution), and if you're so-inclined there's some more performance still there available for the taking with some time and effort. If you're not technically competent to manage an overclock, I'd stick with stock speeds. I think the auto-overclocks generally crank up voltages way too high for daily use.
  15. Keep in mind that the navdata embedded in the RXP Garmin is years out of date--BLAKO was the missed approach hold point at the time that older navdata was current. It changed to CIDUG in Dec 2022.
  16. It should work--it uses FSUIPC to interface with the sim, which makes it relatively platform agnostic. As long as the objects being placed are FSX-compatible, it should be able to do its thing. Back in those days, I ended up moving to Flight1's Instant Scenery, as it had a more intuitive graphical interface.
  17. Yes, it's a system problem.
  18. It depends on how much space you have from the top of the video card to the side of the case. The bend on my cable requires ~2.5 inches of additional headroom above the top of the GPU. If you don't have that headroom, then yes, the 90 deg cable is absolutely worth having. Trying to force a too-tight bend on that thick cable bundle coming off the power connector is asking for big trouble.
  19. Does anyone know how this will impact a Return to Misty Moorings install? It's been a while, but I seem to recall there was some tweaking of PFJ needed to make the two dovetail together.
  20. Let's not hijack this into another sim-vs-sim debate. The point I'm making is that there's a pretty long list of significant shortcomings in the MSFS weather environment that need attention. I'd like to see the guys that proved themselves by solving many of these issues elsewhere get a crack at these problems rather than being summarily excluded. Hope springs eternal from some of the suggestive commentary coming from Asobo that it might be a possibility, where it was a resounding "no" before.
  21. Yep, that's right, I said it backwards I meant to say set Num Lock when using the views...and that only applies if you have the LOAD CUSTOM CAMERA x commands bound to the numpad keys.
  22. Make sure Num Lock is on when saving the custom camera views. Check your control assignments to verify that the keys mapped to the "LOAD CUSTOM CAMERA 0-9" commands are the ones you're using to select the camera view.
  23. Nearly three years in, you still can't set something as basic as visibility in MSFS. Dense clouds look like Krakatoa just blew its top again. Overcast layers look like cotton balls crammed together in a mat. No cirrus. "Real time" weather that shows storms and low clouds 6+ hours after the storms have passed and a quick look out the window says "CAVOK". Inability to do meaningful flight planning due to inaccessability of enroute weather data. Weather that's grossly out of phase w/r/t day/night when flying at distant locations due to time differences. No historical weather capability. "Good enough"??! Oh no no no... Lots of room for improvement here.
  24. ASXP12 brings Active Sky to the X-Plane 12 platform using its new weather and sdk capabilities, enabling highly accurate weather conditions, comprehensive weather reporting, visual weather mapping and planning, specialized XP12 air effects, voice weather delivery, weather briefings, and much, much more! ASXP12 utilizes the latest version of the HiFi DataNet cloud-based weather network, featuring surface observation data, global forecast modeling, air data analysis and curated weather synthesis for the most realistic and best experience possible. Live, custom, and advanced historical weather with historical playback is available. This initial version of ASXP12 is tuned for the latest XP12 releases (official and beta), and will undergo additional improvements as XP12 and its weather system + SDK/API continues to evolve, with additional methods of depiction and several additional new features planned as additional capabilities are realized. Details at http://hifisimtech.com/asxp12
  • Create New...