Export to second monitor

[Padonis]

Has anyone tried exporting RWR or radar to a second monitor?

[7HUNDERH0R53]

I'm also looking to do this and would love to know if it's possible. In my MonitorSetup lua, I've tried F4_DSCG, F4_RWR, PHANTOM_DSCG, F4_RADAR & PHANTOM_RADAR and none of those work.

[bones1014]

I'm also interested in doing this.

[Wostg]

I remember export for the f-15e had to be 'switched on' by the devs, it happened in the first or second patch about a week after release

Edited May 24, 2024 by Wostg

[Zera321]

I was able to get the RWR to export to work.

I added the following lines below, with "F14_F4E_RWR" being whatever you want to label the export in your MonitorSetup.lua. In this case, I use the same location for both the F-14 and F-4E RWRs on my second monitor.

--ViewportHandling
dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
update_screenspace_diplacement(1, true, 0)
try_find_assigned_viewport("F14_F4E_RWR")

Place at the bottom of the code in the following lua. Recommend using Notepad++.

DCS World OpenBeta > Mods > aircraft > F-4E > Cockpit > Scripts > RHAW > indicator > init_bake

I am continuing to work on the radar export but haven't had a lot of time.

[Padonis]

OK, now I have it too, but I had to change the user permissions, I couldn't edit it before... it's DSCG's turn

 

Edited May 26, 2024 by Padonis

[jiandaolaoda]

20小时前，Zera321说：

I was able to get the RWR to export to work.

I added the following lines below, with "F14_F4E_RWR" being whatever you want to label the export in your MonitorSetup.lua. In this case, I use the same location for both the F-14 and F-4E RWRs on my second monitor.

--ViewportHandling
dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
update_screenspace_diplacement(1, true, 0)
try_find_assigned_viewport("F14_F4E_RWR")

Place at the bottom of the code in the following lua. Recommend using Notepad++.

DCS World OpenBeta > Mods > aircraft > F-4E > Cockpit > Scripts > RHAW > indicator > init_bake

I am continuing to work on the radar export but haven't had a lot of time.

did this broke the IC check?

[kadorno]

Question, do you notice that the RWR export causes a repeat of the RWR on the HUD?

[Darkdiz]

I have both the RWR and DSCG working (that is exporting to the correct monitor in the correct position). However, the DSCG only exports a blank, white screen, not what is displayed on the pilot/wso display. Still working on it.

 

[Padonis]

I managed to do it too, but the effect is the same as yours.

I also managed to export the radar, but unfortunately it displays on all monitors and does not respond when I try to scale it to the right place.

Edited May 28, 2024 by Padonis

[Darkdiz]

I think its a bug tbh. The RHAW works fine, but not the DSCG. The radar scaling is clearly SOMEWHERE, just haven't found it.

Hopefully a fix at some point

[Loophole]

I've *almost* been able to get the DSCG export working.  I can get the radar and the Maverick TV display to export to a viewport, but when I do that I *also* get the radar grid-lines (only) displayed full-screen across my entire view!  Have not found why that is or how to stop it happening, which is annoying because otherwise the export works really nicely!

What I did was add the lines:

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
try_find_assigned_viewport("F4E_DSCG", "RIGHT_MFCD")

at the end of the two files:

F-4E\Cockpit\Scripts\DSCG\indicator\ init.lua
F-4E\Cockpit\Scripts\DSCG\Indicator\DSCG_Pilot\init_bake.lua

("F4E_DSCG" being my custom viewport defined in monitorconfig, of course)

 

[Darkdiz]

6 hours ago, Loophole said:

I've *almost* been able to get the DSCG export working.  I can get the radar and the Maverick TV display to export to a viewport, but when I do that I *also* get the radar grid-lines (only) displayed full-screen across my entire view!  Have not found why that is or how to stop it happening, which is annoying because otherwise the export works really nicely!

What I did was add the lines:

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
try_find_assigned_viewport("F4E_DSCG", "RIGHT_MFCD")

