Jump to content

Hans Hartmann

Developer
  • Posts

    5087
  • Joined

  • Last visited

  • Days Won

    31

Hans Hartmann last won the day on June 5

Hans Hartmann had the most liked content!

About Hans Hartmann

Recent Profile Visitors

12364 profile views

Hans Hartmann's Achievements

  1. Yes. Anti-ice systems need bleed air, and to produce more bleed air, the idle N1 is increased. For cowl anti-ice only, it's to about 30% and for cowl and wing anti-ice it's 35%.
  2. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  3. It's because the setting for "high quality textures" is no longer ON by default. We fixed the issue and it will be fine after the upcoming CRJ update is available.
  4. No, you're actually right. I copied the file for P3D4 but forgot the one for P3D5... Please use this for now:ASCRJ Pro 5.7z. I'll make a new and complete update tomorrow. It goes into the <CRJ Main Folder>\SimObjects\Airplanes\Aerosoft CRJ Pro Base\panel Ich bin ein bißchen neben der Spur wegen dem ganzen Ärger um die MSFS Version....
  5. I tried two or three alternative pow() functions but all caused the same issue. There always was something too close to zero... I'll try more. I want to get this done after all.
  6. I am not aware of any downside. I was told that other developers reported a drop in performance but so far, I didn't notice anything like that for the CRJ.
  7. Sorry, I forgot to edit the numbers in the version resource file. I've done that now and re-uploaded the gauge DLLs with the right numbers. That's version 2.5.0.4 now.
  8. Made some spelling fixes and added some missing words. Sorry for that.... I was in a rather angry state when I wrote this.
  9. Thank you for making this post. I hope it's going to help with getting a fix asap. I am also doing what I can to make sure this gets sorted asap.
  10. Guys, I'm sorry that this happens. Please understand that we (Aerosoft and myself) really can't do anything about it. Unfortunately, a lot of bullshit is posted on all kinds of forums by self-proclaimed experts that has nothing to do with reality. I don't like to get the blame for bugs that lie outside the scope of the CRJ. We had this before with the crashes on loading the CRJ (first caused by AI traffic issues, later also for older CPUs) and we have it again with Sim Update 5. And again, it's not the fault of the CRJ. For those who are interested, here's what's going on: You all know the beloved 10 minute wait when the CRJ is loaded for the first time. During these 10 minutes, the .WASM file in the aircraft's panel folder is compiled into a Windows DLL (Dynamic Link Library) which then is loaded by Flight Simulator. The wait was annoying but the process worked (except for some who used older CPUs). With the 1.18.13.0 update, an additional compiler option ("-fast-math") was introduced to make the WASM code even faster. Unfortunately this option has a nasty side effect: it causes decreased calculation precision (faster execution = lower precision; slower execution = higher precision) with the effect that values close to zero can become zero. This happens in a sub-term of the indicated airspeed calculation with the result that the whole formula becomes zero. As a consequence, all three airspeed indicators are stuck at zero. The "Fast WASM compilation" option disables -fast-math and as a result, the airspeed indicator works. Once I started using this option, the problem was gone for me. But of course I didn't know that was the reason. Being able to track this down was like a win in the lottery. I only found out by pure luck because after installing the release 1.18.13.0, the airspeed indicator was stuck again and when I went into the dev mode menu, "Fast WASM Compilation" was disabled. I enabled it and the airspeed indicator worked. So, I tried switching fast compilation on and off a few more times and also asked the CRJ beta testers to give it a try. They confirmed that my finding was right and so I reported it to Asobo who, after some more testing confirmed it and gave me the technical information that I told you above. The bottom line is: It is now known what the problem is and how to fix it. All that is needed is an MSFS update where the fix is deployed. This brings us to the question that all of you want to ask me: "When?". Unfortunately, my answer is: I don't know. Sorry. Thank you for your understanding!
  11. Guys, I'm sorry that this happens. Please understand that we (Aerosoft and myself) really can't do anything about it. For those who are interested, here's what's going on: You all know the beloved 10 minute wait when the CRJ is loaded for the first time. During these 10 minutes, the .WASM file in the aircraft's panel folder is compiled into a Windows DLL (Dynamic Link Library) which then is loaded by Flight Simulator. The wait was annoying but the process worked (except for some who used older CPUs). With the 1.18.13.0 update, an additional compiler option ("-fast-math") was introduced to make the WASM code even faster. Unfortunately this option has a nasty side effect: it causes decreased calculation precision (faster execution = lower precision; slower execution = higher precision) with the effect that values close can become zero. This happens in a sub-term of the indicated airspeed calculation with the result that the whole formula becomes zero. As a consequence, all three airspeed indicators are stuck at zero. The "Fast WASM compilation" option disables -fast-math and as a result, the airspeed indicator works. Once I started using this option, the problem was gone for me. But of course I didn't know that was the reason. Being able to track this down was like a win in the lottery. I only found out by pure because after installing the release 1.18.13.0, the airspeed indicator was stuck again and when I went into the dev mode menu, "Fast WASM Compilation" was disabled. I enabled it and the airspeed indicator worked. So, I tried switching fast compilation on and off a few more times and also asked the CRJ beta testers to give it a try. They confirmed that my finding was right and so I reported it to Asobo who, after some more testing confirmed it and gave me the technical information that I told you above. The bottom line is: It is now known what the problem is and how to fix it. All that is needed is an MSFS update where the fix is deployed. This brings us to the question that all of you want to ask me: "When?". Unfortunately, my answer is: I don't know. Sorry.
  12. There is a need for an update, yes. More for MSFS than for the CRJ, but the CRJ will receive one too.
  13. Well, according to the list of fixes, it would be surprising if it made a difference.
  14. The CRJ Pro update 2.5.0.3 for P3D v4 and v5 is available via the Aerosoft Updater now: - Fixed partially rotated MFD - Fixed missing symbols on MFD - Formula correction for IAS calculation - Fixed L/R selection in MFD Menus - Flaps indication "1" on EICAS for lever position 1 (physical flaps position = 0) - Fixed PA/CALL/EMER pushbutton lights - Fixed setting reserve and taxi fuel on loading a flightplan - Disabled thrust reserver unlock during cold&dark - Fixed Radius to Fix legs - Another attempt to fix the GS Hold that I broke to make it work in MSFS - Fixed a condition where the value for a minute could become 60 and an hour could become 24
  15. The CRJ Pro update 2.5.0.3 for P3D v4 and v5 is available via the Aerosoft Updater now: - Fixed partially rotated MFD - Fixed missing symbols on MFD - Formula correction for IAS calculation - Fixed L/R selection in MFD Menus - Flaps indication "1" on EICAS for lever position 1 (physical flaps position = 0) - Fixed PA/CALL/EMER pushbutton lights - Fixed setting reserve and taxi fuel on loading a flightplan - Disabled thrust reserver unlock during cold&dark - Fixed Radius to Fix legs - Another attempt to fix the GS Hold that I broke to make it work in MSFS - Fixed a condition where the value for a minute could become 60 and an hour could become 24
×
×
  • Create New...