Jump to content

[How To] Export ALL Indicators like MFCD via ViewPorts


Recommended Posts

I have found a way to create all indicators of DCS viewports like MFCD.

 

attachment.php?attachmentid=49478&stc=1&d=1301158107

 

As you can see in the screen shot it's possible to create viewports for all the DCSW Indicators.

 

Here is the way to do that :

 

- First go to S:\DCS A-10C\Scripts\Aircrafts\A-10C\Cockpit

- Then go to the indicator folder you want to use (Eg : AN_ALR69V\indicator

- then open the init.lua file of your indicator (Eg : AN_ALR69V_init.lua here)

- find this line :

indicator_type = indicator_types.COMMON

-And just paste below this code :

 

[color=Red]-- Code below is used for the rendering when no viewport has been created[/color]
purposes      = {render_purpose.GENERAL, [color=DeepSkyBlue]-- Rendering in 3D View[/color]
               render_purpose.HUD_ONLY_VIEW,[color=DeepSkyBlue] -- Rendering In HUD only View[/color]
               render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, [color=DeepSkyBlue]-- Rendering in External View[/color]
               render_purpose.SCREENSPACE_INSIDE_COCKPIT}  [color=DeepSkyBlue]-- Rendering in In cockpit view but NOT in 3D cockpit [/color]
[color=Red]-- End of rendering configuration[/color]

screenspace_scale_initial  = 3;
screenspace_diplacement    = {0,0}

local x_size         = 1
local y_size         = 1

function update_screenspace_diplacement(zoom_value)
   screenspace_scale = screenspace_scale_initial + zoom_value;
   if  screenspace_scale < 1 then
       screenspace_scale = 1   
   end
   local screen_height  = 2.0;
   local screen_width  = screen_height * LockOn_Options.screen.aspect;
   local scaled_width  = SelfWidth  * screenspace_scale 
   local scaled_height = y_size  * scaled_width -- for indicator all sizes is function of width
         scaled_width  = x_size  * scaled_width 
        
   screenspace_diplacement = { 0.5 * screen_width  - 0.5 * scaled_width,
                              -0.5 * screen_height + 0.5 * scaled_height}
   
   screenspace_diplacement_arcade    = {screenspace_diplacement[1],
                                        0.5 * screen_height - 0.5 * scaled_height}
   
end

update_screenspace_diplacement(0)

function set_full_viewport_coverage(viewport)
  local w = LockOn_Options.screen.width
  local h = LockOn_Options.screen.height
  local a = LockOn_Options.screen.aspect
  local x = (-1.0 + 2.0 * (viewport.x / w)) * a
  local y =   1.0 - 2.0 * (viewport.y / h)
  
  local width  = (viewport.width  / w) * a
  local height =  viewport.height / h 
  local scl_hgt_K = y_size * SelfWidth -- size always function of SelfWidth
  local scl_wdt_K = x_size * SelfWidth -- size always function of SelfWidth
     
  screenspace_scale_x           =  2.0 * width  / scl_wdt_K
  screenspace_scale_y           =  2.0 * height / scl_hgt_K 
  screenspace_diplacement    = {x +  width,
                                y -  height}

  screenspace_diplacement_arcade = screenspace_diplacement[color=Red]
-- The code below is used for rendering When you use viewports comments are same as above for rendering[/color]
  purposes      = {render_purpose.HUD_ONLY_VIEW,
                   --render_purpose.GENERAL,[color=DeepSkyBlue] --Uncoment this line by removing the "--" to render in 3D cockpit.[/color]
                   render_purpose.SCREENSPACE_OUTSIDE_COCKPIT,
                   render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- set purposes to draw it always 
[color=Red]-- End of rendering configuration[/color]
  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(multimonitor_setup_name)
if      f     then
     setfenv(f,env)
     pcall(f)
     
   local vp = nil
   vp = env.[color=Red]RWR_SCREEN[/color]
     
     if vp ~= nil then
        dbg_print("ok we have directly assigned viewport to CDU\n")
        set_full_viewport_coverage(vp)
     end       
end

-Change the red value name to set your viewport Name

-Go to \Config\MonitorSetup\YourMonitorFile.lua

- And add Viewport like this :

RWR_SCREEN =
{
x = 1000;
y = 1245;
width = 170;
height = 170;
}

Enjoy!!!

screenshot_82.thumb.jpg.2d47a81b4694266d3384cfd778de342d.jpg

No cockpit avionics display render and ready for export in DCS-A10 1.1.1.1 and a Example LUA.zip


Edited by icemaker
  • Like 16
Link to post
Share on other sites
  • Replies 662
  • Created
  • Last Reply

Top Posters In This Topic

Wow! Very cool! Rep inbound!

 

 

##EDIT: As per PeterP's request, attached exports fix and example LUA.

 

Hereby the readme quoted:

This will switch on the export of of avionics to dedicated view-ports.

 

 

Pre-Sets :

 

1. MFCD in cockpit ON

 

2. MFCD in cockpit OFF (better FPS)

 

3. Backup of default 1.1.1.1 files

 

Make a backup of you "Aircrafts" folder before using my files!

 

Copy the "Aircrafts" from preset 1. or 2 . into:

 

Eagle Dynamics\DCS A-10C\Scripts\

 

 

And allow to overwrite.

 

 

 

 

"Export example.lua"

Copy this file to

\Eagle Dynamics\DCS A-10C\Config\MonitorSetup

and select "Export example" in the Options screen from the "Monitors" drop-down tab.

 

This LUA file already contains al possible exports - delete the one you don't want to use.

 

Keep special attention to the "GUI" export ! - this will determine where you have the in-game GUI.

 

If you want to bind this GUI to a special export you have to change the last line "UIMainView = GUI" - to something else.

Example :

"UIMainView = Center"

 

 

More info: http://forums.eagle.ru/showthread.php?t=70716

 

PeterP 3-1-2012

export -fixed- for DCS-A10 1.1.1.1 and a Example LUA.zip


Edited by MTFDarkEagle
Link to post
Share on other sites

Genious!

 

Just tried it and got RWR displayed on touchscreen :D Very good for cockpit building... now not only can we get switches working with switches but also display pretty much anything on the screens... just awesome... only downside is more performance hit and money spent on more monitors :)


Edited by Kuky

No longer active in DCS...

Link to post
Share on other sites

On this topic, is their a way to export HUD data, say in an attempt to recreate a HUD? I need to study lua export as at the moment I only know about optics and electronics (my background) but nothing of lua scripting. I simply am trying to find out if this is a possible project to undertake.

 

Razi

Link to post
Share on other sites

Brilliant work Well done Rep already sent.

:D

i9 9900x at 5.1 Ghz // ASUS ROG Maximus XI Formula EK Bloc // 64Gb Corsair Vengence 3600Mhz DDR4 Ram // Gigabyte Aorus 2080Ti Watercooled block//Samsung SM951 M2 x4 SSD // Windows 10 64 Bit //50 inch Panasonic TX50-AX802 @ 3840x2160 60Hz//Asus ROG Swift PG35VQ 3440 x 14440 144Hz // TM Warthog HOTAS (Ser. No. 00836) //MFG Crosswind Pedals // TrackIR 5 //Valve Index

 

An old pilot is one who remembers when flying was dangerous and sex was safe.

 

Link to post
Share on other sites

Great work. Any way to get the CDU?

Hammer97 / Hendo97

 

[sIGPIC][/sIGPIC]

Processor Intel®I7 950, 3.06 Mhz, 4 Core(s)/

Microsoft Windows 7 Home Premium 64 bit/ Memory (RAM) 8.00 GB/ HD 6870 1GB DDR5/ 750w PSU/T IR 4/TH Warthog

Link to post
Share on other sites
Great work. Any way to get the CDU?

 

sure you can... he said already you can follow these steps and do the same for CDU (I already tried and got it working with CMSC, CMSP and RWR)

 

look for CDU_init.lua file in .../Scripts/Aircrafts/A-10C/Cockpit/CDU/indicator folder :smilewink:

No longer active in DCS...

Link to post
Share on other sites

This looks great :) Is there a way to copy the caution lights panel on second screen using this method somehow?

