Radar display export

[brettt777]

I am wondering if there might be any chance of Heatblur ever setting the Viggen up to be able to export the radar display to an MFD, such as a Winwing system. I have a three MFD Winwing setup but the Viggen isn't an aircraft that can have it's radar exported onto an MFD. I also have a triple monitor setup. And the thing about that is that when the display is so wide like that, you can't zoom out far enough to be able to see any of the instrument panel without slewing the display down a bunch. Then of course, you can't see what's going on outside. Most DCS aircraft have at least one or two devices than can be exported. A few don't like the F-4E Phantom and of course, the Viggen. The F-1 Mirage isn't on the Winwing SimAppPro list but for some reason, it's radar display just shows up on one of my MFD's, which is quite nice. I wish the Phantom and the Viggen would do that.

[Zabuzard]

Its in the backlog. So yes, it will eventually be done.

[MAXsenna]

I am wondering if there might be any chance of Heatblur ever setting the Viggen up to be able to export the radar display to an MFD, such as a Winwing system. I have a three MFD Winwing setup but the Viggen isn't an aircraft that can have it's radar exported onto an MFD. I also have a triple monitor setup. And the thing about that is that when the display is so wide like that, you can't zoom out far enough to be able to see any of the instrument panel without slewing the display down a bunch. Then of course, you can't see what's going on outside. Most DCS aircraft have at least one or two devices than can be exported. A few don't like the F-4E Phantom and of course, the Viggen. The F-1 Mirage isn't on the Winwing SimAppPro list but for some reason, it's radar display just shows up on one of my MFD's, which is quite nice. I wish the Phantom and the Viggen would do that.

Apologies! But you are mistaken, while you are in luck! You can absolutely export the radar and the maverick sight, (end some other displays), in the Viggen, while they are probably not enabled by default. Look up how to do it in Helios and export threads. As I'm on vacation and don't have access to the information by heart.
For the Viggen I use an Icarus profile, and have all the instruments and RWR on a seconds screen. For the Mavericks I actually put the export on my main screen, because that's a more realistic position.
Basically every module can export relevant displays. Even in the MB-339 I export the gunsight, radio digital displays, the GPS, etc.
Cheers!

Sent from my SM-A536B using Tapatalk

Its in the backlog. So yes, it will eventually be done.

You, should be more accurate. That it's absolutely possible now, for any user, while you haven't enabled it in the files yet. It does break IC though.

Sent from my SM-A536B using Tapatalk

[brettt777]

19 hours ago, MAXsenna said:

 

 

Apologies! But you are mistaken, while you are in luck! You can absolutely export the radar and the maverick sight, (end some other displays), in the Viggen, while they are probably not enabled by default. Look up how to do it in Helios and export threads. As I'm on vacation and don't have access to the information by heart.
For the Viggen I use an Icarus profile, and have all the instruments and RWR on a seconds screen. For the Mavericks I actually put the export on my main screen, because that's a more realistic position.
Basically every module can export relevant displays. Even in the MB-339 I export the gunsight, radio digital displays, the GPS, etc.
Cheers!

Sent from my SM-A536B using Tapatalk

You, should be more accurate. That it's absolutely possible now, for any user, while you haven't enabled it in the files yet. It does break IC though.

Sent from my SM-A536B using Tapatalk
 

 

Well, I tried to do it on my own with the F-4E Phantom and was somewhat successful... kind of. What I ended up with was an overlay of the APG-120 radar on the main display. The display worked as it should even thoug it wasn't where I wanted it, but it had no returns at all. I was wondering if the maker would ever attach the planes to the Winwing app, SimAppPro. 

[MAXsenna]

Well, I tried to do it on my own with the F-4E Phantom and was somewhat successful... kind of. What I ended up with was an overlay of the APG-120 radar on the main display. The display worked as it should even thoug it wasn't where I wanted it, but it had no returns at all. I was wondering if the maker would ever attach the planes to the Winwing app, SimAppPro. 

You can't do it with the F-4 yet. The Viggen, no problem.

Sent from my SM-A536B using Tapatalk

[TheBiggerBass]

vor 20 Minuten schrieb MAXsenna:

You can't do it with the F-4 jet. The Viggen, no problem.

Sent from my SM-A536B using Tapatalk
 

I tried to export the MFDs on a F-4 some months ago but was told that F-4 does not support that (yet?). If there is an update let me know how.

[MAXsenna]

I tried to export the MFDs on a F-4 some months ago but was told that F-4 does not support that (yet?). If there is an update let me know how.

Yeah, "yet", not "jet". Bloody AC!
So, as of now you can't export in the F-4E successfully.
Cheers!

Sent from my SM-A536B using Tapatalk

[brettt777]

On 4/20/2025 at 3:32 AM, TheBiggerBass said:

