scoobie

I don't know Dora (have just downloaded her as a part of this new free trial), so excuse me. You know what saddens me? It takes literally 15 seconds to discover it 15 seconds. However... does Dora really have automatic cowl flaps? If so... how can anybody have an axis for it? You can't have both at the same time... I mean... you can't have an "absolute" axis, you can have only "incremental" axis, which is no better than buttons - for cowl flaps at least. Anyway, the axis seems to be available, but as "Button_13" in Lua file rather than Button_15 (picture attached). It IS an "incremental" axis (not "absolute"), so you can map it to a minijoystick, but not to the "steady" axis such as throttle, friction lever, a classic potentiometer etc. Hence, I guess, it didn't find its place in default.lua. Apart from that... something's wrong with this axis anyways - it moves cowl flaps in "jerky increments", not at all smooth (as do keyboard commands). I don't know why. So... even if one changes Button_15 to Button_13, I don't think you'll be happy with it. Buttons/keyboard just work better for this. I'm sorry - I may be missing something here - but if it's true she's got some kind of auto cowl flaps, you basically CAN'T have a nice, absolute axis for it. (Of course absolute would be very nice to have as you'd see the position of flaps by simply looking at your hardware control assigned to it).

Thanks for the tip, @Old Chap! I've stumbled upon this as well. It really looks like a bug - both versions apparently were meant to be separate - they have separate folders, both... IIRC both need separate export scripts to the DSC Stream Deck plugin (as two separate Spits), but in DCS GUI, in that drop-down (in control assignments window), you can only select one Spit. I also had the impression that my controls got mixed up somehow, i.e. changes I made while flying CW were "invisible" when I jumped into the elliptical wing version or vice versa. Something's wrong with it.

[Deleted. I need to practice reading more ] Regardless of that... I deeply/sincerely believe there is no need to apologize, Sir - you spotted something fishy and dug into it to figure out what the hell was going on. I can't see anything wrong in that - on the contrary! Digging, questioning, challenging, examining - that's the way to go. I can only thank you for that!

Hi, I've noticed it, too, but... when they don't fire, I start swearing and go crazy on my HOTAS - I press all the buttons I've got 7 times each and after a while rockets start working. Perhaps pressing all the buttons has nothing to do with it, maybe it just takes some time for the plane to "recognize" the new set of rockets? Or maybe among all these buttons is one that does the trick? No idea But yeah, basically it's like you say. They respawn, but won't fire, at least not "out of the box". EDIT: Wait a second... I'm not at home, so I can't check now... Does the Jug have this... this black "window" with white number in it - the one that shows which "rocket station" is going to fire next? I might be mixing up aircraft in my head, I don't know. If so - maybe this goes out of sync somehow? And all you need to do is to press weapon release a number of times until the window again reads "1"? Or something like that? I'll give it a go at home today.

Have fun!

(I've got 1060, too. Jug seems to be a bit "heavier" than other warbirds. Can't see a difference between the others.) Hahaha... what an excellent guide, 100% true! People are different, so please take everything with a pinch of salt (it's your money and your flight simming, not mine). TL;DR: Buy the Spit and live happily ever after (Just set the pitch axis response properly for you gear!) Useless elaboration: If you're NOT new to flight simming or RL flying, but you're kind of new to "proper" gun dogfighting... for me it was the Spit! This is the plane that somehow helped me start wrapping my head around the whole concept. I'm still next to useless, I admit, but before I took my time in Spitfire, I had been like it says in this guide: "Goddamn it! I bought another warbird, but it's bloody useless just as all the others!" Obviously the fault was in the driver, not the planes. When I started playing with the Spit, after mere 5-10 hours suddenly something clicked loud in my rusty brain and... now I can somehow fly even all those other planes which previously "sucked", not overly competently, but I can try and fight in them at all - which is true miracle on its own. So somehow Spit paved the way to dogfighting in other warbirds for me. I think I know the reason - if someone is such a noob like me, the only "patent" you can come up with when dogfighting is just turn. That's all - turn like a monkey, nothing else. The "boom and zoom" slang is good for Martians, not a newbie. Spitfire turns like a dream, so it will let you stay in the fight and practice more. Then you discover that you can actually add some vertical maneouvering to that. Then this, then that, gradually you can add new tools to your "dogfight workshop". I'm still very early in this pursuit (I'm not "ambitious" about flight simming, not a bit, I'm taking and enjoying my time), but now it's become so incredibly pleasurable! Of course the Spit isn't the easiest warbird on landing roll, so if you still need to learn how to take off / land (only then how to dogfight), you'd be probably better off buying something easy in this respect - e.g. the Mustang. OR - a better option - buy the Spit either way and just get down to practicing until you learn how to land, it's definitely less of a hassle than bad dogfighting, right? For starters it helps to keep about 5% of wheel brakes on landing (I used that grey "friction" lever on my TM Warthog throttle to pre-set brakes on final) - she gets calm with this. After a week you'll feel so ashamed of doing it that you'll try without brakes - and you'll learn that in 2 hours, take my word for that. German birds don't have a rudder trim, so you will tread on the pedals a lot. If you don't have pedals (say a twist grip instead), you may find it a nuisance. On the other hand German planes don't have the RPM lever, so if you have a single engine throttle - they're good for that. Kurfürst is an extremely potent dogfighter, probably best in the whole flock, while both Fw 190 aren't (IMHO) so good for starters. Especially Anton isn't (it's got its own secret powers, but it isn't a pedigree dogfighter per se). Now... I don't think the Jug is best for your first warbird. It's a beautiful module (no doubt!), but it's got that wobbly nose and... I don't think it can be competent in A2A in a newbie's hands (like mine). Mustang is overall a great plane, but Spit feels (to me) easier when you're taking your first steps in WW2 A2A. Another approach - pseudomathematical one. Given are two functions (for A2A qualities): y = f(competent) - most likely Kurfüurst wins here (but difficult take-offs) y = f(easy, competent) - the Spit (but difficult landing rolls and ground handling rather annoying) The aforementioned guide is true in another respect - you'll want to buy all the warbirds anyway, so at the end of the day it doesn't matter I just think that Spit is a great first choice (if you can land).

And tardigrades are believed to be able to survive in outer space From a few kelvins to above 100°C... and they're living creatures. And humans are warm-blooded, kind of animals that are extremely choosy about their body temperature. It's just not the best comparison, really. Life is different from just chemistry. I don't know what kind of battery (e.g. lead acid?) and how "big" the battery Huey has, and how many amps it needs to spool up its engine to the RPM good for delivering fuel, but incapability of starting it at -12°C may or may not be correct. Car engines definitely have no problems with starting at this temperature, provided they have a healthy battery and they're basically healthy themselves. -12°C is no big deal. Now, -40°C is a whole different story - ask Russians, they know all about it (or Scandinavians, Canadians). -40 - bad, -12 - meh, let's go. Sure, the startup will be harder, but still it's "let's go". From the electrical point of view the internal resistance simply rises in cold (the true chemical reason behind it may not be that "simply", but I know nothing about it), so when you try to draw high amps, the voltage dips and she goes boo... ooo... (sinister silence now). The fact that they may be using external power to start the engine does not have to neccesserily stem from the fact that the aircraft itself cannot start at low temp., but may be (I'm guessing) due to the fact that you don't want a "tired" (heavily drained) battery once you're in the air. If your generators fail, the battery is your last power source. Gyro-driven instruments have gyros driven either by air or by motors. Maybe it's motors in the Huey? (I don't know.) You don't want your instruments to die just because you used your battery for the startup, instead of readily available GPU at the airfield. You may also need your radio etc. No power, no fun. This may be the reason - safety precautions. On the other hand look at this - it's -12 (Celcius) outside, you started her up using GPU at the airfield, flew away, landed in the wild, and you had to shut her down (let's say for 20 minutes, so you didn't want to burn fuel for that long). Now what - do you need to go home on foot because Huey can't restart? At mere -12? Sure, Russians have heaters and stuff, but at -12° they don't even close windows in their bathrooms. For them it's "chilly" They're thinking about -40°C or so. So, really - I'm not sure if the OP's question is illegitimate. Being unable to start at -12°C seems rather poor - admittedly though - to an utter non-expert. It would be great to hear from people who know more about it, or maybe have hands-on experience

Hi. ATC people in DCS always give you QNH in inches Hg, while many "metric" aircraft use hPa instead. You may squander one of your Stream Deck's buttons to have a "live calculator", which always shows your altimeter's current setting both in hPa and inHg. When the guy/gal tells you "altimeter 29.63" you just turn the knob in the cockpit and look at the Stream Deck until it reads 29.63. Once you're finished, the altimeter setting window in the cockpit will read 1003.4 hPa (which is 29.63 inHg). No need for calculators, conversion tables etc. See the picture. Another advantage (a side effect, actually) is that in some A/C you can't read the setting as the digits are so minute, so the Stream Deck gives an enlarged version. Recipe: Use New StreamDeck Plugin by @ctytler Add to the export script for your plane something like below (CAUTION: This is just an example which works in the Spit! For other aircraft you need to modify it accordingly.). function ExportScript.ProcessIkarusDCSConfigHighImportance(mainPanelDevice) (...) local hpa = 800 + 250 * mainPanelDevice:get_argument_value(29) ExportScript.Tools.SendData(2029, string.format("%.1f", hpa) -- altimeter setting in hPa... .. "\n" .. string.format("%.2f", 29.92 * hpa / 1013.25) -- ... and in inHg ) (...) Then assign it in Stream Deck as in the picture below. The very picture shows how it looks on the real button. Done.

That's exactly why these forums are so worth reading! Thanks for the great tip. I was just about to create "fixed views" (those Ctrl-Num0, then tap NumX) for those damned fuel gauges as my ancient TrackIR 3 has a rather narrow field of view and likes to lose track when I look down there, on the floor. I've concocted a mnemonic for that (by brain is rusty, so I must help it): "Left-handed (people) are odd" *) - so I know WHICH tank should be on when. Bob's your uncle, I can remember the rest. *) Obviously there's nothing odd in being left-handed, lots of people are.

You're incredible, dude! Thanks a lot! Your checklists are so "dense", packed with lots of additional information and at the same time clean and somehow... tasteful. Reeeaaaly great job! We owe you a crate of beer... CATCH!

Hey, Weegie! TBH I have no idea if this is going to teach my feet "play the rudder" in warbirds, I only hope so But even if it doesn't, at least it may show you that you're uncoordinated in a dogfight (so you're "underperforming") and you may want to correct for that. I've just done a slightly different version for the Spit and I like it more than the previous one for the Jug: - 7 buttons (so odd number), instead of 8, - the middle button is "dead" (doesn't do anything, works only as a "separator" betweeen left and right slip, so the eye can easily catch it), - scale is more "nervous": <0.3, <0.2, <0.1, >0.1, >0.2, >0.3, - all this is done in the top row of buttons. Technically it's an inferior scale (only 6 buttons work, instead of 8 as in the version for the Jug), but such scale somehow feels nicer. It's more "lively", "faster", I don't know. Of course the Spit is a very different bird from the Jug - probably these different "feels" you get stem from this fact. Anyway, experimenting is the way to go with this, I think

Thank you very much for making this file! It seems to be lacking the "Hardpoint Arm" handles state, though. If anyone's interested add these lines: -- [Hardpoint Arm Panel] [228] = "%d", -- Belly Hardpoint Arm [229] = "%d", -- LH Hardpoint Arm [230] = "%d", -- RH Hardpoint Arm I put them directly under this line from the original file: -- Port Wall ------------------------------------------------------------------------------

Hi, folks! It occurred to me I can have a BIG (!) slip indicator in my Stream Deck XL. My (mini)problem was: 1. I have a new warbird and I'm not sure how to coordinate turns. Sitting in a chair I can't feel slip/skid. 2. The inclinometer in the cockpit is somewhat low on the instrument panel, which forces me to look up-down-up-down all the time (I've got 2D screen and TrackIR) to see both the ball and outside the cockpit. That's why I wanted my "stream deck inclinometer" to be readable with peripheral vision, so that I could look at the screen and still see the slip (more or less would be good enough). I have my SD sitting right under the screen. Since I'm one of the most artistically untalented people in the world, my solution looks ugly. However, it works pretty well. Once I get the feel for rudder in the new plane, I may no longer need this contraption, but for teaching myself muscle memory it may come in handy. I'm using ctytler's great DCS plugin for SD. The patent here is very simple: find slip indicator "variable" in the export script for your plane, then use a string of any two-icon controls from the plugin ("momentary button with lamp", "switch input" or whatever). Then assign "Image State Change" command to this variable (for each of them) and set the appropriate value of the variable - different for each control, of course. Each consecutive control in the row must have a bigger value (in positive or negative values depending on slip direction). For example, in P-47 it is variable "28" and it swings from -1.0 to 1.0, so I set my controls like this: <0.6, <0.4, <0.2, <0.1, >0.1, >0.2, >0.4, >0.6 (I may fine tune the values later on, we'll see.) You can get an idea from one of the pictures below. Credits: @ctytler for his invaluable plugin: New StreamDeck Plugin @nosaMtrevoC (bloody masons!) for P-47D-30.lua export script: DCS-ExportScripts P-47D Thunderbolt .lua script Thanks a lot for your work!

My PC seems to like this crash, so it's easy for me: 1. Turned off Win8 compatibility, because dcs_updater was complaining. 2. Updated to 2.7.1.6709. 3. 2nd mission load crashes immediately (I'm testing other things a bit today and reloading missions quickly) 4. Turned on Win8 comp. mode again, no more crashes (since this is my cure, I assume it still simply "works"). As a side note - yesterday I upgraded to 32 GB RAM and moved DCS to a brand spanking new SATA SSD (from an HDD for masochists) - it doesn't matter a rat's butt as far as this crash is concerned. On my PC of course.

For the record: also for me Win8 compatibility mode seems to prevent 2nd mission load crash. Big thanks for the idea! (I'd never think of that myself.) It's been like 4 or 5 days w/o crashes now, so I hope it's long enough to conclude it works. It certainly seems long enough for me - I was having these crashes every day or every other day at best. No other methods given here really worked on my PC (of those given prior to these 4-5 days, I haven't tried anything else since then). PS. Oh, and yes - as stated above, DCS shuts down long in Win8 comp. mode. First GUI disappears, but DCS process remains running for something like 20-30 seconds more perhaps. I don't really care about it, but I just wanted to point out it happens on my PC as well.

EDIT: [DELETED] I've mixed up two threads. Sorry for making mess

This is a fantastic tip! It just... it never crossed my mind to try and mix "up/down" with "pressed" in a single lua command. So far I've been using "IGN/NORM/MOTOR" switches on my Warthog throttle base. They are (ON)-OFF-ON switches, so I used IGN for cover/uncover and I always wrote a proper "up/down" command for "NORM/MOTOR" to flip the very switch. It's quite nice, but the trouble is you only have two such switches and sometimes you need more. Thanks a lot, LeCuvier!

Yep, this thing seems to be messed up Your post shouldn't be in "Wish List", but in "Bugs and Problems" (missing control assigment). Maybe some good soul can move it there? Until they fix it... If you want to assign it to a joystick - find below what seems to be working for me. Use at own risk! Backup the original file first! First two lines are for 2 separate buttons for cage and uncage, the third line is for a toggle switch (if you don't need a toggle, you don't have to put it in your file). Add the underneath contents as new lines to .\Mods\aircraft\P-47D-30\Input\P-47D-30\joystick\default.lua, somewhere after "join(res.keyCommands, {" (so that it nicely fits other contents you can see there). {down = device_commands.Button_7, cockpit_device_id = devices.AH, value_down = 1.0, name = _('Horizon Uncage'), category = _('Front Dash')}, -- add, originally missing {down = device_commands.Button_7, cockpit_device_id = devices.AH, value_down = 0.0, name = _('Horizon Cage V2'), category = _('Front Dash')}, -- attempt fix, they have it as Button_8 lower down (doesn't seem to work both ways though) {down = device_commands.Button_7, up = device_commands.Button_7, cockpit_device_id = devices.AH, value_down = 1.0, value_up = 0.0, name = _('Horizon UNCAGE else CAGE'), category = _('Front Dash')},

(Please excuse me if this was discussed before. These forums ARE huge.) Currently there's no naming convention for things like "if you hold this button, master arm is arm, if you release it, it goes safe" or for axes that are "absolute" (where position of the hardware control directly translates to an in-game axis position) or are "incremental" (for minijoystick-like controls which "shift" the in-game axis at the rate proportional to the displacement of such control from its neutral position). Such button assignments (let's skip axes for a second) are sometimes called "(joystick special)" (really? it says exactly nothing), sometimes it's "Master ARM (hold) / SAFE (release)". Sometimes it's "Master arm MOMENTARY". C'mon guys - programmers are expected to be more consistent! (It's not their "fault", but team leads could look into it). IIRC there are other ways of naming such bindings in ED modules, these are just the ones I could come up with off the top of my head. So now... how about if ED devs looked into or maybe even considered accepting (for new modules, that is) the Heatblur's system, found in Viggen, which I think is very explicit and dead easy (BTW - kudos for the smart dude in Heatblur): 1. "else" as in "Master ARM else SAFE". If you see "else", it always means "it does this when held ELSE it does that" (never ever the other way round!). By the way - the extra bonus to this system is when you have a 3-way toggle switch. For example (A-10C autopilot): "Autopilot PATH else ALT/HDG", "Autopilot ALT else ALT/HDG" - now you know you can use a single ON-OFF-ON toggle switch to combine both assignments (just as in real Warthog). If you named them "Autopilot PATH MOMENTARY" and "Autopilot ALT MOMENTARY" it wouldn't say it - you wouldn't know so you'd have to plunge into .lua file to see for yourself. 2. "(absolute)" as in "Flood light (absolute)" - this is for axes. This may and I think should be skipped as a default, provided there's no ambiguity in a particular case*). 3. "(incremental)" as in "Pipper depression (incremental)" - for things like pipper depression axis in F-5E (it is incremental, not absolute). These are rare and could be marked as such. Just paint it on the door so devs can see it and Bob's your uncle Yeah, it's not the biggest problem in my life, but it's kind of funny that every guy in ED comes and names these bindings in his own personal way, and then the crowd of users have the privilege to discover and make sense of yet another new "system" (the sixth one in a row) Sober and easy conventions cost nothing (in the long run they actually HELP devs, I guarantee that). Mess costs devs time and nerves. No offence, just a simple idea! *) The particular case is where you have TWO types of binding for one axis, e.g.: Pipper depression (absolute) Pipper depression (incremental) Other than that "(absolute)" would be just unnecessary clutter as the vast majority of axes are "absolute". You expect that, no use elaborating on it. I guess.

