Dentedend10

Hi, My wingman also wasn't responding to 'Engage ground targets'. I tried to convey it on both Channel 1 and 4 radios. I do have VoiceAttack and Vaicom though so it's not the cleanest install. I tried Dive Laydown mode initially, but got caught with SAMs pretty quick maybe I'll try Dive mode next. I was able to remove my battle-damaged F4 with one stabilizer only from the AO . I thought I could put it down on one of the roads. Turned out I did not have enough stabilizer authority for a flare and splashed into the ground. Rough first try

Hi, Loving the campaign so far! After taking out the MiG-23s, I get instructions of 060, 20, low flying enemy planes. I turned 060, however, could not find the bandits. I assume these are BRA calls. I also tried to find them via Bogey Dope, but at that point I got a picture clean response. Looking at tacview, seems like the enemy aircraft was more like 090 at the time of the call, and I missed them by around 7 nm. I'm not sure if you have any control of that call or that's a prerecorded voiceover, just letting you know it's hard to spot them. It did not affect my mission score at all, but I had a spare AIM-9 left at the end Attached is the tacview FYI. Have a good one! Tacview-20251001-175055-DCS.zip.acmi

Thanks for the video. In it, I can see the violent vibration of the stick. What I experienced was a bit different. When entering stall slowly and gradually, the stick would pull forward to decrease AoA. What I mean by this is the virtual stick in game. However, the hardware would stay in my hand pulled back all the way. So that should tell the software that I have pulled through the AoA limiter. But instead, my stick input at the max limit wasn’t registered, and AoA was decreased by the limiter, which also moves the virtual stick forward. now it’s possible that since I have pulled already hard to reach the limit of the stick range, the hardware forces are already maxed out with the stick in my lap, and therefore I wouldn’t feel the returning force (that is visible in the virtual stick). I will test this again. What I would expect based on what’s been said is that the max force required to pull the stick back before AoA limiter should be 17 kg less than after the limiter kicks in. This has to be downscaled of course for hardware limitations. I would still expect a difference in the forces required when I pull back without the limiter, vs when I push through the limiter, and ideally I would feel the returning force as well when the AoA limiter kicks in Edit: so I did some further testing. When the AoA limiter is reached, the stick vibrates aggressively. I personally do not feel an increase in force that would pull the stick back a bit, before being able to pull through it to get back to past the limiter. This is probably beyond the scope of this discussion and should further be discussed in a force feedback section

If Aware29 is correct, could this behaviour be represented in the FFB application? Such as not using full force until AoA limiter activates, at which point FFB pulls forward in sync with the visuals, and then needing to use full force to override AoA limiter? That would be amazing!

I also have reported the laggy stick behaviour in the vertical axis before. I have an FFB stick and it doesn't make sense that I do not FEEL any resistance on the stick while on the ground, yet in the airplane the stick moves like the pilot has to exert so much strength that the stick can only move slowly. Or if it is truly that hard to move the stick while there are no aerodynamic forces, maybe it could be added to the FFB behaviour. I understand how it can be immersion breaking even without the FFB. And to second that, I also think there is no problem with F-14 mirror design and it's much preferable both for immersion and comfort.

I couldn't find the previous post, hence the new one. Thanks, good to know it will be revisited eventually. Btw, I've been flying in VR for years mostly the F14 and never noticed any jumping animations that would throw me off. Sounds like there are two types of sensitive people, one to jumping animations, others to laggy image

Hi, firstly I’d like to say that I love this module and all heatblur modules and appreciate all the work! I know it has been mentioned in the past that the pilot head lags in the mirror in VR. It works perfectly fine in the F-14, or the latest ED release MiG29. It has been dismissed in the past that it is a conscious decision to avoid quick head movements. I do not quite understand why the head movement is perfectly synchronized in the F14 or MIg29A, but in the F4 it is still lagging. Please, if you do not want to change it to completely synchronized like in the other modules, give the player an option for that. It still breaks immersion to see the pilot head movement in the mirror lag behind real movements. Again, I’d like to emphasize the fact that it‘s perfect in the F14, another heatblur module. please take a look into this again. again thanks for this wonderful module!

Please ED include a more precise description of the trigger behaviours in the manual. I would like to replicate the true behaviour with my VKB MCG Pro. Thank you!

Yes visor works awesome in latest patch in VR! Thank you devs

also, anyone wondered how the pilot switched on the navigation operation switch, when it's under that glass cover?

I'm in VR. Initially I had very low FPS mirror image in the Fulcrum. I've tweaked a couple settings and now it's back to good FPS and high resolution. 1024, unchecked both every frame and sequential options. Had to turn off secondary shadows for another reason, and now mirrors works very well.

Hi! I had the same issue on Pimax Crystal OG. Can confirm, turning off the Secondary Shadows fixed it.

I also have issues with AI F4, specifically flying into the ground at a higher rate than one would expect. Attached is an engagement as part of Reflected's F4 campaign. 2/3 AI F4 crash into the ground. Thanks Tacview-20250914-210237-DCS-MIG Killers - 08b - 4vUnk.zip.acmi

So the fix might not have made it? Issue is still present

hi, Could someone help me out with applying different DLSS versions? I have this strange behaviour that if I select DLSS Override - Use the application 3D setting in the NVIDIA App, then DLSS 310.3 is being applied in game, however, only preset C. If I try to choose a different preset, such as J, K, or Latest, it reverts back to DLSS 310.2.1 in game. This happens in other games as well such as MSFS. I used DLSS swapper to change the DLL files. I'd appreciate any insight