Jump to content

AAU 3 now available


Recommended Posts

48 minutes ago, flyingscampi said:

Navigraph is one of the most popular add-ons for MSFS and critical for many of the leading aircraft and other utilities.

You can blame third party developers if you want but expect to alienate a significate chunk of your user base if you release compulsory updates that break their sim.

Out of the lets say 10 million MSFS users, how many of them actually have a Navigraph subscription? It maybe most popular to the hardest of the core, but I bet most MSFS users never even heard of it… 😛

Im sure all this drama will settle in a few days and navigraph will fix it. I have a subscription myself, but I can live without it until fixed… 

Edited by Kaboki
  • Like 2
Link to comment
Share on other sites

Just now, Abriael said:

This kind of completely unsubstantiated sweeping statement on developers when something minor (because make no mistake, this is a minor issue) goes wrong based on entirely wrong assumptions is quite typical of the least logical subset of gamers. 

They don't test with Navigraph or other add-ons because that's how software testing is done. With the clean software. That's industry standard. Using add-ons complicates matters beyond the manageable and anyone who has ever done QA work will happily tell you that.

I know how software is tested, that's a great point if an update breaks a community mod or something similar, but MS has its own 3rd party store.  They want the $$ from after market sales but yet they are going to throw their hands up when non-public betas break things? Cant have it both ways without some blame.

Nick Running

Link to comment
Share on other sites

Just now, Kaboki said:

Out of the lets say 10 million MSFS users, how many of them actually have a Navigraph subscription? It maybe most popular to the hardest of the core, but I bet most MSFS users never even heard of it…

Im sure all this drama will settle in a few days and navigraph will fix it. I have a subscription myself, but I can live without it until fixed… 

common sense says youd test your product with the 5 most popular addons in the community, namely fsiupc, gsx and navigraph.  Its not rocket science. It really isnt.

  • Like 1
 
 
 
 
14ppkc-6.png
  913456
Link to comment
Share on other sites

