Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by BudSpencer

  1. Hi there, a new strange problem occured while using any Airbus since I've got my new Honeycomb Bravo throttles. I've intended to use FSUIPC for the axes and LINDA for buttons. So far, I didn't use any profile in the Honeycomb software, as I wasn't sure if those settings were "global". In any case, I want a certain setting of axes to be loaded automatically with a certain aircraft. And that's what FSUIPC can do very well. Now to the problem: When using the Aerosoft A330, the throttles don't move at all, even when I use the same FSUIPC profile that works without a problem with all other addon aircraft such as PMDG, TFDI,... It doesn't matter wheather I use "Send direct to FSUIPC Calibration" or "Send to FS as a normal exis" - When I move the hardware throttles, nothing happens in the cockpit but the click of the sound of the throttle detents. The FADEC section of the configurator - as described in the manual - isn't there anymore. So, nothing to switch there.. When using the FSL A320, he throttle levers in the either start halfway to full throttle (only half the range that it should be), or they work in the opposite direction. To make it more exact: You have 2 options to set the axes in FSUIPC: 1) Axis assignments => Send direct to FSUIPC Calibration => Assign "Throttle1" and "Throttle2": Then I can influence the direction in "Joystick Calibration" by ticking or unticking the "Rev" tickbar at the corresponding Throttle setting (all the other axes need this setting with my Honeycomb). But this way, the throttle movements in the Airbus effectively start in the middle of the throttle range in the VC and ranges to TO/GA - so only half way of what it should be. No chance to bring it to idle with the Honeycomb throttles. 2) Axis assignments => Send to FS as a normal axis => "Throttle1 Set" and "Throttle2 Set": Then I get the full range from Idle to TO/GA, but in the opposide way (Honeycomb idle causes TO/GA in VC and Honeycomb full power causes Idle power in the VC). In this 2nd option, there is no tickbar to click "Rev". So again, no way to change that. I just can't find a way to tell the Airbus to recognize the full range or the proper direction of my throttles. At first, I thought it must be a special FSL problem. But now, that it doesn't work with the Aerosoft Airbus either, I'm not even sure in which forum I should adress this problem: Here at the AS Airbus forum? At Honeycomb? At FSUIPC? Or at FSLabs? ...as it only seems to come up with the combination Honeycomb throttles and any Airbusses. With the Saitek throttles that I've used before, there was no problem at all, using the same kind of axis assignments. Could you imagine, what is wrong here? Best regards and thanks in advance. Dominik
  2. Thanks a lot! Do the Yoke and the Throttles use the same screws? ...because these are the only things that aren't included in the description of the dimensions from their Website. For the yoke they are not even in the drawing. But at the throttles they are, and I could conclude from the other values how long they should be, as I assume that the dimensions in the drawings are right. I know, but in the long run, I don't trust things too much that are mounted just with a suction pad. At least not for things that you touch weekly or daily over years. Thanks though.
  3. Hello flight simmers, I've already ordered the Honeycomb Throttle to replace my aging Saitek and I'm thinking about to replace my older CH Yoke with the Honeycomb Yoke as well. But before I order anything: Can anyone tell me, how many centimeters the screws exactly need under the tabletop to be mounted?? I've got a desktop with 2 layers: One lower for keyboard and mouse, and one higher (that is a bit further away from the desk chair) for monitor and in my case to mount the throttles and the Yoke. My CH Flight Sim Yoke LE had no problems with the space between those 2 tabletop layers, and the Saitek Throttles didn't either. But the screws on the Honeycomb anyhow look bigger. How much space do they need exactly under the desk? Thanks in advance. Best regards, Dominik
  4. Hello flight simmers, I might need a bit of your advice on a possible purchase of a new monitor. At the moment, I've got an ASUS VS247 24'' as my main monitor. A year ago, I got a smaller Hanns-G.... whatever for free and have been using it as a second monitor. Although a second monitor in general was a huge improvement over a single one, but the 2nd monitor is really old and not very good. The direct comparison always reminds me how of much better the colors on the ASUS are. I got the ASUS a few years ago, I've actually bought 2 then: One bigger (I guess it was 25'', I can't remember exactly), but I decided for the smaller ASUS and took the other one back to the shop, because the ASUS was so much better concerning the colors and, above all, the quality of the image when viewed from different angles. What's more, the ASUS has nearly zero glow, whereas the other one is glowing like a sunrise^^ So, with the increased time spent in front of the screen for home office - plus the still amazing views in P3d v4 - took me to the decision to kick off the smaller no name monitor, use the current ASUS as the second monitor instead, and go for a new one as the main monitor. And the big question is, which one. On the one hand, I've always been happy with my ASUS, but if I go for a new one anyway, I could maybe need something bigger. However, I don't want to lose too much quality just in favour of the size, nor do I want to spend 500€++ for it. These are the 4 options, which I'm uncertain about yet: - Buy another ASUS, very similar to the current one, just bigger (probably the cheapest option and a relatively reliable one) - Buy a curved one with similar capacities than the current one, maybe a bit bigger - Buy an ultra wide one (straight) - Buy a curved ultra-wide one, such as the Xiaomi Mi 34'' Gaming monitor (probably the most expensive option) Does anyone of you have any good suggestions what is worth buying in that situation from his own experiences switching to a new monitor. For example: How much better does a curved monitor make FS experience? And how much better does an ultra wide screen compared to a 16:9 Also important: Does anyone of you have comparisons, how much performance in P3d v4 is lost by the additional pixels it has to deliver at an ultra wide screen? Unfortunately, due to the lockdown, I can't go to any shop to watch several monitors "live". My CPU (i7 9700k @4.4 Ghz) does fine and stays cool. But my GeForce 2060 Super is working pretty hard. Visually, it does a very good job, but it's getting 70°C+ frequently and the fans are howling pretty often, especially in clouds. Thanks in advance. Best regards, Dominik
  5. I've spent 140€ for a single aircraft addon, and I don't regret a single cent of the investment, because I have flown it hundreds of hours and I will keep on doing that with great pleasure. I think flight simmers think a bit different than the typical "gamer". For example, I have a lot of friends, but no "gaming friends", as I have absolutely no interest in "gaming" - I fly FS because I'm interested in flying and can't afford a real aircraft and fly that around the world.
  6. Liebe FS Community, ich nutze seit mehrern Jahren P3D v4 und bin sehr zufrieden damit, sodass ein Umstieg auf MSFS so schnell nicht in Frage kommt. Allerdings strecke ich hin und wieder mal die Fühler aus, um zu sehen, was dort allers geht und was nicht, sodass ich doch eines Tages in der Zukunft mal zum neuen Simulataor switchen werde. Ein wichtiges Argument dafür: AI Traffic! Hat damit schon jemand Erfahrung oder einen Überblick? Man findet ja viele schöne Screenshots über Szenerien, Flugzeuge und die Grafik allgemein, aber an AI Flugzeugen hatte ich dort bisher nur solche "generic" Flugzeuge gesehen. Die sehen zwar besser aus als die fiktiven Airlines in FSX oder P3d, aber es wäre für mich immer noch nicht im Geringsten ein adäquater Ersatz für meinen bisherigen AI Traffic in P3d. Den hatte ich mit bestehenden AI-Modellen (FAIB, FSP, Aardvark,...) und Flugplänen in Textform über die Jahre komplett selbst erstellt, um immer die Kontrolle über Updates oder Sonderbemalungen zu haben. Dass ich diese Arbeit nicht zugunsten eines fiktiven Verkehrs in MSFS über den Haufen werfen will, scheint logisch. Daher die Frage: Kann man mit den P3d v4-Modellen (OK, teilweise auch noch FSX-Code) in MSFS irgendetwas anfangen? Und gibt es für MSFS irgendetwas vergleichbares wie TTools, womit man die Flugpläne in Textform in brauchbare Dateien für den MSFS kompilieren kann? Gibt es überhaupt irgendwelche Aircraft-Modelle, die im MSFS für Repaints und den AI Traffic brauchbar sind? Ich hatte gelesen, dass MSFS "live" reale Flugpläne generieren kann. ABER: Geht das, dass die auch von entsprechenden Flugzeugen samt Bemalung geflogen werden? Das mit dem Live Traffic ist gut und schön. Aber mich interessiert viel eher, ob z.B. in Stuttgart Eurowings, TUIfly, Lufthansa, oder SunExpress-Maschinen stehen und fliegen, als ob irgendwelche Phantasie-Airlines einen realen Flugplan abfliegen. Danke schonmal im Voraus für bisherige Erfahrungsberichte! Gruß, Dominik
  7. Hi Yannick, Was genau meinst du mit den "neuen" Eurowings-Lackierungen? Grundsätzlich ist es möglich, manuell Liveries hinzuzufügen, sofern es für das entsprechende Modell welche gibt. Allerdings müsstest du die ensprechenden Einträge hinter "title=" in der aicraft.cfg auch in deinen Flugplan einbinden, um sie auf den Flughäfen auch zu sehen. Dazu brauchst du den Flugplan in dekompilierter Form, also in Textform mit den Dateien aircraft.txt, airports.txt und flightplans.txt. Dort kannst du dann den einzelnen Flugplänen bestimmte Flugzeuge zuordnen, so auch deine neuen Liveries. Das bedeutet allerdings, dass du dich in das System der Flugpläne einarbeiten müsstest. Ich kenne zumindest mal keine einfachere Lösung, um individuelle Wünsche beim AI Traffic an bereits bestehenden Flugplänen umzusetzen - auch keine kostenpflichtigen. Gruß, Dominik
  8. To be exact, do you think the beta range can finally be properly simulated?? And: What are the chances that the ground handeling (gound friction!) can finally be made as it should be in the new simulator? If those 2 things can be done well, then it will be one of the first addons I will buy for MSFS, when I'm gonna get the new sim at some time in future.
  9. Kann ich so pauschal nicht sagen, weil der Umschwung bei mir damals von einem überladenen P3d v3 auf einen nackten P3d v4.0 stattfand. Ich hatte aber immer das Gefühl, als ob v4 bedeutend flüssiger und wesentlich stabiler lief als v3 - und damit meine ich nicht nur OOMs. Außerdem hat sich mit der Einführung von Dynamic Lights und später auch PBR in v4 auch visuell einiges getan - sofern das jeweilige Addon es denn unterstützt. Ob du jetzt das Framerate-Wunder erlebst, bezweifele ich. Aber wenn das vorher auch kein Problem war, dann glaube ich auch nicht, dass es jetzt plötzlich eins wird. Die große Frage beim Aufrüsten ist für mich mittlerweile: Was packt die CPU so alles? Ne neue Grafikkarte hat man relativ leicht eingebaut (auch wenn sie als Einzelteil teuer ist), weil PCIe 3 als Anschluss immer noch aktuell ist. Und RAM hat man auch leicht dazugebaut. Ich denke diese beiden Komponenten werden bei dir früher oder später dann auch fällig, sobald du nen 64bit-Simulator hast. Denn der kann ja gerade diesbezüglich der Hardware mehr abverlangen. Aber wenn man mal ne neue CPU mit nem anderen Sockel braucht, dann hat man gleich das volle Programm auf der Liste. Und wenn es nicht um Ladezeiten, verschwommene Texturen, fehlende Autogen scenery,... geht, sondern um reine fps, dann scheint die CPU immer noch zumindest eine mitentscheidende Komponente zu sein. Und die scheint ja bei dir mit dem i7 ganz gut zu laufen (im Gegensatz zu meinem i5 3570k, Übertakten hin oder her...). Wie gesagt, das Upgrade meiner Grafikkarte (siehe oben) brachte einige erfreuliche Effekte, aber kaum bessere fps auf den großen Flughäfen. Das kann ich leider gar nicht sagen. Ich hatte nie XP. Und über den FS2020 wird man es ohnehin erst sagen können, wenn er mal draußen und richtig getestet ist. Beide sind für mich im Moment mal keine Option, zumal ich eh nur einen Simulator aufm PC haben will. XP scheitert bei mir an den verfügbaren Addons, die ich - im Gegensatz zu neuen P3d-Versionen wirklich ALLE hätte kaufen müssen. Hin und wieder hört man, dass der etwas "moderner" programmiert sein soll und weniger programmierte Altlasten mit sich trägt wie etwa P3d vom FSX aus der Microsoft-Zeit. Aber keine Ahnung, was man darauf geben kann. Und beim FS2020 weiß man eben auch noch gar nicht, wie kompliziert das Upgrade bestehender P3d-Addons sein wird - oder zumindest wird noch nicht öffentlich darüber gesprochen. Einzig und allein von PMDG ist mir bekannt, dass deren 737 NGXu zumindest zu dem Zeitpunkt, zu dem ich sie gekauft hatte, ohne Aufpreis die Lizenz für den FS2020 beinhaltete. Weiß nicht, ob das Angebot noch gilt. Aber bevor das nicht alles klar ist mit der benötigten Hardware und den Addons, bleibe ich erstmal bei P3d v4 und würde mich freuen, wenn der endlich mal richtig flüssig läuft, jetzt wo die Addon-Sammlung nahezu vollständig und perfekt ist. Neuland würd ich gerne zunächst mal nicht betreten für die nächste Zeit.
  10. Ja, ich hatte auch immer die Philosophie, erst dann in neue Hardware zu investieren, wenn ich genau wusste, dass ich sie brauche. Würde ich an deiner Stelle auch mal so machen. Aufrüsten kann man immer noch. Und der Kaufpreis von P3d v4 ist ja noch vergleichsweise gering im Gegensatz zu den meisten Hardwarekomponenten.
  11. Die große Frage wäre auch noch, ob es stimmt, dass P3d v5 bzw. DirectX 12 direkt abstürzt, wenn der VRAM über das Limit geht oder ob das nur ein Gerücht ist (??).. In P3d v4.5 jedenfalls passiert das nicht. Da ist es nicht schwer, mit einigen Settings die RTX ans VRAM-Limit zu bringen, und die GTX 970 war zuvor quasi permanent über dem Limit. Abgestürzt ist P3d dadurch aber nie, sondern die Darstellung litt einfach darunter. Es gibt Foren, in denen behauptet wird, das sei jetzt anders bei v5. Und der Zweifel daran ist einer der Hauptgründe dafür, warum ich vorerst mal noch bei v4 bleibe.
  12. Ich wundere mich eher, dass du bei P3D v3 nicht ständig OOMs bekommst. Das fand ich damals unausstehlich. Kommt eben immer darauf an, was man nutzt. Aber falls du bisher noch keine solch komplexen Addons wie die von PMDG auf dem Rechner haben solltest: Mit der PMDG 737 + 777 und auch nur irgendeiner halbwegs vernünftigen Scenery hatte ich damals keinen Spaß; war ein reines Glücksspiel, ob es einen OOM gab oder nicht. Mit dem Erscheinen der 64bit-Version hatte ich damals nie wieder v3 angerührt, trotz vieler Addons, die damals nicht direkt kompatibel waren. Ich selbst bin damals mit nem i5 3570k @ 4 GHz, einer GTX 970 und 16 GB RAM klargekommen. Aber mit der Zeit wurden die Addons für P3D v4 (oder mittlerweile v5) natürlich auch anspruchsvoller. Mittlerweile läuft er zwar immer noch sehr stabil, aber einfach zu langsam. Deswegen hab ich jetzt wohl oder übel nen Rundumschlag an Hardware-Update gemacht. Übrigens: Ich hätte mir mit dem Umschwung auf ne neue Grafikkarte westntlich mehr Unterschied erwartet - gerade weil so viele Leute sagen, dass Prepar3d mit der Zeit immer GPU-lastiger programmiert wurde. Aber mit dem Upgrade von GTX 970 auf jetzt RTX 2060 Super (8GB VRAM) ist in Sachen FPS nicht wirklich viel passiert. Ja, er lädt schneller, die Autogen Scenery erscheint nun im Anflug und es gibt dort keine verschwommenen Texturen mehr. Und die 8 GB VEAM machen wirklich viel aus, wie Oliver schon sagt. Aber die FPS sind mittlerweile auf großen, "modernen" Airports weiterhin miserabel, fast unabhängig von den Settings. Im Endeffekt ist P3D dann doch noch CPU-lastiger als ich dachte. Hab jetzt ne i7 9700k bestellt mit dem ganzen leidigen Zeugs, was ich aus Kompatibilitätsgründen ebenfalls upgraden musste (Mainboard, Arbeitsspeicher,...). Aber einmal muss man da durch. Ist mit der Hardware auch nichts anderes als mit den Addons: Wenn man länger nicht mehr upgegradet hat, muss man gleich tief in die Tasche greifen und gleich sehr viel erneuern, weil eine neue Komponente die nächste impliziert (neuer CPU-Sockel => neues Mainboard => nur noch DDR4-RAM,...). Aber wenn ich ehrlich bin: Wenn ich dafür jetzt mit der neuen Hardware + P3d v4 oder demnächst v5 die nächsten 7 Jahre Ruhe hab (so wie beim letzten Mal), dann war es das Wert.
  13. Hallo Mick, das brauchst du nicht weiter zu versuchen. PMDG ist viel zu komplex, als dass man da einfach mal Dateien kopieren kann und ausprobieren kann, ob's geht. Bei Szenerien kann das mal noch funktionieren, aber selbst da wird's zunehmend schwierig und fehleranfällig. Außerdem verkauft PMDG separate Lizenzen für FSX und P3D. Und die legen größten Wert darauf, dass die eine nicht in dem jeweils anderen Simulator verwendet wird. Wenn du sie in P3D nutzen willst, müsstest du dir theoretisch die P3D-Lizenz zum vollen Preis kaufen*. PMDG versprach damals (zu P3D v2-Zeiten), dass sie alle nachfolgenden P3D-Versionen ohne Aufpreis unterstützen werden - und daran haben sie sich auch gehalten, selbst beim Umswitchen von 32bit auf 64bit mit Einführung von P3d v4. Bis eben jetzt die neue 737 NGXu herauskam: Die ist ein neues, separates Produkt und ist nur noch ab P3D v 4.4 und aufwärts zu haben. *PS: ...wobei ich sehe, dass die "alte" 737 NGX auf der PMDG Homepage gar nicht mehr mit der P3D-Lizenz zum Verkauf angeboten wird, sondern tatsächlich nur noch die FSX-Version. Vielleicht gibt's die "alte" NGX für P3D noch irgendwo boxed, keine Ahnung. Aber man geht offenbar davon aus, dass - wenn man die 737 für P3d bis jetzt immer noch nicht gekauft hat - man auch gleich auf P3d v4 oder v5 umswitcht. Würde RAM-mäßig auch Sinn machen bei solch komplexem Gerät. Gruß, Dominik
  14. All right, for the case someone might be interested because he has similar thoughts on upgrading his hardware, here's a little update on what I did: - Just tidying up the sim brought nothing than a little shorter loading times. - Deleting the graphic driver completely and reinstalling didn't help either. - Various settings almost changed nothing at all. - Cleaning the inside of the tower was not point either, it wasn't that dirty. So I had to invest. I tried a new graphic card first, not because I thought it was the main issue, but because it was the easiest part to change. Now, I've got the RTX 2060 Super with 8 GB VRAM. What to expect: The blurred textures on the approach have gone, autogen scenery is now ALWAYS there - yay! Even at very dense settings, and I could extend the LOD, cloud and shadow radius a bit. Very good, but fps only improved very little at the big airports. But at least I've tried if it might have been "good enough" - well, it wasn't. Upgrading the CPU means indeed a new mainboard (no octa core for my 1155 socket), and updating the mainboard meant also updating the RAM - because it now really needs to be DDR4 RAM. And that means probably a new Windows 10 licence, because the old one was a free upgrade from a Win 7 OEM licence, which would be linked to the old mainboard, as people say... (?) You see where things go... I hope at least the CPU cooler, the PSU and the case will do their job as well as before. I've now grit my teeth, closed my eyes and ordered an ASUS Prime Z390-P with an i7 9700k and 16 GB DDR 4 RAM, additionally to my new RTX 2060 Super. Don't this new system dare and work brilliant for anything less than the next 10 years of flightsimming I'm gonna report back again how much better it is when it's done.
  15. I would love to see the ATR-72-500 redone for P3d. And I still hope for the PW and GE variants of the A330, even if it would only be visual and sounds. Concerning scenery, I would look forward for a Saarbrücken (EDDR) scenery for P3d.
  16. OK, I'm really not a fps hunter, so as soon as I get 15-20 fps in the worst situations (for example approach to AS London Heathrow in the Wilco Embraer v3 in clouldy weather and with 50% AI traffic and sliders set to medium in the average, I would be perfectly happy. OK, but has RAM to do with fps? I thought that would be responsible for loading textures and thus for OOM crashes if it's too little. I have DDR4 ram installed, which should be the newest component in my system. I don't remember exactly the name of the CPU cooler (Alpenföhn??), but it was huge and at the time I bought it, it had good recommendations, even for higher overclocking. I did some temperature tests in the beginning, and temps never got more than 60°C, rather below 50°C at maximum. The graphic card has the default coolers, but was never overclocked, so I didn't suspect temperature problems here. No smoking anywhere around my house, so the only problem here could be that it has simply become dirty over the time. I should really open and clean it first. But I don't think that's the main issue here. I've feared it^^ Tried to find a way around that because it's so much work. But that really seems the way to go first. Do you also mean a Windows reinstallation? If I'm gonna do that anyway, would it make sense to just switch to P3d v5 then? I mean... GTX 970 and DX12 is something I never really understood if it would work (??).
  17. Hi together, just wanted to ask you about your opinion on my system, which is slowly growing old, and can't really cope with my P3d v4.5 anymore, at least not at big airports with complex planes. So my system is now: - ASUS Z77 MB - Intel i5-3570K @ 3.4 Ghz - NVidia Geforce GTX 970 (4 GB) - 850W power supply unit - 16 GB RAM - Windows 10 64bit, of course - Only SSD hard drives My problem: At most bigger airports with the famous complex aircraft, I get around 12 fps. And under those circumstances, it's difficult to steer the plane, it's really no fun anymore. What is strange: My settings seem to be less and less relevant to it - for example in earlier P3D versions (yes, even v4.X versions), it seemed there was a very noticable difference between the different AA settings. Now, even after deleting the P3D.cfg and shaders, it seems to have ZERO difference wheather I choose 2 x MSAA or 8 x SSAA. Even other settings are not too important anymore. But what is very significant: In the cockpit, fps are a LOT worse than in any outside view of any plane. For example, with the PMDG 737 in Bogota (PKSIM), it's rather common to get 12 fps inside the VC and 25 fps outside. And I'm not even talking about dynamic lights. Furthermore, when approaching an airport after cruise flight, ground textures are often blurry as soon as I've used even a little time acceleration minutes before, and autogen scenery loads VERY late - even too late. I'm ready to invest money into my system, but I'm not willing to pay 1000€ just to be sure everything works without thinking about anything. So, I'm looking for the most urgent part(s) in my system to be replaced. I've heard newer P3d versions are more and more GPU demanding and less CPU demanding. This is why I was very surprised that on another forum, I was told my CPU would be what should be replaced first. Before that, I've thought about a new graphic card ...GTX 1070 or 1080 maybe. But now, I'm uncertain again, which part(s) to replace first?? Or do you think, there is this ONE setting that can kill performance in the cockpit so much? At the moment, most sliders are in the middle. Thanks in advance. Cheers, Dominik
  18. OK, thanks! So does that mean that, as long as I command the MCDU3 to load the aircraft (instant or gradually) BEFORE even touching GSX2, I'm safe? I want to use GSX2 only for the visual passenger boarding, gate moving and push back, but I don't want it to touch any weight data. Last time the aircraft was loaded again AFTER the flight (after parking at the gate) without any influence by me. Even resetting the status didn't help. Could that be that I accidently commanded GSX to load the aircraft via "boarding" and the MCDU3 functions have been blocked as described??
  19. Hi! I've noticed a little strange behaviour of the A330 wile lifting off and touching down: The aircraft "jumps" several times, especially on touchdown, as if there were problems with the elevation of the airport - but there aren't (no problems with other planes). I've read about some issues by P3D that affecet the landing gear, but this shouldn't be a part of it. It looks as if the sim is resetting the elevation of the plane by a few feet several times within seconds. I'm sure it was neither a hard landing nor a tail strike. On the videos I've seen from the Aerosoft A330, I've never seen this behaviour which I experience almost all the times. Doesn't kill the flight, but seems very odd while taking off or landing. I didn't touch any values on the aircraft.cfg other than adding liveries. version Regards, Dominik
  20. Hey! Few questions about loading the Airbus: - Is it possible to reset the whole loading process if the Airbus already has started to load pax, cargo and fuel gradually? - Is the A330 also meant to be loaded completely wihout the external load manager? (Settings MCDU only)? Why I'm asking: I want to plan my flights at Simbrief, including fuel and weight calculations and only load them via the settings MCDU. I've got GSX and use the boarding function, but I don't want to have 2 separate loading simulations which take different times and interfere with each other. Furthermore, I want to be able to load initially, if GSX2 or the Airbus takes too long to load in a situation. So, of course, I've set my GSX2 to detect custom loading of the aircarft. But more than once it happened that the airbus suddenly started to load by itself, sometimes only pax, sometimes it stopped at a certain number, sometimes it loaded everything correct, but very slow. As I did this by trial-and-error so far, I've looked into the manuals to understand the difference between the green script, the green flashing script and the orange one. However in the manuals, I can only find those things explained that are self-explanatory anyway for my understanding. Did I miss a part of the manual? What can I do to be able to control the loading of the aircraft? Is there a way to force the initial loading? Or is it simply the fact that I don't understand how the aircraft loads? Thanks a lot. Regards, Dominik
  21. I have a similar problem. But it's a bit different, so I'm gonna post it here: 1) If I extend the flaps - no matter if F7 or joystick button - the flap lever goes all the way down to the "FULL" position. And so do the flaps. If I use F6 or the other joystick button to retract them again from FULL to the "1" position, this works. Extending them again from 1 to FULL step by step also works most of the time, but not always. But the main problem is to extend them step by step. Not even the virtual copilot can set them. If he does, the flaps lever and the flaps react the same (wrong) way as described: they go instantly to FULL if he wants to set "1". 2) If I retract the flaps on the ground whenever the flap logic commands the "+F" addition to Flaps 1, the flap lever in the VC goes to 0 and the flaps retract. BUT the slats stay out and are also indicated there, while the flap lever is already at 0. If I press F6 again, then also the slats will retract completely. Can't be the real thing, because there would be no physical "knob" to retract the slats, if the flap lever is already at 0. What works fine is the automatic retraction of the flaps after takeoff from the "1+F" to the "1" position. So problem no. 2 is something different.
  22. Hey! First of all, thank you for this very nice A330! There's really a big improvement over the A320 (32bit) versions - the latest Aerosoft airbus that I have owned. But here's my issue: When I click the "doc" rider on the EFB, I get a CTD instead of the doc files opened. Could it be a problem of a wrong path? There is folder named "Documentation" in my "Aerosoft A330 Professional" folder that contains PDFs (for the case that these are the files that should be shown in the EFB). So, that looks right at least. I'm not sure if it is. Thanks in advance. Regards, Dominik
  23. No idea what that is. So I guess no. The only "global" addons I use are ORBX FTX Global, Vector, OpenLC Europe (in this case), Active Sky 2016, EnvTex + EnvShade and EditVoicePack. Plus in this case the described regional addon of LJLJ. I will report when I see any connection between this and other events..
  24. OK, but what else could I try? I've got no idea what direction I should search. Graphic settings maybe? However after the latest similar CTDs all I could do was wait for the next update - which evenetually helped in most cases.
  25. No, I only updated the Navdata for particular aircraft via Navigraph FMS data manager. I didn't do so since the end of 2018 because their charts always seem to be older than their Nav data and I wanted to "align" them a bit more. OK, I'm gonna try that and report back.
  • Create New...