TexasGary

If you previously calibrated your Bravo in Windows Game Controllers, try going back in there and hit "Properties" then "Settings" then "Reset To Default."  I had the same problem you are having and this fixed it for me.

Here are my specs:

i7-6700K @ 4.00GHz
32.0 GB RAM
GTX 1080
Windows 10 Pro Version 20H2

I have about 1/2 of my settings on high and the other 1/2 on medium running at 2304 X 1296 resolution and I get a smooth, stutter free 30 fps experience in most places.

I can deal with below zero temps, snow, ice, broken pipes, no water, no electricity, and no internet.  But I am really having a hard time with not being able to use MSFS .... lol.

cw, thanks.  I had the AP off, but still had some modes active.  When I got it back to just ROLL and PITCH modes the FD did indeed turn off just as you said.

Thanks.

I want to add my thanks to the Working Title Team for their excellent work on the CJ4.  I did have question that I haven't found answered anywhere yet.  After the Fight Director is activated, how do you deactivate it?  When I click on the FD button again after its activated nothing happens.

Thanks.

Gary

Which plane?  Any mods?

I am also having a lot of problems with stuttering.  I was using simconnect for FSUIPC and GSX in P3DV4.5.  If I'm not running P3DV4.5, could simconnect still be running and affecting MSFS 2020?  If it is, can someone please let me know what I need to do to stop it? 

Thanks.

Gary Merka

Thanks Bryan.  I think my problem is the air start cart is still connected.  Will test this weekend when I get a chance.

I am trying to understand how the GPU is disconnected.  When I initially got FS2Crew for the NGXu, I called for the ground crew to disconnect the GPU right after the FO connects the buses to the APU.  But it never got disconnected.  Then I read in the manual that the GPU can’t be disconnected until the chocks are released when the countdown timer gets to 0 minutes.  But when I get to the 0 minute point, the chocks don’t disconnect.  I know I can use the FMC to manually disconnect the GPU, but can somebody please explain specifically the steps to verbally get the ground crew to do it?

Thanks.

Does the on-line map still work in the 737 NGXu?  I tried using this site http://fs2.fs2crew.com:8080/SimpleTracker/map.do but it doesn't seem to work anymore.  I noticed in the Config Options that it says "On-Line Map: Reserved."  Does this mean it is currently not functional but will be in the future?  The Manual just says "ON-LINE MAP: Displays your position on the FS2Crew on-line map."

I also noticed after a few flights that the FO now sets the ENGINE START SWITCHES to AUTO.  In the 737 NGX version he set them to CONT.  The manual also says on page 15 that he should be setting them to CONT.

That fixed it.  Bryan, thanks for the VERY quick reply. Awesome support.

Hey Bryan, I am having the same problem.  I submitted a ticket (Ticket ID: S32-PZR-W8EW). Hoping for a quick easy fix.

Thanks.

I am also having this issue.  Glad its on the list to get addressed in a future update.  Bryan, as a temporary workaround can u let us know how to rename the sound file?

Thanks.

Gary

Somewhere in Texas

Thanks guys.  I unchecked both of these and that seems to have fixed it.  These are really cool effects, but not worth interfering with the HUD.

I am using W10 with P3D V3.4, the PMDG 738NGX, AS 2016, TrackIR, and the latest version of FSUIPC. I recently noticed a weird issue with the HUD. In clear skies the HUD works fine. But while going thru clouds, the HUD display kind of "fades" in and out (i.e. goes from normal brightness to very dim and back). Its like the HUD is actually outside the aircraft passing thru the clouds. I tried switching from auto to manual mode, turning the brightness up all the way, and zooming my POV in and out, but that didn't help. Any ideas on this one?

Thanks.

I am using W10 with P3D V3.4, the PMDG 738NGX, AS 2016, TrackIR, and the latest version of FSUIPC.  I recently noticed a weird issue with the HUD.  In clear skies the HUD works fine.  But while going thru clouds, the HUD display kind of "fades" in and out (i.e. goes from normal brightness to very dim and back).  Its like the HUD is actually outside the aircraft passing thru the clouds.  I tried switching from auto to manual mode, turning the brightness up all the way, and zooming my POV in and out, but that didn't help.  Any ideas on this one? 

Thanks.

Just made a couple of flights with version 3.0.  Nice work Bryan, thanks for putting out this excellent update.  The only minor issue I have with it is for some reason I can no longer open the secondary panel by mapping a button to waterrudder up/down.  Is there still a way to map a button to open/close the secondary panel, or did this get taken out with version 3.0?

Thanks.

Gary Merka

Techguy, thanks man ........

Hey boddman, I am also looking at the UN40KU6300FXZA.  Will it display 4k at 30 Hz?  Does it support Chroma 4:4:4?

Thanks.

Ah-Ha.  Enter it on the Descent forecast page.  Knew I was missing something.  Thanks for the help.

Sorry, meant to say that the altimeters are set to the local setting on descent not STD.

I have another transition question.  On departure from an airport in the USA, the transition altitude is 18000.  I verify that 18000 is set in the PERF INIT page, and when passing 18000 on the ascent the PM correctly resets the altimeters to STD.  If I am arriving at an airport where the transition altitude is not 18000 (say 14000) I enter 14000 in the PERF INIT page prior to starting the descent.  But on the descent, the PM again resets the altimeters to STD at 18000, not 14000 as set in the PERF INIT page.  Is there somewhere else besides the FMC where I need to set the transition altitude?

Thanks.

That would be great. Thanks Bryan.

Thanks for the quick response Bryan.  OK, I think that was my problem.  I was not selecting the arrival runway before the PM started his flow.

Thanks.

Gary Merka  

Bryan, first of all thank you VERY much for the new reboot version of FS2crew for the NGX.  I am really enjoying it, I especially like the new voices.  I have only run into one issue so far.  I am using SOP 1, and on every flight the PM correctly sets the departure field elevation on the overhead panel prior to departure.  But he never sets the destination field elevation prior to the TOD, it always stays at the departure field elevation.  Am I supposed to set this?  The PM always set the destination field elevation prior to the TOD in the legacy version.

Thanks again for a great addition to the NGX.

Gary Merka