Intel Core i7 9700K@4.6GHz|ASUS Strix Z390-H|G.Skill DDR4 32GB@3200MHz|MSI GeForce RTX 2080 Ti|2xSSD 500GB Samsung 970 EVO M.2 RAID0|SSD Samsung 850 EVO|Corsair HX 750W|Fractal Design Define R6 Blackout|UWQHD 34"|Valve Index|Logitech G9|MS Natural Ergonomic Keyboard 4000|VPC WarBRD Base+MongoosT-50CM2 Grip|VPC MongoosT-50 Throttle|VKB T-Rudder|Beyerdynamic DT770|Boom mic|Windows 10 Home

Link to post
Share on other sites
Here is mine so far....RWR, clock, UHF repeater, CMSC.....

 

Presentation1-8.jpg

 

Would you share your files Sir ?

 

except the monitor setup, that I will make myself, of course.


Edited by FZG_Immel

[sIGPIC]https://forums.eagle.ru/signaturepics/sigpic70550_3.gif[/sIGPIC]

Asus Z390-H - SSD M.2 EVO 970 - Intel I9 @5.0ghz - 32gb DDR4 4000 - ZOTAC 2080ti AMP Extreme Core - Cougar FSSB + Cougar NN_Dan + HOTAS Warthog + Virpil WRBRD + Hornet Stick - Thrustmaster TPR Pedals - Track IR5

