GrEaSeLiTeNiN

I thought this video was helpful in explaining that the fog thickness was measured from MSL (not GL) and applied throughout the map. So we're hoping there can be future options for fog thickness based on GL and at selected locations.

Thanks for asking. I don't understand why simple hotfixes that wouldn't affect others (like switches specific to a module?) cannot be released as and when ready.

Did you try using the dial knob at top right of PDU? Any accidental binding of PDU brightness axis?

Haven't flown the Gazelle in a while but I tried out the AP functions just now. I can't seem to get AP Speed and Altitude to hold. As for CLV and ALV, they seem to be working as before. But you have to be very well trimmed out or CLV has trouble staying green. I wish CLV was more 'capable'. ALV is working but if you slew the crosshairs left and then hit ALV, the resulting left yaw can be unrealistically jerky. I'm assuming it's the clockwise rotor counter torque that's abruptly multiplying the left yaw effect because doing the same procedure with the crosshairs slewed to the right results in a smooth transition. I also think the collective inputs sometimes create a jerky yaw effect that's not realistic, esp when CLV is on. Not a pilot, just guessing.

IIRC it's to do with the Heatblur UI Resolution setting in the Special options tab for the F4E. I have mine checked and set to my screen resolution.

Mine does not vibrate but I do have cockpit shake down to 20.

Post 4 Dec patch: It's fixed thanks. But could the gain increase/decrease be a little faster? It's quite slow now compared to other modules such as the Huey or Apache.

Any chance the "next patch" being a "hotfix" that sometimes comes soon after a main patch?

AI has to be issued a "hover" command before he can be issued a "land" command. Ok, maybe this is by design. BUT as he proceeds to land, if I then issue a hover command halfway, he says "alright..." but will proceed to land because I think he is still following the ground altitude set by the land command. Meaning he is trying to hover at ground zero altitude. Track attached... KIOWA AI - Land Hover Command Issue.trk

Oh I see, how did you do that? Using a separate tool like JoytoKey?

No, it's not in the General or UI Layer tabs for DCS, not that I could find it. If it was it would not be good as I may map it elsewhere on my hotas in other modules. It's in the Assist section for the Kiowa Pilot and is usually available for mapping under each module. In the Kiowa, it used to be mappable to the hotas but not after the recent patch. But I am glad PC has responded quickly here on this forum (instead of their Discord only) and to the other posts on old key binding issues that I have seen, as I was afraid these simple key binding issues have low priority and rarely get fixed.

They were mappable before the 4 Dec update. Bring back this option.

POSITION LIGHTS Bright is actually Off Dim is actually Bright Off is actually Dim FLOOD LIGHTS White/Green/Off are also messed up. FIX THEM !!

Polychop had so many months to fix these simple switches but they didn't. Very frustrating.

Some fixing too needed on the CM8 DLPod missing ground texture video for MT users and maybe tweaking the GB6 SFW wind correction. The English manual is taking too long to materialize though a user made machine translation of the official Chinese manual can be found here. With the way the official manual is written in Chinese, a direct translation to English makes it read a little 'funny'. Some paraphrasing and optimisation would help. IMO, if Chuck could update his manual by cross-checking with the English translated version, that would suffice.

In the real jet, does the pilot steer the CM8 via the a) traction method (steers missile in real time), or b) designated method ('steering' moves missile cam only, designate (does not lock target) then makes missile go where crosshairs are pointing)? I'm thinking it's (a) as it's more realistic and that (b) was added to make it easier in the sim.

Yeah, Chuck's Guide (6/02/2023) pg 622 shows how it used to be, as you've all described.

Yeah it can take a while, so I don't wait for it, I just Alt+Tab out to where I want to go

With ED no, but with a 3rd party maybe.

Yeah seems like it. I happened to have a smoke effect blowing to one side near the target in my test mission and it seemed to me like the SFW was trying to compensate by flying slightly past the target. But it didn't do it quite correctly as the munitions always landed somewhat off. Update: Retested with no wind. Much better, just a little off (long).

I had a similar experience. I had a smoke effect blowing to one side near the target and I thought the SFW was trying to compensate but it didn't do it well. Update: Retested with no wind. Much better, just a little off (long).

With regard to the glide bombs, I should have clarified that I was referring to the GB6 SFW. It seems to dispense slightly right and long of the target consistently. I thought maybe it was modelled with wind correction but the area it eventually blankets still seems off. I’ll test again with zero winds to see if it gets better.

Got back into the JF-17 today after a long time away. What a disappointment. CM8 DLPod ground texture rendering in MT is still truncated. Glide bombs are still inaccurate.

The CM-802AKG has always required MITL in all 3 modes. DIR (SPI), COO (PP) and MAN (RPs) are all fly over points. It's like the IAF's Delilah, and not like the SLAM. The DLPod's missing ground texture rendering in the MT version is still not fixed as of today !!

The ground texture rendering is still truncated as of today. Makes finding your target even more difficult than it is already. FIX IT !!!