Jump to content

[How to] Export displays like RWR and CMSP set-up guide - Jan 2021

jonsky7

By jonsky7
in Multi-Display Bugs

 Share

Recommended Posts

jonsky7

jonsky7

Posted
  • Author
Posted (edited)
35 minutes ago, BaronVonVaderham said:

Question: Helios is failing integrity checks so I’m back to basic export. 
where can I find the name of the devices (viewports) that can be exported?

I can find a devices.lua, which quotes MFD_LEFT/RIGHT, but my export.lua works (or used to anyway) when I use the name LEFT/RIGHT_MFCD. Soo United they changed the name of the MFDs, the devices.lua does not specify it. 
The devices _init.lua states MFD_LEFT/RIGHT, and RMFD/LMFD.

 So I’m a bit lost…

surely someone must know which file will specify the device bashes that can be used for exportable viewports?

i don’t want an answer that says “this is the name”, I want to learn how to fish, to use a biblical expression. This way I can find out with each update if I have to adjust my export for or not, and how, without having to ask here yet again.

The viewport output name is usually in the indicator init.lua file of the display you are looking for. These are located in the aircraft's cockpit/scripts folder.

eg

DCS World/Mods/aircraft/F-16C/Cockpit/Scripts/Displays/EHSI/Indicator/EHSI_init.lua - in which you will find try_find_assigned_viewport("EHSI")
or
DCS World/Mods/aircraft/F14/Cockpit/Scripts/VerticalDisplayIndicator/Indicator/init.lua - try_find_assigned_viewport("F14_VDI")

 

I have just confirmed that my EHSI export is still working with the name EHSI

EHSI =
{
x = 2561;
y = 370;
width = 520;
height = 520;
}

 

A really good tool for this is Notepad++

It has a "find in files" tool, you can use that to search for

try_find_assigned_viewport 

(ignore the replace in files bit)
Filters just filters only .lua files
and directory will speed up the search, otherwise it WILL search your entire computer 🙂
 

It will then display every file with that code in it.

image.png

 

I know you didn't ask for this but......

A list of most of the default exportable displays 
 

A-10C, A-10C_2
LEFT_MFCD, RIGHT_MFCD

AH64-D 
LEFT_MFCD, RIGHT_MFCD, TEDAC or CENTER_MFCD
An entry for TEDAC in your monitor config file takes priority over a CENTER_MFCD entry, so if you have both, the TEDAC will be shown in the TEDAC position.

AV8BNA
LEFT_MFCD, RIGHT_MFCD

F-5
RIGHT_MFCD

F-14
F14_VDI,                   F14_HSD,                F14_TID,                  F14_DDD,               F14_ECMD,                                    F14_UHF_ARC159, F14_VHF_ARC182
Pilot upper display, Pilot lower display, RIO lower display, RIO upper display, RIO right display (by right knee), Radio Freq displays x2

F-15E
Front Seat
LEFT_MFCD, CENTER_MFCD, RIGHT_MFCD, UFC.
Back Seat
OUTER_LEFT_MFCD, LEFT_MFCD, RIGHT_MFCD, OUTER_RIGHT_MFCD, UFC.

F-16 
LEFT_MFCD, RIGHT_MFCD, EHSI

FA-18 
LEFT_MFCD, RIGHT_MFCD, CENTER_MFCD

JF-17
JF17_LEFT_MFCD, JF17_RIGHT_MFCD, JF17_CENTER_MFCD, JF17_CLOCK_WIN1, JF17_CLOCK_WIN2, JF17_RADIO, JF17_UFCP_1, JF17_UFCP_2, JF17_UFCP_3, JF17_UFCP_4
or
LEFT_MFCD, RIGHT_MFCD, CENTER_MFCD, CLOCK_WIN1, CLOCK_WIN2, RADIO, UFCP_1, UFCP_2, UFCP_3, UFCP_4
(if you have JF17_LEFT_MFCD defined in your config file, the LEFT MFCD of the JEFF will be displayed in that position, otherwise it will be shown in the LEFT_MFCD position.
The upper line here takes priority over the lower line, this enables you to have the display export a different size or location to the LEFT_MFCD position, helpful because the JEFF screens are not square.)

