Fakum

Thanks, but I dont see the photos like the one I posted?

Any updates for Threat Guides? I have been searching for awhile, I am looking for any updates that have photos, such as this one:

Thank you kindly all! And Ditto to Eaglewings question,,,,

You give me alot of credit derammo :}. I certainly am willing to give it a go if you are. I just presumed my stuttering was due to the demand of my main screen running at 3840 x 1600 @ 120hz. (which again runs smooth with just using it in DCS). I will respond to your PM, thanks.

Is this a valid statement?

Ya know,, last week (after a couple of weeks of figuring this all out) I finally got everything dialed in and configured, I hopped into my F-18 and BAM,,, away I went. Looking around outside of the cockpit, the terrain was choppy,,,chop chop chop,,, all the way home LOL. I wasnt laughing then. I threw in the towel, ripped out my 2nd monitor, and just kept the 38" single screen, which is smooth as butter by the way. What alot of time & frustration,, I wasn't expecting such a result. I do applaud the efforts by others. This is a fantastic addon. I wish you all well. Thanks for the support.

Ok, so yesterday I found out that it didnt matter what name I tried in the init.lua file, as long as the MonitorSetup.lua had the "SHKVAL" name in all capital letters, no name worked in the init.lua file. Once I changed the name in the MonitorSetup.lua to all lower case "Shkval", it worked fine, and thats when I also found out you dont even have to edit the names in the init.lua So for at least the KA-50, no init.lua file editing is required.

Are you saying you named them "Ka50_Shkval" in your MonitorSetup.lua or your init.lua?

It is now working!!!! After several more hours of experimenting, I found out that no mater what name I changed the “SHKVAL” init,lua file name to, it didn’t work. I eventually opened up the MonitorSetup.lua file again, and changed the name of “SHKVAL” to ”Shkval” Yeah, that’s all that was needed. I got rid of the modified “SHKVAL” init.lua file (with the added lines and name changes) that I was enabling via OVGME and it all still works! I don’t even need to edit any init.lua files to be able to get rid of the (2) Left_MFCD names in the MonitorSetup.lua. All I had to freakin do is rename the KA-50 Left_MFCD to “Shkval” and NOT” SHKVAL” in the MonitorSetup.lua. And BINGO, no more conflict between the F-18 Left_MFCD and the KA-50 SHKVAL! After all of my hours of searching, I don’t recall ever seeing any mention of this?

If anyone who uses Helios, is interested in creating a single MonitorSetup.lua for all of their modules, I started a new thread specifically for that purpose here. Hopefully I can get this working? https://forums.eagle.ru/showthread.php?t=266243

I am using Helios, and I have (2) separate “MonitorSetup.lua” files I can successfully use for the F-18 & the KA-50. Like most others, I would like to combine them into (1) common “MonitorSetup.lua” file. As I have read, the “ reconfigure_for_unit(unit_type)” no longer works. The work around for that (as I have read) is to change the “NAMES” of the Export via its “init.lua” file, so as you don’t have multiple entries within your “MonitorSetup.lua” such as (2) or more “LEFT_MFCD” (because this wont work). So I have been struggling now to get this to work. I have created a single monitor config that incorporates the F-18 & KA-50. In the KA-50 init.lua file for the Shkval (for 1 example), I changed the name to “SHKVAL”. I also call this out in the “MonitorSetup.lua” To make this change work, I leave the default init.lua’s alone in DCS’s Programs folder, and I have created the file structure with the EDITED init.lua file and enable it via OVGME. It wont work? The SHKVAL appears to show up in the same location as the F-18 Left MFCD would show up? I am missing something here? Here are the lines withing the “Shkval init.lua” dofile(LockOn_Options.common_script_path.."devices_defs.lua") ------------------------ added by Fakum dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("SHKVAL") ------------------------ end of added by Fakum indicator_type = indicator_types.COMMON used_render_mask = LockOn_Options.script_path.."../IndicationTextures/SHKVAL_MASK.bmp" render_target_always = LockOn_Options.flight.easy_radar purposes = {render_purpose.GENERAL} ____________________________________________________ Here is my “MonitorSetup.lua” _ = function(p) return p; end; name = _('Fakum All Helios V1'); Description = '38" Top Main, 23" Bottom Touch Screen for ALL Modules' --TOTAL DEL VIEWPORT Viewports = { Center = { x = 0; y = 0; width = 3840; height = 1600; viewDx = 0; viewDy = 0; aspect = 2.4; } } -- ######## -- ## F-18 -- ######## --LEFT LEFT_MFCD = { x = 282; y = 1798; width = 389; height = 375; } --RIGHT RIGHT_MFCD = { x = 1261; y = 1798; width = 389; height = 375; } -- RWR F18_RWR = { x = 1494; y = 2320; width = 182; height = 182; } --AMPCD CENTER_MFCD = { x = 775; y = 2290; width = 370; height = 354; } --IFEI F18_IFEI = { x = 151; y = 2356; width = 530; height = 200; } --UFC F18_UFC = { x = 738; y = 1630; width = 462; height = 262; } -- ######## -- ## KA-50 -- ######## --SHKVAL SHKVAL = { x = 722; y = 1850; width = 505; height = 316; } --ABRIS ABRIS = { x = 1284; y = 1977; width = 418; height = 536; } UIMainView = Viewports.Center _____________________________________________________ Here is the file structure on my OVGME

