F-14B and display exports ?

Hello

Is it possible to move basic instruments like a speedometer.

It is a pity that he does not have HUD along with heights, as in newer models.

Hello

Is it possible to move basic instruments like a speedometer.

It is a pity that he does not have HUD along with heights, as in newer models.

I would love to export speed and alt gauges

Any idea for the RWR ?

You have to edit an Lua file for the RWR export, and it only exports the symbols as the "crosshairs" of the RWR are part of the cockpit textures.

head to

DCS World\Mods\aircraft\F14\Cockpit\Scripts\RWR\Indicator\RIO\init.lua

add the following to the bottom of the file, use notepad++ (normal notepad can break things apparently)

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

try_find_assigned_viewport("F14_RWR")

then you need to add it to your monitor config file. Mine is below, but you will have to alter the numbers for you

F14_RWR =

{

x = 5570;

y = 350;

width = 825;

height = 825;

}

Only shows the centre N in this picture due to mission start.

It seems Jester wheel position is handled by a lua (DCSWorld\Mods\aircraft\F14\Cockpit\Scripts\JesterAI\JesterAI_Page.lua).

Line 43 :

grid_origin.init_pos = {0, 0, 0}

I set it to

grid_origin.init_pos = {-1.8, 0, 0}

and it's much better.

However it may depends on your screen config... I'm running a 2560*1080 on the left (main screen) and a 1920*1080 on the right (instruments).

I think I might lurve you!! :love:

I used -2.7 for my 2560*1440 + 1920*1080 + 1920*1080

and it's now bang in the middle

Cheers my man :thumbup:

F14_DDD F14_TID

F14_VDI F14_HSD

Can you give an example of the code needed for the export please. I have done the A10 and F18 already, but an example would help me alot.

You have to edit an Lua file for the RWR export, and it only exports the symbols as the "crosshairs" of the RWR are part of the cockpit textures.

 

head to

DCS World\Mods\aircraft\F14\Cockpit\Scripts\RWR\Indicator\RIO\init.lua

 

add the following to the bottom of the file, use notepad++ (normal notepad can break things apparently)

 

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

try_find_assigned_viewport("F14_RWR")

 

then you need to add it to your monitor config file. Mine is below, but you will have to alter the numbers for you

 

F14_RWR =

{

x = 5570;

y = 350;

width = 825;

height = 825;

}

 

 

Only shows the centre N in this picture due to mission start.

[ATTACH]206572[/ATTACH]

Perfect thanks !

Say, how would one make the TID (or LANTIRN) in Hud-Only Mode (ALT+F1) larger?

Can you give an example of the code needed for the export please. I have done the A10 and F18 already, but an example would help me alot.

Its been a while ago since i did this the last time, an example an which file to edit would be nice to know.

Cheers

Evilfisher

Its been a while ago since i did this the last time, an example an which file to edit would be nice to know.

 

Cheers

Evilfisher

NVM just like jonsky posted, it works :smilewink:

Can you give an example of the code needed for the export please. I have done the A10 and F18 already, but an example would help me alot.

Go to saved games/DCS/Config/monitor setup/your monitor setup file.lua

Add something like this for each screen you wish to export.

If you export screens from other aircraft, you can copy the numbers from them.

F14_RWR =

{

x = 5570;

y = 350;

width = 825;

height = 825;

}

instrument export is not position dependant, so you have to define 2 monitors setup, one for pilot, one for RIO

-- F14B Pilot Instruments SETUP

F14_VDI=

{

x = 1921;

y = 270;

width = 480;

height = 480;

}

F14_RWR=

{

x = 2401;

y = 50;

width = 480;

height = 480;

}

F14_HSD =

{

x = 2891;

y = 492;

width = 718;

height = 718;

}

-- F14B RIO Instruments SETUP

F14_DDD =

{

x = 1921;

y = 270;

width = 480;

height = 480;

}

F14_RWR=

{

x = 2401;

y = 50;

width = 480;

height = 480;

}

F14_TID =

{

x = 2891;

y = 492;

width = 718;

height = 718;

}

How do you switch from pilot to rio ? Or you simply load the desired monitor set up each time ?

Tornado seems a logical choice for Hearblur. I’d bet a muffin on it.

instrument export is not position dependant, so you have to define 2 monitors setup, one for pilot, one for RIO

 

-- F14B Pilot Instruments SETUP

 

F14_VDI=

{

x = 1921;

y = 270;

width = 480;

height = 480;

}

 

F14_RWR=

{

x = 2401;

y = 50;

width = 480;

height = 480;

}

 

F14_HSD =

{

x = 2891;

y = 492;

width = 718;

height = 718;

}

 

 

-- F14B RIO Instruments SETUP

 

 

F14_DDD =

{

x = 1921;

y = 270;

width = 480;

height = 480;

}

 

F14_RWR=

{

x = 2401;

y = 50;

width = 480;

height = 480;

}

 

F14_TID =