Ka-50 and Ka-50_3
Shkval, ABRIS
or
LEFT_MFCD, RIGHT_MFCD
(again, if you define ABRIS in your config file, the ABRIS will be shown in that position, otherwise it will be displayed in the RIGHT_MFCD position.)

M-2000C
VTB displays in RIGHT_MFCD position

FC3
LEFT_MFCD, RIGHT_MFCD (can not be changed)

Edited by jonsky7
  • Like 2
jonsky7

jonsky7

Posted
  • Author
Posted (edited)

Only other thing I can think of is your graphics' card maximum display resolution.

This is quite often 2x 4k monitors

ie
7680x4320

but it might be worth checking if you can't get anything to display on your monitor (2)

Edited by jonsky7
  • Like 1
BaronVonVaderham

BaronVonVaderham

Posted
Posted

Thanks for the explanation. 
it’s not a resolution problem I think, as with Helios I was over the 2x4k in the horizontal. That worked fine. 
this weekend I’ll be passing around with what you said. Some time ago before I used Helios, calling EHSI didn’t really do it, but thinking about it, maybe that’s because I plugged the EHSI disks in the wrong hdmi port (the du didn’t like using hff do mi to use against but works with the gpu directly. So maybe that was my problem at the time).

 

 Another question, I know I can probably find out using the info you gave me, but I want to export the RWR as well. I understood for the f-16 that’s possible without modifying other files. You didn’t mention if, but then again, you did refer to the usual viewports 😊

  • Like 1
jonsky7

jonsky7

Posted
  • Author
Posted
33 minutes ago, BaronVonVaderham said:

Thanks for the explanation. 
it’s not a resolution problem I think, as with Helios I was over the 2x4k in the horizontal. That worked fine. 
this weekend I’ll be passing around with what you said. Some time ago before I used Helios, calling EHSI didn’t really do it, but thinking about it, maybe that’s because I plugged the EHSI disks in the wrong hdmi port (the du didn’t like using hff do mi to use against but works with the gpu directly. So maybe that was my problem at the time).

 

 Another question, I know I can probably find out using the info you gave me, but I want to export the RWR as well. I understood for the f-16 that’s possible without modifying other files. You didn’t mention if, but then again, you did refer to the usual viewports 😊

You can export the RWR but it will break integrity check. It requires modifying the init.lua of the RWR display indicator file.

It's not a particularly good export either, as only the symbols get exported, the "crosshair" of the RWR is part of the cockpit panel texture.

If you still want to go ahead and do it, the required info can be found here

Save me typing it out again 😋

  • Like 1
Hobel

Hobel

Posted
Posted
vor 21 Stunden schrieb BaronVonVaderham:

Thanks for the explanation. 
it’s not a resolution problem I think, as with Helios I was over the 2x4k in the horizontal. That worked fine. 
this weekend I’ll be passing around with what you said. Some time ago before I used Helios, calling EHSI didn’t really do it, but thinking about it, maybe that’s because I plugged the EHSI disks in the wrong hdmi port (the du didn’t like using hff do mi to use against but works with the gpu directly. So maybe that was my problem at the time).

 

 Another question, I know I can probably find out using the info you gave me, but I want to export the RWR as well. I understood for the f-16 that’s possible without modifying other files. You didn’t mention if, but then again, you did refer to the usual viewports 😊

Can you export the EHSI now?

Basically, this must be entered in your monitor config and, of course, your values for X and Y 

EHSI =
{
     x = 1200;
     y = 1940;
     width = 500;
     height = 500;
}

 

  • 1 month later...
Purzel

Purzel

Posted
Posted (edited)

*kicked again*

What is the viewport for the F/A-18C?
I've got one little 480 x 480px monitor plugged into my GPU (it works, it shows the desktop), is there way to connect it and get it run without that helios stuff?

Somewhere I've found this code:  

  F18_RWR =
{
    x = 3421;
    y = 305;
    width = 480;
    height = 480;
}

Any ideas what could be wrong?
Or how I could connect it via USB

Thx!

RWR_Viewport.jpg

Edited by Purzel
jonsky7

jonsky7

Posted
  • Author
