r2dseu

looks like this didnt get clearly closed out. This is a bug with the F-15C module for the Clickable-FC3. Fix is available in the discord channel but the fixed dev_install.lua file is also attached here. dev_install.lua

I also thought that the missile could have been launched on HOJ mode (I did have my EW turned on) but I did see the initial RWR lock (which prompted me to notch) that indicates that it didn't launch on HOJ mode to begin with. Does R27-ER switch to HOJ mode if the launching platform stops providing guidance?

Hi folks, I've noticed that R27-ER continues to track even after I've broken lock both by notching (and verifying no lock on RWR) and that the bandit (SU27) has turned away. I don't have a track file but I do have the Tacview file that clearly demonstrates (around the 23:29 mark when the engagement starts): 1. The first SU27 that fires off the R27ER clearly disengages beyond it's gimbal limit (actually turns cold) 2. The second SU27 is destroyed (confirmed on BDA during the mission) 3. I'm not seeing any other opforce unit that could be providing guidance via datalink or otherwise 4. You can clearly see around 24:57 that the R27ER cranks to engage I initially thought that I got hit with the ET but Tacview states otherwise. Could Tacview be incorrect here (if so, it doesn't makes sense since I did receive a RWR lock in the first place which forced me to crank). I know this was a known bug few years ago but surprised to see it coming back. Tacview-20240118-234053-DCS-F15C TGW M09.zip.acmi

+100 This is super important. I can't go back to running 20 fps. Not after I've tasted running 100 fps.

To be specific, you also need to repair the DCS files. Just disabling the mod isn't sufficient.

Hey folks, so it looks like this might be due to corruption in some files during upgrade, most likely caused by FC Clickable cockpit. Try uninstalling the modules completely, and doing a repair (if in Steam, do an file integrity check) and reinstall the module.

Im seeing the same thing with Winwing Orion2. Completely blew my config away and it's not mappable. At this point, the module is unplayable so I guess I'll have to wait or play something else until fixed.