theIRIEone

To be fair: The carrier tells me to switch frequency, not the other way around.... Give it 5 more years, i'd suspect for Supercarrier's 10th anniversary we'll get the promised ATC, then 1 year later there'll be a paid upgrade "Supercarrier 2.0".

Honestly i feel like they're existing just so an item could be checked off the "missing features" list before the clock strikes 5 years of age.. Besides the bugs ("awaiting ATC Status", anyone?) i feel cyclic ops aren't represented properly: 2 Hornets, nothing else around, both get assigned CAT 1... Why? Also while i never seen an aircraft carrier irl, leave alone being deployed on one, i feel the deck crew has some sort of psychic ability: There is 0 reaction time at all, as soon as the "point at next handler animation" hits, the next handler's animation starts rolling already, making it all look very mechanic and not really human... To further decrease our immersion (that's all we have and why a lot of us sim in the first place), we get bright yellow text in the center of our screen that cannot be disabled or at least moved to somewhere less intrusive, like the corner of the screen.. No it has to be right in our faces with no means of being disabled. And then, after everything is done and we returned to the boat, the abrupt 180 auto-turn / respawn thing kills it all off one last time.... Where's the passion? There is no passion, it's business.. and the deck crew demonstrates that to me more than everything before.

Given the new deck crew feels like an item produced just to "finally put a checkmark on a missing feature" that has been there for almost half a decade, i'd say "probably not"... Hey, at least we can all get in a row to use CAT 1 exclusively from now, i guess... That is, when we're not stuck due to "awaiting ATC status".

At this point i'd take the "free for all" over the "not being able to fly at all" any day.....

I see.. That surely sounds like a great option. Just to be clear: If i switch on "INVISIBLE" in the unit's options, the threat ring would still be generated? Funny how my brain bends itself thinking if i set a unit to "Late Activation" the ring would be visible from the start but somehow that wouldn't be the case when the unit is set to "invisible". I'll just test these things out, thanks again. Much appreciated for sure.

Thank you for this detailed explanation, i think these are exactly the points / hints i didn't know i needed. I really like what you are describing here. Obviously nothing will ever be completely random as we still place the defenses manually as you mentioned, but combining everything you wrote should be more than sufficient to help me achieve what i realistically want to achieve. Sounds like it's a quite a bit of extra work initially tbh, but given the replayability of such a .miz i feel it's surely worth it. I'll probably keep some of the threat rings for stationary defenses active on the AMPCD because imho it helps increase the immersion (given partially correct INTEL) and i tend to keep everything regarding F10 map / labels etc switched off anyways, but other than these few threat rings i'll stick to following your advice closely for now. While i stumbled over "random flags" a few times, i never tried using them - to be fair i'm not the most experienced with the ME but at least know how to spawn stuff via F10 menu etc, which is great for training purpose, not so much for missions themselves. Instead of learning Moose and potentially various other scripts, i might as well take a look into random flags first, 100%. Still need to wrap my head around the concept of how to determine 1/X active randomly via triggers/Flags, but i think (hope) with a piece of paper and some basic math i'll be able to figure that one out. Thanks again, i'll dive into random flags and then start building a fresh .miz.

Hi, I took a timeout from DCS and after returning a few weeks ago i immediately got reminded on one of the main reasons i stopped playing (simming, flying, call it whatever) in the first place: I love the sim, but i hate the game... Specially the fact that whenever i build a mission, i know 100% of the things that will happen during the flight. There are 0 surprises going on, the only surprise i'll get once in a while is "great, now xyz doesn't even work".. I know some people are working with Moose etc to make interceptors spawn dynamically, my question is: Would there be something similar for ground units / AA and such as well? At this point i got the hunch that it's faster for me to learn all this stuff rather than waiting for the "dynamic campaign" any longer.... Hints, tips and pointers are much appreciated, other than "just join a squad" (still have some ppl to fly with from old squad and not wanting the huge commitment of joining an active one rn) thx.

So i decided to fly R1 again, and got stuck in mission 2. I then found a "fixed version" of the mission on the official DCS user files section, which stated that it would be baked into the next update. However this was a few updates ago and i couldn't anything about that in changelogs i searched. So first question: Which version should i use? The one that comes with the module manager in-game or the one from user files section? Currently trying with user files version: Tanker TCN supposed to be 55X, but it isn't (A/A is active on my end), that is true for both versions as this bug triggered me to download the user files version. When you manage to find the tanker for 2nd refuel, which is not seen on S/A page despite that E2 being not too far off, and constantly circling downwards into the clouds, you have to send in Smoke first. He gets his fuel, but upon disconnect he just crashes the tanker bursting into flames.. Obviously this is rather frustrating as this happens towards the end of the mission and without being able to save midflight / prior to this happening you have to go through the whole thing again.. there go another 4-5hrs today without any progress, just doing the same things a couple of times and giving up. I think i probably have to find away to cheat the mission somehow whenever i decide to try again, just to end up with enough fuel to spare out the 2nd AAR, albeit i'd prefer having the full experience here. Well, at least i know what is happening when and where by now, so i might get a headstart on that Fencer, just ignoring the training or something on that line.