At this point, I have to agree with you. I do believe that those using Helios are interested in how to create a single MonitorSetup.lua, but this has morphed into more of an issue on my end. I will find another home. Thanks to all that have helped to date. Capt Zeen, thanks for the response,,, you are The Man by the way, thanks for your major contributions sir.

I just don’t understand,,, hours and hours again, and I cant get the SHKVAL for example to export to the location I have set in my MonitorSetup.lua? I re-named the init.lua for the Shkval to “SHKVAL” as shown here: dofile(LockOn_Options.common_script_path.."devices_defs.lua") ------------------------ added by Fakum dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("SHKVAL") ------------------------ end of added by Fakum indicator_type = indicator_types.COMMON used_render_mask = LockOn_Options.script_path.."../IndicationTextures/SHKVAL_MASK.bmp" render_target_always = LockOn_Options.flight.easy_radar purposes = {render_purpose.GENERAL} __________________________________________________________________________________________ Then I have the MonitorSetup.lua as shown here: _ = function(p) return p; end; name = _('Fakum All Helios V1'); Description = '38" Top Main, 23" Bottom Touch Screen for ALL Modules' --TOTAL DEL VIEWPORT Viewports = { Center = { x = 0; y = 0; width = 3840; height = 1600; viewDx = 0; viewDy = 0; aspect = 2.4; } } -- ######## -- ## F-18 -- ######## --LEFT LEFT_MFCD = { x = 282; y = 1798; width = 389; height = 375; } --RIGHT RIGHT_MFCD = { x = 1261; y = 1798; width = 389; height = 375; } -- RWR F18_RWR = { x = 1494; y = 2320; width = 182; height = 182; } --AMPCD CENTER_MFCD = { x = 775; y = 2290; width = 370; height = 354; } --IFEI F18_IFEI = { x = 151; y = 2356; width = 530; height = 200; } --UFC F18_UFC = { x = 738; y = 1630; width = 462; height = 262; } -- ######## -- ## KA-50 -- ######## --SHKVAL SHKVAL = { x = 722; y = 1850; width = 505; height = 316; } --ABRIS ABRIS = { x = 1284; y = 1977; width = 418; height = 536; } UIMainView = Viewports.Center ____________________________________________________________________________ What the heck am I missing to make this work? OVGME MOD file structure=

Ok, thanks sobe

I think I found the answer and will test tonight, but I found this embedded within one of the many init.lua files I have been digging into. If my guess is correct, I have to locate the Line: ------------------------ added by Capt Zeen dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_IFEI") ------------------------ end of added by Capt Zeen try_find_assigned_viewport being the key here I think? (If its NOT there already, place it there) Then on that line will be a Bracket, and within that Bracket, the name should be placed there, correct? Example would be, for the KA-50, I would create a name "SHKVAL" and place it within the Bracket, so the result would be; try_find_assigned_viewport("SHKVAL") If correct, then within my MonitorSetup I will have the location of my Shkval name "SHKVAL" instead of Left_MFD Correct? Is that all I need to edit in the init.lua file for these exports? Thanks

Yeah, I have 2 different sizes, but thanks sobe,,,, this may be a lost cause for now? Thanks for the info sir