at the end of the two files:

F-4E\Cockpit\Scripts\DSCG\indicator\ init.lua
F-4E\Cockpit\Scripts\DSCG\Indicator\DSCG_Pilot\init_bake.lua

("F4E_DSCG" being my custom viewport defined in monitorconfig, of course)

 

I HAD that, but I managed to get rid of it by adding the following to the dscg/indicator/init.lua between dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") and try_find_assigned_viewport lines:

update_screenspace_displacement(1, true, 0)

It should look like this... (my custom viewport is F4_DSCG)

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
update_screenspace_displacement(1, true, 0)
try_find_assigned_viewport("F4_DSCG")

I also added the same line as above to the following files:

/indicator/Radar_indicator/radar_page.lua, TV_Indicator/walleye_page.lua, pave_spike_page.lua, maverick_page.lua and hobos_page.lua.

There is STILL a bug that I haven't figured out yet... When you select (arm) one of the stations you have a tv on (Maverick, Walleye etc) you get the image not only on the monitor, BUT IN THE MIDDLE OF THE HUD! Clearly a bug. Seems that whichever the first monitor export you define (I also have the ALR46 exported to a different monitor), this will be displayed in the center of the HUD. If I disable the ALR46 export, the DSCG image gets displayed in the HUD.

One more thing I see: If you switch from Radar to TV and get an image, the crosshairs from the TV display will remain on the radar image.

Its early access, so I guess these things are to be expected. I'll be playing with this, and trying to sort out a few other issues today

[Darkdiz]

So after more f!@#ing around with this...

RHAW export works fine, I couldn't see any side affects of this export. To export this, do the following:

Monitor config file, add your viewport. I called mine F4_ALR46, the final input into this lua file should look something like:

--///////////////////////
--F-4
--///////////////////////

F4_ALR46 = -- MFD 2
{
    x = 1205;
    y = 600;
    width = 600;
    height = 600;
    aspect = 1--600/600
}

--F4_DSCG = -- MFD 1
--{
--     x = 90;
--     y = 600;
--     width = 595;
--     height = 595;
--     aspect = 1--600/600
--}

Note that I have double-dashed my DSCG viewport, just too many bugs right now in this export, I'll discuss that later in the post.

For the ALR46, you will have to adjust the x and y pixel coords, as well as the width, height and aspect for your own setup.

For the DSCG, clearly a few bugs that need to be worked out by HB. In no particular order:

1 - If the DSCG is exported, I lost my ability to control the radar cursor. Bindings work without the export. Range NOT displayed on the DSCG

2 - If a TV source is selected, it displays, but also displays on the HUD. Looks like its the first monitor export contents that are displayed (so since mine is the ALR46, this is what got displayed, if I disabled this export, the TV image was displayed)

3 - Most folks get the radar grid lines displayed over their entire DCS-defined screenspace. After much testing, I found that adding

update_screenspace_displacement(1, true, 0)

to various files in addition to the

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

lines got rid of the overlaid gridlines.

