airdog

You can just make 3 generic mfd's in helios and then bind each button to a keystroke. Pretty sure every module that has come out is capable of binding keystrokes to the OSB buttons. Here is a video of a helios profile made by Sicario for the Harrier that I am using. All the button presses are emulating keystrokes and do not require that you add an interface. I did all this by adding the keystrokes in the DCS module page then coding those keystrokes into each button using the helios profile editor.

Quick AAR (No Homo) would be a more appropriate title

Here is the link https://www.digitalcombatsimulator.com/en/files/3084265/

I uploaded it to the DCS files page with the title "Av8B NA Helios File by Sicario" It's just awaiting a moderator to approve it. It will show up at this link eventually https://www.digitalcombatsimulator.com/en/files/ under Device Profiles

http://www.dcskneeboardbuilder.com/index.html This program will make it much easier for you. You can put the kneeboard where ever you want and have it custom depending on which aircraft you fly/

Most likely you damaged the engine at some point. I guessing its its related to the hexagon that shows up with a R or J in it on the HUD. If its a goes full hexagon and then gets the tail most likely some degradation to engine power happens.....just my theory currently. Not sure how that relates to the water system not working but i'm just throwing things out there since ive dealt with this also. Supposedly IRL if you get 3 bars of the hexagon you wave off the vertical landing and reevaluate the type of landing or lower the weight of the aircraft to alleviate the problem. IRl you should be able to evaluate it with engine performance charts in the NATOPS... RPM vs Temp charts or something along those lines. As I said ive experienced this along with a couple of my squadmates at times but really havent got into an in depth troubleshooting to see what exactly is happening

That's pretty much how the rest of our conversation went. I just was adding "fuel" to the fire on this topic. I was in aviation (military and civilian) as a mechanic for 20 years...i know all to much about about fuel consumption...its the driving factor behind everything at the airlines.

Quote from a real Marine infantryman I was drinking with the other day. "Harriers show up for battle just in time to RTB for fuel"

It would be real helpful if you could tell us what you have done so far. Your computer specs would be helpful. Monitor resolution..monitor configuration. What exactly are you wanting to export. What aircraft you would like to export. F16 is not an option as far I know.

Todays Change log of open Beta says it supports the Harrier....all is well peeps. https://forums.eagle.ru/showthread.php?p=3304547#post3304547

