We are looking for two additional A330 pilots to join our advisory team.  We will ask for credentials (sorry for that), but if you are willing to assist contact us on mathijs.kok@aerosoft.com

Jump to content


  • Posts

  • Joined

  • Last visited

1 Follower

About BudSpencer

Recent Profile Visitors

2872 profile views

BudSpencer's Achievements


Newbie (1/14)

  • Dedicated Rare
  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done

Recent Badges



  1. I fear exactly the same. Why? Because it is beyond me how a further improvement wouldn't be possible with the current recordings??! Unless someone has coded the whole sound, protected it with a password and then immediately left Aerosoft, so that no other person there has any more access to the sound files (I don't think that's the case), I see no reason why the current sound set couldn't be improved in the simple matter of enabeling the tone pitch to go up and down, like any person who can open the config file should be able to. Obviously someone at Flightsim.to already did a makeshift mod for it. So, the developer himself should be able to access his own files as well^^ I appreciate their approach to rework the whole sound (even if I think some small mods at the right place would be enough), but I'm not too confident with the upcoming result.
  2. Agreed 100% !! This is exactly what I wrote in another thread about the bad sound transitions before the fix. It's just the frequencies that didn't change at all with increasing engingne power, and that still don't even a Hz after the patch! And somehow I would have guessed that this main problem wouldn't be fixed at all in the announced fix. I've never ever attacked a developer for anything technical in detail, because I have no clue of programming, nor with designing. But as an experienced musician, the only thing I really got (even without an app like the one shown above) are the variables in the sound files of the aircraft (at least in FSX/P3d times). And so this is the first time that I really think the sound designer of this professional product has no clue what we're talking about if we're talking about PITCH / FREQUENCY change depending on engine power! ...as good as the samples might be. If yes, I'd like to know a single reason, why this was released like that (twice)?! Sorry, this is really unbelievable, at least if it won't be adressed anytime in future. After listening to a youtube video of the FIXED version, I saw my concerns confirmed. I won't buy this, at least not if the only words by Aerosoft will be that most of the customers would be happy with the sounds... or the the sounds were recorded by professionals from the real aircraft... that the loss of sound quality in youtube videos would be to blame... or anything else that just tries to "talk" the problem away. @Payt Laros: Thanks, now after decades of trial and error with the numbers, I've learned that there is a program to visualize those variables and transitions.
  3. Folks, no one ever spoke out the exact problem of the Twin Otter sound. That's why I'm writing here in the hope that someone reads it who is really working on a fix: The 2 most important things that makes an engine sound appear "smooth" is: 1) a proper cross-fading of the volumes from one sound recording (yes the *.wav files) to another. 2) a proper change in frequencies that match the next sound file. ...given that there are proper sound recordings in those files are correct. From what I can hear in the youtube videos, there's nothing wrong with the recordings themselves, and there's nothing to little wrong with the fading of the volumes. But there's a lot (!) wrong with the frequencies of the files, because they don't change at all or only very little while increasing or decreasing power. I've seen the exact issue years ago at Carenado's C 206 (the old one) and with their Seneca II. Various people claimed to have made it smoother by editing the sound.cfg then, but did exactly nothing to the core of the problem: the spooling up of the frequencies of the files. So, at that time, I fixed it myself by adjusting the "rparms=..." entries in the sound.cfg with success. OK, it took quite some time, because if you have no app that visualises this for you - and I don't know any - it's pretty much trial and error, until you come close to what it's right. But it works. So, in short, here's a generic example from P3d (same thing since FS2004 or even 2002, I believe): [Spool-Sound1] filename=Spool1 => name of the sound file, minus the .wav extention in its name (...) rparams=0.6000,1.000000,0.87000,1.3000 => ...which means: At 60 % power (1st value), the sound engine of FS plays the file with 100% (second value) of its speed, thus as it is recoded. At 87 % power (3rd value), it plays the file with 1.3x (4th value) of its speed, thus pitching up all frequencies of in the file by factor 1.3 It's the same principle like playing a sound file in time lapse, making the music sound in higher or lower scales, or transposing them, as musicians would say. Just with the difference that the sound engine of FSX and Prepar3d is able to smoothen that transposition depending on engine power (I'm sure every aircraft developer can tell more exactly which parameter of the engine power exactly). In Any case, those "rparams=..." define two points within a linear line (I don't know the exact mathematic term in English), that connect engine power to the way the *.wav file is played. And that is what has to be fixed here. I've seen in various aircraft in MSFS that the sound information are packed (pck-file??) so that I can't directly see the sound.cfg or whatever it is called now. But even if the structure of the files might differ from P3d and earlier sims, the musical problem remains the same. You might say now, that you know every single bit of what I've written here, but I'm not completely sure if the proper things are discussed here in this thread, regarding the sound issue. I'm not saying that as a programmer (actually I have no clue about this), but as a musician with an acued sense of hearing: This has not to do with recording quality, nor with sound dynamics (OK, that might be a seperate little problem), but with proper pitching of the files. Thanks for concidering that in the fix.
  4. OK, I can try. But how can I avoid then that there are duplicate assignments (default and FSUIPC) for all my other aircraft in P3d? ...exept removing and reactivating the default assignments every time I switch between the A330 and something else??
  5. Yes, I've checked the tutorial section. Lots of information about the TCA Thrustmaster in connection with the Airbusses, but not with Honeycomb. I should add that I left any Honeycomb profiles untouched so far, because I wanted to avoid any interferings with FSUIPC, which I'm using as the tool for assignments. I'm still not sure, weather Honeycomb profiles are linked to specific "title=" entries in the aircraft.cfg's (like the FSUIPC profiles can be) or if they are globally set. If they are NOT "title" specific, they are no option for me.
  6. Hello again, the problem with the thrust levers still exists. To make it clear: It isn't possible to assign any axis to the throttles using FSUIPC. No problem with the other axes (aileron, elevater, rudder). I'm using the Thrustmaster T.1600 as a sidestick, the Saitek rudder pedals for the rudders and I'm trying to use the Honeycomb Throttles for throttles. Never had a problem with the old Saitek throttles, but only now with the Honeycomb - and ONLY with the AS A330. All other planes work fine with it. To describe the problem more exactly: With any Honeycomb axis assigned, the throttle levers in the virtual cockpit don't move at all, nor does the movement of the physical throttles any effect on the thrust. Moving them just triggers a "click". Then, I tried the throttle lever of my Thrustmaster (for both engines): There, the throttles in the vc are moving, but the thrust settings don't respond to it. Example: The thrust levers show TO/GA, but the thrust hardly increases and decreases to idle a few seconds later, while the throttle levers still remain in the TO/GA position. Even the commands of the keyboard don't show any reasonable influence: I can use F1-F4, and anyhow the thrust increases and decreases, but far from being controllable. With the release of the AS airliners from the past years, there was always an option to click at the config. panel "If your throttles show strange behaviour, check this box"... or similar. Whenever I did this, the problems were solved. Where has this checkbox gone in the A330 config panel?? And why isn't it there any more? What can I do about the problem? The throttle assignments are a complete mess at the moment, as if there were 2 or 3 systems trying to move the throttles at the same time. And thus the A330 is still unflyable because of this here in my sim. A330 version is: (problem already occured in previous versions) P3d v Thanks in advance. Regards, Dominik
  7. 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
  8. 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.
  9. 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
  10. 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
  11. 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.
  12. 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
  13. 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
  14. 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.
  15. 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.
  • Create New...