tekwoj

2 questions. Do you have any mods installed and can you upload a track so that others can take a look at what's going on? The WMD issues sound a bit familiar but at the same time more extreme (and more consistent) than anything I had issues with.

In your 2nd screenshot it didn't disappear, the colors are still a little washed out. When canopy is partially fogged up certain angles of light will make it more opaque. I don't manage to reproduce that extreme effect on my side without fogging up the cockpit. Might be some settings that cause it. And yeah, wish everything wasn't dirty and that we had a working visor.

Are you sure your canopy is not just fogged up? My canopy is opaque only in the back section where angle becomes very narrow.

Open the chinese manual, search VS, go to the VS chapter, copy it to google translate, here's the relevant part translated: The quick guide mentions only TWS for SAM mode, it's Chuck's guide that has an error.

I was able to use it few months ago, the trick was to play a bit with gain and level, using the designated steering mode. Taking control before the missile reaches the 10nm distance also helped.

I wasn't aware AK has a mode where it doesn't activate the radar. Is it documented anywhere?

We have very different experiences, from what I see in the game AK works fine, AKG is currently supersonic and not flying the correct profile, GB6 is fine, LS6 will fly into your wing because for some reason they loft unless you swap stations before launching them. Can you expand which AK launch mode doesn't work and what steps you're taking?

test_dst.mizdst59 bug.trk @uboats here's an example mission and track attached showing bug. Steps to reproduce (did it in hot start, didn't test if it happens during cold start): 1. Load the cartridge in, load at least the Nav data. 2. Select WPT 59 3. Press DST 4. On the left MFD make sure that waypoint 59 is selected. Press CLR. 5. Enter a valid value for latitude 6. Press button to confirm the value, it will remove the value but not save it. 7. Try the same for other waypoint parameters, the result is same as for latitude.

ED being ED, they change weapons without testing if it brakes other modules.

The ED flight plan tool replaces any waypoints created by mission maker with what you create before spawning in. It's going to be treated as if it was a flight plan created by the mission maker, so planes that use DTC like Jf-17 or Viggen will have the waypoints available the moment they load the cartridge. Exactly same as normal. The F10 map nav points that you create when you're spawned in the mission: WPT don't work. Others do. They require DTC update because your cartridge has some other flight plan loaded when you spawned.

That's my point, the dtc that's "in your hand, but not yet sloted in the socket" when you do hot start already has the planned route in it. No need to ask for update.

I've tested it in hot start from the ground, you just have to put the dtc in and the moment the nav data is loaded the route should show on HSD

Do you have a bind for Fuel Pump and is it by chance close to speed up/down time? The only alarm lit up after the view swaps to the cockpit is Fuel Pump warning light.

Steps 4 and 5 are not necessary, it will treat the created route as if it was prepared for the plane in mission editor.

AFAIK F10 at the moment allows you to enter only PP/RP points and the air zones. No flight plan waypoints.

From what I can translate in google translate from the Chinese manual - maybe usually but not necessarily in this case.

Why is everyone so bent on the manual? There's a good chuck's guide for JF-17, not like the manual brings anything more.

Can confirm it's bugged. If you clear the point 59 first then you can't enter anything. Workaround is either not clearing it before or if you did then do what Napillo wrote.

Do you have any mods installed? Are you running multithreaded version of DCS? I've ran your track file, if I take over control before the view switches to plane, the engine works fine.

Yeah, it's going to be one of the mods. Last time me and someone else had this kind of difference was caused by mods.

Yes, I know it can be very convenient with weapons that can have more complex setups. However if I'm using gbu + rocket pods it means that when I fence in I have to go through all the pages and set fuzes on each page or else I risk that in combat I pull up a page where it's still set to the default safe. In simple missions with limited loadouts I need only 1 or 2 pages. On a side note I'm not sure LD-10 in SP mode is useful lately, damage is very low and it seems to hit always offset rather than a direct hit.

My question was meant as "is there a way to reduce page number". I guess a pilot doing a2g will rather use mfd buttons to manually select page cause they are in their hand's reach and weapon switch is only for a2a engagements.

That brings a lot to a discussion where we try to figure out why someone's rockets don't hit target.

I watched the track, 3 rockets hit, 4th one misses cause it's launched too close and it can't turn hard enough to hit the target (but it really tried so don't be angry at it). Here's the video If on your end it looks different, do you have mods installed?