Thanks sobe, I will try and clarify my question. I am trying to combine (2) MonitorSetup lua files. For example, the F-18 & KA-50 Monitor setup files work just fine individually, but if you try and combine them into (1), they wont work because of example, now you have (2) LEFT_MFCD's incorporated into the file, when their can only be one. E.G. _ = function(p) return p; end; name = _('F18 - KA50 Combine Test'); Description = 'Right, Left, RWR, IFEI, UFC, and AMPCD in right monitor' --TOTAL DEL VIEWPORT Viewports = { Center = { x = 0; y = 0; width = 3840; height = 1600; viewDx = 0; viewDy = 0; aspect = 2.4; } } --LEFT LEFT_MFCD = { x = 282; y = 1798; width = 389; height = 375; } --RIGHT RIGHT_MFCD = { x = 1261; y = 1798; width = 389; height = 375; } -- RWR F18_RWR = { x = 1494; y = 2320; width = 182; height = 182; } --AMPCD CENTER_MFCD = { x = 775; y = 2290; width = 370; height = 354; } --IFEI F18_IFEI = { x = 151; y = 2356; width = 530; height = 200; } --UFC F18_UFC = { x = 738; y = 1630; width = 462; height = 262; } --SHKIVAL LEFT_MFCD = { x = 722; y = 1850; width = 505; height = 316; } --ABRIS RIGHT_MFCD = { x = 1284; y = 1977; width = 418; height = 536; } UIMainView = Viewports.Center Now from what I understand, this can be resolved by simply changing the names of (1) of the "Left_MFCD". You can call it "SHKVAL" if you like, you just need to change the name in its associated init.lua file. The issue I am have is, I can find the associated init.lua file, I just dont know what line to change/add the "SHKVAL"? Hope that explains my question better?

I have been searching for quite awhile today, but no real luck. Can someone tell me exactly where I would be changing a "NAME" in any of the init.lua files? Below is an extract, I assume it is on one of these lines? -- SelfWidth - width of device in meters -- SelfHeight - height of device in meters dofile(LockOn_Options.common_script_path.."devices_defs.lua") dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") indicator_type = indicator_types.COMMON used_render_mask = "interleave.bmp" purposes = {render_purpose.GENERAL,render_purpose.HUD_ONLY_VIEW} screenspace_scale = 5; x_size = 1.0 y_size = SelfHeight/SelfWidth frame_start_y = 23/1024 frame_end_y = 754/1024 tex_scale = (frame_end_y - frame_start_y)/(2*y_size) render_start = 55/1024 render_end = 497/1024 y_render_size = 0.5 * (render_end - render_start)/tex_scale aspect_render_map = y_render_size/x_size map_window_params = { cursor_limit_y = y_render_size/x_size, cursor_size = 16/422, scale_factor = SelfWidth * 0.5 } -- x_size and y_size from ABRIS pages : update_screenspace_diplacement(SelfWidth/SelfHeight,false) try_find_assigned_viewport("ED_KA50_ABRIS","ABRIS","RIGHT_MFCD") --ED_KA50_ABRIS added for backward compatibility with Instrument mod 1.2.5

Sobe, did you confirm this? I am struggling to get my init.lua configured in such a way that the exports are well enough to read.

I agree with you Stew, I did however find that it snaps well to the sides as well. My setup is the same as yours, I was about to set it up for side to side, but I discovered that the sides snap just as well as the top edge. So I am now configured top & Bottom, although not centered. Works fine. All I had to do was reconfigure only the X positions only to make this change. Thanks Stew

I struggled to get Ikarus implemented,,, jumping all over the globe to find pieces of broken instructions. There is alot of info out there to help fill in the info that you NEED to do a successful install ,you just have to find it. I wound up falling back on some Helios instructions, which turned into re-installing Helios again. Helios was much more intuitive, and I have it running!

"Readability" MOD,,, Bueller?

OHHH SH%$! I spent the last few days tinkering with my MonitorConfig to get all of the X & Y positions setup nice and crisp. My Main screen is above my touch screen. I had the arrangement as such that the touch screen on the bottom was centered below the main. I actually thought when I did this, that Windows snapped it in place DEAD CENTER!!! NOT,, I booted up today and had to rearrange my monitor screen positions because of some other work I was doing at lower resolutions. I went to start my F-18 Helios profile, I got prompted to RESET my monitor? I figured i would just go back in and snap it back to center,,, NOT! After farting around for awhile, I could not find any info online regarding how I could consistently rearrange my monitor so it would always snap back to center. What I did seem to find is that if I configure the monitor on the side, it appears that I can consistently snap it to the right of the main, as long as I keep the top edges reasonably level to each other, and it will snap perfectly. Has anyone overcome such an issue with your monitors left on bottom center? Thanks,

Thanks Stew,, there is no MonitorConfig attached to reference though?

I did read that in another thread as a suggestion, but I didnt see any follow ups on it. And that was a bit outdated info, was just wondering what current status was,, ,thanks Sobe