General Disappointment (Why?)

  • Hello to all users and developers,


    I hope this message finds you well. Please allow me to clarify that I've been a loyal customer for 9.5 years and still adore the simulator and the painstaking work the IPACS staff goes through to create realistic products. HOWEVER:


    I've noticed that the past few updates have been rushed into launches and experienced numerous bugs since. For example, the 777F, which should have had proper sound based upon what others have noted, retained its original sound and still lacks flap sounds.


    Long-running bugs, such as the inability to land the Sopwith Camel ( Truncana) and the "tapping sound" that can be heard after engine shutdown on most Boeing and Airbus aircraft still haven't been fixed.


    However, the memory-saver update completely ruined Aerofly FS for me. I've seen many users complaining about how the update affects their gameplay and realism, but their device wasn't an affected model anyway. I am one of these users as well. I have 16GB of RAM and an Apple M1 chip, yet the density of autogenerated buildings and frame rate have decreased since these updates were rolled out. I have also noticed more "black squares" appearing in the scenery, as it fails to load more often now. Additionally, it takes at least 70% longer to load now when compared with app builds before October. With these new and nonexistent RAM constraints, the PAPI lights have disappeared at most airports for me. Flyish and Small Planes have observed even more egregious issues.


    The sounds have been ruined on numerous aircraft, such as the A319 and 737s through this "reduction" in file size. Why was this necessary? Why are the passenger view camera sounds destroyed? The "improvement in memory footprint" was code for completely destroying the sound quality for these aircraft.

    The MAX 9 has also been downgraded by having the functionality of "time elapsed" and "squawk code" panels on the PFD being deactivated. Why??? Observe that the "time elapsed" panel still works in replay mode, as seen here. Why??? I had my transponder set to 1036 but nothing changed on the PFD in either mode.

    Furthermore, the sounds on many aircraft are still disappointing. The "new" CFM sounds from earlier this year are still terrible, and the 747, 777, and 787 have hugely unrealistic sounds to this day. Excluding the 777s, none of these aircraft have startup or flap noises either.


    To add on, FADECs haven't been fixed on most airliners. I'll name a few examples:

    1) A321 climb power still too high on CFM models, but it was fixed on A320 (see the 7-10% N1 decrease per detent): note that the takeoff thrust entries are still correct for TOGA and FLEX applications, but the climb is lower than the MCT detent by a tangible margin

    2) 737-900ER's N1 is STILL too low on TO-B (should be 102.1% in ideal Q1013 OAT18 conditions), cost index and derates don't work

    3) A319 IAE thrust ratings have been completely destroyed since the update.


    Some liveries still have errors after YEARS, such as the EVA, KLM, and United 787-10s, the Delta 737-900ER and 747 logos, and the absolutely deplorable Delta A320 colours. The Delta A319's registration doesn't match its registration listed on the vertical stabiliser either. N301NB and N356NB are different aircraft. At least these could have been fixed for what has traditionally been the biggest update of the year?


    It's been quite a while since most base aircraft variants were released. When will we see a 787-9, 777-200ER, and 737-800? The argument that the Boeings could be shrunk is ridiculous, since we haven't seen any of these aircraft in the sim years after the base aircraft releases. The 777F is an exception— I assume most of the fuselage needed to be remodelled to accommodate the useless cargo door and lack of windows- why do we have a freighter when we can't load it or use dynamic weights?


    I also want to speak about the glaring omission of Australian liveries. There were clear opportunities to depict:

    1) Jetstar A321SL (IAE)

    2) Qantas 747, widely requested

    3) Virgin Australia and Qantas Link A320s (on IAE)

    4) IAE Qantaslink A319

    5) Virgin Australia 777s (2x): WHY were these PUBLICLY POSTED on the liveries list then never implemented? They were good enough to be added to the sim!!!


    The CRJ900 is evidently lacking in features, such as a basic FMS or even FLEX derates! It still flies and looks like a beta build!


    There is also an appalling new glitch that occurs when more than 6 digits are entered into the INIT page of the MCDU on all Airbus aircraft. Why does this now happen. For a such a high-quality simulator, how can ridiculous bugs like this one manage to remain in the consumer release? Customers are NOT beta testers.

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.


    Here's another picture from the mysterious "INIT drone"

    I was stuck on a flight from KMSP to KLAX by clicking the INIT button and suddenly being ejected from the aircraft three weeks ago.


    This really disappoints me, as IPACS has been the epitome of quality finishing since its earliest products, such as FS1, which I bought almost a decade ago.


    I've also noticed that airports on the blog post lists have either existed for over a year, or aren't actually included in the update that they were advertised for. Why is there such a discrepancy between that heyday and this rushed nonsense? For example, Taipei has been listed for the past few posts, but isn't actually implemented. There was a list of improved airports such as EHAM and KLGA that were due, so why aren't they in this supposedly "major" update?


    These issues and more have been irking me for some time, so I am publicising my concerns with this post.


    Kind regards,


    VolerSuisse333


    Dear IPACS team, I wish you a sincere thank you for your work on KMSP and LSGG! It is incredibly impactful for me!

    Kind regards, good day, and bon vol!

    -VolerSuisse333

    Edited once, last by VolerSuisse333 (December 9, 2024 at 5:23 AM).

  • Hello to all users and developers,

    I hope this message finds you well. ...

    I have read your message as a user in peace. Unfortunately, I don't know what to do with it.:/

    I have understood,
    - that on the one hand, after various updates, some things no longer work as well as before and
    - that on the other hand, you lack content that you have often asked for.
    And this annoys you so much that you have now written this to us.

    I do not see myself in a position to offer you a concrete remedy. And as a long-time user, I assume that IPACS will implement the points you raised.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2021); Chip: Apple M1 Max; actual macOS || Thrustmaster TCA AIRBUS EDITION: 1x Sidestick, 2x Quadrant, 2x Quadrant Add-On || Pro-Flight-Trainer PUMA X

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS || nimbus steelseries

  • I got dumped on a bit for suggesting dual download streams so that higher performance devices could be allowed to perform well. I was told that optimising for older or less expensive devices could not possibly degrade the sim with higher performance devices, the sim cleverly selected and protected, a bit (ein bisschen) like don’t be silly.

    My Aerofly PC and mobile glass is 9/10 full, the fault persistence is my 1/10 empty. Our annual mobile scenery download payment is due soon and I’ll pay without hesitation. I still cannot get over how good it is in mobile.

    Edited once, last by Overloaded (December 8, 2024 at 12:12 AM).

  • Wow dude okay fair enough make your point but while the consistent bold and underlined text does work to highlight certain issues, this did seem like “yes good job i like this sim BUT cue the rest of the post feeling just a tad bit like you’re berating the devs rather than offering constructive feedback.

    On the note of that strange tapping sound before engine start/in cold and dark states, i raised it before when i found it had appeared on the A321, but if i may divide your attention to a thread which Jan has responded in, it looks like the dev team are trying to figure out the exact source of this sound and will hopefully fix it. To say it hadn’t been fixed is obvious yet to fix it, a source and replication needs to be done first in order to figure out where it comes from and what code in the sound files to edit in order to get rid of it. Maybe a tad over the top on that point.

    Some very valid points, united 78-10 livery is off and EVA one is wayy too light in colour, but maybe tone it down because this to me felt more like feedback with a slight sprinkle of overaggression within the reinforcement of certain points.

    i found my own bugs that i probably have raised before but they didnt get noticed so once again might just have to list out what ive found so it gets seen in this thread and hopefully fixed sometime next year.

  • N12003 isn’t even Evo Blue in real life, so the livery is fundamentally flawed.

    Kind regards, good day, and bon vol!

    -VolerSuisse333

  • so i found stuff like:

    - the outside camera being able to zoom through engines and wheel wells as of an update a few months ago

    - of course that united 78-10 livery being off kilter in where the registration and lettering should

    - runways in amsterdam, boston and chicago o hare not showing as blue in the navigation menu


    787 engines show as GENC not GENX in the INIT page of the FMC


    777 and 747 still show IAS on the PFD even when in MACH mode. The 787 does this right and does show selected mach speed when the speed section of the MCP is changed over to MACH (displays 0.82 instead of 264K IAS)

    And emirates/garuda indonesia 777 front nose lettering doesn’t include the ER, only shows -300 but i brought this up and i hope jan made the aircraft livery designers aware

  • N12003 isn’t even Evo Blue in real life, so the livery is fundamentally flawed.

    Regardless, EVO blue is the new livery and therefore the reg should be changed or simply have the livery fixed because chances are the real one will get updated sooner or later. I was in houston last year and saw the odd united 777 in the old grey with blue painted engine cowlings so part of me thinks the airline is slowly repainting the entire fleet.

  • i found my own bugs that i probably have raised before but they didnt get noticed so once again might just have to list out what ive found so it gets seen in this thread and hopefully fixed sometime next year.

    I assume it's been seen but ignored already. It's certain that the A319 thrust isn't getting fixed any time soon.

    Regardless, EVO blue is the new livery and therefore the reg should be changed or simply have the livery fixed because chances are the real one will get updated sooner or later. I was in houston last year and saw the odd united 777 in the old grey with blue painted engine cowlings so part of me thinks the airline is slowly repainting the entire fleet.

    Exactly, I assume Evo Blue is being rolled out across the entire fleet. The 787-8s and 737 MAX 9s are gradually being repainted from Unicon now. If IPACS ever developed a -200ER, which is highly unlikely, it would be interesting to see both Evo Blue and the Continental livery with the blue cowlings.

    Kind regards, good day, and bon vol!

    -VolerSuisse333

  • Jet-Pack (IPACS)I’ve done some more research, and on the -900ER, TO-B actually matches the GA thrust output for the given altitude. For example, at sea level, the GA N1 is listed as 102.1% N1 under ideal conditions with standard barometric pressure. Thus, it seems to me that TO-B aligns with that based on my research and own ears aboard full 737-900ER flights operated under ideal atmospheric conditions.


    I also noticed that below a certain altitude on approach, the THRUST LIM page defaults to takeoff values (D-TO 1, D-TO 2) and cannot be set to CLB, CON, or GA.

    Kind regards, good day, and bon vol!

    -VolerSuisse333

  • Some issues were downplayed and even justified of the ones listed above.

    Dude I have to agree with not being fixed anytime soon part. Just like the cockpit glare shield windows on the 320 series the planes look so uncanny with the windows straight. It’s a little hypocritical for ipacs to say they care about detail but are ignoring ones like these 🤷‍♂️