It is possible. I just messed with the files and got it to work like this below Your Monitor Config needs the below code added to it and then your own coordinates F5E_RWR_SCREEN = { x = 606; y = 1354; width = 150; height = 150; } This is what the AN_ALR87_init.lua should look like. Its located in the x:\DCS World\Mods\aircraft\F-5E\Cockpit\Scripts\AN_ALR87\indicator Folder 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("F5E_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, PAGE_TEST = 3 } id_pagesubset = { COMMON = 0, MAIN = 1, BIT = 2, TEST = 3 } page_subsets = {} page_subsets[id_pagesubset.COMMON] = LockOn_Options.script_path.."AN_ALR87/indicator/AN_ALR87_COMMON_page.lua" page_subsets[id_pagesubset.MAIN] = LockOn_Options.script_path.."AN_ALR87/indicator/AN_ALR87_MAIN_page.lua" page_subsets[id_pagesubset.BIT] = LockOn_Options.script_path.."AN_ALR87/indicator/AN_ALR87_BIT_page.lua" page_subsets[id_pagesubset.TEST] = LockOn_Options.script_path.."AN_ALR87/indicator/AN_ALR87_TEST_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} pages[id_Page.PAGE_TEST] = {id_pagesubset.COMMON, id_pagesubset.TEST} init_pageID = id_Page.PAGE_OFF use_parser = false --- master modes F5E_ALR87_OFF = 0 F5E_ALR87_MAIN = 1 F5E_ALR87_BIT = 2 F5E_ALR87_TEST = 3 ------------------------------------ pages_by_mode = {} clear_mode_table(pages_by_mode, 3, 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[F5E_ALR87_OFF][0][0][0] = id_Page.PAGE_OFF pages_by_mode[F5E_ALR87_MAIN][0][0][0] = id_Page.PAGE_MAIN pages_by_mode[F5E_ALR87_BIT][0][0][0] = id_Page.PAGE_BIT pages_by_mode[F5E_ALR87_TEST][0][0][0] = id_Page.PAGE_TEST opacity_sensitive_materials = { "font_RWR", "INDICATION_RWR" }

It is possible. I just messed with the files and got it to work like this below Your Monitor Config needs the below code added to it and then your own coordinates F5E_RWR_SCREEN = { x = 606; y = 1354; width = 150; height = 150; } This is what the AN_ALR87_init.lua should look like. Its located in the x:\DCS World\Mods\aircraft\F-5E\Cockpit\Scripts\AN_ALR87\indicator Folder 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("F5E_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, PAGE_TEST = 3 } id_pagesubset = { COMMON = 0, MAIN = 1, BIT = 2, TEST = 3 } page_subsets = {} page_subsets[id_pagesubset.COMMON] = LockOn_Options.script_path.."AN_ALR87/indicator/AN_ALR87_COMMON_page.lua" page_subsets[id_pagesubset.MAIN] = LockOn_Options.script_path.."AN_ALR87/indicator/AN_ALR87_MAIN_page.lua" page_subsets[id_pagesubset.BIT] = LockOn_Options.script_path.."AN_ALR87/indicator/AN_ALR87_BIT_page.lua" page_subsets[id_pagesubset.TEST] = LockOn_Options.script_path.."AN_ALR87/indicator/AN_ALR87_TEST_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} pages[id_Page.PAGE_TEST] = {id_pagesubset.COMMON, id_pagesubset.TEST} init_pageID = id_Page.PAGE_OFF use_parser = false --- master modes F5E_ALR87_OFF = 0 F5E_ALR87_MAIN = 1 F5E_ALR87_BIT = 2 F5E_ALR87_TEST = 3 ------------------------------------ pages_by_mode = {} clear_mode_table(pages_by_mode, 3, 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[F5E_ALR87_OFF][0][0][0] = id_Page.PAGE_OFF pages_by_mode[F5E_ALR87_MAIN][0][0][0] = id_Page.PAGE_MAIN pages_by_mode[F5E_ALR87_BIT][0][0][0] = id_Page.PAGE_BIT pages_by_mode[F5E_ALR87_TEST][0][0][0] = id_Page.PAGE_TEST opacity_sensitive_materials = { "font_RWR", "INDICATION_RWR" }

Mine

No issues here at all. Though I'd like to know if you all are running TS3 in "run as administrator" mode. If not it may be worth a try to see if it fixes the issue.

There is a way to fix this within the helios profile. You would open up the helios .hpf profile in notepad++ From there you would click on search tab and select find Select the replace tab then you would put Monitor 2 in the "find what" box then monitor 1 in the "replace with" box then select replace all That should solve the problem without messing with windows settings. This also needs to be done with any other helios profiles that you use.

You should have just made the scripts folder and put the export.lua in there. If you modified the one in the program files it will be overwritten when you do updates or repairs to your install.

Sounds like the problem with how windows numbered your monitors and the fact that they dont match what is in the Helios .hpf profile. I'm pretty sure captain zeen is aware of how to fix this as i'm pretty sure I read the fix from him. Its a matter of opening up your .hpf profile in Notepad++ and changing all entries that say for example: monitor 2 to say monitor 1. there is a replace all function within notepad++ that will do this for you. First you need to see how Helios numbers your monitors in the helios profile editor and compare it to how windows numbered your monitors. Sorry if I'm not explaining it well but possibly Capt Zeen could be of more help with this issue. I've had to do it with several of my helios files.

Great work as usual!!! Modified for my setup and loving it!!

As soon as you are done with either an Apache or a Cobra with a co-op pit you can do whatever you want but not until either one of those are done! ;)

Again great work Capt'n. For anybody using an over/under monitor setup her are the numbers I came up with for my setup. _ = function(p) return p; end; name = _('2_monitors_SA342'); Description = 'prepared for the SA342' --TOTAL DEL VIEWPORT Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 16/9; } } --NADIR NADIR = { x = 152; y = 1664; width = 345; height = 193; } -- SA342_RWR SA342_RWR = { x = 604; y = 1106; width = 218; height = 218; } --SA342_TV SA342_TV = { x = 104; y = 1070; width = 465; height = 370; } --SA342_WP1 SA342_WP1 = { x = 231; y = 1623; width = 197; height = 27; } --SA342_UHF SA342_UHF = { x = 235; y = 1804; width = 152; height = 30; } --SA342_FM SA342_FM = { x = 270; y = 1540; width = 188; height = 31; } UIMainView = Viewports.Center

Screenshots

Screen Shots from Match 2. Most are from the F-5 perspective but I was stuck to a blue side view while hosting. https://www.flickr.com/gp/19843514@N03/9ADWU4

Here's a link to about 50 screenshots of some of the battles https://flic.kr/s/aHskEehpeh Feel free to use any of the images as you see fit. I hosted the match on my machine. Hopefully it all was smooth. I didn't hear any complaints so I'll take it that the connection was good for everyone.

First try to uninstall and reinstall the F5 module if that doesnt work I'd do a repair to your install of DCS. Looks like you are missing a few texture files.