I tried to export the MFDs on a F-4 some months ago but was told that F-4 does not support that (yet?). If there is an update let me know how.

 

On 4/20/2025 at 3:41 AM, MAXsenna said:

Yeah, "yet", not "jet". Bloody AC!
So, as of now you can't export in the F-4E successfully.
Cheers!

Sent from my SM-A536B using Tapatalk
 

Okay, I figured it out for both the AJS-37 and the F-4E. Here's what I did...

I added the following to one lua file for eack aircraft.

For the AJS-37, it was "Install directlry/Mods/Aircraft/AJS-37/Cockpit/Scripts/Radar/Indicator" and the file is called init.lua.

For the F-4E, it was "Install Directory/Mods/Aircraft/F-4E/Cockpit/Scripts/DSCG/Indicator/DSCG_Pilot" and the file is called init_bake.lua. 

In that same "indicator" directory there is also a directory called DSCG_WSO. There is an "init_bake.lua" file in that one as well. I think it is safe to assume that this same code can be added to that lua file and you could have a radar display exported from the WSO seat as well. I have done this but I haven't tried it yet.

 

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")

local HUD_onlyRightAligned = true
local HUD_onlySz = 0 --8

if HUD_onlyRightAligned then
    update_screenspace_diplacement(1, false, HUD_onlySz)
    try_find_assigned_viewport("RIGHT_MFCD")
else
    update_screenspace_diplacement(1, true, HUD_onlySz)
    try_find_assigned_viewport("LEFT_MFCD")
end

 

This was the same code I found in a similar file for the F-1 Mirage. Now, for this to work, your monitor setup has to match it. This is how I did that. I will be somewhat different for anyone else cuz my monitor setup is... different. I have three 2560x1440 curved monitors that are my main game picture and then I have the three Winwing MFD USB displays that are for display exports. If you have Winwing stuff and use the SimAppPro app, then when ever you have an MFD setup selected that uses at least two MFD's, then the above code will work. If not, you will have to create a lua file for it. This is one that I can use instead of the Winwing file.

 

_  = function(p) return p; end;
name = _('BCTCockpit');
Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center'

Viewports =
{
    Center =
    {
        x = 0;
        y = 0;
        width = 7680;
        height = 1440;
        aspect = 5.333333333333333;
    }
}
UIMainView = Viewports.Center
GU_MAIN_VIEWPORT = Viewports.Center

LEFT_MFCD =
{
    x = 5128;
    y = 1696;
    width = 752;
    height = 762;
}

RIGHT_MFCD =
{
    x = 6664;
    y = 1696;
    width = 752;
    height = 762;
}

CENTER_MFCD =
{
    x = 5896;
    y = 1696;
    width = 752;
    height = 762;
}

 

Again, this one matches my particular monitor setup. You would have to figure out your own X/Y coordinates for whatever monitor setup you have, and obviously the name can be whatever you want. This .lua file will be in "Install Directlry/Config/Monitorsetup". If you only have one MFD you want to export to, you obviously wouldn't need the "LEFT_MFCD, RIGHT_MFCD, CENTER_MFCD" entries like I have. As long as the first code group that goes in the init.lua matches the monitor setup, it works.

I do apologize if I am telling y'all a lot of stuff you already know. 

Now, as I said, this worked for the Viggen and for the Phantom. This was all I did for both aircraft. I didn't see anywhere else where the Phantom needed to be "activated" or some such thing. That being said...  one  issue with the Phantom export. Whereas the exported radar display on the Viggen worked perfectly on my Winwing MFD without any weird brightness or contrast adjustment, not so with the Phantom radar display. If you do the first part of this mod and add the code to the DSCG_Pilot init_bake lua file, you will get the radar display on your MFD. But it is extremely bright and saturated. To get the MFD display usable, I had to adjust the brightness and contrast and everything else to get it there. In doing so, it made the radar display inside the cockpit on the game display too dark to see. I have another mod installed that allows me to adjust the picture/s on my MFDs separate from the main display. This helped me get the MFD display usable but I still had an extremely dim radar display on the game page. Ironically, when I first got some kind of export for the Phantom, it showed as an overlay on the main display. After I added that group of code to the init_bake.lua file, I got the radar on the MFD as I wanted but I also still had the overlay. When I had it like this, I had no brilliance issue with the MFD. It looked great. It wasn't until I removed that code group from a different init.lua file in the "ControlsIndicator" directory that I had the brilliance issue. It got rid of the overlay on the main game doisplay but then my MFD radar picture was just a big bright blob.

So, anyone have any idea how I can dim my Phantom MFD radar display without having to reinvent the wheel everytime?

I'd also like to know what/where they have the gauge files because I would really love to have the F-4E HSI and altitude or airspeed on the other displays if possible. Especially since there is no flight or navigation data on the HUD.

 

 

Edited April 27 by brettt777