lh6800

member
  • Content count

    20
  • Joined

  • Last visited

Community Reputation

1 Neutral

About lh6800

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

787 profile views
  1. Hi, thanks for the quick reaction. Now everything is working fine. Your support, as allways, is outstanding! Thanks, Kurt
  2. Hi, it seems that the latest update screwed up a few things within simstarter ng. First: The program picks always the first paintscheme of an airplane. For my standard flight this is Piper Cup, but simstarter ng uses Piper Cup Paint1. If you save your profile with another paintscheme, than simstarter will revert back to the first paint scheme. But more serious: I have activatet the scenery selection screen on startup of a profile. But you will not be asked to select a scenery. P3D V4.2 simply starts without any further information and simstarter ng remains open. All was perfect before the last two updates. Thanks, Kurt
  3. +1 for Prepar3D V4.2
  4. lh6800

    Are OOMs really gone with V4?

    Hi Nicolas, I use P3D V4.1 since it's release in May/June (32 GB RAM, MSI GTX 1080, Windows 7-64 Pro). I never had a system so stable before, but I also went into trouble sometimes: Flytampa - flying into Athens with Dynamic Lights on and at Down or Dusk ends with "P3D stopped working" - so "DL" allways off. One month ago, I decided to give FSDT-Airports and GSX a try again in P3D V4.1, despite I had to remove their airports and GSX from FS2004 and also FSX before - allways after a few weeks and on different PC's with different Windows versions, thanks to the famous couatl-Engine and Addon-manager. A few days ago, my P3D got unstable with PMDG 737NG just on final approach at every airport (... stopped working and I landed on the desktop with no message), my thoughts were "voilà, the good old FSX days with OOMs a back finallly". But I found out, if you have GSX installed, just remove it and everything is fine again. FSDT New York V2 together with Drzewiecki's New York runs fine, but GSX killed my P3D V4 and I had to remove it completely. Now my sim is stable again. Hope that helps. Best wishes Kurt
  5. Hallo, zunächst ein mal ein riesiges Dankeschön für all die neuen Features - vor allem die Möglichkeit, vorab die Szenerien auswählen zu können. Nun aber zu einem kleinen Fehler in SimStarter NG (Fsuipc.ini). Der Parameter TrafficLimit kann von 0-100 verändert werden, ich vermute, Du hast ebenso wie ich diesen Parameter als %-Wert interpretiert, denn so geistert dieser Parameter auch durch diverse Foren. Ich hatte das vor einiger Zeit nicht so recht verstanden und mich direkt an Pete Dowson in seinem Support-Forum gewandt. Ich erhielt ein ziemlich kauzige und harsche Antwort nach dem Motto, er verstehe gar nicht, was ich wolle, der Parameter sei ganz simpel die maximale Anzahl an Flugzeugen, die innerhalb der FSX-Bubble dargestellt werden sollten und er habe den Wert auf 250 gesetzt. D. h. also, mit dem TrafficLimit legt man schlicht und einfach die maximale Anzahl an dargestellten Flugzeugen fest, alles oberhalb davon wird gelöscht. Die weiteren Parameter arbeiten dann mit dieser Obergrenze. Unbeeinflusst davon bleibt als oberste Ebene das Setting im Register "Verkehr" beim FSX. Beispiel: In FSX wird die Prozentzahl an Linienflügen auf 50% gesetzt -> dies ergäbe lt. der hinterlegten Flugpläne 273 Flüge (also AI-Flugzeuge in Luft und am Boden) für EDDF und den Umkreis von 80 Meilen, FSUIPC kappt das auf 250 über den Wert bei TrafficLimit und reduziert dann weiter gemäß der folgenden Parameter. Der Schieberegler von 0 - 100 müsste idealerweise durch ein Eingabefeld ersetzt werden, in das der gewünschte Wert eingegeben werden kann. Viele Grüße und nochmals Danke für SimStarter NG, Kurt
  6. lh6800

    Edit scenery entries before start flying

    Perfect! That's exactly what we talked about. Looking forward to get the update - but, there's no hurry. Thank's, Kurt
  7. lh6800

    Edit scenery entries before start flying

    Great, one of my favorite tools is getting better and better and your support is outstanding.
  8. Hello, with PMDG 737NGX and even more with FSLabs A320X the problem of used VAS and running out of memory came back to FSX(-SE). Adjusting the settings in FSX is one way to deal with this and I have done it by defining individual profiles for PMDG and FSLabs. Another solution could be the activation and/or deactivation of scenery-files. I have defined a scenery-configuration called "All off", where every airport is deactivated. The only entries, that are active, are all the FSX-related basic stuff and orbx textures, orbx vectors, orbx europe, ai-traffic and of course the essential libraries (like Flytampa, SODE or Aerosoft). Before every flight with PMDG or FSLabs I go into the Scenery Manager and mark the departure and destination scenery as active and save the changes. Do you think, it would be possible to implement an option in simstarter ng to ask for activating/deactivating scenery-entries - after hitting the button "Start Profile"? (... in a scenery-configuration file, you can define as to be opened for editing before starting FSX)? It would be very easy and save to handle (during my last flight I forgot to adapt my scenery-file and ended on the default fsx-airport). Just an idea to add another option to simstarter ng. Regards, Kurt
  9. lh6800

    Error

    Hello, it is not a big problem. As described, when I change something in Scenery Manager and save it - there will be this error message "Diese Anwendung konnte nicht gestartet werden, weil mfc80.dll nicht gefunden wurde. Eine Neuinstallation der Anwendung könnte dieses Problem beheben." one time. After that everything runs fine. There is no information in the windows event protocol, that would help. FSX simply don't start - I have to press "Start Profile" again in Simstarter NG and that's it - FSX starts and everything is ok. I can live with this and there is no need to fix it. Best regards, Kurt
  10. lh6800

    Error

    Hi Max, I have this error-message also sometimes. It happens allways, when I change something in Simstarter NG (mostly if I change settings in the scenery editor) and save the changes. After that I get the missing MFC80.dll-message, when trying to start FSX. I have to click ok, start FSX once again with Simstarter (without closing simstarter) and everything runs fine. It is strange and I never noticed this before Release 1.4.4 rev7. Starting Simstarter NG and then FSX after having selected a profile never ends with this error-message. Regards, Kurt
  11. lh6800

    FSX-SE

    I'll stay with it for the next years. Tons of addons force me to stay and I am happy with it.