Jump to content

Bnash00

Members
  • Content Count

    155
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

85 Good

About Bnash00

  • Rank
    Member
  • Birthday 07/31/1983

Profile Information

  • Gender
    Male
  • Location
    Reno NV
  • Interests
    Airplanes, MSFSX, Prepar3d, Airplanes, Programming, Airplanes

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes

Recent Profile Visitors

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

  1. I’ve read through this thread for a while now and thought I would give this app a try. I’ve done several flights now with it. The results are truly amazing. The software is absolutely brilliant. @Reset XPDR thank you for this gift of improved performance and visuals.
  2. I began on DX11 with a 3080ti. DX12 did not work well for me as 12GB of VRAM just isn’t enough at 4K resolution. Then I tried the FG mod. My mind was blown. I was so impressed with the gain in performance I purchased a 4090 and now use the native FG option. With 24GB of VRAM everything runs so much better. There is no going back.
  3. I’m just curious… When you see the ground patches are you using the Fenix?
  4. I have almost the exact same system as you except I have a 4090. With DX12 and frame generation turned on I can easily get 115fps in flight. Sitting on the ground at iniBuilds KLAX for example. 90FPS. Are you using DX12 with frame generation?
  5. I started seeing ground patches once I switched to DX12 after upgrading from a 3080ti to a 4090 and it seems to occur more when using the Fenix. I have found using the alternate renderer, prefer CPU rendering, and display sync off in the Fenix app gives me the best performance and I haven’t seen any patches since making this adjustment. I’ve done several flights now.
  6. While not for MSFS, the FSLabs Airbus comes to mind for P3D. They were trying to catch pirates. https://www.pcmag.com/news/flight-sim-labs-fights-piracy-by-installing-malware
  7. After re-installing windows and re-installing the simulator, all configured control profiles will still be there as they are stored in the "cloud". Don't forget about your camera definition files for all favorite aircraft. Otherwise you will have to manually re-setup all your camera views per aircraft. In my setup (Steam version), the path to the camera definition files are located here: "C:\users\YourProfileName\AppData\Roaming\Microsoft Flight Simulator\SimObjects\Airplanes" Each airplane will have it's own folder. You want to backup camera.cfg.
  8. Pause event are now well sent through SimConnect. 🥳
  9. Without question… Steam. Use the MS Store version if you like Microsoft burying program files in convoluted folders with special permissions on your file system.
  10. I want to warn you about a known issue. Its kind of rare and very specific. Airports that have recent runway identifier changes break aircraft like the HJet and iniBuilds A310. For example, at KRNO (Reno NV) the runway identifiers were recently changed from 16L/R to 17L/R. Navigraph is aware of this change and their data reflects this change. Microsoft/Asobo have not updated the runway identifiers in the scenery. When you load up KRNO the runways are still listed as 16L/R. Because the Navigraph data doesn't match the sim scenery data you don't see any SIDs or STARS when entering your flight plan. This issue does not effect aircraft that have their own sperate nav data like the PMDG 737 or Fenix A320. Only aircraft that lean on the sim base data. Basically anything Working Title, the HJet, and the iniBuilds A310, and this only happens at airports that are not 100% perfectly up to date as far as the sim navdata is concerned. KRNO is an example. I'm sure there are more. I would expect the more time that passes more and more airports will break. Here is a link to the Navigraph forum where I asked about this problem: https://forum.navigraph.com/t/krno-sid-star-problem/10020 To get around this problem you just have to uninstall the navigraph simulation base data and use the default nav data from Microsoft\Asobo. Aircraft that use their own Navigraph nav data that you install into the aircraft are not affected. I bring this up because you mentioned the HJet and just wanted you to be aware of this issue. Other than this issue, a Navigraph subscription is totally worth every penny.
  11. I just installed KB5020044 and the micro-stuttering is gone! I'm brand new to VR. HP had the Reverb G2 on sale, so I though I would give it a try. After applying this update I am very pleased with the result. Thank you again for the help and pointing me in the right direction.
  12. In my opinion (and this is just my opinion, nobody has to agree) the mouse should not time out if the user is actively using the mouse. The mouse never times out if you constantly keep moving it around the screen. Why does the mouse time out if you stop moving the mouse around the screen, pause over a line select key on the CDU and repeatedly click a line select key? Every left click event should reset the mouse auto hide countdown timer. The mouse should absolutely 100% auto hide and become inactive and disappear after x amount of seconds when not in use. I guess I'm arguing moving the mouse around the screen counts as the mouse is in use, so should left clicking the mouse but not moving it. Overall, this is a very minor issue. I'm sure Asobo and Microsoft have way bigger fish to fry.
  13. Microsoft said this mouse behavior is on purpose and by design so, just keep moving your mouse every 5 seconds when stepping through your flight plan everyone 👍👍 https://forums.flightsimulator.com/t/mouse-cursor-times-out-while-you-are-actively-left-clicking/560984/1
  14. I think I am experiencing exactly this problem. I have a pretty strong system but experience micro-stuttering. I am running Windows 11. I will give this a try. Thank you for posting.
×
×
  • Create New...