Sandman1330

@NineLine Any info on what timeframe this map will represent? 80s, early 2000s, late 2010s?

Kandahar and Helmand were anything but. Americans weren’t the only forces in Afghanistan. British, Canadian, Dutch and many others were fighting and dying in regional command south for years. Yes Americans mostly focussed on the east, but it doesn’t mean the south was calm. In fact the area just southwest of Kandahar (Panjwayi / Zhari) was the site of one of OEF’s biggest battles, Op Medusa. Its also where the Mujahideen kicked the crap out of the Russians.

I've played with the curves to see if I can make it better, still happier with the 15 curve I have set. I personally love it to be finger responsive. I have a good stick, and I mostly do helicopters, so finger touch is where it's at for me. I dislike the Viper's AAR law, where everything becomes less sensitive, for that reason. I want it so sensitive I just have to "think" about moving the stick and the aircraft responds. Now the Hornet feels to me like I move the stick, and there's a pause before it responds, so I end up moving it a bit too much and start a PIO. Could be realistic due to inertia, don't really know...

Thanks. To be clear I'm not looking for any assists or tricks - I can AAR, I have always been able to AAR, and have no interest in using autopilots or tricks to do so My stick is a Virpil Warbrd, so good quality. I'm just wondering if anyone knows if the flight model is going to stay this way or not (ie was it intended behaviour). It seems you've noticed the change as well, though from my perspective it feels like lag (a delayed response to control inputs), where you don't perceive it that way. It just feels "spongy" now. I don't recall having any delay to fine control inputs during the real formation flying I've done, though it's been awhile to be fair and it wasn't in a hornet At least I'm not alone in knowing something has changed!

Is there a known / acknowledged issue with AAR in the new FM? Before the update, I could slide in, plug and fuel first try, every time. Now it almost feels like there's a lag in the pitch controls - it's really easy to get into pitch PIO. I can still do it, but it's much much harder, and not as clean and pretty as I used to. Is it a known / documented change? Is it a bug, or intended?

I wonder when we will see this. I have several campaigns that I want to finish but keep getting turned off by flying over an hour, refuelling, etc only to get hit by a golden BB over the objective area and have to do it all over again. Glad it's coming, hope it's soon!

I guess one could simply roll back using the updater if there are any game breaking bugs, that would be analogous to using stable version. The only impact would be connectivity to MP servers, but they all used open beta anyway, so playing on stable wouldn't have been much help in that regard. Makes sense to me!

Look at Caucuses though. The detailed map is a very small percentage of the actual map. I think both Iraq and Afghanistan could easily include water for carrier ops in low detail. This would require minimal effort and resource (both dev and PC), while providing those who want realistic carrier ops and transit times to have it. Imagine putting a carrier on the far western side of the caucuses map! It totally can be done.

I was confused myself when he said Bagram - I've flown a fair bit in and out of Baghdad, and I was sure that was Baghdad! I was also looking for the mountains around Bagram and wondering where they were. Glad to hear it was a simple mis-speak. No harm no foul. Baghdad looks great, I can't wait for it!

I suppose it could be possible, for both Iraq and Afghanistan, to extend the map south in low detail to allow placement of carriers in historical positions. It's not unprecedented - look at the Caucuses map. It extends very far west (the entire black sea and Crimea), just in low detail. That way, we could simulate the carrier ops with longer transits in with aerial refuelling, in order to operate in the detailed area of the map.

+1!

Hi BN, Thank you for the quick reply. I hadn't realized those mods were installed (none are in use for the mission in question). I've done as directed, removed all mods (and associated scripts from the scripts folder), and I've run the slow repair. Unfortunately, the issue persists - however, this time it gave me a crash log. Please see attached. I also removed the two red helicopter client spots and changed the apache from client to player - this allowed the mission to run without an issue. So it may have something to do with the two client red side helos? Cheers dcs.log-20231228-181708.zip

Trying to load attached mission. Very simple mission, only a couple units, no scripting whatsoever, all vanilla ME. No mods installed. Load into blue coalition, apache. CTD on spawn - almost every time. No error messages, no log, direct crash to desktop. Log and mission attached: helo v helo.miz dcs.log

Was doing some air to air testing against the AI MI-24, and it would appear that even after his aircraft is destroyed, the AT-9 continues tracking its target. AT-9, if I'm correct, is a beam riding SACLOS missile that requires the launching platform to continuously guide. If the launching platform is dead, the missile should go unguided, I believe? Track attached:AT-9 tracking after dead.trk

I have gotten it "working". I put air quotes around "working", as I don't see any perceptible difference whatsoever. AMD Adrenaline tells me it's on, and the AMD FPS overlay reflects the increase in FPS, but in the headset.... nothing. No perception of increased FPS whatsoever, and no frame gen artefacting (which I'd expect to see at least some). I can only conclude that, while the driver may be generating those extra frames, they aren't making it across the WMR bridge into DCS. I still have a smoother experience using Radeon Chill to lock FPS at 45 (half refresh rate). This removes most micro stutters and greatly smooths out my experience. With FMF on, the stuttering returns as if I was still running around at 60fps. Note, that in order to get it "working", I had to select "use DCS system resolution in mirror" in the VR settings. This made the mirror full screen and that's when Adrenaline started reporting FMF was working.