Luzifer

Für die Originaltreue brauchst du am Stick nichts belegen. Zumindest bei mir wurde der Warthog Stick automatisch richtig belegt. Basteln muss man nur für zusätzliche Funktionen. Die einzigen Funktionen die ich dazu noch belegt habe sind der Starterknopf (auf L/G Warn Silence am Throttle gelegt) und Throttle auf/zu auf den Luftbremsenschalter. Hatte ich ursprünglich auf einem der Schubhebel und den anderen für Collective, aber da man den Throttle im Normalfall nach dem Startup nicht mehr bewegt, habe ich lieber beide Hebel zusammen für Collective, liegt besser in der Hand. Sonstige Funktionen habe ich nicht belegt, allerdings habe ich auch noch nicht viel mit Waffen gemacht, dagegen mehr reines Fliegen.

I have reduced curves a lot (10 at most) for the cyclic and even less for the pedals. Curvature makes control around trim more precise but that much worse far away from trim. And in transitions of flight regimes, until you have the time to trim, you need the control authority as well as precision far off trim. Once you have figured how to prevent pendulum oscillations in hover (fixating a distant ground feature is a good practice) then hovering in ground effect is actually relatively easy. Ground effect becomes stronger closer to the ground, so hover altitude is stable with a given collective setting. Taxiing around the whole airfield is a breeze then without even touching the collective. So I got that down within a few hours of practice. Take-Off with transition to forward flight at speed is okay. Landing at the spot I'm aiming at with transition to hover? Oh, I definitely have to still work at that. Half the time I end up somewhere way off. The other half I driver the Huey into the ground. Ahem. So yeah, just practice is all you need, and not a tamed flight model.

Should it be working for carriers, too? Two days ago there were lots of Hueys on the Virtual Aerobatics server going for a picnic on the American carrier and it felt like there was no ground effect. Hilarity ensued. :D It is really hard to hover on the deck and you need to pitch up more to hold position or slow down, and many tail strikes were had. Are these things indicative of missing ground effect?

Do you have weapons active and targeted? That reconfigures the HUD, if you want to go back to navigation mode you have to cancel targetting, there's a button / command for that.

I can't hear the instructor narrating in the training missions. I do hear the radio call "kchk" sound at the start of each narration but then only silence. The text boxes are there, just not the sound.

Basically you have a set of default profiles for every weapon you have in your loadout. Those profiles are loaded from the data cartridge during your startup preparations (as part of the "Load All"). I guess in real life the pilots would set up the profiles and save them to the cartridge during mission planning, we in the sim only get defaults and have to change them ourselves. The "normal" way to attack is to set the HUD as SOI and select the desired profile with the DMS short left/right. That way you can have multiple profiles for the same weapons with different settings set up in advance and only have to choose from them to get all the settings. Creating a manual profile by selecting weapon stations on the DSMS is really just for those situations where you don't have the profile you require and need to set it up quickly. Well, that, and for creating new profiles from scratch without editing or copying existing profiles. The name field is on the left on the first page you see when you view a profile and it's initially empty. One more thing, when you go into an existing profile, set the name field and save you rename the profile. When you change the settings and set no name, you edit the profile. When you both set the name and change the settings then you get a copy with the new settings under the given name.

You are working with temporary (manual) profiles when you select stations directly. There are several possibilities to make those changes permanent: 1. Don't select stations, view the list of profiles and edit the existing profile for the weapons you want to change. 2. Same as 1., but you copy the existing profile to still have the original. Same editing, but also set the name field before saving. 3. Save the manual profile by setting the name field before saving.

That is generally true, but the AMD64 architecture is something of a special case. They didn't just expand the address space, they also added a lot of general purpose registers to the notoriously register starved x86 architecture. Technically these are unrelated improvements that could have been added separately, but since they came together making use of the extra registers boils down to "compiling for 64 bit". To benefit from those the software has to be recompiled for 64 bit, of course. Merely running the 32 bit executable under a 64 bit OS wouldn't help.