EDIT: Please ignore, today's update appeared to have fixed the issue again. Made some observations on more recent YT videos and flying myself: Prior, depending on weight, we used to approach the carrier at around 135kts - give or take a few kts depending on weight. Obviously we fly on-speed and not numbers in the box, yet you keep an eye on those. Nowadays, on-speed is more like 145kts, not sure when that changed. Is this a bug or am i missing some infos here? As far as i remember, Charlie Hornets always landed around 135kts (as explained in Wags' Supercarrier landing How To video as well), what did change and why?

That makes total sense. After all this time of "works as intended" i must've missed that the relating logic was changed. Thanks a lot gentlemen, much appreciated.

Hi, I always was under the impression that CM (chaff/flare) release is only functional with Master Arm switched ON. However, earlier today during a mock dogfight with a squadmate, i was in A/A master mode with SIM boxed/active, Master Arm switch SAFE - and actually released CM. So i guess my question is: Does SIM mode while in A/A master mode let us release CM regardless of Master Arm settings (override?) or did i stumble over a bug? I would assume the latter being the case but thought i'd ask if i'm missing something here before posting in the actual "Bugs" section. For the record : Master Arm switch was set to ON for a brief moment while setting up for the mock dogfight but was set to SAFE immediately again after consulting with flight lead - long before the first merge happened. I have footage reassuring myself i didn't remember wrong, Master Arm was 100% SAFE but CMs been released still.

Ok, so i decided to give OP Pontus another shot after giving up on it quite a while ago because the random (but not so random?) unbearable performance hits, the AI loving to kiss the ground and basically never managing to RTB successful among some other problems (like tgt coordinates sometimes being inaccurate leading to guesswork regarding the actual target building etc). Fresh start, roll the intro.. First flight: During Mission 1 you have to make a decision about wanting to AAR or not - Of course i wanted to AAR.. i am a bit rusty and can use that training myself, also don't want morale to drop! ..as i said, i am a bit rusty and have taken a little longer than usual, but i connected and took a proper sip from the tanker - just to lose awareness of my airspeed and therefor disconnect.. Slowly pushing myself back towards the basket, Lt Trimmer apparently has finished his refueling process but never cared to say a word, neither did the tanker.. Guess what Trimmer did next? Sparks flying, me plummeting towards the sea in a rather uncontrolled manner - not what i expected at all. Right, i guess i lay OP Pontus aside for the next 6 or so months..

I'm not using ATTH that much really, but BALT. I don't think it's important what A/P mode is active prior to / the moment of dirtying up, but just that any A/P mode is active. You can see me cycling gear / flaps in the recording as well, problems didn't disappear this time - meybe i was too fast with the cycling, but i remember being successful the same way during a flight some time earlier (few weeks back).

The *new FLIR renderer* ,responsible for the push back in ATFLIR delivery, may help you out with this a little when it is released... Oh, wait^^ On the real though: Practice, practice, practice... and actively switching modes and brightness / contrast etc can help a lot. If possible fly an orbit over tgt area, depending on the angles etc bulidings and the likes may also block direct LoS to targets - so it's good to get a view of the area from as many sides as possible, with as many filters switched / tuned as necessary.

Experienced the same issue here on Sunday, also a few weeks back as well. Thing is, i can get the plane trimmed after a while despite nose initially shooting for a cobra, but it appears that FCS does not enter PA Mode correctly as the trimmed aircraft does not stay trimmed: - in PA mode, E-bracket and VV are tied to one another rather rigid, but this is not the case when described bug appears. Rather slow power changes will result in slow drift of e-bracket. Note that A/P advisory is displayed despite disengaging all A/Ps by the use of paddle switch. Trackfile is probably too long, but as usual i have an unlisted YT recording of this (problems described from timestamp til landing - ignore bad r/t, was heavily distracted by the bug)

Thanks a lot for your input. I would assume elevation blanks being filled by the MC would mean no drifting coordinates, but also an actual altitude input being present in the O/S data - i know that elevation data is not displayed when leaving elevation blank, but that doesn't mean it couldn't exist somewhere in the background. To be clear this has nothing to do with SLAM-ERs really, they're just here for context. Basically we wanted to write down the O/S coordinates, but that wasn't possible because they kept changing - and i am not sure what caused that drift, thinking it may be us not having entered altitude data - and if that would really cause the GRID to be drifting?