Oh, hi... old stuff. There's a grievously mundane elaboration (my attempted "investigation") in this topic: Bombing altimeter (MPC) incorrectly modelled? but I also included a picture there - a huge closeup on the bombing altimeter from the RL manual. I'm sure this picture makes it easier to get my point there.

Thanks for clarifications, Ironhand, Art-J! In that case I'll just try some more tips given in this thread.

This rings a bell! I was getting (and I still am) these "second mission load crashes" routinely, so I did take a few steps recommended here on the forums (pagefile, cleanup & repair etc.). None of them seemed to work except... uninstalling Community A-4E. I unistalled and DCS stopped crashing. So I flew my new Viggen a bit. Then installed it again just out of curiosity, the next day - crashes again. So I flew my Viggen a short bit and went to bed. Then I uninstalled A-4E one more time - no crashes. I wasn't flying A-4E during those days, I just had it installed/uninstalled, that's all. Bear in mind that such tests take time, for example it took me a while to notice that bad things happen on the second mission load - sometimes I only launch DCS for a single mission, fly and exit. Anyway, I thought I found the culprit - community A-4E. Well... no! After a day or two - so quite like "24-30 hours" mentioned by Ironhand - it started crashing again, this time without A-4E. These crashes are always (on my rig) in d3dx11.dll or d3...something...backend.dll, IIRC the name of the latter file. The former file crashes predominantly, the latter - seldom. Another way of DCS "going wrong" (other than just crashing) is that I get this funny "freeze" sometimes. DCS stops in a mission load screen, with progress bar full and "Mission Load Done" status string. The hard drive remains silent (no activity), nothing happens, as if DCS was actually running happily. No crash. You may wait 10 minutes, but you'll find it stuck in this mission load screen. I've never been patient enough to wait longer. It may be just a voodoo story, but I do have impression that every 2 or 3 days DCS has a "good day" and doesn't crash/stop. It happens. The next day it crashes/stops, repetitively, reliably, for a day or two. Then comes another good day. I haven't installed/uninstalled any software on this PC since DCS 2.7 (and in long weeks prior to its release). Likewise, I haven't been even launching any other software than DCS, a PDF viewer and the Firefox (mostly for Youtube) since I can't remember when. No other games, fancy software, nothing. I guess all of this makes exactly no sense, but that's how it works. If today is one of those bad days, DCS will be crashing (or stopping at the "mission load done") until you need to go to sleep. Again, I wasn't patient enough to reset Windows to check if that helps. I'll try that. I'm not sure if people really should do all these recommended repair attemps on their computers. They, like me, do lots of chaotic maneouvers and then spill "fake news" on the forums. A few days ago I was just about to report that uninstalling A-4E solved my problem. Wrong! Maybe if people did absolutely nothing with their PC's it would be easier for the devs to "pigeonhole" users, find a common denominator for those who get crashes. I don't know. Anyway, please take your time (count in days) before reporting problem solved - you may be wrong just as I was. (For the record - I had no problems in 2.5.6. DCS in this version might have crashed... maybe 3 times in a year.)

