Shiroka

I'll add a track when I get a chance, but if you start a mission in a half empty harrier with no load, then rearm and add external tanks, then then refuel, it does not fill them up. Same if you do an air start with empty tanks then land and attempt to refuel - the refueling only fills up the internal tanks.

I also find once I've used the TPOD I can't change the built in FLIR WH/BH (it works fine on the HUD NAVFLIR but no change on the MPCD except the selection getting boxed/unboxed). Is this also known already?

Parking brake on

Still an issue in the latest OB (2.7.4.9847) - hopefully now that ROUTE has been redone, this will get looked at!

The NSEQ gets stuck on once you select it for the first time. Then even if you deselect it you can't remove the NSEQ overlay or reset the string in data.

Yeah, I've tried with APKWS, GBU12, GBU38, LMavs (E2). Bascially can't fire anything with the TPOD up. This is a track trying to use a GBU38 - won't let me select the station or set a fuze and no attack symbology. AV8B - GBU38trk.trk

The Map PB doesn't toggle properly. It's only unboxed when you hold it down then reverts as soon as you release. Same with the one below (OL1). AV8B - EHSD - Map Button.trk

With the latest OB: When you program a NSEQ/SEQ string initially, you can reset them fine. Once you have returned out of the data page and hit the ROUTE PB and selected an NSEQ string, the overlay stays on the map, you can't remove it. Even if you deselect NSEQ/route PB, you then can't reset the SEQ/NSEQ strings in the data page, they are stuck. Also there is no overlay for the SEQ string anymore (though this may be correct as is). AV8B - EHSD - NSEQ.trk

Yes - more details in this thread:

This worked wonders for me in VR in a G2, thank you. Quite why fixes like this need to come from "customers" I don't understand. No problem, glad I could help. It still looks pretty bad if you set the MPCDs to night (probably actually worse), but my next task is to see if I can do anything about that!

@sedenionfound something else - the AP star on the the HUD and the waypoint crosses (that appear under 10nm) are a different color to the rest at night! Not sure if that is something your mod would have changed but I don’t notice it in Vanilla

https://www.digitalcombatsimulator.com/en/files/3317400/ I combined the stuff I posted above with some of the changes from the files that were posted on the RAZBAM discord yesterday.

Could well be Out of interest what was the other error?

So I really liked @Draken35solution but some of the symbology was still getting a bit lost for me. I had a free evening just now so I spent a long time playing with values and loading up in VR. I reckon I've found a solution that works even better for me. Tested in VR on Reverb G2, 1.0PD and 90%SS. I also added comments on what I did and why in case that helps anyone else who wants to adjust for themselves. Now I can see everything clearly with no gain/contrast adjustment needed. --Overall MOD Comment: Tested in VR on a Reverb G2 at 1.0PD, and 90% Steam SS. YMMV --MOD Comment: These are used for the HUD, the current values look too thick so I reduced them by 50% to give a cleaner look stroke_thickness = 0.25 --0.5 stroke_fuzziness = 0.2 --0.4 --MOD Comment: As far as I can tell, the DMC is just used for the route lines (OL2, TERM, NSEQ). I couldn't work out --how to get an outline to appear for TERM or NSEQ (I looked at the other lua files but no joy), so adjusted this last to get them about --the same thickness as the other lines on the EHSD. I also changed the order to define the outline thickness based off --the stroke thickness not the HUD thickness above. -- Currently is used for DMC generated fonts black outline --DMC_outline_thickness = stroke_thickness * 3 --DMC_outline_fuzziness = stroke_fuzziness * 1.1 DMC_stroke_thickness = 8 --0.65 DMC_stroke_fuzziness = 4 --0.42 DMC_outline_thickness = DMC_stroke_thickness*0.25 DMC_outline_fuzziness = DMC_stroke_fuzziness*0.1 --MOD Comment: These are for the MPCD symbology. I think it looks too thick and blurry, however when you make it thinner --it becomes less readable and gets lost in the background. Therefore I made it thinner by half whilst simultaneously --increasing the outline thickness so things are still visible. I think this gives the best contrast of sharpness and --readability. -- MPCDs -- MFDs MPCD_stroke_thickness = 0.5 --0.9 MPCD_stroke_fuzziness = 0.25 --0.4 MPCD_outline_thickness = MPCD_stroke_thickness * 5 -- MPCD_stroke_thickness * 3 MPCD_outline_fuzziness = MPCD_stroke_fuzziness * 3 -- MPCD_stroke_fuzziness * 1.1