Link to post
Share on other sites

Im trying to have the UFC up there. How do you get it ?

 

I can't find the UFC in the scripts folders.

 

thx a lot

[sIGPIC]https://forums.eagle.ru/signaturepics/sigpic70550_3.gif[/sIGPIC]

Asus Z390-H - SSD M.2 EVO 970 - Intel I9 @5.0ghz - 32gb DDR4 4000 - ZOTAC 2080ti AMP Extreme Core - Cougar FSSB + Cougar NN_Dan + HOTAS Warthog + Virpil WRBRD + Hornet Stick - Thrustmaster TPR Pedals - Track IR5

Link to post
Share on other sites

I only find a few things that I could export btw...

 

- First go to S:\DCS A-10C\Scripts\Aircrafts\A-10C\Cockpit

- Then go to the indicator folder you want to use (Eg : AN_ALR69V\indicator

- then open the init.lua file of your indicator (Eg : AN_ALR69V_init.lua here)

- find this line :

 

 

for example, I couldnt find nothing for the UFC...

 

How did you do it Paulrkiii ? Are you using Helios or what ?

[sIGPIC]https://forums.eagle.ru/signaturepics/sigpic70550_3.gif[/sIGPIC]

Asus Z390-H - SSD M.2 EVO 970 - Intel I9 @5.0ghz - 32gb DDR4 4000 - ZOTAC 2080ti AMP Extreme Core - Cougar FSSB + Cougar NN_Dan + HOTAS Warthog + Virpil WRBRD + Hornet Stick - Thrustmaster TPR Pedals - Track IR5

Link to post
Share on other sites
Would you share your files Sir ?

 

except the monitor setup, that I will make myself, of course.

 

Of course, as soon as I get everything done to my liking I will upload and let you know the location....

 

yes it's all helios in his pannel but indicators that are from dcsw

 

That's correct...everything is helios, exported by DCS are both MFCDs, RWR, UHF repeater, CMSC, and the clock

Link to post
Share on other sites

Profile uploaded....

 

http://www.scsimulations.com/forums/downloads.php?do=file&id=39

 

Profile is done and uploaded (to include .lau files) at scsimulations website (waiting on mod to approve). Make sure you look at the date, anything prior to todays date is an old profile of mine.

 

Presentation1-9.jpg

 

http://www.scsimulations.com/forums/downloads.php?do=cat&id=3


Edited by Snoopy
Link to post
Share on other sites

Just awesome find!!

 

This with Hawg Touch is gonna be sooo much better than Helios :)

i5-3570K @ 4.5 Ghz, Asus P8Z77-V, 8 GB DDR3, 1.5GB GTX 480 (EVGA, superclocked), SSD, 2 x 1680x1050, x-fi extreme music.



TM Warthog, Saitek combat pro pedals, TrackIR 4

Link to post
Share on other sites
Are you effin' serious Snoop? That's awesome!

 

HOw are you running this bad boy? 3 monitors?

 

Thanks...I used the texters in game and modified as needed....currenty running of my HD 5970 but will be upgrading to another card in 6 months or so...need a little more "juice"

 

Just awesome find!!

 

This with Hawg Touch is gonna be sooo much better than Helios :)

 

That's one opinion....How is this with Hawg Touch gonna be so much better than helios? Because it's free an helios isn't?!

Link to post
Share on other sites
That's one opinion....How is this with Hawg Touch gonna be so much better than helios? Because it's free an helios isn't?!

 

Being free is part of it, it also uses a lot less resources, and would appear to be more flexible and adaptable. Effectively open source and completely moddable. I only tried helios briefly.. i didn't take to it.

 

But of course it is just one opinion, as you put it.

i5-3570K @ 4.5 Ghz, Asus P8Z77-V, 8 GB DDR3, 1.5GB GTX 480 (EVGA, superclocked), SSD, 2 x 1680x1050, x-fi extreme music.



TM Warthog, Saitek combat pro pedals, TrackIR 4

Link to post
Share on other sites
Being free is part of it, it also uses a lot less resources, and would appear to be more flexible and adaptable. Effectively open source and completely moddable. I only tried helios briefly.. i didn't take to it.

 

But of course it is just one opinion, as you put it.

 

I got ya....

Link to post
Share on other sites

Noob question... is there a difference in the FPS hit between exporting the MFCD image the old way and using viewports method?

[sIGPIC][/sIGPIC]

i7 10700K OC 5.1GHZ / 500GB SSD & 1TB M:2 & 4TB HDD / MSI Gaming MB / GTX 1080 / 32GB RAM / Win 10 / TrackIR 4 Pro / CH Pedals / TM Warthog

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...