[How To] Export ALL Indicators like MFCD via ViewPorts

[PeterP]

Yes, the pack from PeterP worked for me expect the "simbuilder views".

A-10 will not start with this view for any reason. I tried

 

 

yes- that's why I didn't update it in the user files section.

 

 

Still struggling with DCS how to tell it to use a .lom file instead the EDM...

[HuggyBear]

Understood, I didn't explain myself correctly.

 

Thanks,

 

- Bear

[USAFMTL]

Well I got my MFCD's et up but havign a hell of a time trying to get the DCU and the RWR to show.

 

Here is my CDU

 

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

 

indicator_type = indicator_types.COMMON

purposes = {render_purpose.GENERAL}

 

local x_size = 1

local y_size = 1

 

function update_screenspace_diplacement(zoom_value)

local default_width = 0.5 * LockOn_Options.screen.height + (64 * zoom_value)

if default_width > LockOn_Options.screen.height then

default_width = LockOn_Options.screen.height

end

 

if default_width > 0.5 * LockOn_Options.screen.width then

default_width = 0.5 * LockOn_Options.screen.width

end

 

local default_height = (y_size/x_size) * default_width

local default_y = LockOn_Options.screen.height - default_height

local default_x = LockOn_Options.screen.width - default_width

 

dedicated_viewport = {default_x,default_y,default_width,default_height}

dedicated_viewport_arcade = {default_x, 0 ,default_width,default_height}

end

 

update_screenspace_diplacement(0)

 

function set_full_viewport_coverage(viewport)

 

dedicated_viewport = {viewport.x,

viewport.y,

viewport.width,

viewport.height}

dedicated_viewport_arcade = dedicated_viewport

