

airdog
Members-
Posts
620 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Everything posted by airdog
-
That line does not exist in the 1110 AN_ALR69V_init.lua the line now reads [color=#ff0000]try_find_assigned_viewport("RWR_SCREEN")[/color] THough you monitor .lua does have to reflect what is in the quotes in order for it to show up on your screen. Ragtop quick question now as I think I may be confused here. Did you take the old 1109 .lua files and add them into the 1110 script files? So for example: Take the modded AN_ALR69V_init.lua from the 1109 install and drop it into the 1110 install folder. That could explain why the vp=env line still exists. But on my 1110 install the RWR export has changed to this HERE. Is it possible to do it both ways now? Thanks and i'm not trying to step on any toes here as I am just curious to know without having to mod my setup to find out.
-
LOL ......11-1-A-799 to add a bit more from my memory.....only thing I remember from the navy after being out for 22 years.
-
For exports in 1110 you can read up starting on this page http://forums.eagle.ru/showthread.php?t=70716&page=27 And the next 2 pages after that one has more info
-
Your right I missed it....so what is "yellow flaps" down under?
-
Actually it isnt the flaps but the underside of the wing area...it could be painted that color. We called it Zinc Chromate when I worked for McDonnell Douglas years ago. Whatever was not painted remained that color....inside the fuel tanks for example.
-
Your reply was so helpful.......but if it makes you feel better I was inside my blackshark when the A10 flew by me and I noticed it.....so there you go smarta**.:thumbup:
-
-
Otherwise known as Mig Alley..was a very good sim at the time. I still have the disc around here somewhere.
-
[How To] Export ALL Indicators like MFCD via ViewPorts
airdog replied to icemaker's topic in Multi-Display Bugs
I've attached a zip file with the modifies .lua files. I did not include the MFD lua because they were not modded at all by me. I did not include the UHF repeater because I can't figure out which one I modified but it is the same as 1109. The only files I had to redo for 1110 were: RWR(AN_ALR69V_init.lua) ViewportHandling.lua I modded to get rid of the incockpit displays Everything else worked as they did in 1109. The CMSC text had to be resized a bit but not much. I included my monitor .lua also...set up for two 1920x1080 configured in a top/bottom config LuaFiles.zip -
Helis does not do the exports of any of the BS2 displays. That is all done within BS2. I have yet to see anyone export the Shkval or Abris over a network.
-
[How To] Export ALL Indicators like MFCD via ViewPorts
airdog replied to icemaker's topic in Multi-Display Bugs
Are you unchecking fullscreen mode in the A10 graphic option page? What do you have set for resoulution on the same page? -
[How To] Export ALL Indicators like MFCD via ViewPorts
airdog replied to icemaker's topic in Multi-Display Bugs
dofile(LockOn_Options.common_script_path.."devices_defs.lua") [color=red]dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")[/color] indicator_type = indicator_types.COMMON [color=red]purposes = {render_purpose.GENERAL}[/color] [color=red]try_find_assigned_viewport("[b][color=royalblue]RWR_SCREEN[/color][/b]")[/color] Ok what you see above in Bold/Blue text can be anything you want to name it. But whatever you name it has to be named the same in you monitor .lua I have Bolded and Blued the RWR_SCREEN in my monitor .lua below....so those 2 just have to be named the same....get it now? _ = function(p) return p; end; name = _('Airdogs Pit'); Description = 'Indicators configured with Easy Monitor Setup' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.77777777777778; } } RIGHT_MFCD = { x = 1890; y = 1143; width = 860; height = 430; } LEFT_MFCD = { x = -830; y = 1143; width = 860; height = 430; } UHF_REPEATER = { x = 415; y = 1782; width = 140; height = 20; } DIGIT_CLOCK = { x = 113; y = 1891; width = 200; height = 100; } [color=royalblue][b]RWR_SCREEN[/b][/color] = { x = 252; y = 1354; width = 300; height = 150; } CMSP = { x = 1775; y = 1637; width = 600; height = 75; } CMSC = { x = 745; y = 1379; width = 450; height = 65; } UIMainView = Viewports.Center -
[How To] Export ALL Indicators like MFCD via ViewPorts
airdog replied to icemaker's topic in Multi-Display Bugs
I left those other 3 as they were in 1109. So i would suggest using the 1109 method for the items that are not working for you. Should just be a cut and paste job into the init.lua of each export. -
HERE is a link to a fix to get Helios working in BS2 multiplayer. Unbelievable how easy a fix it is too. This also works for A10 if you have the same issue.
-
[How To] Export ALL Indicators like MFCD via ViewPorts
airdog replied to icemaker's topic in Multi-Display Bugs
You only have to go back 1 page for your answer.....hell its only 3 posts before yours....LOL ;) LINK -
It seems to be a Helios issue. Gadroc will hopefully be looking into it this weekend.
-
Mine has been perect...no .problems at all.
-
Patch 1.1.1.0 for DCS: A-10C Warthog (English) Released
airdog replied to pvtkramer's topic in DCS: A-10C Warthog
Here is how the exporting seems to be working. MFD's exports are similar to 1109 but to turn off incockpit displays is different see here for instructions RWR is now like BS2 exports see here for instructions on how to do it. (Full credit for this goes to Hellfrog_C6 as it was his work in BS2 that led me to this fix) All the other exports seem the same as 1109. IF you had it working in 1109 you will be fine with just fixing the RWR export. If you have 1108 you are just going to have to fiddle with the x/y coordinates until you get what you want. It looks as if EMC will not work for 1110. -
[How To] Export ALL Indicators like MFCD via ViewPorts
airdog replied to icemaker's topic in Multi-Display Bugs
Ok just found another item not working...the RWR. To get it exported you have to do it the same way that HellfrogC6 explained in the blackshark2 thread. All credit for this goes to him as I just copied what he did in the BS2 over to A10 and it worked...so here we go: Open up file x:\Program Files\Eagle Dynamics\DCS A-10C\Scripts\Aircrafts\A-10C\Cockpit\AN_ALR69V\indicator\AN_ALR69V.lua Add the lines highlighted in red below. The line that has the RWR_SCREEN in quotes is what you put into your monitorsetup .lua. It can actually be named anything provided it is the same in your monitorsetup .lua dofile(LockOn_Options.common_script_path.."devices_defs.lua") [color=red]dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")[/color] indicator_type = indicator_types.COMMON [color=red]purposes = {render_purpose.GENERAL}[/color] [color=red]try_find_assigned_viewport("RWR_SCREEN")[/color] ---------------------- 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" } My monitorsetup Lua _ = function(p) return p; end; name = _('Airdogs Pit'); Description = 'Indicators configured with Easy Monitor Setup' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.77777777777778; } } RIGHT_MFCD = { x = 1890; y = 1143; width = 860; height = 430; } LEFT_MFCD = { x = -830; y = 1143; width = 860; height = 430; } UHF_REPEATER = { x = 415; y = 1782; width = 140; height = 20; } DIGIT_CLOCK = { x = 113; y = 1891; width = 200; height = 100; } RWR_SCREEN = { x = 252; y = 1354; width = 300; height = 150; } CMSP = { x = 1775; y = 1637; width = 600; height = 75; } CMSC = { x = 752; y = 1379; width = 420; height = 65; } UIMainView = Viewports.Center -
[How To] Export ALL Indicators like MFCD via ViewPorts
airdog replied to icemaker's topic in Multi-Display Bugs
To get the incockpit MFD's to not render you now need to go to this file: x:\Program Files\Eagle Dynamics\DCS A-10C\Scripts\Aircrafts\_Common\Cockpit\ViewportHandling.lua Comment out line 31 by adding the -- as highlighted in red below purposes = [color=red]{--render_purpose.GENERAL[/color], 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 -
[How To] Export ALL Indicators like MFCD via ViewPorts
airdog replied to icemaker's topic in Multi-Display Bugs
All my exports worked fine without me touching a thing. This includes the MFD's, CMSP, UHF Repeater, Clock and CMSC. The only issue I notiiced was the CMSP text was larger and it needs to be adjusted to fit my Helios CMSP panel. -
[How To] Export ALL Indicators like MFCD via ViewPorts
airdog replied to icemaker's topic in Multi-Display Bugs
you can use Helios from http://www.scsimulations.com also -
[How To] Export ALL Indicators like MFCD via ViewPorts
airdog replied to icemaker's topic in Multi-Display Bugs
It only removes the picture in the main cockpit...the buttons are still available to push. -
[How To] Export ALL Indicators like MFCD via ViewPorts
airdog replied to icemaker's topic in Multi-Display Bugs
Open up the below file in notepad++ and put a -- as highlighted in red below it should be located at line 54 or real close to that x:\program files\Eagle Dynamics\DCS A-10c\MFCD\indicator\MFCD_Init.lua purposes = [color=red]{--render_purpose.GENERAL[/color], 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 -
Has been LUA upgraded/improved too in BS2?
airdog replied to Terrorvogel's topic in DCS: Ka-50 Black Shark
Here http://forums.eagle.ru/showthread.php?t=80921&page=3