Ala13_ManOWar

As a matter of fact, I probably noticed those tiny details (don't get me started on default EdA skins ) sooner than most people if not before anyone else just in the screenshots they had shown all the way to release . I just happen to have a more positive attitude in face of those, still tiny, details. And those don't prevent me from enjoying the sim in it's full glory, I just know I know those things, I notice those things, but not only many people don't notice/don't care, probably most of the people don't notice nor they care, so I'm very happy living with those, still tiny, remember, details instead of running to these forums to point out everything which is "wrong", inconsistent, inaccurate, whatever. If I want those to be better I can download further skins, don't worry, somebody will make them for sure, or even if it's so bad and unacceptable and unbearable to me I can paint those myself to my liking. Maybe there was a time I was bothered by those tiny, minuscule, stupid details but I just can't be bothered any more . Anyhow, I know what I'm watching, I know what I know, I just choose the battle worth fighting. P.S. BTW, you can thank ME specifically for the now correct markings on the IA B-17 . Couldn't make it happen anyhow for default F-86 skins but I told back in the day… P.S. 2 , forgot to mention I also got the Spanish skins in the Hornet to be corrected with accurate markings and bort numbers

Yep, fans made skins aren't tied to copyright laws, but official skins on the other hand… Fictional ones maybe possible, wouldn't recall that particular one, but RL ones probably not with regards to official publishers.

Probably copyright related, same a names in Nevada map hotels, casinos and everything .

Demanding them to be absolute experts in every Air Force in the World about cammo patterns, markings, and everything is perhaps a bit too much to ask for. They do their best, they're software developers, we aviation geeks are only on this side of the barrier not there having to develop every tiny detail of a full module .

Yep, perhaps you're mixing there Early Access, Pre-Purchase, release in Open Beta and stable release (which I don't blame you for ). F1 didn't have a pre-purchase time, which usually means 30% discount, one, two, three months ahead of release, usually as said, not written in stone, but usually goes like that. When pre-purchase period ends (the minute they release it in OB) it's still in EA with a 20% discount, but no 30 as pre-purchase. Usually. Early Access means you're getting the module in advance without being in a 100% finished state. In F1 case we got it being Early Access, right, but there were no pre-purchase ahead of release, hence 20% discount. Early Access per sé anyhow can last whatever Devs think is necessary, it might be months, or even years until Devs think it's complete enough to qualify as out of Early-Access which in turn still doesn't mean it's 100% complete and module can be still under development, just lacking minor things and all, but not 100%. Either Mi-24 and Apache ARE still in Early-Access state as you can check yourself at each module shop place at ED's store, so it actually matches your experience no matter you knew it or not . Still, 20% discount happens because it's Early-Access (very first stages, but no different name) but once it's released, released for good in Stable, that's "real" release, to name it, and discount goes away. Perhaps they could have named it pre-release or something on the like, but too many names and states, I don't know. We're in sort of pre-release state in Open Beta now, still discount, but no pre-purchase discount, but it isn't full released in Stable version, if any of it makes sense . On a side note, the Early-Access subject is actually controversial, some folks think it makes no sense to have an EA label still on modules released years ago, but they do sometimes despite being used by many people regularly. It's up only to the developer when that state ends or how "finished" is or isn't the module to call it one way or another. If they feel it's still pretty much WIP no matter how users feel it, the EA label can be there for a way long time.

Este es el foro en inglés, no tardará en decírtelo algún moderador si continuamos en español (está más abajo la sección en español). El tema es que si el avión real no tiene esos manuales en español, si los controles en el avión real no están en español, pues se modela lo que hay en la realidad no lo que le pueda gustar a unos y otros. Las cabinas con diferentes idiomas se ponen (a posteriori) en muchos módulos pero es una cuestión de cortesía, no de realismo porque lo realista es tal cual está. Pasa lo mismo con los cockpits en ruso y demás. Habrás notado que este avión tiene placards en tres idiomas, por cierto, pues eso . Por cierto, lo mismo para el manual, el manual "en español" del EF-18 Hornet que anda por internet verás que tiene en español el título porque en el EdA se usa el inglés como es normal, así que eso es "lo realista". This is English forum, won't last until a mod comes to tell if we keep like this (in Spanish) (Spanish forum section further down). The thing is, if the real aircraft doesn't feature those manuals in Spanish, if the aircraft cockpit labels aren't in Spanish, so they model what there is in real life and not what people might like or not. Different languages in cockpits are given (at a later stage) in many modules but it's a courtesy question, not realism because what's realistic is how it is IRL. Happens the same with Russian cockpits. You may have notice three different languages in cockpit's placards, so. BTW, same goes for the manual, in the "Spanish" manual for the EF-18, found online, your might notice the firsts sentences and title saying "Spanish manual", but then it's all in English and Spanish Air Force uses English, so that's what's realistic.

