YoYo

Full Earth incoming, however when it will be released I will look like he :

I know, ED loves a water and sand, a lot of sand!

The name of this topic should be renamed , it won't be "Fulda Gap" but DCS: Germany. If the map contains Berlin Schönefeld Airport - and Fulda (maybe?) it could be probably 480x350 km map, so even bigger than Normandy 2 (about 400x400 km), with only land (not 1/3 of the sea). very big map and a lot of work. So very reasonably - from the border of Poland, until slightly beyond Frankfurt. It's possible, but it would be one of the largest maps (and basically the land itself) and then I honestly don't think they would just call such a large map with an obscure name - Fulda Gap (small part of this map to be honest), instead of simply DCS: Germany. That's why I'm writing that it won't be Fulda (I don't mean the content, because it could definitely be there) and I can even bet on it. It may contain this fragment, of course, but since the map goes so far and will be so large, they will not call it a small fragment, but DCS Germany. From a marketing perspective, it would be a shot in the own arm. I just hope it won't be divided in sectors and we won't get the Halfgermany option .

Someone tested it in multiplayer? No issue with „pure client needed”? I use it in MSFS and here its „must have addon”.

v 2.9.5.55918 Static object, no texture:

Two weeks!

DCS: Germany I could be 400x400km, so samething like this, maybe part of Poland too?

Yep, it was Berlin Schönefeld Airport! https://www.mil-airfields.de/de/berlin-schoenefeld-airport.htm The picture was done from this side: Looks like version is from 1980-1990. Also notice the very distinctive taxiways and the two angled strips at the top. A little modern:

Everything is fine here, if you have a good eye, you can shoot better maybe, but I see a big spread and I always have to correct the fire after the first shot of first detent. I also don't know what distance you are writing about. If you are 200 meters away from the target, it is definitely not an easy hit. Nothing needs improvement here, everything is ok. I aim with the crosshair on the glass. The KW pilots practically did not use the additional sight.

You are a pessimist ;)! I rather expect it in August. Videos maybe are ready or in part with not buggy features, we dont know this.

(As a target) https://www.twz.com/air/aim-174-super-hornet-launched-variant-of-sm-6-missile-breaks-cover-in-hawaii Tarawa was stricken from the naval registry on April 30, 2024. The newspaper Stars and Stripes reported that the ship would be used in a sinking exercise as part of Exercise RIMPAC 2024.

I noticed it also few times, I havent idea why. Mostly it was in LOAL condition I suppose, with LOBL no issue.

I remember something like that somewhere. Thanks for the lead, I'll check it out.

Does anyone know the options if it is possible to set two missiles to the same code at once? By default, they have different laser codes, yes, it changes automatically, but I also had several situations where the code was an alternative one without switching from my side (MAN/NORM). Then you had to switch manually.

Save mission? Its is in Mission editor, or maybe do you think about the option during the flight? Its not possible.

Yes, its a very good news that the radar for F-15E is fixed already.

LAlt+C? Try it.

I know, probably yes, but they wrote clearly: so that's why few pople are surprised . For me Discord its a waste of time for scrooling and chat only. Good for possibly quick information, with lots of LOL, ROFL and WTF, thats all.

Why on social media and Discord only?

Btw. And BTW2. (dev update of AzurPoly for MSFS) +1 for this for DCS!

+1, I need it too.

Everyone will agree on that.

What planet are you from? Pre Order and EA are the main, main and again main policy for DCS. This policy is also focused on pricing strategy for Pre orders and EA. 2/3 (or even more) producs for DCS are EA still. Secondly, "not EA" status - does not guarantee anything (Kiowa example, issues are present too) just. EA only serves to make the developer assume that there may be bugs, and the customer accepts it and waits, it is convenient for the developer and safe (we have a discount for that, which is fine). It was also never the case that EA's policy presupposed failure to meet the deadline and it was not specified (maybe the F-15E exception). EA assumes bugs, but not lack of release. As far as we know, it is the changes and improvements are that cause the patch to be moved, not the new module (there are exceptions, of course, e.g. CH-47F), but that is understandable. However, I think the Afghanistan map is ok and ready for release, just like other things (new content), and the patch causes the whole thing to be moved.

But postponed SU15 didnt affect World Upade and new content notice (+ in Marketplace as well) and all it was on the time, here is a biggest problem. Generally, I had no problem with SU15 being postponed and tested (like patches for DCS), but I would be more angry if I didn't receive my product from pre order on time. Also modules cannot contain anything that the DCS SDK does not allow btw.

For ED - maybe it's worth considering whether the current policy is good, because as you can see, it simply doesn't work. Unfortunately, for the last 2-3 months, basically everything has been postponed (I think only Kiowa was on time). Maybe it's better to adopt the strategy that is in MSFS, so: 1/ SimUpdate - patches, 2/ World/Content update - maps, new content, new modules, but not improvements (based on the current SDK from the last patch) Of course such a „World Update” requires a new version of DCS, but it does not contain improvements that can break DCS and other things. This approach will allow for more flexibility, while not affecting the release of an expansion, campaigns, or anything else (new content) that is bug-free. Personally, I understand that some improvements could have messed something up, but this just shows that the current policy is bad, because it causes ED to miss the deadline, and it causes frustration for people who bought something and don't get it on time. So, maybe the strategy proposed by Microsoft is better - in the other times new things come out, and other times there are patches with fixes. thanks to this, the patch does not affect the timing of new modules which are ok. A request to consider whether it can be separated into SimUpdate and Content update (without improvements) for the future. I think the division in MSFS (SimUpdate / Content update - the first one contains engine fixes and is released less frequently, the second is new content.) suits me better, at least it's a bit more predictable and less painful if you have to wait, and on the other hand it gives more flexibility for the publisher.