dectenor1

Yeah the aircraft takes off like an helicopter...

Yep, still an issue with v.1.1.4 I don't know why things are released like this that are clearly completely broken. The HUD as is is just a total gimmick.

VSD is showing terrain over 40000 ft flying across the UK, but nothing on the terrain radar.. on PNF VSD and terrain radar there is nothing at all. Bit of a mess really. Best

I have made various reports on issues relating to VNAV stuff, F-PLN page predictions and how these are displayed, managed speeds, and again how these are displayed, constraint behaviour etc., etc. Please feel free to reach out for any info that may help in this regard. VNAV related things need a LOT of work currently! Best

Just to clarify pretty much all of these bugs are still present with v1.1.2. And I think I forgot to mention the CAB V/S is constantly fluctuating between 0 and 50 FT/MIN during cruise.

Great thanks @Eddie As always, if you want/need any further info, examples to demonstrate, info from the FCOM, etc., just let me know. Best

Thanks, I deleted the WASM folders before updating as I usually do, but thanks anyway.

Yeah beyond that, was still appearing and disappearing as I reached the gate, which was well after 1 minute.

The sounds when using reversers on landing roll need some work. The mixing is pretty bad. It is like all other sounds are completely killed and you then get this muffled reversers sound. Just needs a remix really, with more ambient stuff at that point. If the team thinks the reversers completely dominate the soundscape at this point, then fine. But then the reversers need to be much louder, with the other sounds still in the background but just the reversers are so loud that you can't hear anything else. At the moment it kinda feels like 'oh we think you should only be able to hear the reversers at this moment, so let's just kill all other sounds and so you can hear the reversers, but let's not make the the reversers that loud themselves'. No, if you can only hear the reversers then they need to be louder than anything else, not just remove the other sounds. Hope that makes sense. In fact, I think this applies to all iniBuilds aircraft across the board really. It is like there is always the same volume, and other sounds are dropped out to make room for what the team think should be the dominant sound at any point, rather than increasing the sound of something that should be dominant and keeping the background sounds that should be at a consistent volume in the mix. As if there is a constant aim to keep the aircraft at the same decibel level no matter what. Almost as if the sounds have been taken from some cheap recording that has been auto equalised or something. The sounds themselves are good I think, just the mixing is really not. Sorry ended up a bit of a long post, and hope it is understood! Anyway, thanks for the continued work as always.

Another regression with v1.1.1 is the LDG INHIBIT ECAM memo that comes up whilst taxiing after landing. Seems to be related to the brakes somehow.

VNAV seriously needs a proper look at and an update dedicated to it. There are so many issues relating to how the aircraft targets constraints and speeds. How it displays these targets and predictions, how the F-PLN page target speeds, relate to the PERF pages and indications on the PFD, ND, like the level - off arrow, like magenta and orange dots around waypoints etc., etc. Level-Off Arrow in OP DES for example, it just most off the time in the completely wrong place on the ND. Makes doing continuous descents so much harder than it needs to be for example. How it calculates descents etc. Like here, as can be seen, there are no constraints before EGNUG, but the aircraft is planning to be at EGNUG, 3000ft too high. It should simply start the descent sooner to meet this constraint. There are no speed, or altitude restrictions that mean it can't do this. It should simply start the descent sooner to make this constraint.

Sadly still all an issue with 1.1.1.

Same issue here, and the fix above did not work!

You can actually click the button next to the lower screens to just display the OIS on those, and then connect the GPU.

@Eddie Following from DM, here is a bunch of stuff with v1.1.0 to get started on. Do feel free to ask here or DM, if you need any more info. Best