The recommendation from the Navigraph forum seems to be to make sure you uninstall the navdata before installing AAU3 (if you haven't already).  Not sure if this works myself, but worth trying.  One person says they were able to put it back in after with no issue (again no widespread confirmation of this).  

(Pointing fingers and arguing blame is pointless.  It will get fixed by whoever needs to fix it, but in the meantime, it is more productive to talk about workarounds for people to get up and running).  

  • Like 1

-------------------------

Craig from KBUF

Link to comment
Share on other sites

6 minutes ago, nrunning24 said:

I know how software is tested, that's a great point if an update breaks a community mod or something similar, but MS has its own 3rd party store.  They want the $$ from after market sales but yet they are going to throw their hands up when non-public betas break things? Cant have it both ways without some blame.

No. You obviously do not know how software is tested. Otherwise, you would not suggest testing with add-ons. 

Having a marketplace doesn't add any sort of burden to the developer to test these add-ons. The burden remains on the developer of every single add-on. 

"blame" is what gamers do when they can't contain their pettiness and anger because they don't know how the cake is made. 

Edited by Abriael
  • Like 1

spacer.png

Editor-in-Chief at SimulationDaily.com

spacer.png

Link to comment
Share on other sites

Airbus A310-300

Fixed – Interior model appears to be missing when viewed by other users

Fixed – Auto throttle does not animate the throttle but does work

Fixed – ATC not honoring custom registration / tail number.

Fixed – FMS PRED Page Bearing seems to be in “true” instead of magnetic.

Inclusion of Pan Am livery.

Airbus A320neo V2

Fixed – GWCG value being in ZFWCG on MCDU.

Fixed – EFB Dashboard Aircraft Type incorrect. (Change to Engine type).

Fixed – Init request fixed – (will pickup all functions from EFB ID entry now)

Fixed – Engines are too loud when starting or shutting down [ADO].

Fixed – Reworked and modified engine mixing to cover overall sounds feedback covering items such as flaps sound, TO howl, AC in cockpit looping and too quiet from outside even compared to inside.

Fixed – Engines at TOGA more quiet than CLB.

Fixed – Engines are too loud when starting or shutting down.

Improvement – Beacon light and strobe lights overhauled and reviewed following feedback.

Fixed – Weird effect on brakes.

Fixed – PFD Selected ALT window black background.

Added – TERR radar now available.

Improvement – Adjusted pitch in cruise to better reflect lower attitudes expected.

Improvement – Adjusted engine thrust while at FLX power to give shorter takeoff roll while using higher flex temperatures.

Improvement – Flight director logic adjusted, while on an RNAV/ ILS approach, you should notice the flight directors moving over a larger range and giving more precise guidance.

Improvement – Increased gain control within rotation law to give higher commanded rates at lower stick deflections.

Improvement – Significant improvements to stability with WASM crashes and CTD.

Fixed – Rudder Trim Knob / Reset Button not animated when key command sent.

Fixed – [AFS] REC MAX not rounded to 500.

Fixed – Init Page B Errors with BLOCK fuel/ Planning vs Prediction Modes [ADO].

Fixed – Autobrake disarm on landing too sensitive.

Fixed – T/D Top of Descent ETA’s not calculated correctly on Flight Plan Page [ADO].

Fixed – Remove Align on ref.

Fixed – FPLN A Page TIME vs UTC.

Fixed – PROG RPT page – Winds shown as MAG instead of TRU bearing.

Fixed – TCAS – Alerts and Filtering Improvements.

Fixed – TCAS Target shown as single digit instead of double.

Fixed – When starting the engines as soon as you move the ENG MASTER to on the FADEC grey boxes should show to indicate ENG START in progress.

Fixed – Selecting descent angle in Fpa mode bug.

Fixed – MCDU sometimes getting stuck on PLEASE WAIT.

Fixed – 240NM mark not showing in the 320NM range option.

Fixed – MCDU WPT ETAs not matching.

Fixed – AP/AT Disconnect switches not animated via control input.

Fixed – Changing COM Frequencies via Radio Panel (Simconnect Events).

Fixed – ND/PFD Track discrepancy.

Fixed – ECAMs not auto switching back to CRUISE page when deselected.

Fixed – Missing Approach procedures.

Fixed – TCAS traffic logic improved.

Fixed – No upper or lower limits on the speed tape during DES mode.

Fixed – Wrong CG value being inputted.

Fixed – Slat/flap “boxes” look dim when compared to other green writing in the EWD.

Fixed – Wheel when above 100c should show green arc above hottest break at the moment shows no green arc.

Fixed – FPLN should update ND and sequence in the background regardless of the MCDU page selected. It currently only updates ND if FPLN is active page in MCDU.

Fixed – BRK FAN doesn’t seem to be effective.

Fixed – Spacing of the DME below waypoint name is too tight should be like ref image.

Fixed – When you turn off one of the gens the loading is not transferred to the other one. Example GEN 1 selected off AC BUS 1 and 2 now run from GEN 2 but the % loading is the same.

Fixed – When you are below MDA for example LFMN RNAV 04L with MDA of 2000ft the AP should disconnect MDA -50ft. which is currently working correctly. But if want to put the AP back in you can so for example if you go around and press the AP in then it will work. So it’s just the one disconnect not forcing the AP to not work.

Fixed – APU burn rate is high 80 kgs in 20 mins when should be around 100kgs per hour.

Fixed – 30’ GPWS callout later than others.

Fixed – FO side push button for TERR RADAR not currently mapped.

Fixed – INIT B page – Cannot edit FINAL/TIME fields.

Fixed – FL400 shown in flight plan when no CRZ level and no SC set not present on old build.

Fixed – When AC BUS 1 INOP SYS have clipping line and an FWS 1+2 shows and will not clear on the MEMO side where it shows NOT AVAIL.

Fixed – Baro limited to 8000’.

Fixed – APU/Eng shutdown sequencing.

Fixed – [XBOX] SPD managed mode not engaging after switching to manual SPD mode.

Fixed – Excessive fuel flow.

Fixed – MACH VNAV tables giving high rate of des feedback.

Fixed – Route flickering and not rendering every few seconds.

Fixed – Pro ATC X – Radios Not Working.

Fixed – Negative VOR CRS on Radio NAV.

Fixed – VNAV on LEMD NONT3C arr RNP Z 32R – computed path not following alt constraints.

Fixed – Cannot reset FCU SPD/HDG back to managed mode when previewing by pushing in respective knob.

Fixed – Selected speed/managed DES engines remain THR IDLE.

Fixed – FPLN B / VERT REV B / INIT B – Cruise winds.

Fixed – Stuck TCAS returns/targets.

Fixed – APU will not shut down after engine start randomly.

Fixed – Rudder Trim Knob / Reset Button animations.

Fixed – TD on FL220 CST.

Fixed – EFOB more than FOB – FPLN and PROG page.

Fixed – OH – C&D startup logic.

Fixed – Fuel broken after inserting hold.

Fixed – Can’t edit Engine out ACC height.

Fixed – Lower ECAM not staying on ENGINE page after start.

Fixed – INIT B box prompts in kgs regardless of weight value set in EFB.

Fixed – Wheel when above 100c should show green arc above hottest brake.

Fixed – FCU Mach Preview showing XX.XX value during CLB/DES, ok in CRZ.

Fixed – Extra time incorrect on perf page.

Fixed – Fuel prediction calculations.

Fixed – Erroneous Arrival time vs T/D estimate.

Fixed – Aircraft pitching up in OP DES while in selected HDG ahead of VPATH.

Fixed – FMGS exception when selecting APP RNAV15.

Fixed – WASM Crash reports from Discord.

Fixed – Stairs / Boarding Ramp option missing from Aircraft.cfg.

Fixed – Speed brake animation greater than commanded from flight deck (e.g. ½ showing full deflection.

Fixed – Excessive pitch nose up on rotation.

Fixed – NAV mode won’t engage after switching to HDG once.

Fixed – [Instruments][NAV] A320neo (v2) fails to display accurate bearing pointer direction when manually tuning NDB frequency.

Fixed – Black Dot/artefact appearing on the Windshield when nose lights turned on.

Fixed – No Smoking TT value reversed.

Fixed – Stairs can’t be called to the aircraft.

Fixed – [KO-KR] Missing LOC for “Open Descent” in the checklist.

Fixed – [FI-FI] Missing LOC for “REFERENCE RWY IN BRG/DIST FIELD” in the checklist.

Fixed – External Power Button Not Making Sounds.

Fixed – [ENG] IDLE engine N1 not correct this is why at higher FLs it gets off path so much idle shown in sim around 55% but should be 41% N1 might have been a bad table export.

Fixed – Jetway is misaligned.

Fixed – Dome Lights do not emit any light.

Fixed – Regression] Nav/logo lights do not turn off when using the “Toggle Lights” keybind.

Fixed – No Highlighting to Push Tray Table In.

Fixed – Buttons tooltips does not change when they are used.

Fixed – FD pitching too low during takeoff.

Fixed – After landing, pitch trim goes to 4 units up and bounces around the upper limit.

Fixed – [ENG] EGT rises while full paused.

Fixed – FUEL PRED- MIN DEST FOB does not update when custom ALTN fuel removed.

Fixed – [ECAM] When booting up FWS 1+2 stays for about 3 minutes.

Fixed – [ECAM] Overflow arrow showing all the time on STS page even when not data.

Fixed – [FCTL] Speed brakes not working correctly with AP on and AP off but I think I worked out why.

Fixed – [AFS] Manually entered speed constraints show up as XXX.XX on PFD.

Fixed – Radio altimeter would show numbers like “-1” even “-2” when you are rotating.

Fixed – [Radials] When going direct to a waypoint via the MCDU, it would point to a complete random non-existent waypoint instead of the selected one.

Fixed – [Radial in] When you execute the RADIAL in it takes about 3 seconds for NAV to ARM after inserting

Fixed – [Radial In] When you have put a Radial in current not showing any offset on the ND it should show L or R of the current track at the moment it shows nothing.

Fixed – [Radial in] When you have a Radial in ND shows 2671 miles at the TO point.

Fixed – [Radial in] After doing the radial in and flying the approach in heading then following the ILS the waypoints should sequence still otherwise when you go around the waypoints are behind you are will not go into NAV.

Fixed – Pink cockpit textures with enhanced build.

Fixed – EFOB for T/C T/D + DECEL is wrong.

Fixed – Pulling speed in APPR mode behaviour.

Fixed – [ECAM] When getting low FUEL warning in DES the FUEL SD page showed which is correct but after the ECAM was gone the ECAM SD page didn’t self-clear it stayed.

Fixed – Aircraft is in TOGA Configuration While Spawning onto an Arrival.

Fixed – [VNAV] Not respecting VNAV speed constraints on some STARS.

Fixed – [VNAV] For the targeted VS for DES path it seems to not match the tables exported for A320neo.

Fixed – Crew Supply Oxygen is off on runway spawn.

Pilatus PC-6 Porter

Fixed missing tooltips on fuel filter clogged and starter lights.

Fixed AI checklist auto-complete issues with fuel system valve and parking brake.

Imported new localizations.

Fixed tooltip value for the left column of lights (main panel).

Fixed dimmers for annunciator lights not working.

Added ForceCamera entries to checklists.

Added AI sound XML for PC-6 Classic Wheels

Reverted to original Asobo project structure

Fixed a faulty version number in a packagedefinition file

Replaced Asobo GNS530/430 with Working Title GNS530/430 in Classic variants

Fixed lights circuit toggling GNS 530/430.

Fixed (and extended) engine auto start.

Fixed (and extended) engine auto stop.

Added fuel system control valve closed to shutdown checklists.

Fixed panel lights switch not reacting to L key.

Fixed instrument lights brightness getting overwritten by G1000.

Fixed KR87 ADF light potentiometer index.

Added Radio Magnetic Indicator (RMI) to Gauge variants.

Reduced the pointer animation speed on RMI.

Fixed keyboard input not available in GNS530/430 units.

Fixed flickering glass around rear doors.

Fixed LOD issues on Gauge Livery 01, Gauge Livery 02 and G950 Wheels Livery.

Fixed cockpit camera being able to clip through fuselage.

Backup attitude Indicator does not work and part of it is upside down

  • Like 8

5800X3D. 32 GB RAM. 1TB SATA SSD. 3TB HDD. RTX 3070 Ti.

Link to comment
Share on other sites

2 minutes ago, Abriael said:

No. You obviously do not know how software is tested. Otherwise, you would not suggest testing with add-ons. 

Having a marketplace doesn't add any sort of burden to the developer to test these add-ons. The burden remains on the developer of every single add-on. 

"blame" is what gamers do when they can't contain their pettiness and anger because they don't know how the cake is made. 

You might know software testing, but dont understand business decisions surrounding it.  If I buy MSFS from Microsoft and then buy an addon from Microsoft Marketplace and it craps out my purchase after an update, its defiantly a Microsoft problem, your the only vender I've worked with!!!!  As a Software Engineer you might not agree, but when you wade into the $$$$ of aftermarket purchases these are things you need to deal with and if you are only testing in a sandbox environment when your whole business is tied into making $ of third party purchases through your store, then your leadership needs to be fired. 

Nick Running

Link to comment
Share on other sites

  • Moderator
7 minutes ago, Abriael said:

No. You obviously do not know how software is tested. 

Having a marketplace doesn't add any sort of burden to the developer to test these add-ons. The burden remains on the developer of every single add-on. 

"blame" is what gamers do when they can't contain their pettiness and anger because they don't know how the cake is made. 

this is only so true.  We have heard many 3rd party developers complain about limited communications from asobo.  Many have said they are flat out ignored.  If communication was better, everyone would benefit.  

  • Like 4
  • Upvote 2

5800X3D, Gigabyte X570S MB, 4090FE, 64GB DDR4 3600 CL16, EVO 970 M.2's, Alienware 3821DW  and 2  22" monitors,  Corsair RM1000x PSU,  360MM MSI MEG, MFG Crosswind, T16000M Stick, Boeing TCA Yoke/Throttle, Skalarki MCDU and FCU, Logitech Radio Panel/Switch Panel, Spad.Next

Link to comment
Share on other sites

6 minutes ago, fluffyflops said:

common sense says youd test your product with the 5 most popular addons in the community, namely fsiupc, gsx and navigraph.  Its not rocket science. It really isnt.

My point is 10 million users, maybe  0,1 % of them use navigraph, how the hell does that make navigraph the most popular? Its probably not even among the 1000 most popular addon among all those users. Unless you consider 0,1 % of users to be the only communety…. Maybe we like to think “we” are the communety, but after MSFS 2020 came about, the communety is way bigger than the few elitists here at avsim…

  • Like 2
Link to comment
Share on other sites

20 minutes ago, Georgleboui said:

It’s so weird for them not to do a beta first. Asobo/MS have been through this before, learned their lesson with the early SUs and I’d say have been on a good streak of stable patches.

The MSFS team probably thought the scope of changes was way more narrow than a typical Sim Update release, so they decided to take the risk that this release was unlikely to have a major bug.  This is comparable to the World Updates, where the scope of changes are also usually narrow (maybe no code changes at all in the World Update), and World Updates don't have open betas either, so the MSFS team felt they could get away with a release with out a proper public beta test.

In any case, I guess their gamble didn't work out this time. I'm also curious if they had a closed beta, how many people participated in the closed beta, and whether any of the participants in the closed beta had navigraph setup in a way similar to the people who are CTDing today.

i5-12400, RTX 3060 Ti, 32 GB RAM

Link to comment
Share on other sites

2 minutes ago, micstatic said:

this is only so true.  We have heard many 3rd party developers complain about limited communications from asobo.  Many have said they are flat out ignored.  If communication was better, everyone would benefit.  

Many 3rd party developers are glorified gamers. And yes. It certainly is their interest to assign blame to someone who isn't themselves.

Communicating with literally thousands of developers each of which thinks they're entitled to a direct red phone to Jorg is a tad on the challenging side (and very weird to expect). 

3 minutes ago, nrunning24 said:

You might know software testing, but dont understand business decisions surrounding it.  If I buy MSFS from Microsoft and then buy an addon from Microsoft Marketplace and it craps out my purchase after an update, its defiantly a Microsoft problem, your the only vender I've worked with!!!!  As a Software Engineer you might not agree, but when you wade into the $$$$ of aftermarket purchases these are things you need to deal with and if you are only testing in a sandbox environment when your whole business is tied into making $ of third party purchases through your store, then your leadership needs to be fired. 

Oh yeah the "X needs to be fired" delirium. Your arguments have completely devolved into the most toxic areas of the "gamer" discourse. 

It's not a matter of agreeing or disagreeing. It's not how it works. You likely shouldn't mention "business decisions" when you don't know a single thing about business. 

Edited by Abriael
  • Like 3
  • Upvote 2

spacer.png

Editor-in-Chief at SimulationDaily.com

spacer.png

Link to comment
Share on other sites

1 minute ago, micstatic said:

this is only so true.  We have heard many 3rd party developers complain about limited communications from asobo.  Many have said they are flat out ignored.  If communication was better, everyone would benefit.  

Asobo would be so much more in the clear if they just didnt sell 3rd party software and take a commission off it.  But once you do that your in the muck now and updates matter, compatibility matters.  Sorry its just a fact.

  • Like 1
  • Upvote 1

Nick Running

Link to comment
Share on other sites

  • Moderator
2 minutes ago, nrunning24 said:

Asobo would be so much more in the clear if they just didnt sell 3rd party software and take a commission off it.  But once you do that your in the muck now and updates matter, compatibility matters.  Sorry its just a fact.

don't have to apologize to me when it appears you are agreeing with my point...

5800X3D, Gigabyte X570S MB, 4090FE, 64GB DDR4 3600 CL16, EVO 970 M.2's, Alienware 3821DW  and 2  22" monitors,  Corsair RM1000x PSU,  360MM MSI MEG, MFG Crosswind, T16000M Stick, Boeing TCA Yoke/Throttle, Skalarki MCDU and FCU, Logitech Radio Panel/Switch Panel, Spad.Next

Link to comment
Share on other sites

  • Moderator
3 minutes ago, Abriael said:

Many 3rd party developers are glorified gamers. And yes. It certainly is their interest to assign blame to someone who isn't themselves.

Communicating with literally thousands of developers each of which thinks they're entitled to a direct red phone to Jorg is a tad on the challenging side. 

you are on avsim.  A much higher percentage of people on this site do not use any other "games".  All we know is our simulator now won't work after asobo pushed out an unannounced update.  

  • Like 5
  • Upvote 1

5800X3D, Gigabyte X570S MB, 4090FE, 64GB DDR4 3600 CL16, EVO 970 M.2's, Alienware 3821DW  and 2  22" monitors,  Corsair RM1000x PSU,  360MM MSI MEG, MFG Crosswind, T16000M Stick, Boeing TCA Yoke/Throttle, Skalarki MCDU and FCU, Logitech Radio Panel/Switch Panel, Spad.Next

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...