Posted
On 2/2/2024 at 2:55 PM, Purzel said:

*kicked again*

What is the viewport for the F/A-18C?
I've got one little 480 x 480px monitor plugged into my GPU (it works, it shows the desktop), is there way to connect it and get it run without that helios stuff?

Somewhere I've found this code:  

  F18_RWR =
{
    x = 3421;
    y = 305;
    width = 480;
    height = 480;
}

Any ideas what could be wrong?
Or how I could connect it via USB

Thx!

RWR_Viewport.jpg

 

The RWR is not exportable by default in any aircraft, which means it requires modification of game files. These files are in the cockpit scripts portion of the aircraft game files and are subject to checks for modifications by the "Integrity Check". 

If the server you are playing on has the option "Require Pure Scripts = Yes", you will be kicked for applying said modification.

So whether that game file is modified by Helios, or manually, you will be kicked from servers requiring "Pure" scripts.

Also, if the server has this option set to No, you will still see a red shield (Intergity check fail) when you leave the server and go back to the server list, or if you play a bit of single player and then go to the multiplayer server list. The workaround is to restart DCS.

A few posts up you will find a list of the default exportable displays. Exporting any of these does not effect the integrity check and should allow to play on "pure scripts only" servers without being kicked.

 

The solution is to either not export the RWR and play on any server you like, or do export it and find a server you like that does not require pure scripts.

and

beg ED to make the RWR exportable by default.

  • Like 1
  • 2 months later...
lone82

lone82

Posted
Posted (edited)

I'm trying to get my MFD (TV) for the SA342 Gazelle on my second monitor with no luck. Perhaps I have the wrong viewport name?

 

_  = function(p) return p end
name = _('Thomas+Custom+Test')
description = 'JF17, KA50_3, SU25T'
Viewports =
{
    Center =
    {
         x = 0;
         y = 1080;
         width  = 3840;
         height = 1080;
         aspect = 3840/1080;
    }
}

local ui = 2
{    
    x         = 0;
    y         = 1080;
    width    = 3840;
    height    = 1080;
    aspect    = 3840/1080;
}

local bino =
{
    x         = 0;
    y         = 1080;
    width    = 3840;
    height    = 1080;
    aspect    = 3840/1080;
}

function reconfigure_for_unit(unit_type) 

if unit_type == "JF-17" then

  CENTER_MFCD =
{
    x = 960;
    y = 0;
    width = 960;
    height = 1080;
}

  RIGHT_MFCD =
{
    x = 1920;
    y = 0;
    width = 960;
    height = 1080;
}

elseif unit_type == "Ka-50_3" then

 Shkval =
{
    x = 960;
    y = 0;
    width = 1920;
    height = 1080;
}

elseif unit_type == "Su-25T" then

  RIGHT_MFCD =
{
    x = 960;
    y = 0;
    width = 1920;
    height = 1080;
}

elseif unit_type == "SA342M" then

  LEFT_MFCD =
{
    x = 960;
    y = 0;
    width = 960;
    height = 1080;
}
end
end


UIMainView                      = ui
GU_MAIN_VIEWPORT              = ui
BINOS_NOSTEREO_VIEWPORT      = bino

Edited by lone82
IanC58

IanC58

Posted
Posted

Obviously my number settings for one screen but TV screen works

 

SA342_TV =
{
    x = 3050;
    y = 780;
    width = 800;
    height = 635;
}

74_Fox

lone82

lone82

Posted
Posted

Somebody should compile a complete list of all Aircraft MFCD names and post. If I knew how to look them up I would. It would be a great document to have saved.

  • 3 months later...
jonsky7

jonsky7

Posted
  • Author
Posted
On 4/23/2024 at 12:14 PM, lone82 said:

Somebody should compile a complete list of all Aircraft MFCD names and post. If I knew how to look them up I would. It would be a great document to have saved.

 

  • 3 months later...
Bigity

Bigity

Posted
Posted (edited)

I have set up the A10C2 rwr init file but it doesn't show anything on the export monitor, but it does in game.  Any ideas?

 

EDIT: Disregard, it was there just under a MFD because my math is bad.

Edited by Bigity
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...