Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender:

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Todd's Achievements


Member (2/6)



  1. Hello, I just tried LOWI in the latest MSFS update and the bump was there for the first time for me as well. It was most apparent when landing on runway 8 in the Cirrus; sort of like a hidden hole/drop in the surface during the rollout. Anyway, I just deleted the Asobo version as Nick suggested and all well again. I wonder is other Asobo airport scenery conflicts may show up with the latest MSFS update. I will now test my Flightbeam KDEN to test this out; they had been coexisting well thus far. Todd P.S. Just tested Flightbeam KDEN and it appears unaffected by the new update.
  2. A KBUR update just became available on Orbx Central. Used Orbx Central to update and then restarted MSFS to test in FlybyWire A320neoN and was very pleased to find internal cockpit/panel view FPS stable at (35-39 fps) in in my rig on tailored MSFS settings that are mainly Ultra and High at 1440x2560. External views even better running at 45-60 fps. No stutters, but GPU memory about 7230 MB and CPU memory over 2000 MB in cockpit/panel view. Hand fly of pattern circuit takeoff and return landing at KBUR were no problem. A big improvement, thanks Orbx team and developer. Regards, Todd
  3. Just a short observation, but the recent MSFS release has surprisingly improved overall performance and smoothness in my representative 10700K + 2080 Super rig. The metrics seen using GPU-Z shown a very significant drop in GPU average TDP and Temp and accompanied by the elimination of frequent GPU power limit throttling that produced stutters in taxing scenery/aircraft situations. KBUR is now smooth and I have been able to takeoff and tight-circle to land back at KBUR in the A320 without stutters while maintaining ~30 FPS with vsysnc off and just relying on the nvidia gysnc feature to dynamically manageireduce the frame rate as needed. Anyway, KBUR is still a bit slower than comparable sceneries but the very low FPS and stutters are now gone for on my rig. Nick, I know this observation probably does help much, but it suggests that a major part of the performance problems rest with the constantly evolving/fixing-up of MSFS. Patience indicated for sure. Todd
  4. For RichUK, I also noted that the 456.38 driver installation took some unwanted liberties with my MSFS settings AND also modified my CPU OC settings. The regular driver install is fine, but when combined with the optional Nvidia Experience and then ticking off the beta test extensions for "optimizing" the balance between the game settings and the CPU OC bad/undersirable things began to happen. I used Nvidia Experience one final time to undo/revert the MSFS settings that Nvidia Experience modified and then uninstalled it. Note that I had to fully back-out the Nvidia Experience carefully in order to expunge some remnants hiding around in the Win 10 system area. I think thin biggest improvement in in FPS and overall stutter-free smoothness was the 456.38 driver's newly optimized use of Nvidia Gsynch that automatically recognizes the graphics card, OS, monitor and game/simulator as supporting Gsynch. During driver installation it will prompt you setup/select available Gsynch options. I use an EVGA 2080 Super and an LG GL850 27" IPS at 2560 x 1440 and turn off VSYNCH in MSFS. This way the driver on sends the frames at the rate and time the GPU can handle. And so I get crazy high refresh rates on the static startup screens (700-900 FPS) and those then are synchronized down-to 33-51 FPS (very smooth and no stutters) for most planes and complex airports along with real weather and clouds. Clear skies at altitude in tube-liners gets up 60 FPS or so. I am getting very close to being fully satisfied the smoothness and visual in MSFS. Now if we can just get all of the other problems worked out.... no doubt it will be long journey, but worth it. Todd
  5. Good news; the new 456.38 Nvidia drivers did the trick for me; FPS went from just 10 at KBUR back up to my normal 33-46 FPS at similar airports like KSBA.
  6. Thanks, Nick My MSFS installation went fine, although taking longer than I anticipated. I will now go ahead and install Orbx Central on the new rig as you recommend, and presume that I will be able to purchase MSFS versions of select Orbx products that I already own in the FSX version while making use of the reduced pricing being offered at the Orbx Store. Observation; MSFS visuals and rendering are amazing, however the procedural simulation fidelity and functionality have a long way way to go to match what FSX has attained over many years and with the many add-ons and extensions from third-party vendors. I hope the MSFS opens their new platform to this so as to transform a gaming heavy initial product into a great flight simulator with top-notch complex aircraft and more detailed/accurate airports and scenery. Years, and years of opportunities ahead for developers like Orbx and PMDG. Regards, Todd
  7. Hi Nick and Everyone, I have just finished setting up my new PC rig that is equipped and sized properly for MSFS, and it is a blank canvas software-wise. I am just now preparing to download and install MSFS 2020 from the MS Store and then install and setup Orbx Central so as to manage the ongoing installation and maintenance of Orbx Managed Scenery and Add-Ons; just as I have become accustomed to over many years of FSX + Orbx. Many thanks to the Orbx Team for helping squeeze so much enjoyment out my orphaned FSX/Accel software. Now, what is Orbx recommended sequence to setup Orbx Central on the my new rig after MSFS has been installed and initialized? Recognize that I may still use my old PC/FSX occasionally, and that it is running Orbx Central 4.1.22 and currently managing dozens of Orbx/Holgermesh/Oz global/LC/regional/airports + expansion utilities from //42. My new rig will ONLY be used for MSFS + Orbx hopefully years of future scenery add-ons. I am hoping that the installation of Orbx Central (supporting MSFS) on the new rig will not somehow conflict/interfere with my old rig via the common shared User Orbx account underlying both usage domains (i.e FSX and MSFS on separate, but co-existing rigs). I recognize that Orbx thankfully thinks ahead and probably anticipated the type of transition that I now have underway, but I would dearly like to see/find/use a recommended sequence/approach/plan with the Orbx imprimatur so as to avoid any unpleasant surprises. Thanks for listening, and Happy flights to all i7-10700K 5.1 \ EVGA RTX 2080 Super KO GAMING \ Seagate Firecuda 520 M.2 PCI-E 4.0 NVME 1TB C Drive \ Seagate Barracuda 1TB HDD\ 32GB ADATA XPG SPECTRIX DDR4 4000MHZ \ Windows 10 Home\ LG GL850-B 27" 2.5K IPS monitor
  8. Just an update to anyone following this thread. Ed Correia has been working with me for several days via private email to diagnose and resolve this issue. Ed is apparently making significant progress in understanding the problem and a positive resolution may soon follow. Thanks to ORBX customer support process and to Ed Correia in particular. Todd
  9. Ed, Just emailed you the requested file, but it appears empty (null). Standing by. Todd
  10. Hi Ed, et al It has been a long time since I have had an issue with FTX/Orbx product installation and operation but I am now stumped and need some help. My FSX system has been up and stable for at least 5 years and just now experiencing problems with Installers terminating prematurely without actually updating and files. I am using FTX Central 2 and it has been working very well to manage all my updates and configuration settings. Just a few days ago FTX Central updated itself (successfully) and then on the following day indicated the availability of openLC NA/AK/Canada and the August 15 dated Orbx Library update. The library update was run from FTX Central and was successful. Then I went to the FSS and purchased the openLC NA from my account, again no problems. I downloaded the openLC using GetRight (no problem), unzipped using WinZip to an Orbx installation folder on my C: drive (same drive as my C:\FSX) without problem. I then ran the executable to commence installation. Unwrapper starts normally, select online validation, enter purchase credentials (no problem), unwrapper begins and takes about 3 minutes to unwrap everything... 460 GB remaining on drive. Get normal messages about Installer ready to begin and the caution not to click finish on the wrapper, click OK and Installer window opens, read the messages to cancel other programs, press Next button and the troubles begin. I briefly see the message regarding the "latest Orbx Libraries, then the "I Accept" window, and then the check box for FSX installation just flashes momentarily and the Installer (irsetup I think) then spontaneously terminates leaving only the Wrapper window still showing the "Finish" button. I repeated several times after verifying UAC disabled, firewall and virus scanner both off, free disk space, and FTX Central happy with everything, Nothing works... just getting same result. To make it more interesting I tried to reinstall the Orbx Library again, this time not using the auto FTX Central auto install, and the Installer fails to install the files... exactly the same way the Installer failed with openLC NA. I took the liberty of running the Diagnostic Reporter troubleshooter in FTX Central, uploaded to Orbx as ot5d7f025f94e1c42b34b20b308bf982ac. I think this is something simple but I can't recall the remedy... all assistance will be greatly appreciated. Thanks, Todd
  11. Ditto the don't hold your breath comment. Lawrence Livermore National Laboratory (LLNL) has been developing deuterium/tritium pellet fusion via multiple laser beam inertial confinement for several decades in the context of original Strategic Defense Inititaive (SDI)program under President Reagan. The LLNL gizmo is massive applied physics that has been demonstrated to produce more energy than required to actually operate the gizmo. The low efficiency/energy-gain challanges still remain, along with a host of practical shielding/safety and energy capture and transfer issues. If you are interested in cutting edge fusion pursuits, albeit still a HUGE challenge, take a gander (http://lockheedmartin.com/us/products/compact-fusion.html)at the Lockheed Martin Skunk Works pursuit of a very novel approach to small scale fusion as could be applied to electric power generation and aerospace propulsion.
  12. Henrik, When I researched the decision to acquire an SSD type solution I found a number of folks on the AVSIM forum that reported good FSX outcomes with the Crucial Adrenaline. The trick to its performance advantage is the heuristic/learning algorithm in the Nvelo software that accompanies the Crucial Adrenaline. When you use the Nvelo driver the SSD is not visible to Windows (i.e. does not show on the "Computer" or "Device Manager" at all). It just displays at the BIOS level detection and firrmare configuration menu, the OS is unaware this device is installed and intercepting all HDD calls using the custom device driver that is installed prior to Windows startup. The Nvelo software handles all of the mapping tasks and synchronizes the HDD with SSD periodically during normal ops and during Windows shutdown. The net result is that the most frequenly used data are always available from the SSD cache and delivered to the Windows apps (like FSX) at an optimal speed. When I run benchmark test of the HDDs (with the SSD cache installed) the various tests always report astonishingly low latency values times along with high delivery throughput. Reads are super fast, writes are a bit slower, but still much better than either of my HDDs. So, the Crucial Adrenaline solution is not a general bootable SSD replacement gizmo, but instead a very contrived solution to automatically accelerate access to specific sets of frequently accessed data. That being said, it actually works well for my typical FSX data flows. It has breathed new life into my rig until I can get a new Haswell setup. Todd
  13. I have an first generation i7 920k system that is OC to about 4.1 GHz (water cooled + Crucial Extreme memory, stock 1.2 Gb GTX570), FSGENESIS mesh, an assortment of LC upgrades, all of the UTX packages, FSDT and FTX airports, many ORBX regions, UT2, FS Global, REX 3+OD, and, most recently, REX 4 Texture Direct. My HDDs are 2 x 1TB/7200 RPM Seagates (monthly cloning to backup everything)... kinda of slow through my SATA 2. Limiting performance for initial FSX load and dynamic texture loading while flying. My rig has been near optimally tweaked and balanced over 10+ years of continuous additions, deletions and mods.... probably par for the course amongst this crowd. Anyway, I have managed to keep the FPS (smooth, without stutters or blurries ) at 15-30 FPS with the scenery and autogen sliders 1 step from max and 100m of max clouds. However, after twiddling to find an optimal FTF and TBM I was left with periods of slow texture loading and progressive MIPMAP sharpening... this was annoying, but I just did not have enough "power" in my rig to overcome this texture loading limitation. Each new hires scenery, aircraft, and environmental texture add-on was very tight fit to accomodate onto a nearly maxed-out hardware platform. And so I became aware of how SSDs could help overcome some of my texture loading limitations. About a year agao I got a small Crucial Adrenaline 59.5 Gb caching SSD that uses Nvelo software to manage the HDD-SSD mapping and caching, it was relatively inexpensive and would allow me to keep all of my software installations totaly as is. As it turns out this SSD/cache very significantly improved my FSX experience. The FSX load time is now about 30 seconds compared with several minutes with the HDD. Also, the in-flight texture loading bottleneck is totally gone now. The texture loading is now only limted by the 1.2 Gb capacity of my GTX570, not by the disk access and transfer speed bottleneck. So, my experience with a "light sized" SSD cache has been very positive. The Nvelo software has caught and corrected the occosional SSD to HDD mis-synchronization that can occur with an improper Windows shutdown or the fortunately rare freeze/BSOD. It also very nice not having to do periodic HDD defragmentation, as this were time very consuming and sometimes introduced some problematic artifacts. I do use O & O V16 to manage/check the HDDs, but with the defrag features turned-off. Win 7 64 Premium automatically takes care of the SSD trim function.
  14. I had 531GB available on a 1TB. The errors I encountered were during the installation phase and were identified as decompression errors.
  15. Got some help from a non-Orbx forum and got a partial fix. The problem was traced down to a missing or corrupted file during the installation phase of AUSP4. These were the unspecified decompression type errors that the installer can report when installing a region into FSX. The option is given to abort, retry or skip upon encountering these errors. I did uninstall and fresh reinstall of AUSP4 amd encountered no problems with the FSS download, zip extraction (CRC and integrity checks passed), the FSS online registration, and the FSS unwrapping operation. The installer hit a few decompression errors, I chose the skip option. The installation finished normally and the wrapper eas exited. Problem is, was that YBCS would still not load and caused the now too familiar FSX APPCRASH. I then disabled FTXAU18_CUSTOM in the FSX scenery library and lo and behold YBCS and the surrounding AU GREEN scenery and shores loaded and ran just fine. I don't know what I am in missing with FTXAU18_CUSTOM disabled but at least I can fly in the region again. Still I wish there were a way to get an uncorrupted/complete installation. Seems like when the files get bigger than 2GB more folks encounter problems with zip extraction and decompression errors.
  • Create New...