ldnz

Yeah this stopped me flying the ka-50, too annoying and confusing to glance down only to find the map is completely wrong.

Yes, if set to player or client

Its a pretty cool system if you know expected range and altitude of your target. Bit out of touch but doesn't the Mirage F1 have a similar mode?

This is great practice, helping me get my head around the radar. Love it, thanks!

Could we please get some confirmation? In the current public build there is obvious huge barometric altitude input, and no evidence of using the laser when bombing. Is this intended (and can more information be given on how to deal with it), or a bug?

Interesting, that makes sense for toss bombing

Thanks, but which part of the calculation? Just density? Right now it appears only barometric altitude is used in the slant range calculation, not laser

In opt mode, a2g, in a dive with a good steady solution bombs appear to always fall short. In active pause, the only thing that appears to affect the indicated slant range is the altimeter setting, laser makes no difference. It appears that radar altimeter and laser aren't being used for slant range calculation, only baro alt. Unsure, but in previous mission in mountainous terrain I found a2g cannon with laser (I think, but altimeter would have been no use) to be pinpoint accurate, so possibly just not right with bombs. LastMissionTrack.trk

Yep, with no idea how barometric/radar/laser ranging is supposed to interact, let alone whether (ED known) bug fixes have been delivered yet its pretty tricky to proceed.

I tried this on Nevada and saw similar. I was trying to zero the altimeter (for Groom Lake QFE) and found that my bombs were miles out and I go NOLA warnings. Also using pre-desig when set with altimeter far from QNH I noticed the desig symbol altitude is wrong. Had A for laser on the hud, but it seems almost like only barometric altitude is being used (in a dive so probably too steep for radar?) not laser range

Yep, my design was as close to a paper approach as I could get while still being usable in VR - so although it has the slide rule, it will do the basic calcs for you as well. But no gps, everything is manual, POI, sam locations, the lot. Fixes are placed by double tapping where you think you are - so if you don't plan well with good landmarks its easy to misjudge and get lost. I've found I can comfortably get TOT within +/- 10 seconds with this approach, with or without INS (though INS more useful higher you get/more cloud cover/night - blue ticks are at 5nm (or 5km if in metric) from waypoint so you can glance down and see where you should be up to compared to INS distance to go, and purple ticks are minutes to go as planned. I was improving fix logging and got this flight through South Atlantic in a gazelle with its tablet disabled and no INS that was cool image.pngimage.png

I kinda built this sorta thing for my own use - a simple little server app that pulls the map tiles and navaids from DCS, and is designed for manual, warbird, helo, F-4 style nav. I use it within openkneeboard with a wacom tablet. You can double tap to select a point and use it as a waypoint, threat mark or a nav fix, or can use the new alt-click in the F10 map and then copy to clipboard to get coords easily from DCS. If anyone is interested I've been meaning to polish it up for an opensource release.null

Try full dirty, 80kn, left turn and apply throttle anything other than smoothly - you'll definitely see an aggressive snap roll. Easy to avoid if you're conscious of it, but I've replicated all the spin into the drink footage by accident

Huh my apologies for poor information earlier - quite right it doesn't trim follow. In VR I'd just naturally been adding in trim and centering my stick, just checked in pancake and yeah, even at 80 kn with full flap and heaps of nose up trim the stick position is centered.

I got this to work from the hooks environment: return net.dostring_in('scripting', "local mps = world.getMarkPanels(); local mps2 = {}; for k,v in pairs(mps) do table.insert(mps2,v['text']); end; return table.concat(mps2, '|')") It seems that only trivial return values are being passed - single number or string, no complex objects. I wish there was a way for this to work online too. I can't believe its not possible to get the mark panels which are literally user generated points, would be so handy for any DTC type tool (or in my case plotting board style nav kneeboard)