Jump to content

Hans Hartmann [OLD]

Deputy Sheriffs
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Hans Hartmann [OLD]

  1. I'm not the Aerosoft management (thanks to any deity I don't believe in!) but I can answer this as it's more of a technical question. In case of the CRJ, it works in all versions of P3D v3 (and most likely even in v1 and v2). But since it's impossible to test everything on each version, we (Aerosoft as well as the developers) only guarantee that it works in P3D v3.4. Besides, every customer of P3D v3 has access to the latest v3.4 anyway (yes, I heard about the OOM rumours).
  2. You will be able to register your product on the Aerosoft page and then download the new version from there. Aerosoft is just compiling a new installer (a file was missing). Once that is done, the update should be available to CD customers too.
  3. No, sorry. I think that won't work (in a non-complicated way).
  4. What you need to do is to replace our NAV/GPS gauge by a default one. (The Trimble is not based on FS' GPS engine and thus doesn't use the default GPS mode).
  5. Sorry, dass ich hier erst so spät was zu sage. Ich bin zwar von Digital Aviation, habe aber mit der Do nichts zu tun. Von daher schaue ich auch nur relativ selten in Do-Threads rein. Voll kompatibel sind die Do und die Katana beide nicht. Es gibt Probleme, die allerdings behoben werden können (und zumindest bei der Katana teilweise oder ganz auch schon behoben worden sind). Das eigentliche Problem ist vielmehr personeller Art. Ich werde mich darum kümmern und Druck machen, nur versprechen kann ich leider nichts. Ich gebe hier Bescheid, sobald ich etwas Neues weiß.
  6. Das ist ein false positive, es ist also kein Trojaner/Virus/sonstwas drin. Einfach auf "Ignorieren" klicken und weitermachen. Nicht auf "Zugriff verweigern", dann geht alles wie gehabt.
  7. Wenn Hannover ein wenig anders programmiert ist, kann das schon sein. Einfach mal probieren. Du musst ja nur in den Anzeigeeinstellungen den Schieber testweise einmal nach rechts ziehen.
  8. Hast du evtl. die Szeneriedichte nicht hoch genug eingestellt? Das ist üblicherweise der Grund für fehlende Gebäude.
  9. Thomas, er meint die Sim Icons in der ATR. Davon ist eins für ein user-definiertes Subpanel freigehalten (Shift+9). Ich habe allerdings keine Ahnung, ob FSMap das überhaupt nutzt
  10. Pressing FPL three times will open the current flight plan. There may be something wrong with it. Please zip up all files from your FSDigital-AviationPA31T CheyenneFlightplans folder and email them to *removed* After you've done that, just delete the (alphabetically) first flight plan file from this folder and try again.
  11. There are two ways to solve this problem: a) Do NOT install FS in C:Program Files - OK, this only makes sense if you do a new installation anyway Grant "Full Access" rights to the user group "Everybody" in the Properties window for C:Program Files (or C:Program Files (x86) if you use Vista 64)
  12. The BAe will need an updated panel.cfg file. I think I will do this once I'm finished with the current work on the Cheyenne and ATR (F1, not EW).
  13. No, it is and will always be SP2 only.
  14. This happens when you activate the DirectX 10 preview. Switch back to DirectX 9 mode and both aircraft will work just fine (well the Katana will have a few more issues in dusk/night/dawn and during rain but we're working on that and hope to release a fix very soon).
  15. That's just like the real thing. It's a spring loaded switch that starts a de-ice cycle (I don't remember how long it was). After the cycle is complete you can start a new one by pressing the de-ice switch again. I think Piper did this as a measure against overheating of the de-icing equipment.
  16. I tried to reproduce this but no luck yet, so I need some more information from you. - What kind of crashes do you get? Blue screen or just CTD? Do you get any error messages? - I there any way to reproduce a crash most times/everytime? If there is, please give me a detailed description of how to do it. Thanks a lot.
  17. This problem has been fixed. The fix is going to be available as part of v1.01 next week.
  18. That's why the PC-12 and Twin Comanche were mentioned. Nothing else. Just because Grahame used them as an example in his initial question.
  19. That is because you directly change the heading by using FSUIPC. It should work fine if you assign the buttons to the "increase heading bug" and "decrease heading bug" shortcuts in FS itself.
  20. Did you flip the GPU switch? It's the little silver switch near the ammeters and voltmeters on the overhead panel. (It's real counterpart is for something else, but some people don't want to see the GPU at all times so we introduced that switch - in the first version for FS9).
  21. @gwolb: Please DON'T spam other threads with the same error message. Open a new one exactly for this one problem and also please only on one forum, not DA and Aerosoft (preferrably DA). There's only one person who deals with problems at this point and that's me. Posting in multiple threads and forums will only slow down things as I have to read/answer more and have less time to fix things. Thank you. @Everybody else: Please: one thread for one issue! Don't mix things. And - if possible - ask questions/post problems in the DA forum, not here. Thanks a lot
  22. A missing userwpt.txt means that somehow the installation has failed. Please check <FSX Folder>Digital AviationNavData for it. I think, the low framerates might somehow be related to that (if one file is missing, it's likely that other things went wrong too).
  23. The NAV1 frequency mustn't be a valid ILS frequency. Otherwise the rocker switch won't work. Valid ILS frequencies are defined like this: - the whole part of the frequency is less than 112 - the first digit of the fractional part of the frequency is an odd number. This means: 108.10, 108.15, 108.30, 108.35, 108.50, 108.55, .... 111.55, 111.70, 111.75, 111.90, 111.95 Hope that helps :wink:
  • Create New...