Got it! Thanks

Hi, if a Viggen "freshman" pilot's opinion may be of any value at all, then... She seems to be worth every penny. (Someone stole my Rb05 controller, though! There's only some kind of stump of the controller sticking out of the console. Damned thieves!) Anyway, you just can't go wrong with aircraft so advanced that it's got Automatisk Fart Kontroll... I wish my bro had had such system when we were kids! Seriously now, I think it's the most "specific" aircraft in DCS of all I've got so far. An antonym to Hornet. A very specific philosophy, doctrine and design. It may be bad, it may be good, depending on what you're looking for. In terms of sheer module quality - it's at least very good (I'm new so I prefer to stick to cursory words), however she definitely looks great - inside and outside, she sounds great+ ("Great+ Pro Definitive Edition") and has a few absolutely riveting systems on board... "Inca pictogram HUD" of sorts and many others. These I'm currently trying to figure out. Absolutely fascinating plane. I think for its time Viggen was an ultra-modern aircraft, I'm really humbled by the engineering put into it. The manual is honest/solid, and while it seems a bit succinct ("mere" 400- pages), I think it's because she may actually be a bit simpler than it appears at the first glance. Swedish is not a problem, you don't have to read poems in Swedish, just learn "TILL" ("ON"), "FRÅN" ("OFF") and a few other words ("fart" included). No sweat.

Yeah, I know about "hold" for trigger safety bracket. I bought Viggy the other day and have absolutely no idea how she works... I heard or read somewhere that the computer (that CK37) is somehow "looking" at that bracket and it somehow (I don't know how) matters when exactly you flip it from safe to arm. It may be rubbish, of course, but if it's not - it occurred to me it would be better if I had more "freedom" in choosing when exactly I flip the bracket, instead of having to keep the trigger half-way squeezed for I don't know how long. I guess I really need to finish reading the manual. Maybe it actually is all rubbish - what I've (mis)heard or (mis)read. Viggy just seems so different from anything else that I feel kind of dizzy Anyways, for those who don't have two-detent triggers - here's a ready to use solution that doesn't require Heatblur's intervention. That's why I posted it.