purposes = {render_purpose.GENERAL,

render_purpose.HUD_ONLY_VIEW,

render_purpose.SCREENSPACE_OUTSIDE_COCKPIT,

render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- set purposes to draw it always

render_target_always = true

end

 

-- try to find assigned viewport

local multimonitor_setup_name = "Config/MonitorSetup/"..get_multimonitor_preset_name()..".lua"

local env = {}

env.screen = LockOn_Options.screen

local f = loadfile(Dave)

if f then

setfenv(f,env)

pcall(f)

 

local vp = nil

vp = env.CDU_SCREEN

 

if vp ~= nil then

dbg_print("ok we have directly assigned viewport to MFCD\n")

set_full_viewport_coverage(vp)

end

end

dofile(LockOn_Options.script_path.."CDU/indicator/CDU_pages.lua")

init_pageID = id_CDU_Pages.CDU_PAGE_OFF

 

CDU_preinit_files_path = LockOn_Options.script_path.."CDU/Indicator/Preinit/"

page_subsets = {}

dofile(LockOn_Options.script_path.."CDU/indicator/CDU_subsets_init.lua")

 

----------------------

pages = {}

pages_by_mode = {}

clear_mode_table(pages_by_mode, 10, 10, 29)

 

function get_page_by_mode(master, L2, L3, L4)

return get_page_by_mode_global(pages_by_mode,init_pageID,master,L2,L3,L4)

end

 

dofile(LockOn_Options.script_path.."CDU/indicator/CDU_pages_init.lua")

 

use_parser = false

 

 

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

 

indicator_type = indicator_types.COMMON

used_render_mask = "interleave.bmp"

 

--------------------------------------------------------------------------------------------

 

Here is my RWR

 

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

 

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

 

indicator_type = indicator_types.COMMON

 

purposes = {render_purpose.GENERAL}

try_find_assigned_viewport("RWR_SCREEN")

 

----------------------

rwr_symbols_bound = 0.027 -- coeff to limit indication on RWR when symbol can't be place on RWR entirely

-------PAGE IDs-------

id_Page =

{

PAGE_OFF = 0,

PAGE_MAIN = 1,

PAGE_BIT = 2

}

 

id_pagesubset =

{

COMMON = 0,

MAIN = 1,

BIT = 2,

}

 

page_subsets = {}

page_subsets[id_pagesubset.COMMON] = LockOn_Options.script_path.."AN_ALR69V/Indicator/AN_ALR69V_COMMON_page.lua"

page_subsets[id_pagesubset.MAIN] = LockOn_Options.script_path.."AN_ALR69V/Indicator/AN_ALR69V_MAIN_page.lua"

page_subsets[id_pagesubset.BIT] = LockOn_Options.script_path.."AN_ALR69V/Indicator/AN_ALR69V_BIT_page.lua"

 

----------------------

pages = {}

 

pages[id_Page.PAGE_OFF] = {}

pages[id_Page.PAGE_MAIN] = {id_pagesubset.COMMON, id_pagesubset.MAIN}

pages[id_Page.PAGE_BIT] = {id_pagesubset.COMMON, id_pagesubset.BIT}

 

init_pageID = id_Page.PAGE_OFF

use_parser = false

 

--- master modes

A10C_ALR69V_OFF = 0

A10C_ALR69V_MAIN = 1

A10C_ALR69V_BIT = 2

 

------------------------------------

pages_by_mode = {}

clear_mode_table(pages_by_mode, 2, 0, 0)

 

function get_page_by_mode(master,L2,L3,L4)

return get_page_by_mode_global(pages_by_mode,init_pageID,master,L2,L3,L4)

end

 

pages_by_mode[A10C_ALR69V_OFF][0][0][0] = id_Page.PAGE_OFF

pages_by_mode[A10C_ALR69V_MAIN][0][0][0] = id_Page.PAGE_MAIN

pages_by_mode[A10C_ALR69V_BIT][0][0][0] = id_Page.PAGE_BIT

 

opacity_sensitive_materials =

{

"font_RWR",

"INDICATION_RWR"

}

 

-----------------------------------------------------------------------------------

 

Here is my monitor setup

 

_ = function(p) return p; end;

name = _('Dave');

Description = 'Left and Right MFCD on the right monitor'

Viewports =

{

Center =

{

x = 0;

y = 0;

width = 1920;

height = 1080;

viewDx = 0;

viewDy = 0;

aspect = 1.6;

}

}

 

LEFT_MFCD =

{

x = 1980;

y = 600;

width = 410;

height = 410;

}

 

RIGHT_MFCD =

{

x = 3370;

y = 600;

width = 410;

height = 410;

}

 

CDU_SCREEN =

{

x = 2100;

y = 300;

width = 420;

height = 324;

}

 

RWR_SCREEN =

{

x = 3000;

y = 300;

width = 178;

height = 178;

}

 

 

 

UIMainView = Viewports.Center

 

 

--------------------------------------------------------------------------------------

 

 

 

I want to add the CMSC too.

 

So here I am stuck.....

[ilikepie]

dofile(LockOn_Options.common_script_path.."Viewpor tHandling.lua")

 

maybe the space between the r and the in "Viewpor tHandling.lua for the rwr problem

 

i dont export the cdu as i use it on the right MFCD with the loz 2.0 helios profile.

[USAFMTL]

What is this Helios I keep reading about?

 

I'm still stuck though.

[BIGNEWY]

What is this Helios I keep reading about?

 

 

 

http://www.scsimulations.com/content.php?204

[USAFMTL]

I will check that out when I off duty.

 

In regard to my problem. Im still a newb to all this but am I supposed to put info in the parenthesis? Or just copy and paste? Sorry for being a pain.

[USAFMTL]

Anyone.....please....... :D

[PeterP]

Use these files for DCS World:

 

A) This pre-sets will keep the usual export naming and can cause conflicts between Ka-50 and A-10C when using the MFCDs

All Exports On in A10C for DCS World 1.2.0

 

B) This pre-sets changes the Export-names and removes the conflict of the ABRIS/Shkval and MFCDs.

 

http://forums.eagle.ru/showthread.php?p=1541311#post1541311

 

There is no need to edit any init.lua when using the files above.

Edited September 4, 2012 by PeterP

[USAFMTL]

Thanks Pete!!!! Wish me luck.

[USAFMTL]

Pete I sent you a PM. I'm almost there, just need a little more help.

[PeterP]

the answer:Dummies Guide for the “MonitorSetup.lua“

[USAFMTL]

That answered most however the problem is after the CDU I can's get nothing else to show up.

 

_ = function(p) return p; end;

name = _('Export example');

Description = 'Export example';

Viewports =

 

{

Center =

{

x = 0;

y = 0;

width = 1920;

height = 1080;

viewDx = 0;

viewDy = 0;

aspect = 1.6;

}

}

 

ED_A10C_LEFT_MFCD =