That's nailed it. Thanks for being so responsive and for all your hard work, like I said this is one of the mods that I always use so it's great to see it being kept up to date with all the M2000C changes! As a side note I did have a minor a problem (or at least something I hadn't noticed before) with the radar designation diamond staying in view after designation for a while and being on top of the VV but that may be a) as designed or b) something I'm doing wrong, so probably don't take my word for it and check it when you get a chance as I'm sure you know much better than me how it's supposed to look/work together

Thanks for the quick reply. Just tried this, still the same issue with the steering wings.

From what I found it works fine for the first waypoint in the string, then starts going crazy after that - so if you just had 2 waypoints and the second was pretty close to the first you may not see it. Try setting up 3 or 4 a couple of minutes flight distance apart

advance warning: I’m not an expert, this is just my understanding from reading the TACMAN/NATOPS and watching a few videos etc (see TACMAN vol 1 1.15, in particular 1.15.6.1). 1) when you set TOT with ROUTE unboxed on the EHSD then the TOT guides you to the currently selected waypoint (or mark point or target point I guess). So with 2) there is no IGRS or EGRS string, just a term point. Say you have waypoints 1-8 and you set 4 as TERM (ODU: TERM, UFC “03”, UFC “ENT”) then the TOT will route you through waypoints 1, 2, and 3 to arrive at 4 at the required TOT you enter (doesn’t matter which waypoint is selected when you enter the TOT as long as ROUTE is selected on the EHSD). With 3 if you set up strings as say IGRS = 1, 2, 5, 4 and EGRS = 7, 8 (for example) then set TOT with ROUTE selected on the EHSD then TOT should route you through waypoints 1, 2, and 5 to get to 4 at the right time (but it doesn’t work currentlyq due to the aforementioned CS/T bug).

Hey @sedenion firstly I love this mod, makes everything look awesome, always use it! Thank you for all the effort you put into it! Think I found a bug - with the CCRP INS bombing (using the PI/BAD) the HUD symbology is off: the steering wings should be level with the VV but they are below it. I can send screenshots if you want but it’s pretty easy to reproduce in seconds on the instant action INS bombing mission. Not sure if this affects regular CCRP bombing too, I first noticed it on the campaign M13 where you have to drop a GBU.

So I've been playing with the TOT. Here are my findings: 1) No NSEQ: Just setting a straight TOT to a waypoint works fine, but after you pass the waypoint (at the correct time), the CS/T goes to a crazy number which sticks out the left end of the UFC. AV8B TOT UFC.trk 2) TERM: This is the same setting a TERM waypoint (say I have waypoints 1-5 and I set 3 as TERM, then the TOT guides me through 1-3 to arrive at 3 at the correct time, but then I still get this crazy UFC bug). AV8B TOT TERM UFC.trk 3) IGRS/EGRS: If I set a NSEQ string, then the TOT is fine up to the first waypoint in the string, then the CS/T starts increasing exponentially until its unachievable (even though at max speed you would get to the end of the IGRS string, i.e., the target, before the TOT entered). AV8B NSEQ TOT.trk I thought these were two unrelated bugs, but after I arrived at the NSEQ target early I kept flying and the CS/T speed kept increasing until the TOT I had originally entered at which point it maxed out to the same value I am seeing when I pass the waypoint or TERM in 1) and 2). This makes me thing that after you pass the waypoint the display switches to this "max speed" (which is too long for the UFC). AV8B TOT NSEQ UFC.trk So I guess there are 2 bugs in here (NSEQ TOT, and the UFC display) but grouping them together as they may well be related.

I worked out my problem. I was trying to enter TD in the RD field on the PCN and vice versa. Working for me now.

Have the same problem with TD - I can't find the TEL button that the manual says. I tried pressing the TOP button but it's not doing anything.

May be remembering wrong but I’m pretty sure in the JF-17 special options you can set the TDC sensitivity differently for the HUD, MFDs etc. something like that would be ideal.

Are you using an X55/56 by any chance? If so I had ghosting issues with this for a while (lots of threads about it). Resolved it by buying a separate USB PCI card (about $10 from Amazon) to connect the throttle also via a powered USB hub. motherboard -> PCI USB -> powered hub -> joystick + throttle. If not, no idea, sorry.

Yeah I edited it so that it was just the changes to the AMPCD and not the MFDs, works fine for me (I haven’t tried the LMAV on the AMPCD though).