Jump to content

rlashier

Members
  • Content Count

    202
  • Donations

    $25.00 
  • Joined

  • Last visited

Community Reputation

95 Good

About rlashier

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Baltimore, MD

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

2,321 profile views
  1. I have had this ECAM alert about the sidestick fault in the Fenix repeatedly of late. Initially, I thought the problem was related to using a decades old MS Sidewinder flight stick, assuming that the old stick was no longer providing accurate control inputs. So, I just purchased a Thrustmaster Airbus flight stick to replace the old Sidewinder and guess what? The same sidestick fault message appeared with the new stick. Putting the stick thru the motions on the MCDU calibration page did not help for long, nor did trying adjustments to the null zones. But the Fenix knowledge base article about this fault included a note that some have found the problem can occur on multiple devices if a button on a device was used to control the autopilot. Sure enough, after deleting button assignments on my flight stick and throttle quadrant that disengaged the AP, the error no longer occurred. And when I reassigned a controller button to the AP, the side stick fault message promptly returned. I have no idea why a simple button assignment that I use to disengage the AP when a few hundred feet above the runway would cause this fault message, but it’s clearly the culprit. Wish there was a fix for this, as it is awkward to have to disengage the AP during landing with a mouse click on the flight deck’s AP button! Anyone else experiencing this bit of nonsense? Rich
  2. Thanks for updating your settings guidance. I will definitely give this close scrutiny as you have proven to be a consistently sound and thorough expert on MSFS settings and system enhancements. Well done Captain! Rich
  3. Two years ago, I went with a nice quality LG 60 Hz 4K monitor, and I have never regretted it. Like Ray, I previously would lock this display at 30 fps (half refresh rate setting) with good results. But I since have upgraded my GPU to RTX 4080 Super, and running this with a Ryzen 5800 X3D, my system is running MSFS butter smooth with complex aircraft and scenery locked at 80 fps (FG on) or 40 native. Not too shabby!
  4. Waltpop, Tips and Tricks and VR selections are separate subforums. If you continue below those two listed subforums you will see the list of current topics in the general MSFS 2020 Forum. That is where you should post your questions. Rich
  5. Having mixed results with Block 2 now. Worked out the issue with AP disconnects. But now I have a new problem where I cannot get the a320 to descend in managed mode when at (or before) TOD. Aircraft climbs to cruise altitude with AP engaged just fine. While at cruise altitude, I enter the lower, desired altitude for the IAF with altitude knob, which I press in (arrow up) with the mouse when about 10 nm prior to TOD. The managed mode dot “o” does not appear and the aircraft continues to cruise. I have a support ticket with Fenix for this, but I wonder if any other Avsim pilots have had this experience using the Block 2 a320. Never had this problem with earlier versions. Rich
  6. I’ve seen much advice in this topic and others to use RTSS to cap frame rates in MSFS, as this presumably affords greater consistency and smoothness. I’ve used the NVCP max frame rate setting, as well as the half refresh rate Vsync setting in MSFS, with the goal of attaining a stutter free 30 fps on my 4K LG 60 Hz monitor. Today, I tried the recommended RTSS approach. Set Vsync off in MSFS, Vsync on in NVCP, set the frame limit at 30 in RTSS, and then enabled the frame limiter in the setup menu and set it to front edge sync. Oddly, the on screen display in RTSS shows frames locked at 15, not 30. When I change the frame limiter setting to async, I get 30 fps, but with front edge sync, only 15. Can someone suggest what is going on here? I am running MSFS on a system with an RTX 3080 GPU, and a Ryzen 5700 CPU. Thanks!
  7. Agree wholeheartedly. The IAE engine modeling, the new liveries (e.g., JetBlue), and the EFB enhancements are so welcome an addition, and for free no less. Especially enjoy that the EFB more tightly integrates the flight plan, fuel and payload, and takeoff performance data entry into the MCDU. Also, it’s a plus having the Simbrief flight briefing and the Navigraph charts available in the EFB. Loading Navigraph charts via the MSFS menu always introduces an FPS hit, but not so via the Fenix EFB. Hats off to Fenix for a great update. When they fix a few annoyances - AP disconnects and such - it will be nearly perfect. Rich
  8. Quick install question. GitHub shows 3 assets for this app, the install or exe file and two source code items, one a zip file. Must I download all 3 to use this app, or just the install file? And do I unzip the source code file before running the install? Thanks, Rich
  9. Have never seen this in my experience with this airport. It is excellent all around. Hesitate no more! Rich
  10. I also use the CH throttle quadrant with the PMDG 737. Using FSUIPC, I have no issues with engaging the reversers. Rich.
  11. My own peeve - those who use the term “irregardless” when regardless is more than sufficient. Rich
  12. That should be the last word on this matter. Rich
  13. Whether you start with Fenix or PMDG is your choice, but it would be a shame not to have both. They fly similar routes with similar results, but their methods are very different and make for interesting experiences. Rich
  14. And a fine vintage it is! Thanks so much for this. It’s like a homecoming. Rich
  15. Also, you must turn off all assists, particularly auto rudder, when taxiing the FBW A320. Otherwise, it is uncontrollable. Rich
×
×
  • Create New...