Things that are still broken
-
Pretty disappointed in the patch. They didn't fix the rudder trim knob being backwards like they said, and broke the compass. I thought they said they fixed NAV2 not working for the AP, still doesn't work (at least when using the GPS100)
Also:
They said they fixed the GPS100 being stuck in test mode. Still happens, but less often.
They fixed the OAT gauge, but using either that temp or the temp given by the GPS100 and adjusting the TAS knob does not give you an accurate TAS at all.Also: If you start with the GPS100, the NAV1 needle is stuck, you have to turn on the 430 or 530 and turn that to VLOC before you can switch back to the GPS100 to have a working NAV1
Also:
Com1 and Com2 are both labeled "Com1"
Also:
You can only transmit on com2 on vatsim
Also:
NAV1/2 ident modes either don't work or are so quiet as to be inaudible.
something else I noticed which I'm not sure is a bug exactly but is really weird. The engine start sequence seems to have 0 sound or notice of the engine actually firing, it just makes a starting noise until you push up the mixture. It's also extremely quiet if you leave the idle too low (and it probably shouldn't even be able to start cold with the throttle totally closed, but it does). I thought the engine sound was broken until I realized I just had the throttle closed and the engine was running smoothly at an extremely low RPM which made almost no sound effect.
-
@rinkerbuck said in Things that are still broken:
They fixed the OAT gauge, but using either that temp or the temp given by the GPS100 and adjusting the TAS knob does not give you an accurate TAS at all.
The OAT gauge is fine now, but the TAS scale is entirely off. Plus the IAS gauge shows a value ~4-5kts too high.
Also check our more detailed thread about the TAS inconsistency and performance discrepancy:
https://community.justflight.com/topic/1774/tas-gs-weirdness@rinkerbuck said in Things that are still broken:
Com1 and Com2 are both labeled "Com1"
Look closer, there is a "2" written on COM2 manually. So it was a repurposed radio on that specific Arrow that they used to model this addon. It's actually a nice detail and fully intentional on the "used" looking panel.
Make sure you open a ticket to support with all your findings since posting them in the forum is not the right way to report. See sticky thread here in the forum.
-
- Compass already fixed
- Rudder trim is now fixed
- I wasn't aware of the NAV 2 AP issue and that wasn't listed on the update change log. I've just confirmed that it works OK here but changes have been made to the AP logic for other reasons so that might have fixed this too.
- The GPS 100 self-test issue is a difficult one to reproduce but we've made some changes to the logic which will hopefully address any last remnants of that issue
- We are looking at the TAS scale issue on the ASI
- COM 1/2 label addressed above
- NAV ident - see this thread: https://community.justflight.com/topic/1748/morse-code-identification-signal/11
- Engine start sounds - not experienced that one but have asked our sound artist to investigate
Hopefully you were at least slightly pleased by all the other fixes and improvements?
Martyn
-
@rinkerbuck said in Things that are still broken:
Pretty disappointed in the patch. They didn't fix the rudder trim knob being backwards like they said, and broke the compass. I thought they said they fixed NAV2 not working for the AP, still doesn't work (at least when using the GPS100)
Also:
They said they fixed the GPS100 being stuck in test mode. Still happens, but less often.
They fixed the OAT gauge, but using either that temp or the temp given by the GPS100 and adjusting the TAS knob does not give you an accurate TAS at all.Also: If you start with the GPS100, the NAV1 needle is stuck, you have to turn on the 430 or 530 and turn that to VLOC before you can switch back to the GPS100 to have a working NAV1
Also:
Com1 and Com2 are both labeled "Com1"
Also:
You can only transmit on com2 on vatsim
Also:
NAV1/2 ident modes either don't work or are so quiet as to be inaudible.
something else I noticed which I'm not sure is a bug exactly but is really weird. The engine start sequence seems to have 0 sound or notice of the engine actually firing, it just makes a starting noise until you push up the mixture. It's also extremely quiet if you leave the idle too low (and it probably shouldn't even be able to start cold with the throttle totally closed, but it does). I thought the engine sound was broken until I realized I just had the throttle closed and the engine was running smoothly at an extremely low RPM which made almost no sound effect.
I think you need a reality check, the speed and scope of the first patch is nothing less than stellar performance by any development metric. Have some gratitude, just because there are still some things floating around doesn't mean the first patch was a bust...anything but.
-
For me, it went from being truly great to just another unreliable MSFS plane after the update. GNS 530 screen now won't come on (not battery related before you ask), autopilot doing weird random things (tonight it decided to start flying in circles halfway through the flight for no apparent reason), co-pilot there despite not being enabled.
However I realise not everyone is having these issues and I appreciate the devs getting updates out quickly. I just hope the next update puts it back in a flyable state for me, because at the moment it isn't. -
@rinkerbuck said in Things that are still broken:
something else I noticed which I'm not sure is a bug exactly but is really weird. The engine start sequence seems to have 0 sound or notice of the engine actually firing, it just makes a starting noise until you push up the mixture. It's also extremely quiet if you leave the idle too low (and it probably shouldn't even be able to start cold with the throttle totally closed, but it does). I thought the engine sound was broken until I realized I just had the throttle closed and the engine was running smoothly at an extremely low RPM which made almost no sound effect.
I think the problem lies with the simulation not coded to know that fuel has already been introduced into the engine by priming via the fuel pump when the mixture was added at the start of the process perhaps? I’m sure il be corrected if that’s not the case. It’s like the engine is either digitally OFF or ON when you apply the mixture. I was also expecting the engine to at least start spluttering into life (before adding the mixture)with the small amount of fuel that’s been introduced ( like the A2A piper planes. Even engine flooding was simulated) But maybe this requires a more complexed flight model? Maybe it’s a limitation with the MSFS’s SDK? if just flight could add this that would add a lot of immersion for me.
-
@set3times said in Things that are still broken:
@solzhi Regarding the GNS 530, if you have the WT mod, make sure to turn the volume/power knob, the "C" labelled knob between the COMM and NAV transfer buttons.
You probably mean the (amazing) pimarc mod, since WT has no mod for the 530?
@solzhi Make sure battery is ON, INST panel breaker is closed, and turn the volume knob up. Also make sure you "restart flight" as a last resort and then recheck those items, there is a core sim bug posted by Asobo that can cause blank glass displays.
-
@sluflyer06 Yes that's exactly the mod I mean, sorry I was sleepy :D