{

x = 2891;

y = 492;

width = 718;

height = 718;

}

Thank for the example. I made a custom export with no problem using your code, just changed pixel coordinates.:smilewink:

How do you switch from pilot to rio ? Or you simply load the desired monitor set up each time ?

I used the entire code in a custom setup, only changing the pixel coordinates. Also the filename and the name in the .lua should match as per my experience. I have a 3440 x 1440 on the left and a 1920 x 1080 on the right. Make sure in windows or nvidia settings, the top of the monitors are the same.

I am trying an edit on the rwr init.lua per one of the guys that posted before in this thread.

Example of my monitor setup code:

name = _('F-14B Combined');

Description = 'EXPORTED DISPLAYS'

Viewports =

{

Center =

{

x = 0;

y = 0;

width = 3440;

height = 1440;

viewDx = 0;

viewDy = 0;

aspect = 3.722222;

}

}

F14_VDI=

{

x = 3440;

y = 0;

width = 500;

height = 500;

}

F14_HSD =

{

x = 4860;

y = 0;

width = 500;

height = 500;

}

F14_DDD =

{

x = 3440;

y = 580;

width = 500;

height = 500;

}

F14_RWR=

{

x = 4150;

y = 580;

width = 500;

height = 500;

}

F14_TID =

{

x = 4860;

y = 580;

width = 500;

height = 500;

}

UIMainView = Viewports.Center

GU_MAIN_VIEWPORT = Viewports.Center

Hope this helps

I used the entire code in a custom setup, only changing the pixel coordinates. Also the filename and the name in the .lua should match as per my experience. I have a 3440 x 1440 on the left and a 1920 x 1080 on the right. Make sure in windows or nvidia settings, the top of the monitors are the same.

 

I am trying an edit on the rwr init.lua per one of the guys that posted before in this thread.

 

Example of my monitor setup code:

 

name = _('F-14B Combined');

Description = 'EXPORTED DISPLAYS'

Viewports =

{

Center =

{

x = 0;

y = 0;

width = 3440;

height = 1440;

viewDx = 0;

viewDy = 0;

aspect = 3.722222;

}

 

}

F14_VDI=

{

x = 3440;

y = 0;

width = 500;

height = 500;

}

 

F14_HSD =

{

x = 4860;

y = 0;

width = 500;

height = 500;

}

 

F14_DDD =

{

x = 3440;

y = 580;

width = 500;

height = 500;

}

 

F14_RWR=

{

x = 4150;

y = 580;

width = 500;

height = 500;

}

 

F14_TID =

{

x = 4860;

y = 580;

width = 500;

height = 500;

}

 

UIMainView = Viewports.Center

GU_MAIN_VIEWPORT = Viewports.Center

 

Hope this helps

my file works just fine. the only thing I don't know how to do is make the game export the proper displays ONLY wether I am in the front or the back seat.

I use a pair of Thrustmaster Cougar MFDs with the F/A-18 and I have figured out how to extract the TID and DDD to my secondary monitor where they reside. Unfortunately, the F-14 does not have nearly as nice of an interface as an MFD.

So my thought was to utilize those digital inputs where they could be most helpful, the CAP. I made a rough concept drawing below:

So the real question is, can I extract the message indicator drum to the external monitor inside the MFD bezel to streamline the process?

Is it already exportable, or could I generate a separate camera/viewport to send to an outside window?

Display export

my file works just fine. the only thing I don't know how to do is make the game export the proper displays ONLY wether I am in the front or the back seat.

I am no expert, but I believe it is all or nothing. I think you would need two seperate lua files, and you would have to switch between them depending on which seat you were going to be flying in.

IMO, that would be a hassle. If you had three monitors, you could split them up. RIO Displays on one and the Pilot on the other.

For me, I like all five on my second monitor.

Good Luck Mate.:joystick:

In the RIO seat what is the view port called for the screen on the right that can be mirrored to the Pilot HSD? Is it also HSD?

Hi guys, need a hand here. Have these exporting great to my mfd screens, But I seem to have a slight issue when I’m using Tid relay on the HSD when I’m flying, in the flat I’m getting a double image on the screen. It’s almost like it’s exporting both the HSD image and the RIO TID image at the same time and over laying them on the same screen.

This only happens when I’m in the front seat and select TID relay. Any ideas how to correct this so it only displays the HSD monitor in the front seat?

What are the viewports you're exporting?

Sent from my ASUS_I01WDX using Tapatalk

Hi there,

how do I get the ddd to work properly in an export in the front seat, I have it all in the Lua but the radar only moves when jump into the rear seat and freezes when I'm back in the front seat.

I'm trying to use it to check on what old mate in the back is seeing

how do I get the ddd to work properly in an export in the front seat

https://forums.eagle.ru/showpost.php?p=3827869&postcount=8

So there’s no way to get around it? Like with the rwr?

So there’s no way to get around it? Like with the rwr?

Idk, but the RWR is available for both the pilot and RIO as this instrument is present in both cockpits.