I'd add that Außenlasten is specifically external payloads, but that was probably obvious. The best translation for Stirnfläche I could find is "projected frontal area", i.e. the area of the shadow you get when shining wide parallel light onto the object straight from the front. Cross section wouldn't be entirely accurate because that would be a slice out of the object and e.g. for a cross section of a bomb taken from the middle wouldn't include the fins buuuut all of that was, again, likely obvious and I'm just being nitpicky here. :)

I do think that comment by Wags was slightly… naive. When Nevada is released eventually it will be the first map using EDGE and likely the only one for quite a while. So I think players and mission builders alike will descend on it like a pack of hungry wolves and not be held back by such minor trifles like plausibility.:D

Probably the reason the word popped into your head is that "cheat sheet" is a commonly used term for such collections of commonly needed and important functions. There's certainly a lot of cheat sheets for things such as text editors out there, so it's a pretty accurate term.:thumbup:

I'm not sure where I read it, but the new Nevada map is supposed to be much bigger. Also, the "practice mission" comment was with respect to there being no believable scenario for war in Nevada, not because the map is small.

Gar nicht. Entweder du verwendest Ruderpedale oder du musst das über die Tastatur steuern.

That is a good example of something that can't be parallelized. Here a depends on the result of b, c depends on the result of a, d depends on the result of c. So even if you distribute it to more threads, it will end up being done in sequence and nothing is gained but performance is lost. Parallelizing only makes sense when you have multiple computation cores actually running in parallel. Actually gaining something from such a setup requires that the problem can be split in multiple independent parts that only occasionally need synchronization across threads. Lots of problems simply can't be processed in parallel. For those where it is possible, it's hard to do when the code isn't designed to do so from the ground up. Converting an existing code base to parallel execution thus needs a lot of work and introduces a lot of potential bugs in the required synchronization. And you better hope that in the end you gain more by parallel execution than you lose by the synchronization and communication you have to introduce.

No, you don't. Reduce throttle and you will increase descend at the same airspeed. Pitch trim sets speed. Unless you make a radical change, then you would get oscillations around the target speed and descend rate for some time and you should use pitch input to suppress those.

Because that's how physics work and DCS simulates it. If you do it backwards, for example push the stick when you're at correct speed but too high, you will increase descend but also your speed. Then you have to reduce speed with your throttle again, adapt pitch again, … Just do it the right way around and you won't wobble around adjusting another variable because you adjusted the wrong one in the first place, it'll be easier and smoother.

That… does not even make sense.

I don't think there even is such a thing as a graphics card with a single core anymore. The number of compute cores is typically measured in the dozens to hundreds.

Mit nicht überlappen meine ich, dass es keine Frequenz gibt, auf der sowohl das FM als auch das AM Funkgerät funktionieren. Das mit dem Pfeifen kenne ich halt, wenn man eines der beiden Geräte in ungültige Bereiche stellt, also etwa das FM (das erste) auf über 100 MHz. Deshalb dachte ich, dass du vielleicht das falsche eingestellt hast.

Only 800 if you count the D-9 alone, maybe. There were over 20,000 built across all variants.

Geht es um die A-10C? Wenn ja, dann hast du vermutlich das FM-Funkgerät eingestellt. Flugsicherung läuft über AM, das ist das dritte (von hinten nach vorn) Funkgerät. Wenn die AM/FM Funkgeräte aus ihrem zugewiesenen Bereich (die überlappen sich nicht) heraus verstellt werden, dann pfeift es.

If they're wobbling all over the place so much that they actually can feel the acceleration, I'd wager they wouldn't be able to get much refueling done…

Unless they're powered by pressurized air or vacuum, as the flight instruments in the P-51 are.

No, what I read is that Huey and 1.2.4 will be released together.

In movie land, everything that flies makes a Stuka sound when it's diving. Also in movie land, every pilot religiously trims as nose heavy as possible at all times so that their vehicle will immediately dive as soon as they let go of the stick.