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.

I have gotten it "working" myself. 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.

Are you referring to full motion frames? From what I can tell, this DOES NOT work in DCS VR. I've enabled it, and it makes absolutely 0 difference. No change in quality or performance, and AMD Adrenaline isn't even recognizing DCS as running. I don't think it knows DCS is a game, even though I've manually added it. If you've got it working, can you advise how? Edit: And to make things worse, I had been using Radeon Chill to lock frames at 45 and reduce stutter. Now that I've enabled (and disabled) FMF, it has locked anti lag on - even with FMF off, I can't turn anti lag off. Which means I can't turn chill back on.... Thanks!

Yup, he’s fine, still chat now and again in the discord. But as the name implies, guys are busy dads and the group has lost steam. Still made some great friends on there back when it was more active.

Thanks for replying BN. I’m 99% sure it’s not a DCS issue, as DCS is still running correctly within WMR. It’s when the headset powers off or briefly loses connection (USB issues), the headset seems to lose its connection with WMR. I was just hoping someone in the community had maybe found a fix / workaround.

Thanks, I’ll give it a try. So my read on this is, while there have been several great suggestions on how to avoid the situation, it would seem once it has happened there is no way to recover the game. That’s a shame, as the game is clearly still running and WMR is still functioning, there’s just nothing displayed on the headset. There should be some way to “reboot” the headset and sync it up again. Not a DCS problem (I think the issue is WMR / HP), but a shame nonetheless.

I’ll try that, thx. The sleep is already set to off, it was my monitors that went to sleep. I won’t turn that off as I used to have it off and got bad burn-in on my expensive ultrawide monitor…

So this is one of my greatest frustrations with DCS / WMR / Reverb G2 right now. At various times, for various reasons, the headset will "de-sync" from the WMR environment. This leaves the headset with just a black screen (screen on, just black), while the WMR window correctly reflects what's happening in game, head movements, etc - the headset is just black. This sometimes happens on startup if things don't sync correctly, or sometimes for other reasons. Just now I stepped away from the computer mid-mission to answer some pressing work emails, and when came back the screens had gone to sleep. On waking up, everything woke up, except the headset. Black screen of death. Game still running, WMR window still showing everything, just nothing in the headset. Other reasons this has happened is if there's a brief USB cut-out (happens rarely though). Anyway, my question, has anyone found a way to recover from this? Any way to make it re-sync?

So assuming it’s not a fox 2 fight, yes you can extend. But when you recommit, you are now in a head on situation - against a tank of a jet with an invulnerable pilot. Advantage tomcat pilot I don’t want to derail this thread, as I said earlier I only posted to bring context to why so many are fascinated with the bypass breaker, so I’m going to withdraw from further discussion on this topic and hopefully let the thread stay OT.

Unfortunately, in the common BFM arenas of DCS, many (I may even venture to say most) Tomcat guys now spend more time gaming the edge cases of the flight model than flying actual BFM. They’ve figured out exactly how many G they can get away with (it’s in the vicinity of 20G if pulled progressively), use flaps jammed at 400kts for extreme turn rates and AoA excursions, manual wing sweep forward, and things like the MCB breaker. This results in an aircraft that performs wholly outside the realm of where it should, enabling basically instant 180 degree turns and unreal turn rates that they exploit into head-on passes to again exploit the fact the tomcat pilot cannot be “pilot sniped”. It’s all about playing to one exploit after the next. It’s really too bad, because one can’t enjoy proper BFM in this module anymore since the community has found every little edge case that I’m sure was never intended by the devs. If you try and fly it “proper”, you have no chance anymore. I only say this as context as to why this MCB has generated so much discussion. It’s players wanting to find yet another exploit in a module full of them. I do not mean this as criticism to the module (I love this thing), and other modules have their own exploits (paddles and overrides are the norm rather than the exception). However, the nature of the Tomcat not having FCS makes it more susceptible to these exploits, and it has become the reality on open dogfight servers.

Helicopter controls are extremely sensitive in hover, it’s realistic. It is exacerbated by the controls most players have at their disposal - short joysticks with limited throw increase sensitivity even more. Extensions help. You can also adjust saturation in the axis settings (I do not advocate curves), saturation will reduce your maximum range of motion but the extreme edges are rarely needed anyway (exception being forward pitch, you may run out of forward authority in fast forward flight). Try and hover like we do in the real thing - set yourself up so your wrist is resting comfortably on something. We use our leg with a center cyclic, if you have a side mounted joystick try and use the arm of your chair or something. Rest your arm comfortably, relaxed, and control the stick with just fingertip control. Don’t move the controls, just ‘think’ about moving the controls. The rest is just practice