Hi, ran into some issued trying to use O/S coordinates as STP for our SLAM-ERs, not sure if what we experienced is intended behavior. Given was a designated waypoint with multiple targets around for a 2ship - we set up an O/S from that in this order: 1. hit UFC from according HSI/DATA format 2. hit O/S on UFCP 3. entered 30NM range 4. entered 145MAG and 235MAG for BRG respectively as we wanted 45deg offsets from our inbound HDG of 010 to create separation between the missiles 5. We left the altitude blank as the intend was not to use the Offset as such, but to read the calculated O/S coordinates (GRID) from the HSI to use as creation for another waypoint in the sequence - which we then would use as STP for our SLAM-ERs. That's where things went wrong: While writing down the given O/S GRID from the HSI/DATA/WYPT sub-format, the coordinates actually where slowly, but constantly changing aka the offset was drifting and not a fixed point in space (it was still roughly correct according to tacview as the SLAM-ER still took a turn at roughly 30NM and correct-ish BRG from TGT). While i couldn't find any reports of this exact issue described on the forums, i found another user's entry that is marked 'solved' - their screenshots also show their O/S Grid drifting, but nobody in the comments mention this. The marked solution there was "Check O/S Altitude" - which in that case made sense as they where trying to acquire a specific point on the ground with ATFLIR using F10 map shenanigans. - I'll leave their topic linked here for the screenshots, since i don't have own recordings of the O/S drift so far unfortunately. Question boils down to: Should Offset always be a fixed point in space or start drifting when (deliberately) not entering altitude? Considering WPT creation does not necessarily require altitude to be entered for the GRID to be stable, i would assume same logic applies for O/S creation (with the addition of offset logic such as BRG/RNG)?

Don't speak for everybody in the community please, at least not for me! I'm not going into a "my Hornet can't do it so no other plane can" argument because obviously, each airframe differs in equipment and capabilities, some more than others. While i don't know about other, specially REDFOR, aircraft capabilities in that regard, i tend to side with @Csgo GE oh yeah: If you use macros in FC aircraft to simulate likely realistic CM programs, that is all fine and well, but if you use macros to spam 20chaff in 0.1 second because "i say the aircraft is capable of doing so", there's something wrong with it imho.. All that discussion gives me is more reasons to stay away from public MP airquake servers and enjoy the sim for what it is with the community i fly with on a regular. Keep in mind "the community" exists of very different folks enjoying the sim in different ways, loads of them not daily on the forums - don't act like your way is the only one everybody else is in agreement with. Thanks.

can confirm it happening from time to time - this is what it looks like in practice - note that superquick box/unbox toggling

As far as i'm aware, the official DLC campaigns are SP only.. That at least goes for the ones i own: F-5 BFM F/A-18C BFM F/A-18C Raven One F/A-18C Operation Pontus Be aware at least some people having troubles with campaign progression at the moment (Sim does not allow us to "End Mission" resulting into all progress being lost) Examples: However there are inofficial MP campaigns, your best bet would probably be searching the user files section on the official website: https://www.digitalcombatsimulator.com/en/files/filter/type-is-campaign/apply/ I don't know about their quality or if they're affected by the progression bug, but since they're free i guess they're worth a shot anyways.

I experience exactly the same with Pontus. Hope a fix is found soon, as of now campaigns appear unplayable.

IIRC these coordinates don't need to be converted, however I would suggest to just use GRID [MGRS] instead - no need to worry about conversion, and even if you have never used it before it's pretty self explanatory and a breeze compared to lat/long: 1. Hit GRID on UFCP - watch GRID DDI page pop up on right DDI 2. make sure you're on correct GZD [38T in example - '38' is displayed above/below the actual grid symbology on DDI] you can move the displayed GZD towards N/E/S/W with corresponding pushbuttons if necessary, it will start out with whatever you overfly upon first pressing GRID in center. 3. enter all following number values [01337 92812] in UFCP at once, hit enter once done - numbers correspond to lat/long positioning within that 100km GRID and each digit increases precision. 4. enter altitude as usual. Either way coordinates given are *precise* so you wanna make sure you set up your jet accordingly - and obviously make sure your general DCS coordinates display is set up accordingly as well. Hope that helps.

To chime in as a GTX1050TI User: The update was not "too much" at all, matter of fact the sim looks better and runs smoother through the bench, on my system and the systems of all my squadmates (who use all kinds of different systems from "great" to "not so well"). Stuff that worked flawless before is still flawless, and very taxing things like low level flying over cities in Syria are still not really great (understandable with my setup) but actually improved a little as well. For completion's sake find my settings in the attached screenshot - assuming you're on 1080p and everything's alright with your system & installation (+mods), you really should be able to crank things up quite a bit higher without compromising your overall simming experience.

Great update, it's some kind of magic no doubt, but i am sure these visual effects while zooming on boat in darkness are unwanted:

Not sure if the fix went through already or not, but if so it didn't help much and this issue still needs tackling. Doesn't really matter if it's an ED issue or not imho, i wonder if these things really can slip through testing, or if the campaign is released regardless as one can always wave the "open beta" flag (not saying anybody does that, just wondering how this can be released in such a state, really). I mean, how can you expect your customers to fly like that? DCS usually runs just fine with the exception of low level flying over Syria, but even then FPS drops are nowhere near as severe as in Ponuts sometimes.. Issue is as OP described, campaign goes from smooth to unplayable in the blink of an eye - but for me it lasted about 5mins before i just quit to desktop yesterday. On another occasion it was gone after a few mins and i was able to continue the flight. I started recording after issue was persistent for a few mins already.