Gat0 Loc0

It's been a while since release, but I remember there not really being a specific timeline for much of anything regarding the SC, and they were VERY clear that everything about the SC was subject to change due to it's early access release. They had a specific statement somehwere along the lines of "if timelines are important to you, then early access is NOT for you." You can thank this impatient community for the multiple launch day bugs you mentioned--the community, at the start of quarantine, nearly did the internet equivalent of a full scale street riot when the module didn't release on that day in April 2020. To be fair, ED the previous week did say it was slated for release, and then they pulled a 180 the next week. I really feel like if the community were more patient, they would have released it a few weeks later in a much more polished state with fewer bugs. You know the old saying, you can't have your cake and eat it too.

Alright my guy, might be a good time to grab a cup of calming tea and relax for a bit. There are so many things that can affect how quickly/slowly these things hash out, but I'll just give you a couple main points. 1) ED is not a massive corporate publisher with nearly unlimited resources, both human and otherwise. Fewer resources means things can move slowly at times, regardless of if a product is early access or not. Super simple stuff. 2) The supercarrier is early access, and has been very clearly labeled as such. This means a generally usable product is available to those who wish to purchase, but users also agree that functionality is limited and there can be bugs (sometimes severe). Just because YOU paid for and want a fully functioning early access module ASAP is not in line with how early access works. 3) Coding. It's complex and full of issues that not even very experienced coders can predict. This can slow seemingly easy things down to a screeching halt. Maybe an experienced coder is on vacation/sick/whatever for 2 weeks before a problem can be addressed, then he/she finds out it's going to take a lot of effort to fix, so it gets delayed another 2 weeks. Not hard to understand. Tie in all three of these points together, and you can see how things can get delayed pretty quickly. ED does a great job with the VERY limited resources they have. Be patient, and god speed.

I struggled in the exact same way, and the solution was simple for my setup: set a curve of 15 on pitch and roll. I have a TM 16000M hotas. As soon as I did this, I've had a 100% success rate. The hardest part now is controlling airspeed.

Take a deep breath and repeat after me: Early Access Covid Unrest in Belarus Thank you.

I literally have no words for this. Incredible.

I had the exact same thought, and over 200 posts at that...lol

Are you trolling or are you actually this daft?

Agree 100%. An i5 at 3.2ghz and a 960 just wont cut it

For some reason, this made me laugh uncontrollably.

If you want 4x msaa, I'd fork over the extra $$$ for a 2070super or a 2080. My 1070ti is basically a 2060 super, and it would struggle to get 60fps with those settings.

In typical ED fashion, they neither confirm nor deny the supercarrier release on the 15th.

Newsletter doesn't say it's delayed, but also doesn't confirm it will release on the 15th...

I just bought some faster ram, and I have two options on what to do. I can either run: 32gb ddr4 @ 2400mhz Or 16gb ddr4 @3200mhz Anyone know which would be better for dcs world? I mostly fly in the Aerobatics Online server often with 50+ people in it

+1 David OC I have the t16000m setup with throttle, and it's a really amazing mid-range hotas setup. Better than anything saitek puts out at 3x the price.

If you're on a strict budget: i5 8350k and gtx 1060 or 1070, plus a SSD If you can spend more: i5 9600k and rtx 2060 or higher, plus SSD A SSD is pretty much required to play DCS these days.

Wags just mentioned in the Hornet mini update that they are working on data link. Does anyone know if this is for all aircraft, especially the Russian jets, or just the Hornet?

In the hornet, once you are trimmed for on speed aoa and level flight, you no longer use the stick for pitch adjustments, you will use the throttle to increase or decrease pitch. This must be a somewhat key difference between the su33 and hornet, if I'm understanding correctly. So it seems the flanker strategy is something like this: get on the glide path, set speed to 240kph +or- 20kph depending on weight, then use very small stick inputs to touch the flanker down on the deck, trying to keep aoa reasonably in range. This is what I did twice last night, and landing was almost too easy honestly.

So am I supposed to make small adjustments with pitch in the stick, or is there an option to make small increases or decreases to throttle?

So I've been doing carrier traps with the hornet for a few weeks. Within a week the standard pattern became too easy, so I started doing SHBs and got good at those too. I can consistently trap the hornet with a centered ball and a 3 or 4 wire. The su33 is considerably more difficult. Getting to on speed aoa is so much less intuitive, and getting the glide path correct in the middle to in close is so damn hard. Rocking the throttle can still result in flanker dropping like a rock or sailing 50ft high in close. Any pro tips to keep the flanker more on glide slope and on speed aoa especially in close?

I can also vouch for the absolute necessity of a SSD. NVME will give best results, but SATA III will still be a mind-blowing improvement over a HDD. It's really no longer a viable option to use a HDD for DCS any more.