We are looking for two additional A330 pilots to join our advisory team.  We will ask for credentials (sorry for that), but if you are willing to assist contact us on mathijs.kok@aerosoft.com

Jump to content

Moridin

Members
  • Posts

    148
  • Joined

  • Last visited

Everything posted by Moridin

  1. Dear Aerosoft team, On December 14 we were assured there would be bugfixes for the CRJ5/7/9/X. Do we have an expected ETA? Anything, e.g. Q4 2022? Thanks.
  2. So just to summarize two of the problems... Sound bug, which I have on all CRJs and all liveries: No resolution. No acknowledgement. SPEED bug: Acknowledged. No resolution. Hence my earlier questions... Can we expect fixes for these bugs in the future? Or should we just accept them?
  3. This should be stated clearly in the EFB or the EFB should simulate 2 clicks when a user presses it once (launch the relavant function twice?), if this is an SDK limitation.
  4. Re 1: It's already been reported by others but I'll do a comparison video one day. Re 2: How can it "work properly" when I cannot click it? It worked fine earlier, before one of the updates. Re 3: Here's a topic from the forum. One example: Re 4: Reported by others already multiple times. One example: Re 5: I am not required to read every single post in this forum and know everything, lest I would have no time for anything else. If it's an SDK limitation, just say so.
  5. LNAV - Fly a curvy route and compare it to the CJ4 + WT mod. BARO - Nope. I want it to work properly. No sounds - I don't have the Marketplace version, so no. CLR - Yes. Again, I'm interested in the final result, not excuses. Phantom - Happens on every Direct To. Very frustrating on VATSIM. N/W Steering - Yeah, that's the problem. Works even when the switch is OFF. ūüėČ
  6. This is one issue. We know about the bugs. The question is if there will be on-going maintenance and evolution of the CRJ.
  7. Hello, This is a current bug list (some things might be what I consider bugs) in no particular order, that I found and remember: FMC sometimes freezes, when entering a flight plan, when a wrong waypoint is entered, when trying to overwrite it; solution: "Erase" and start again. LNAV is not very good. HOLD performance (LNAV) is atrocious. VATSIM controller: "Can you please explain what your aircraft is doing Lufthansa 337? I'm in the Aerosoft CRJ, Sir. | Ahh yes. Continue." SPEED doesn't work 90% of the time, ignored completely. BARO button unpressable; solution: press 15-20 times, maybe it will work. No sounds on dials rotation and button presses. This worked earlier. CLR hard to press because of speed brake handle. Phantom waypoints on Direct To; solution: use LEGS page. EFB - set payload in simulator - need to press twice. No info anywhere on this (critical for new pilots). N/W Steering INOP. BARO not linked between Captain and FO, even when setting this option in EFB. VNAV always on MCP, even if turned off in EFB. If turned off in EFB, VNAV button pressable, but doesn't do anything. VNAV must be turned off otherwise ILS doesn't work (might actually work like this, unsure). A/I (all of the switches) turned on during icing conditions. Did not work on last flight - MFD showed "ICE" warning. Sometimes it works properly. Can we expect fixes to these bugs in the future? Or should we just accept that they'll be present? Some of them are over 6 months old. And I'm sure I missed some. Merry x-mas! ūüéĄ
  8. Just checked, none of those 2 things are relevant to the CRJ HUD.
  9. Hi, The HUD in the CRJ is blank after the update. I can see just the glass...
  10. Same problem on CRJ-1000 on the HOP special livery. No sounds from almost all knobs.
  11. I mentioned earlier, in another thread, that I will wait with the 900/1000 upgrade for the CRJ until there is a bugfix update, that will fix LNAV, phantom waypoints, the speed tape and a few other things. Unfortunately (for me), @Mathijs Kok and Co. decided to address a few bugfixes in this release, which I was led to believe would not be done. Well done, bravo! This of course meant that I had to put my money where my mouth was, so I purchased it last night. There are still a few issues to iron out but it is better. I spent a few hours in the CRJ9 doing a real ops from EKCH to EDDM, and then a few more in the CRJX flying around LOWI. This is easily the best jet airliner in MSFS at the moment. Now, I hope the remaining bug fixes are still being worked on and I trust there will be an update in the following weeks, and that the CRJ won't be put on the shelf while Aerosoft works on other projects. Good luck! ūüĖĖūüŹĽ Changelog from Aerosoft One
  12. Something changed with the weather. Again. I think there was a server-side tweak since yesterday. Better today, but still not perfect. BUT now I get massive wind changes and huge turbulence when switching METARs on Live Weather. So I was flying along at M.78, minding my own business, when suddenly the wind changed to +40 KTS TW which made me overspeed. How the hell is this STILL a thing?
  13. I am using AAO. A 2 KT x-wind should not blow a CRJ or DC-6 off a runway with max rudder applied.
  14. It seems all aircraft are impacted by wind when on ground. Veering off the runway has been documented on the CRJ, DC-6, CJ4 WT, and JF Piper Arrows. Haven‚Äôt searched for others. A 2 KT crosswind has thrown people off the runway with full left/right rudder. Turning off live weather helps. Using REX Weather Force doesn‚Äôt help. There is also a ‚Äúnosedive‚ÄĚ problem during approaches because of this too.
  15. Another CTD, while entering the runway at EGCC.
  16. The CRJ will veer off to the left while taking off. I need to keep around 25-30% right rudder otherwise it’ll just exit the runway. Same issues when landing. My rudder and controls are correctly configured. This happened on all my flights yesterday and today, only on the ground. Less pronounced when taxiing. I assume this a new SDK change which was mentioned. Any ideas when we can expect an update to address this @Mathijs Kok? I’m asking because the bugs are starting to add up and I’m starting to get frustrated with them not being addressed as smaller incremental updates for months on end.
  17. Crashes when entering ALT flight level into FMC. Happened to my friend and I. Two different computers, two different flights. EXEC after entering alternative flight level = crash. cc @Mathijs Kok
  18. So I took the ASCRJ_FCP_HCBRAVO (only this one, there are 2 others!) template from here: I then loaded it in, and modified it to suit my needs.
  19. Step 1 (L:AAO_LROT_SEL)·1·==·if{·(L:ASCRJ_FCP_ALT_SEL,·Number)·10·(L:AAO_RROT_ACCEL)·++·*·+·dnor·(>L:ASCRJ_FCP_ALT_SEL,·Number)·(L:AAO_RROT_ACCEL)·++·(>L:ASCRJ_FCP_ALT_CHANGE,·Number)·}·els{·(L:AAO_LROT_SEL)·2·==·if{·(L:ASCRJ_FCP_WHEEL,·Number)·10·-·dnor·(>L:ASCRJ_FCP_WHEEL,·Number)·-1·(>L:ASCRJ_FCP_WHEEL_CHANGE,·Number)·}·els{·(L:AAO_LROT_SEL)·3·==·if{·(L:ASCRJ_FCP_HDG_SEL,·Number)·10·(L:AAO_RROT_ACCEL)·++·*·+·dnor·(>L:ASCRJ_FCP_HDG_SEL,·Number)·(L:AAO_RROT_ACCEL)·++·(>L:ASCRJ_FCP_HDG_CHANGE,·Number)·}·els{·(L:AAO_LROT_SEL)·4·==·if{·(L:ASCRJ_FCP_CRS1_SEL,·Number)·10·(L:AAO_RROT_ACCEL)·++·*·+·dnor·(>L:ASCRJ_FCP_CRS1_SEL,·Number)·(L:AAO_RROT_ACCEL)·++·(>L:ASCRJ_FCP_CRS1_CHANGE,·Number)·}·els{·(L:AAO_LROT_SEL)·5·==·if{·(L:ASCRJ_FCP_SPEED_SEL,·Number)·10·(L:AAO_RROT_ACCEL)·++·*·+·dnor·(>L:ASCRJ_FCP_SPEED_SEL,·Number)·(L:AAO_RROT_ACCEL)·++·(>L:ASCRJ_FCP_SPEED_CHANGE,·Number)·}·}·}·}·} Step 2 (L:AAO_LROT_SEL)·1·==·if{·(L:ASCRJ_FCP_ALT_SEL,·Number)·10·(L:AAO_RROT_ACCEL)·++·*·+·dnor·(>L:ASCRJ_FCP_ALT_SEL,·Number)·(L:AAO_RROT_ACCEL)·++·(>L:ASCRJ_FCP_ALT_CHANGE,·Number)·}·els{·(L:AAO_LROT_SEL)·2·==·if{·(L:ASCRJ_FCP_WHEEL,·Number)·10·-·dnor·(>L:ASCRJ_FCP_WHEEL,·Number)·-1·(>L:ASCRJ_FCP_WHEEL_CHANGE,·Number)·}·els{·(L:AAO_LROT_SEL)·3·==·if{·(L:ASCRJ_FCP_HDG_SEL,·Number)·10·(L:AAO_RROT_ACCEL)·++·*·+·dnor·(>L:ASCRJ_FCP_HDG_SEL,·Number)·(L:AAO_RROT_ACCEL)·++·(>L:ASCRJ_FCP_HDG_CHANGE,·Number)·}·els{·(L:AAO_LROT_SEL)·4·==·if{·(L:ASCRJ_FCP_CRS1_SEL,·Number)·10·(L:AAO_RROT_ACCEL)·++·*·+·dnor·(>L:ASCRJ_FCP_CRS1_SEL,·Number)·(L:AAO_RROT_ACCEL)·++·(>L:ASCRJ_FCP_CRS1_CHANGE,·Number)·}·els{·(L:AAO_LROT_SEL)·5·==·if{·(L:ASCRJ_FCP_SPEED_SEL,·Number)·10·(L:AAO_RROT_ACCEL)·++·*·+·dnor·(>L:ASCRJ_FCP_SPEED_SEL,·Number)·(L:AAO_RROT_ACCEL)·++·(>L:ASCRJ_FCP_SPEED_CHANGE,·Number)·}·}·}·}·} Step 3 1·(>L:AAO_LROT_SEL) Basically I took the scripts from the other person here (was it in this post? it's on the forum somewhere anyway) and adapted it slightly to my needs.
  20. 8/10 times it will fail when setting SPEED on initial climb from airport if you don't quickly dial in a speed higher than your current speed, as it continues to climb. Alternatively, climb to e.g. 5000, manually slow down waiting for clearance to a higher altitude, then engage SPEED again to climb to e.g. FL120, and it will often blow past.
×
×
  • Create New...