Jump to content

Hans Hartmann

Developer
  • Posts

    5142
  • Joined

  • Last visited

  • Days Won

    33

Everything posted by Hans Hartmann

  1. Well, listening to ATIS on COM2, I hear scratches and noises, like very bad reception (that's an actual MSFS feature) and can see the ATIS ticker in the ATC window. The COM2 volume knob changes the volume of the noises and switching it on and off does works as well. However, the latest update removed the COM controls from the right audio panel. Only the left will work now. With these settings COM2 reception works.
  2. The issue is known but not easy to reproduce. Sometimes it happens, sometimes not. Anyway, a fix for it was NOT part of the latest update. We're still searching.
  3. 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.
  4. This is nothing new for this update. The table with the speed calculations (original manufacturer data) becomes quite sketchy at altitudes at or above 6000ft, especially with high take off weights (Denver and Aspen are prime examples). Some airlines apparently have more complete tables but these include additional temperature limits ("38°/132") where the manufacturer tables just have a blank field. If we can get a hold of those, we will add them to a future update.
  5. The version numbers and the change log say differently, but whatever... One word on the weather radar: This can not be implemented before an SDK update for Sim Update 10 is released which gives us access to the functionality. For the recent Sim Updates, the SDK has been released between a few hours and a few days after the Sim Update itself (I'm not talking about the beta but the actual final Sim Update release). That means that there can't be a weather radar update until after this date. How long after this date depends on how complex the integration is going to be. For now, I am unable to give you any estimate for this. On future updates: Yes, there will be future updates, but it's too early to talk about features or release dates.
  6. This CRJ mod is just a panel.cfg and therefore not considered to be actual code. From my perspective as the author of the original file, that's fine.
  7. This will become part of the standard Twin Otter package with the next update. Thanks @TheFly77 for allowing us to include it.
  8. I found that it's easier to just select the altitude, switch the AP on and then set a VS with the UP/DOWN keys - this will get you to the selected altitude. The ALT key itself is only for ALT HOLD (= hold current altitude). To change to another altitude, select your target altitude, press VS and then UP/DOWN again.
  9. No need to blame Microsoft here. We were aware of the issue before release and we know that it's being worked on. Xbox will follow as soon as technically possible.
  10. Is there a file named: C:\Users\user name\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt? And does it end with a like that looks similar to this (with another path of course): InstalledPackagesPath "F:\MSFS_Store" ?
  11. Die Grasflächen... die nicht beleuchtet sind (und die nichts mit dem Traffic Add-on zu tun haben).
  12. Ja, an den Bestandteilen des Produkts - den Flugzeugen. Das ist 100% korrekt, was die schreiben. Wenn eine Beleuchtung des Flughafens selbst gewünscht wird, dann muss man sich eine entsprechende Scenery installieren und nicht ein Traffic Add-on, was damit nichts zu tun hat.
  13. Ich habe das hier gerade probiert und es lief ohne Fehlermeldungen durch. Auch der Flieger lädt ohne Probleme und die Schalter funktionieren. Was die Ursache für die Fehlermeldung bei Dir sein kann, weiß ich leider auch nicht. Von unserer (meiner und Aerosofts) bleibt somit leider tatsächlich nur die Empfehlung, den CRJ 550/700 zu löschen und neu zu installieren. Sorry.
  14. It's not in our hands when it will be available. The only thing I can promise is that it will be ready and available to Microsoft when the sun rises in Seattle.
  15. Sorry guys. Mea culpa! This one is on me, not on the marketplace. Apparently, I got confused and put one single wrong file into the package which messed everything up. I will provide a new version to the Marketplace people right away. Sorry again.
  16. Sorry guys. Mea culpa! This one is on me, not on the marketplace. Apparently, I got confused and put one single wrong file into the package which messed everything up. I will provide a new version to the Marketplace people right away. Sorry again. As for VR: The knobs in question have been changed from my own templates to Asobo templates a while ago, so they should work in VR.
  17. I just checked this. I switched to Cold & Dark in the EFB; the ATC windows switched to what your screenshot shows. Then I clicked Ready for Taxi and the ATC window changed to COM1/2/3 right after the battery switched on. I was able to switch on the autopilot without any problem. My first idea on this would be hardware. I know that several people had problems with the controls settings after Sim Update 7. So, may be there is something colliding with the Avionics Master Switch (for ATC) and the Autopilot Master Switch. My recommendation is that you check your controls setting for this or, if you don't have any custom controls settings, just reset them to default. Another possible reason for the autopilot disconnect would be a noisy signal from a joystick axis. In this case, you can try to reduce the AP Disconnect sensitivity in the EFB (Options, Page 1)
  18. 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.
  19. The 550/700 is indeed Version 1.0.11.0. The 900/1000 and the bundle along with it were bumped to 1.0.14.0 because of an issue with some knobs in the -1000. The jump from 10.11.0 to 1.0.14.0 is because the Marketplace increases the version number every time the ingestion process is done and this was required to implement the 900/1000 upgrade. So, basically 1.0.11.0 equals 1.0.14.0 in everything but the -1000 knobs. Sorry for the mess, but everything is OK. Really 🙂
  20. The just received info from Asobo that the HUD issue has been solved. However, there's is no ETA for the availabilty of the solution yet.
  21. The just received info from Asobo that the HUD issue has been solved. However, there's is no ETA for the availabilty of the solution yet.
×
×
  • Create New...