{

x = 1980;

y = 600;

width = 410;

height = 410;

}

 

ED_A10C_RIGHT_MFCD =

{

x = 3370;

y = 600;

width = 410;

height = 410;

}

 

ED_A10C_CDU =

{

x = 3370;

y = 200;

width = 420;

height = 324;

}

 

ED_A10C_RWR =

{

x = 1980;

y = 200;

width = 178;

height = 178;

}

 

ED_A10C_CMSP =

{

x = 2550;

y = 200;

width = 300;

height = 300;

}

 

ED_A10C_CMSC =

{

x = 2100;

y = 200;

width = 300;

height = 300;

}

 

UIMainView = Viewports.Center

[USAFMTL]

Ok I got the clock to show too but after that, nada. Anyone have any ideas?

 

ED_A10C_LEFT_MFCD =

{

x = 1980;

y = 600;

width = 410;

height = 410;

}

 

ED_A10C_RIGHT_MFCD =

{

x = 3370;

y = 600;

width = 410;

height = 410;

}

 

ED_A10C_CDU =

{

x = 3370;

y = 100;

width = 410;

height = 410;

}

 

ED_A10C_CLOCK =

{

x = 2500;

y = 600;

width = 400;

height = 400;

}

 

ED_A10C_RWR =

{

x = 2500;

y = 100;

width = 300;

height = 300;

}

 

ED_A10C_CMSP =

{

x = 1100;

y = 0;

width = 300;

height = 300;

}

[USAFMTL]

Well its all working, and here is why....when testing, start airborne, that way the displays will be on. Im such a dope....

[SV_huMMer]

Well its all working, and here is why....when testing, start airborne, that way the displays will be on. Im such a dope....

 

Wow?!... Does it mean if you start on the runway, or parked and cold, this will not work?..

[PeterP]

Wow?!... Does it mean if you start on the runway, or parked and cold, this will not work?..

No - USAFMTL just want to tell that it's advisable to have the systems up'n'running to be able to see working exports on your secondary monitors.

[Fakum]

Ive been out since january due to a PC failure, just getting back online now. got the latest DCS World installed, using helios again on a touchscreen as before, but man, I have been reading the last 4 pages of this thread, and my head is still spinning. I have to start exporting stuff, and it seems very confusing sifting through all this. I know things have changed, but I remember editing some instrument lua's, then adding them to my monitor lua, what im not clear about here is, where are the new file locations that need to be edited as I think I see 2 possible paths, and I dont see any examples of instrument changes, meaning, what the originals look like, and what is changed, I dont know what to paste in the original files is what I am getting at I suppose.

 

This link http://files.digitalcombatsimulator.com/en/208103/ I read does not make any sence to me at the moment. Thanks for any help

[PeterP]

Here is all you need to know for a successful Multi-monitor living with DCS world:

 

First Read this:

Dummies Guide for the “MonitorSetup.lua“

 

and than copy pre-set 1* into your DCS World 1.2.0 install to make all exports functional without the need of manual editing the init.lua files.

 

Than start to play around with the exports - so you will learn by doing.

 

Use the included Export example.lua as a guideline and template.

 

 

Also read here to know how to deal with several design flaws when using more than one monitor in DCS:

A Plea for View-Export/Multi-head/TH Users. - ED Forums

 

 

That's all!:)

 

 

*optional:

Or you can also use this present to maintain separation between the A-10 and Ka-50 exports.

But this is only needed if you switch often between the KA-50 and A-10.

>> #68

Edited September 22, 2012 by PeterP

[Fakum]

Thank you, I will look into all this and report back. Thanks

[wolfstone]

i really would like to get all mine up and running, i have helios working and my 2 mfds exported, i have tried reading all this but i am more confused than ever so i proberly will never get my rwr cdu and the rest up and running ,i just dont get it :-(

[Abnaxus]

Works fine with the 1.2.1??

[USAFMTL]

Works fine with the 1.2.1??

All my view exports work just find after patching.

[Ranger79]

I wish, I only get like 5fps using exports, dont know what happened. Just two MFCD's...

[TomDK]

All my view exports work just find after patching.

 

 

I found a strange behavior with the new update function ... every time I start an update all my viewports are gone but copied to a folder "backup00". In this folder are exactly those files I use for my exports and "no mfcd´s view".