LazyBoot

How does the new ground safety override work?

Just checking... does this mean it passes IC or gets flagged by IC?

Are you using the unofficial english cockpit? If so, that's known to be broken in this patch... And you should probably re-test without it.

The new kneeboard options for things like the RB04 settings and the safety height does not seem work on cold start... only on hot starts

Currently all the Viggen anti-ship missiles requires you to stay alive for them to guide properly.

I can't seem to get these to work... pressing them does nothing EDIT: It seems to work from a hot start, but not a cold start. EDIT2: I'll make a separate bug post for this, so it's easier to track

Here's what I see when I do that... Datalink status are still clearly showing even on "none" While what I would like to have some way to see would be something closer to what is shown with datalink off (as in the image below), but without needing to turn the entire datalink system off

Last time I tested, this did not work... It would only hide contacts your own fcr haven't detected, but any the fcr has detected will still be shown with all datalink information. The only way I've found to see the underlying track status (and not datalink info) is to turn off the datalink using the mids switch.

I am certainly happy to see how many things you guys have managed to get fixed... And I'm also happy that my little feature request (about the ground crew settings) managed to get in

Looks like Cobra has posed a preview of the upcoming change log over on reddit And it's looking awesome! https://www.reddit.com/r/hoggit/comments/rij8ip/dcs_newsletter_prepare_for_open_beta_279_voice/hoxjn8a/?utm_source=reddit&utm_medium=web2x&context=3

So they'll be manually configured instead of automatically now (soon™)?

if you set the base selector (righthand knob) to "ALLM" you can use the "A/G", "C/F" and "D/E" buttons to access G, F and E respectively.

Why "avoid"? you can easily access E, F and G from the FR-22 as well Though I'm thinking the bugreport is about the group numbers (in yellow on my screenshot), not the presets that @Flappie is talking about.

take just the image files and drop them into c:\users\<username>\Saved Games\DCS\Kneeboard\AJS37

It's been like this for as long as I can remember. I believe it has to do with how the guidance has been implemented.

I believe it was Cobra, not IronMike

The reason why you're not seeing a box is because the system thinks it has found it very accurately... According to the coordinates in the file you provided, there's only 1 second of uncertainty, so the box will be tiny. As for the position error... Are you making sure to keep your nav drift to a minimum? I've noticed that especially when circling, drift tends to accumulate a lot faster than the estimation shown on the info panel.

fair enough... if you insist @IronMike

I guess I was hoping he'd see it without needing to be tagged... It's not like this sub-forum moves all that quickly. However it's hard to know since there's been no official replies.

Would it be possible to be able to edit the "groundcrew settings" from either the kneeboard or the ground crew menu when landed at an airfield/farp or otherwise near ground crew?

This is what I get on the airbase kneeboard page on Syria. Almost 20 bases are missing, and no space for FARPs or anything else. Though all of this is mostly just workarounds anyway... I'd still like to know if there actually is a way to assign L1 and/or L2 points to road bases or FARPs in the mission editor. And if there isn't, then I'd like to ask Heatblur if something can be added to allow for this.

Another quirk I ran into during testing, it seems ships also gets their own codes in the list. Since it would set those as L1 as well, if they were the closest at spawn.

Testing with just a single FARP gave code 9052... Though I'd still prefer if something a bit more user friendly was available. Like what if the mission requires the use of more than one FARP...? Like for example one for a road base, but multiple helicopter bases

In this case that doesn't work, since the map is Syria which already have too many airbases to show on the kneeboard.

Attempting to enter coordinates for a roadbase though the datapanel doesn't update the REF/LOLA, just staying on whatever base was already loaded as L1. Though it seems to track towards the new point. viggen-L1-coords.trk