4 - Finally, if you select a TV source, the targetting crosshairs (looks like # on the display) will remain on your display, and cannot be erased (at least I did not find a way)

The list of files I played with are as follows, all in the mods/aircraft/F-4E/cockpit/Scripts folder

RHAW/Indicator/init_bake.lua --> added

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

DSCG/indicator/init.lua

DSCG/indicator/DSCG_Pilot/init_bake.lua, DSCG/indicator/DSCG_WSO/init_bake.lua --> added

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
--update_screenspace_displacement(1, true, 0)
try_find_assigned_viewport("F4_DSCG")

Note the update_screenspace_displacement(1, true, 0) is remmed out (ignored by the system)

Radar_Indicator/radar_page.lua, TV_Indicator/hobos_page.lua, init.lua, maverick_page.lua, pave_spike_page.lua, walleye_page.lua --> added

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

TV_Sensor/init.lua --> added
dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
--update_screenspace_displacement(1, true, 0)
try_find_assigned_viewport("F4_DSCG")

Clearly more testing needed here, there are a myriad of combination left to try (I never got around to playing with the remaining files in the TV_Sensor folder other than the init.lua file.

As I stated above, Until someone with more talent (and time) than I figures out the DSCG export, I'm just going to use the ALR46 export.

Sorry for the long a technical post, good luck to folks who use this try try and move the football.

Diz out

[Loophole]

9 hours ago, Darkdiz said:

After much testing, I found that adding

update_screenspace_displacement(1, true, 0)

to various files in addition to the

I think the method name you meant to use is update_screenspace_diplacement - with the typo in the name?

[Darkdiz]

17 hours ago, Loophole said:

I think the method name you meant to use is update_screenspace_diplacement - with the typo in the name?

Could be. The post I got it from said diplacement, but to me that didn't make sense, so I changed it to displacement. Did you test it with diplacement? If so, did it work? Hope so, that would be AWESOME!

UPDATE: Tried it with diplacement, I get the whole screen grid once again, and no ability to control the radar cursor

Edited June 2, 2024 by Darkdiz

[Loophole]

4 hours ago, Darkdiz said:

UPDATE: Tried it with diplacement, I get the whole screen grid once again, and no ability to control the radar cursor

Same for me.  update_screenspace_diplacement is the right name for the method - if you do a search of all the Lua scripts in DCS you'll find its defined in ViewportHandling.lua with that misspelled name.  I found that putting in the call with corrected spelling resulted in no export at all for me - I'm assuming the scripts fail because they can't find the method.  I didn't test your full process, though; I only tested putting the call into the "initxxx" lua's.

Oddly, early on in my testing the "TV on the HUD" thing happened to me, but in all my subsequent tests it hasn't happened again; just the full-screen grid, even with TV up on the DSCG.

One thing I did notice is that the grid itself (but not the horizon line) is a texture, not drawn lines - which in itself makes no difference, but does explain how it come to exist when the draw_grid and draw_ppi_grid methods in radar_page.lua never get called by anyone. 

I've put a post about this in the Bugs sub-forum, so hopefully Heatblur will notice and put it on their to-do list, if it isn't there already.

[Darkdiz]

Outstanding work Loophole, outstanding.

Maybe the "displacement" spelling works, because IIRC when I remmed certain ones out as in my original post I got a different result on the display.

At the end of the day though, clearly a bug

[Usagi]

The radar grid at HUD seems also go away if you use DLAA as anti aliasing method so there's clearly something weird going on. How can anti aliasing method affect the placement of the radar display in DCS display?

[Padonis]

I would like to refresh the topic, has anyone managed to export DSCG correctly?

[MAXsenna]

1 hour ago, Padonis said:

I would like to refresh the topic, has anyone managed to export DSCG correctly?

I thought I had. Unless I do a repair, I have it looking great, on the HUD. Probably have the export placement wrong. While I do have a green round empty circle on my second screen. It feels like they should have been on top of each other.  

[Padonis]

On 6/1/2024 at 7:16 PM, Darkdiz said:

So after more f!@#ing around with this...

RHAW export works fine, I couldn't see any side affects of this export. To export this, do the following:

Monitor config file, add your viewport. I called mine F4_ALR46, the final input into this lua file should look something like:

--///////////////////////
--F-4
--///////////////////////

F4_ALR46 = -- MFD 2
{
    x = 1205;
    y = 600;
    width = 600;
    height = 600;
    aspect = 1--600/600
}

--F4_DSCG = -- MFD 1
--{
--     x = 90;
--     y = 600;
--     width = 595;
--     height = 595;
--     aspect = 1--600/600
--}

Note that I have double-dashed my DSCG viewport, just too many bugs right now in this export, I'll discuss that later in the post.

For the ALR46, you will have to adjust the x and y pixel coords, as well as the width, height and aspect for your own setup.

For the DSCG, clearly a few bugs that need to be worked out by HB. In no particular order:

1 - If the DSCG is exported, I lost my ability to control the radar cursor. Bindings work without the export. Range NOT displayed on the DSCG

2 - If a TV source is selected, it displays, but also displays on the HUD. Looks like its the first monitor export contents that are displayed (so since mine is the ALR46, this is what got displayed, if I disabled this export, the TV image was displayed)

3 - Most folks get the radar grid lines displayed over their entire DCS-defined screenspace. After much testing, I found that adding

update_screenspace_displacement(1, true, 0)

to various files in addition to the

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

lines got rid of the overlaid gridlines.

4 - Finally, if you select a TV source, the targetting crosshairs (looks like # on the display) will remain on your display, and cannot be erased (at least I did not find a way)

The list of files I played with are as follows, all in the mods/aircraft/F-4E/cockpit/Scripts folder

RHAW/Indicator/init_bake.lua --> added

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

DSCG/indicator/init.lua

DSCG/indicator/DSCG_Pilot/init_bake.lua, DSCG/indicator/DSCG_WSO/init_bake.lua --> added

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
--update_screenspace_displacement(1, true, 0)
try_find_assigned_viewport("F4_DSCG")

Note the update_screenspace_displacement(1, true, 0) is remmed out (ignored by the system)

Radar_Indicator/radar_page.lua, TV_Indicator/hobos_page.lua, init.lua, maverick_page.lua, pave_spike_page.lua, walleye_page.lua --> added

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

TV_Sensor/init.lua --> added
dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
--update_screenspace_displacement(1, true, 0)
try_find_assigned_viewport("F4_DSCG")

Clearly more testing needed here, there are a myriad of combination left to try (I never got around to playing with the remaining files in the TV_Sensor folder other than the init.lua file.

As I stated above, Until someone with more talent (and time) than I figures out the DSCG export, I'm just going to use the ALR46 export.

Sorry for the long a technical post, good luck to folks who use this try try and move the football.

Diz out

Unfortunately I didn't succeed, I added the line
update_screenspace_displacement(1, true, 0)

in the given place, but the result was a green spot. If I add the line

--update_screenspace_displacement(1, true, 0)

, the radar export will be with a grid on the whole screen.
After the last updates, the RHAW folder changed its name to RWR, fortunately the export still works correctly here.

Edited December 5, 2024 by Padonis

[Quasi]

I have written to “Heatblur Customer Support” on this subject.

Hello Heatblur Team,

I wanted to ask if it will be possible with the F-4E, like with the F-14, to export viewports (RWR/RADAR/TV)
to an external second monitor. Or, is this option planned for the near future?

 

 

Here is the answer:

Hey Quasi!

Thank you for contacting us!

It is not available for the F-4 yet but it is planned for the future, unfortunately can't say anything about the timelines just yet.

Let me know if you have any other questions.

Thank you for your support!

---

Best regards from the entire Heatblur Team

Sincerely

Daria Kurhuzova
(Heatblur Customer Support + Administration)

Edited December 13, 2024 by Quasi

[MAXsenna]

8 hours ago, Quasi said:

I have written to “Heatblur Customer Support” on this subject.

Hello Heatblur Team,

I wanted to ask if it will be possible with the F-4E, like with the F-14, to export viewports (RWR/RADAR/TV)
to an external second monitor. Or, is this option planned for the near future?

 

 

Here is the answer:

Hey Quasi!

Thank you for contacting us!

It is not available for the F-4 yet but it is planned for the future, unfortunately can't say anything about the timelines just yet.

Let me know if you have any other questions.

Thank you for your support!

---

Best regards from the entire Heatblur Team

Sincerely

Daria Kurhuzova
(Heatblur Customer Support + Administration)

Thanks! Basically the same answer rec9 in another thread!

Wish it would happen soon, but it is what it is.  

Cheers!