PiedDroit

I can confirm this happening, I've been doing a mock fight with a friend, one in front each other at ~30NM, he had me locked, then I dived while beaming his radar and he lost lock. After that, he couldn't pick anything on the radar and it was still in PIC on the VTB. Until he pressed unlock.

I was talking about the radar caret on the VTB, not interception flight director VTH. Here's a picture showing how I guess radar azimuth will be shown on the VTB - again, it's a guess ;)

Can anyone explain me how that is displayed on radar screen ? I dont see radar Azimuth or elevation infos on screen ? I think the little caret indicating radar sweeps will show it (on top of radar screen), by only sweeping one portion of the radar screen. The radar screen itself covers the full 120° so that should be enough I suppose. Maybe there's additional symbology as well?

You're the best, we know, thanks, that's very helpful. Will check that out, thanks. How to feel the movement of the aircraft is unfortunately difficult to get from a video.

I'm really struggling with it right now, I find much harder than with A-10C. The big difference is that with A-10C the operator guides the boom, so you only need to have a stable flight behind the tanker. There is no one to guide the basket, and when you start oscillating things get really ugly, quickly. Also the Mirage is much more snappy than the A-10C, aggravating said oscillations. I will continue practicing... So far one effective technique I found is to focus on putting the FPM at the same time on the basket and on the horizon. Then focus on keeping the FPM very close to the horizon, to limit altitude changes when readjusting altitude. After connection, trying to stay in formation by using the FPM again, but I have yet to find a good visual reference as the tanker is then almost completely hidden by the canopy. Usually I stay connected only a few seconds :doh: The fact that M-2000C is WIP also doesn't make the task easy, S-3B changes speed while refueling (discussed here). Also I don't always trust the artificial horizon as it has a tendency to shift a bit when banking.

You can take off with a cold radar, so you don't even have to wait.

Maybe standby gunnery piper? (in French viseur=reticle and visière=visor so it's easy to confuse the two)

I export the radar on the main screen (on a 512x512) Viewport). If I want to glance at the radar while looking elsewhere, I use the toggle key then I hide the radar again. But I can't keep it on all the time because I find it obstructive. I fully understand your point of view too, this is why instead of calling for a feature removal I prefer asking for something tbat makes it flexible enough. In that case, an option somewhere that controls the initial visibility state of the viewport. It could be done in game options or from the monitor configuration .lua The only thing I don't like much right now is the transparency of the display.

I must have missed it, will look again thoroughly, thanks.

Great, thanks for your efforts! :thumbup: Is there a keyboard shortcut to go in SIL? Right now we can only do ON/OFF ;)

My guess is that it's not their primary mission, so they don't have the controls to do that on the HOTAS, it requires additional wiring, either to add new controls or to connect existing controls to the A-G targeting system. In the end, the gain is minimal, since in the limited A/G configurations, those aircraft can at best drop dumb bombs that are not accurate or laser-guided bombs that do not require high delivery accuracy. Also they don't have the target marking ability. However what is annoying with the Mirage is designator drifting, I attribute this to the lack of accurate target distance measurement at the moment (only radalt is available, no radar beam distance measurement yet). While I'd be interested to see some slewing available, I don't count much on it...

Some people do not use a secondary monitor and welcome the ability to toggle the display.

I won't complain, the more, the better ;)

Some of the bad reviews on Steam are quite funny :D

Terrain mapping? Flabbergasting! I genuinely though this radar couldn't do that.

Ground avoidance has nothing to do with A-G, that's why I didn't mention it. I don't think it needs anything from A/G radar, my understanding is ground avoidance is merely something that checks if there is any obstacle in front of the aircraft and send pull commands to the flight controls if something is detected that risk a ground collision. This is much different from low altitude penetration mode that maps the ground in order to allow very low flying.

Ranging, fixed beam only.

Interesting, thanks for the link. I want to keep it vanillia but if I'm really desperate I'll have a look at it.

When radar warmup is implemented we'll need a keyboard shortcut to go from ON to SIL :music_whistling:

Thanks! Looks promising!

I assume we all want it fast and at a fair price :music_whistling:

It's hidden on the left wall, right below the hook/parachute lever.

The crash is caused by the 476 range object or Ranger 79 mods. It's a lua error, if you dig which function causes it then search for it in the lua files, you end up in the lua files from those mods. Just remove them and you're good. More info: In "Scripts/Database/scripts/utils.lua", line 31: Search for it: ...\Mods\tech\476 Range Targets\Aim_Off_Marker.lua (2 hits) Line 5: set_recursive_metatable(GT, GT_t.generic_stationary) Line 6: set_recursive_metatable(GT.chassis, GT_t.CH_t.STATIC); ...\Mods\tech\476 Range Targets\Conventional_Circle_A.lua (2 hits) Line 5: set_recursive_metatable(GT, GT_t.generic_stationary) Line 6: set_recursive_metatable(GT.chassis, GT_t.CH_t.STATIC); etc ...\Ranger Pack\buildings.lua (90 hits) Line 9: set_recursive_metatable(CWAA, GT_t.generic_stationary) Line 10: set_recursive_metatable(CWAA.chassis, GT_t.CH_t.STATIC); Line 36: set_recursive_metatable(CWAB, GT_t.generic_stationary) etc

Cool :D If you missed it, please read this interesting comment from zaelu, and my answer on next page: http://forums.eagle.ru/showthread.php?t=161075#10 I think it should have a black background and not be transparent.

Why not? Head tracking, limited FoV and resolution doesn't make it easy to glance at the HDD. However, the transparency we get with the HDD viewport is a bit too much HUD-like, I'm with you here. I think it should be with a black background all the time.