Jump to content

FWAviation

Members
  • Posts

    553
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by FWAviation

  1. I'm glad to see that the problem is already known. I noticed it in my sim only yesterday. I'll cross my fingers that you and your colleagues find a fix soon, @masterhawk. Until then, I might revert to version 1.3.1.0 which is the latest installer available for my P3Dv4. I re-installed it this morning and the problem with the A319 with IAE engines vanished. By the way, after updating from 1.3.1.0 to 1.4.2.1 this morning via the Aerosoft Updater, not only the loading problem re-appeared, but P3D also couldn't find the ASC_PF_OnAuto.wav file anymore. @IBE1133 mentioned that problem also here. So it would be great if you and your colleagues could look into that problem for the next update, too. Thank you!
  2. I'm only a user of the CRJ and can't help regarding the other issues, but I'm not sure whether the above described is really an issue. To me, it's self-evident that you have to stay in the room and constantly adjust thrust in the CRJ if you want to maintain a certain airspeed at all times. Wind conditions can change at any time during flight, including cruise, so airspeed will change all the time as long as you don't counter that by according thrust settings, due to the lack of autothrust in the CRJ. And I think that a very short drop of N1 numbers before they increase is not all that worrying, I think that (depending on the thrust lever quadrant you use) it's not unusual that there's a certain lack of precision as soon as you push or pull the thrust lever only very slightly. I believe I have witnessed that effect in every P3D plane I had to control by manual thrust so far. Maybe one can counter the effect by changing the sensibility of the thrust lever in the according P3D menu or via FSUIPC, but I haven't tried it.
  3. @Mathijs Kok Maybe my question got overlooked between all the other text of my previous post, but have I understood correctly that Jo Erlend's version of Paderborn/Lippstadt will be part of the default MSFS and no separate add-on?
  4. @Mathijs Kok So this is what you guys have been working on all the time. Thank you for the heads up and congratulations on your cooperation with Asobo and on those add-ons which look splendid already now! Have I understood you correctly, Paderborn/Lippstadt was done by Jo Erlend Sund (that alone is fantastic news) and Microsoft/Asobo even included his rendition of EDLP into the default simulator so that we will be able to fly there already on August 18? That would be even more fantastic news, especially for me who lives not far away from EDLP and who always dreamt of seeing a new version of my home airport, originally in P3D, but now I don't mind at all to see it in MSFS. I must say that each day that I see more previews from MSFS, I'm getting more and more excited even if there truly still seems a lot of work to be done. All the best to you and your team for all the exciting challenges ahead! I am truly convinced now that the real golden age of flight simulation has only begun!
  5. Oh Mann, schon wieder so eine genervte Reaktion, nachdem ich ganz höflich geschrieben habe... Sehr urlaubsreif? 😉 Dass du nicht empfohlen hast, HDR auszuschalten, habe ich verstanden. Ich habe es aber trotzdem getan, zumal HDR ja auch etwas umstritten ist und ich einfach testen wollte, wie es dann aussieht. Du hattest ja auch selber weiter oben geschrieben "Im V4 fand ich HDR off immer noch am stimmigsten", und ich bin noch im P3Dv4. Von daher... Das Runterdrehen auf 0.7 habe ich auch ausprobiert, da war mir die Beleuchtung des Bodens aber auch noch zu hell. Leider beantwortet das alles auch nicht meine Frage nach den selbstleuchtenden Gebäuden in Schwaig. Ich wünsche aber lieber mal einen schönen Urlaub und vielleicht möchte ja @Autopiloth oder eine andere Person, die im Thema ist, meine Frage beantworten.
  6. @jwcruz825 I'm no member of the Aerosoft staff or support team, so you should address your questions at @OPabst, @mopperle or @masterhawk. Sorry.
  7. I sadly have to confirm that also the solution I mentioned in this topic hasn't really solved the problem. A few minutes ago, I couldn't start P3D anymore - it crashed to desktop after each of three start attempts. I now have uninstalled the SODE jetways for Munich, and P3D is starting again and running normally. So there must be a bug in the recent version 1.0.1.0 SODE jetways. Do you have the SODE jetways installed as well, @mburkhard? I use P3D v4.5. If necessary, I can provide the content SODE.log file, but it's a really long list and I couldn't find any suspicious entries about the Munich scenery in it yet.
  8. It was there since yesterday. So probably, as Oliver Pabst suggested, you hadn't refreshed your browser cache then and thus couldn't see the link.
  9. Okay, danke. Ich habe HDR jetzt mal ganz ausgeschaltet, damit sieht es in der Tat passabel aus. Aber vielleicht findet sich hier ja auch noch eine Lösung für die HDR-Nutzer, sodass wir München auch mit dem Aerosoft-A330 bei Nacht nutzen können, ohne bei der einen oder der anderen Darstellung (Airbus-Cockpit oder Boden in München) Abstriche machen zu müssen. Und noch eine Frage: Geht ihr noch das Problem mit den selbstleuchtenden Gebäuden an? Selbst bei ausgeschaltetem HDR sehen die Autogen-Gebäude in Schwaig (Lufthansa Aviation Training Center, NH-Hotel und Co.) immer noch aus - um deine treffende Formulierung aufzugreifen -, als ob sie vom THW angestrahlt werden:
  10. @OPabst Ja, ich habe HDR ebenfalls auf 1.0 eingestellt - da ist es eben alles sehr hell. Oder muss ich da mit den anderen HDR-Werten spielen?
  11. Yes, I would second that. That's better than having no numbers at all.
  12. I don't know what can be misunderstood about this sentence: "PS: Gate numbers on jetways is not an easy task as this will need a different jetway model at every gate. Maybe we´ll find a solution, but this cannot be fixed short term." I understood that it is a big task but Thorsten did not definitely exclude the possibility that you find a solution. And no, I'm not even argueing with GSX, so I don't know why you get so defensive. It was just a polite question.
  13. Thanks for the swift response, but @Autopiloth has stated above that you as a team will maybe find a solution for the individual gate numbers on the jet bridges as well, albeit not in the short term. Maybe it will be also a solution for the staircase gate numbers at the same time? Of course they are not absolutely necessary for the immersion, but they sure add a nice touch. And I forgot one more thing: How about the illuminated coloured stripes in the "M" logo of Munich Airport which can be seen on the jetbridges and around the airport? It doesn't have to have changing colours, but some permanent colouring would be great as opposed to the current (unusual) grey.
  14. If I may add to @MatthiasKNU's list if it isn't on your to-do list yet, @Autopiloth: The staircases for the gates at the Terminal 2 main building currently all carry the gate numbers "G23/H23" and "G24/H24". If you could change those to the respective gate numbers, it would be great. And when having HDR lighting set at 1.00 (as recommended for the use of Aerosoft's A330), I get "self-illuminating" buildings at and around the airport, that means buildings that are completely lit at night. Also the ground around the taxiways and aprons and also in the western access to the airport (around the Zentralallee and the S-Bahn tracks) is far too bright at night, it looks as if there are lanterns lighting it everywhere.
  15. In meinem Nachtleben gibt es zwar immer noch die selbstleuchtenden Gebäude (teilweise auch aufgrund meiner von Aerosoft für den A330 empfohlenen HDR-Einstellungen) und vor allem den hell erleuchteten Boden rund um die Vorfelder, an der westlichen Zufahrt und teilweise auch um die Startbahnen herum, aber ich nehme an, dass das Bugs sind, die nicht so auf die Schnelle zu beheben sind. Das heutige Update finde ich jedenfalls schon vielversprechend - toll, dass hier auf Hinweise der Community reagiert wird!
  16. Um mal wieder zum Thema zurückzukehren: Ich finde es gut, @Flying_Timm, dass du dir die Mühe gemacht hast, beide Szenerien mal gegenüber zu stellen und auch im Detail dir anzusehen, wo die sim-wings-Szenerie noch steigerungsfähig ist. Danke dir! Das ist sehr aufschlussreich, auch wenn die T2G-Version ja auch nicht gerade durch hohe Detailtreue und Immersion aufgefallen ist. Du listest ja auch auf, was du eigenhändig an deren Szenerie alles getweakt hast, bis sie mal so aussah, wie sie jetzt aussah/aussieht. Ich vertraue da auf das sim-wings- bzw. Aerosoft-Team und hier auch namentlich @OPabst, dass sie wie gewohnt sich mit der Kritik in der Sache auseinandersetzen und hier auch Updates durchführen werden. Denn das war ja nun immer gerade gegenüber dem genannten Entwickler der "Konkurrenzversion" ein wesentliches Qualitätsmerkmal von sim-wings, dass dieses Entwicklerteam fleißig Support leistet und auch bereit ist, die eigenen Szenerien zu verbessern und weiterzuentwickeln. Und noch ein Nachtrag zum gelben Gras in der sim-Wings-Szenerie: Ich erinnere mich noch lebhaft an die beiden letzten sehr trockenen Sommer, vor allem den Dürresommer 2018, als ich mehrmals den echten Münchner Flughafen als Passagier angeflogen habe - da war das Gras dort, wie im Rest der Republik, auch eher gelb als grün. Im aktuellen Luftbild bei Bing Maps kann man auch sehen, dass es in München durchaus auch mal "gelbliche" Zeiten gibt... Vielleicht stammt das Luftbild der sim-wings-Version ja genau aus dieser Zeit?
  17. @Wolkenschreck I would urgently recommend you to post only links to the photos you got from Wikipedia and the Munich Airport website. Due to copyright, it's not permitted to post third-party pictures here. Links are okay.
  18. Thank you for the heads up! Would have been nice to get a reply by Aerosoft or Hans, but if the issue is well known (also for the new version) already, then I'm fine.
  19. @Hoffie3000 Even if your question seems to refer to the P3Dv5 version, I can confirm also for the new 2.2.0.0 version for P3Dv4 that ILS capturing seems to have gotten worse. In my case, the problem is not the glideslope, but the localizer, though. The autopilot has great difficulties catching the localizer beam unless I "line up" the airplane myself or only deviate from the localizer by a few degrees. I had a test flight this morning, approaching Paderborn Lippstadt's runway 24 in real-world weather conditions where there was a little crosswind initially that got a bit weaker and changed towards more of a headwind at approximately 800 feet above ground. Until that wind change, the airplane was pretty much on the localizer beam, but then suddenly it got confused again by the changed conditions and I had to take manual control of the plane because I didn't want it to swerve to the left and right during the final few hundred feet of the approach. I Catching the localizer from an angle of more than just a few degrees is practically impossible - the autopilot reacts extremely slowly and thus constantly overshoots the localizer beam. Really unnerving. I should add that I did not have the FMS programmed in all the cases I described, but only flew a traffic pattern around an airfield with the autopilot activated most of the time. In previous versions, in such scenarios the autopilot had difficulties catching the localizer from "steeper" angles (that is, 20 degrees and more) as well, but after a few swerving maneuvers, lined up perfectly in the end. @Hans Hartmann, are you aware of this issue?
  20. Yes, they work for me, too. Sadly, both liveries are out of date already. D-ACKL in real life only carries a "Lufthansa" instead of a "Lufthansa Regional" livery now, while D-ACNW has been painted in Lufthansa's new livery a few weeks ago.
  21. Thanks for pointing out, @vali - good to know! EDIT: Did he take those two liveries down? I can't see anything about them on his Facebook page and I sadly don't have my login data for AVSIM with me (so I can't check whether those two download links still work), but I can't find the two liveries via the AVSIM search function.
  22. That's good advice for a truly annoying problem. I can give everyone the advice to do without third-party AV software (at your own risk, of course) and simply use the Windows virus protection and firewall (if you are a Windows user). My brother-in-law who is an IT professional recommended it to me and I never regretted it since. As Mathijs already pointed out, AV software can do more harm than being helpful.
  23. I second that request. @vali, Max Wohlerdt (who does a lot of Lufthansa repaints) also plans to update his CRJ textures for the CRJ Professional in the months to come. So I expect the D-ACNN livery in its current form to be released in the near future anyway. Nevertheless, it would be great if the livery included in the default package would already lose the Eurowings paint.
  24. May I give you a recommendation from another customer's standpoint, @greycap? If you behave that aggressively and reproach the Aerosoft team of not checking your problem thoroughly, you can't be sure of getting a reply. As Mathijs and Otto (mopperle) already pointed out, they could not reproduce the problem. Otto even posted a video where he panned around to the corner you meant. They also suggested you to address that problem also to FSDT, since your problems indicate that GSX could be the culprit. Did you do so? In any case, you ask them to do something they already did and although they already said they can't reproduce it and gave you further advice, you react in such a destructive manner. This is not a good idea.
×
×
  • Create New...