nuNce

Of course, because once sold, even if people refund they will still have to buy something from the store, even if they are not interested in. ED wins either way.

Some of the "in development" feature have been there for more than 4 years. This is unacceptable from my side, selling a module with a feature set that is still in development 4 years is borderline dishonest. Imagine buying a game like "The Last of Us" where after 4 years you still can't complete the main story because "Last chapter is under development". I was already taking a break from DCS, but after the RAZBAM affair I'm putting it on pause indefinetly and will just enjoy what I've already bought from time to time. Sinai map is another sore eye, and the whole range of new modules being released makes me feel like ED is cashing out on us customers to get through their dire economic situation.

Imagine people stop buying their modules for 8 months because of the insane amount of broken promises (supercarrier, combined arms, AI updates, the list goes on) and lets see how long the train ride lasts.

Now replace RAZBAM with Eagle Dynamics...

I know your stance on the subject, but it ain't going to change my mind. Current spotting with dots on makes it unrealistically hard to track enemy airplanes even against the blue sky.

They are on but the airplanes are hard to spot again. Why on earth did they make them worse again? Now spotting aircrafts is terrible.

Hello, would love to implement the script but the objects killed by the secondary explosions won't allow me to track IniPlayerName, since they are DCS generated. Any idea how to track kills for them?

Is there anything that can be done to revert to the much improved visible dots that we had mid-october? Currrent situation is horrible with airplanes disappearing against the blue sky.

Tried today and can confirm this bug still persist.

Seems like deleting my Saved Games\DCS.openbeta folder has worked. Steps I took: Backed up the whole folder by renaming it DCS.openbeta_old Launched a full DCS repair Launched DCS and exited Copied back the following folders from the backed up folder Config\Input Config\MonitorSetup Config\options.lua Config\SRSConfig.lua (since I use SRS) Launched DCS, my settings were back and the ASL was behaving correctly

I'll give it another go, might be an issue with my user profile just like other issues that arose since 2.9.

Any of them: GBU-12, 16 and 24. Target in front of me, ASL completely off. I tried airstart in the ME and whenever GBU-10s are onboard nothing works. 12 and 24 are fine.

I had this bug today, could designate target but the ASL or CCIP pipper were never working and completely offset either left or right.

Sorry, your picture was incomplete.

Agreed. Seems like the biggest issues are related to VR, and it's gonna be just a matter of time before this gets balanced the right way. The opinion of a small minority of very vocal users shouldn't be the benchmark for the whole community regarding spotting issues that have plagued the game for years. The Improved Spotting Mod poll was a landslide victory in terms of how positively the community viewed the changes, and is way more representative of the positive reception of this new version.

In that case you are looking at 1.5 times the length. In the case of larger jets like the F-15 or F-14 you get the value I'm talking about.

Which means that 10km for a modern fighter which is twice the size of a WWII aircraft is more than fair.

Just a note, my intention wasn't to bash ED, as I finally feel that work is being done to address long standing issues and feels like a really positive sign from them. It was just to point out that "realism" has many angles and is not just graphics and systems.

As a temporary workaround you can probabily already do that with your HOTAS software or with Joystick Gremlin.

Sometimes launching Fox2s at AI makes me feel like my trigger is hardwired to their flare dispenser.

In the current DCS version the external camera management enforcement for users has basically 3 options that can control granularity: External F2, F7 and F9 views can be restricted to All \ Coalition \ Player \ None External F11 view can be enabled or disabled External F5 view can be enabled or disabled The cameras need to be correctly set by the mission designer in the ME, and F5 and F11 are even worse in this regard since they need to be set from MISC options before saving the mission and cannot be quickly changed when launching it. Then there is the F6 camera, which cannot be managed separately, and to be disabled it requires denying players the usage of the external views altogether. It would be great to be able to: Override mission camera settings from the server, when launching the scenario, letting admin choose which ones to enable and which ones to disable, including padlock (F5), ground (F7), naval (F9) and free look (F11) cameras instead of having to preset that in the mission editor or game settings Be able to restrict weapon (F6) camera usage separately from the external air (F2) cameras. This would allow for a comfortable middle ground between creating more tension by not letting the player to check constantly if he hit or not the target and allowing to take screenshots \ clips of his own and other friendly A\C I think this would improve quality of life, and let admins choose the right level of uncertainty that the player will experience during a session.

This iteration is much closer to real spotting than the previous Flying Dutchman planes we had in 2.8 and we have way bigger problems in the way of realism than spotting. Just on the top of my head: RWR lock spikes across the whole map AI denying laws of physics AI bandits knowing your location at all times, and having perfect SA Ground units having radar-like accuracy with autocannons and machine-guns making them better AA than a Shilka These are the issues that are really holding back the sim when playing in a cold war scenario where your SA tools are very limited and you rely mainly on your Eyeballs Mk1 to understand the battlefield and locate targets. If I have to choose between "Too hard to spot" and "Too easy to spot" I will definitely go with the latter, since the former makes the game worse in every aspect. In the current state, spotting is not easy at all when flying low. I get that there are some users that are experiencing unwanted results, but I'm sure ED will iron those out with future updates, while preserving the ability to spot visually for the rest.

It's very different to bee able to see something at a distance, and being able to "spot" it while flying, managing the engines and navigation and your weapon systems. DCS 2.8 had a terrible spotting. At one time me and a mate of mine were trying to fly in formation on two Mig-21, unable to find eachother over Caucasus while using the F10 map and Teamspeak on a 1440p. Finally, after so much time, DCS 2.9 addresses those issues, and to me is a much more important improvement than any DLSS or FSR will ever be.

GOD NO! We finally have decent spotting and can have real fun in dogfights being able to finally have a quick glance at your instruments without losing track of the enemy. Don't event start complaining about "My god, dots are too big", they are PERFECT right now!

What is your usual release altitude for those cluster bombs?