Jump to content

Hans Hartmann

Developer
  • Posts

    5108
  • Joined

  • Last visited

  • Days Won

    32

Everything posted by Hans Hartmann

  1. Yes, but even that is normal, if you start moving around the cockpit with the mouse pointer of a brightness knob. The mouse has two functions in this situation. This can be fixed by changing the mouse settings, but otherwise it's a default setting in FS. I could reproduce it a couple of times. Sometimes it happens, sometimes it doesn't. But it has nothing to do with the CRJ itself, that's for sure.
  2. I change my opinion. That's not the beacon, it's the ramp guy outside the aircraft with his pushback truck. Just found that out while testing. So, no bug.
  3. Apparently something changed with the effects in SU6. We're investigating how this can be solved.
  4. I switched my XML to ASOBO_GT_Knob_Infinite_Push as well (I don't think this template existed when I created the CRJ animation code). It will be available with the next update which will coincide with the release of the CRJ-900 & 1000. I can't give you a specific date yet though.
  5. Ist es möglich, dass die ASUpdate.dat bereits von einer vorherigen Installation existiert, schreibgeschützt ist und deshalb nicht überschrieben werden kann? In dem Fall bitte einmal im Explorer mit der rechten Maustaste anklicken, Eigenschaften auswählen und den Haken bei "Schreibgeschützt" weg machen.
  6. The CRJ for P3D has a completely different sound set than the one for MSFS. The sounds in MSFS are more or less automatically played by Wwise and the sound.xml. The ones in P3D need to be played manually in the C++ gauge code. It's certainly possible that some knobs or buttons have no sound in P3D. I'll put it on my list.
  7. I just tried this departure from Fuerteventura but everything between LTE and VASTO was flown just fine. Do you remember what weather conditions you had when you made the flight?
  8. No, it's a clean overwrite. From my point of view there's no need to uninstall the previous version first. As long as the new WASM files are detected and you get the 6-10 minute wait, you should be fine. There may be some obsolete texture files that don't get removed this way, but since those are no longer referenced in the model, the worst that happens is some wasted space on your drive.
  9. Talking about bindings: Some key bindings indeed have changed with Sim Update 5. One example is the "ESC" key for "SET PAUSE OFF" that was newly introduced, so it's not part of any custom keyboard profile that was created before Sim Update 5. If you see any issues with key bindings and if you're using a custom profile, you should temporarily switch back to the default keyboard profile and check if the issue is still there. If it isn't, you need to update (or re-create) your custom keyboard profile.
  10. You're flying Mach 0.817 and the speed bug is below that at Mach 0.77. This doesn't look like a disagreement to me. Neither on the PFD nor the HGS. Or am I looking at the wrong things?
  11. I really don't know why that is. The manifest.json file has the correct number 1.0.6 in it.
  12. There have been a lot of model and texture updates as well as WASM files etc. Too much to use the updater, so we decided to go for a new installer.
  13. In this world. As you can see. So, if you really can do all these things and have all this knowledge, I would even more expect from you that you know what you're talking about. Your bragging just makes it worse. And with this, this discussion ends.
  14. A completely new system of input events has been introduced with Sim Update 5. Part of its consequences is what you currently experience with the center pushbuttons on the FCP. I'm going to update the CRJ with these input events but it needs to be done for all switches, knobs, levers etc. That's a huge amount of work and is going to take several months - even if I don't run into many issues. The whole thing is not exactly easy to handle either, so I can't give you any estimate right now. All that I can promise you is that I'm going to start working on it this weekend.
  15. 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.
  16. You weren't mocked. Mathijs told you that you are wrong when you compare mostly HTML/Javascript based aircraft with a fully WASM/C++ based aircraft. And he was 100% right with that. It's not that one is better than the other, but each uses a different programming language and a different runtime environment, so WASM comes with its own problems that Javascript doesn't have and vice versa. Feel free to read the SDK documentation and check out www.fsdeveloper.com and you will find out that you were comparing apples with oranges. You don't want to? Too complicated? Too much effort? Well, fine. But then, you shouldn't comment on such things either. Customer support did absolutely nothing wrong here. I guess I just proved the opposite. The customer is by no means always right and it's important to let him know if he isn't, because it's the only way to fight that general attitude of "I have no clue but I'm entitled to my opinion" which is spreading over the internet at an alarming rate.
  17. Abusing my moderator rights to post a comment: 1) Yes, there have been three other issues that were found during the testing at Microsoft. Two in the CRJ, which have been there since day 1, but never showed until Sim Update 5 (dark instruments after loading and HUD constantly flipped down) and one in the Marketplace ingestion process which wasn't directly related to the CRJ, but caused a delay anyway. 2) Everything has been fixed and as of 18:47 CEST yesterday evening, the ingestion process has been completed and the CRJ was sent to Microsoft's testing team. When it will be available? I don't know. Will Microsoft find another issue that needs fixing first? I don't know. I will have to wait - just like you.
  18. I recommend to disable Fast WASM Compilation because it's kind of a debug mode and less optimized (read: slower) than without.
  19. The problem sorted itself when we rebuilt the project with SU5 and the latest SDK.
  20. 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%.
  21. 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.
  22. 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.
  23. 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....
×
×
  • Create New...