Wider explain now upwards.

Agreed on the somewhat too shiny colours on flag and markings, cammo colours though aren't what you think. That's a badly weathered and faded paint, not exactly a different colour. On top of that, patterns in cammoes are usually told by whatever the airforce it is, but patterns aren't that exact same every time. After all, they are painted by human beings who interpret what they can out of a sheet of paper. Believe me, I've made lots of aircraft models and I know what a cammo looks like and how they are and aren't painted. The author of the skin might have just used a different airframe as a reference for the pattern, but still it's spot on for the subject .

For reasons not important here I can't push brakes on my rudder pedals, and I certainly have brakes set either in my Warthog throttle base extra axis and in a spare button of my joystick grip. They both work, they both can be bound at the same time, no problem at all. Axis's controls list is one bind, buttons controls are a different controls list, if you select axis's controls you have to use an axis for the control, but in the regular button's control list you can set all the axis controls to buttons either. They're just two different controls' lists.

But remember it wasn't EF-18M (cockpit picture) all of the time, they were plain A model for many time after they first arrived in 1986, then A+ (alike C, but not completely), then M for Modernised or overhauled (same as F1M) with that fancy super Hornet UFC, but that was only in relatively recent times. It's curious anyhow, and funny since now we know all that equipment close and personal from DCS, how cockpit is a mixed bag. No IFEI but the old analogue fuel gauge already seen in AV-8B and F-15E, new digital UFC and I believe slightly bigger DDIs and definitely bigger new AMPCD, but some other stuff kept from old A equipment. It's said (I wouldn't know exactly since I haven't flown the real deal) software wise it's now at a super Hornet block 1 level, but in a legacy Hornet airframe. Original radar AN/APG-65 (same as AV-8B+) is also kept despite other upgrades, like new F404 engines which weren't the original ones. Interesting mixed bag, yeah.

I believe it works like that in other modules alike, Hornet for instance. You select the radio you want to use, then radio menu works for that selected radio alone until you select another radio to speak/listen to.

I didn't, it just happens like that in every module since DCSW exists as a sandbox with modules added.

Not exactly, it could remain EA for a long time until release status is reached, but discount will only last until it jumps out of OB to stable.

IIRC it works the same in C101, BTW.

I believe it was discussed somewhere else and only M version got something alike a CCIP, but couldn't remember details.

Those are coming from ED at some given time, by the way.

To my knowledge, map teams aren't usually related to other development areas. No need to stop a thing because they have to finish Apache.

I believe I've seen a pic showing an early Spanish F1CE mounting a Matra Magic, but if it were like that apparently they were replaced pretty soon. The Sidewinder main version used was J, and later on I believe there were an L version (or was it N?) because of the all aspect thing, but J model missiles were overhauled to be all aspect so apparently the JULI version was the most common in the end.

Yep, set it to custom curve, best if you use it as "slider" option, and set the curve till AB kick in matches your detent. To illustrate (it's on a Warthog, so most probably useless to you) in custom curve I had to put 40% slider from 40 to 47 and it is spot on to my push throw detent. The two other sides imagine them just tweaked until they're the straightest line you can to AB peak.

Since AB bombs are cluster bombs, they need to be dropped at a certain altitude in order for it to open and free the canisters. If you drop it close enough to the ground not only it won't open, it of course doesn't explode at all.

Those French guys painting their cockpits pitch black, how could they dare to do so .

Not that I've noticed, in the end you just have more room to run in the non-AB area (so you have not less but more room and it should ease handling I guess), and AB has just less room but since it's already on and it's an area you won't spend much time on burning lots of fuel, I didn't notice big differences in handling. First day anyhow, I'll check in the long term how it feels or if there's any disadvantage in having less room for AB. I guess it won't be, but we'll see.

It doesn't feel like multi-stage AB, but it might well be that. Anyhow, I just planted custom curve the second I got airborne and matched AB kick with my Warthog detent, no big deal.

Can you tell us a bit more about how it happens, conditions, what kind of mission, etc? Lag in DCS can happen due to many reasons to my limited knowledge about the subject, but, for instance, it's usual you can be perfectly fine in a server and should a single player join having a bad ping the hole game is borked for everyone which as you might guess has anything to do with the map itself. Maybe that player has a bad internet connection, or has an old PC not allowing him better performance, or both and the game if ruined for everyone which should be synced to him and it's just impossible to be synced with that. Has it happened to you in a regular server? Some friend/squadmate/whoever server? Can you play just fine offline? What mission was it in, heavy mission plenty of ground units or just a few ones? That kind of stuff giving more details.

Who said they can't? They pretty much can as almost any aircraft I guess, but you have to practise it to master, like you have to do IRL as opposed to other games were you can do it straight out of the box. Sincerely that little detail alone only tells me about how accurate behaviour is in DCS, but whatever .