Fakum

A year+ Later, but im still interested to find out if this has been overcome? Would love to have an module inclusive Monitor config ;},,, anybody? Thanks,

No response to this at all?

LOL,, I dont know what happened to my above post, but what I started saying was that I have been tinkering with this with poor results. I consolidated some of the notes in here. Rackmonkey, Where is this "Readability" MOD you speak of? Thanks,

__________________________________________________

Thanks for your help Goldwolf

That is interesting, and confusing, LOL,,, you were able to export both without even editing the init.lua files for either.I wonder if you already have a modified config file already installed that was created by others? McMicha mentions above that I should already have a modified init.lua file because I have a Capt. Zeen monitor config,,, but I will have to dig arounf for that,, that file I probably downloaded many, many years ago. Thanks for the help

Yeah, I have confusion over files, I will agree with that. Regarding exporting special displays etc, I have carefully considered the fact that this may not be the appropriate place to post up. But my thoughts are this. I am here to try and install your software that you have graciously provided to all of us, and for that I am truly grateful. One of the issues I have is that there are people like me that do not have the background needed to try and figure out what the missing pieces are, and how to resolve them. My point is basically, that if someone see's this software and gets excited enough to want to try it, the presentation AND the instructions basically tell you to install a few of the files you provided, make a few X & Y adjustments, and your good to go! That is not the case at all, here I am struggling to try and get stuff like the KA-50 SHKVAL to work in Ikarus, Most folks would not realize there are other installation processes required to make this a complete package. This info is not represented in your product information. So I am of the opinion that they should be aware, and this is what you need to do if you want to run Ikarus and see stuff like MFCD's etc. Wouldnt you think? I believe I am contributing to the installation processes of your fine product by presenting this hurdle in the hopes to resolve, so others can see the path. Respectfully, Fakum

That does help actually. I kind of see what your doing there with the init.lua, but since I dont have the Viggen, I can not reverse engineer how you came up with finding the exact NAME to insert "Viggen_Radar"? For example here, i want to export the KA-50 Shkval, those lines your told me to install, what name would i insert? I am assuming it may already be on one of the lines in the init.lua, but which one to use for sure? Thanks, dofile(LockOn_Options.common_script_path.."devices_defs.lua") 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 = {100} -------PAGE IDs------- id_Page = { PAGE_NULL = 0, PAGE_OFF = 1, PAGE_TEST = 2, PAGE_MAIN = 3 } id_pagesubset = { COMMON = 0, MAIN = 1, TEST = 2, } page_subsets = {} page_subsets[id_pagesubset.COMMON] = LockOn_Options.script_path.."SHKVAL\\SHKVAL_base_page.lua" page_subsets[id_pagesubset.MAIN] = LockOn_Options.script_path.."SHKVAL\\SHKVAL_page.lua" page_subsets[id_pagesubset.TEST] = LockOn_Options.script_path.."SHKVAL\\SHKVAL_page_test.lua" ---------------------- pages = {} pages[id_Page.PAGE_MAIN] = { id_pagesubset.COMMON, id_pagesubset.MAIN} pages[id_Page.PAGE_TEST] = { id_pagesubset.COMMON, id_pagesubset.TEST} init_pageID = id_Page.PAGE_MAIN test_pageID = id_Page.PAGE_TEST always_show_ground = false --use_parser = false

Apparently, the WIKI resource page on how to do this needs to be updated? I could find no such file structure in current DCS? I even did a search for this file in widows explorer, and no results? - First go to 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) Ohhhh, Ive got about 15 hours into this so far and Im about to pop a cork!

Apparently, I have to edit a bunch of init.lua files for each item I want to export. That is in addition to creating a Monitor.cfg. Is there anywhere i can go to download these files that have already been reconfigured? Im saying this based on what I have read so far in the last few hours. https://forums.eagle.ru/showthread.php?t=70716

Thank you sir! In addition, I need some help. I know its me, but I cant seem to get anything exported to either monitor. I do realize this is Not an Ikarus issue, but I could really use some help getting Ikarus finished up. My main monitor is on top at 3840x1600. My TouchScreen monitor is right below on bottom at 1920 x 1600. DCS is NOT set for “FullScreen” DCS Resolution is set as 3840 x 2680 Monitor Config file is set to look at “Fakums Ikarus All in One” I took a lot of stuff out of exports out of this Monitor.lua, just to see if I could get at least 1 thing working. I eventually set the X & Y axis both to “0”, just to see if I could get the Shkval to show up in the upper left corner of the main screen,, it wont? Any help would be greatly appreciated. _ = function(p) return p; end; name = _('Fakums Ikarus All in One'); Description = 'Created from Fakums All Helios 2 on 3-6-20.' Viewports = { Center = { x = 0; y = 0; width = 3840; height = 1600; viewDx = 0; viewDy = 0; aspect = 2.4; } } -- ┌─────────────────────────────────────────┐ -- │ K A - 5 0 for Capt. Zeen's profile. -- └─────────────────────────────────────────┘ --SHKIVAL ED_KA50_Shkval = { x = 0; y = 0; width = 432; height = 309; } UIMainView = Viewports.Center

Sorry for any confusion JG14 Smil, I am not looking for where it is located within any file structure, I was asking for a link to DOWnLOAD the "Ikarus.exe" file as it is NOT incorporated in the Ikarus program file that you downloaded. It is a separate file that must be placed in "Per REDDIT Guide": Part 1 - Ikarus.exe The downloads above do not include the ikarus.exe file. You have to download it also. It can be found here. If you follow the instructions, you will install the Ikarus software (not ikarus.exe) into C:\Users\USERNAME\Saved Games\DCS\ikarus. You will also update the scripts folder in C:\Users\USERNAME\Saved Games\DCS\Scripts\ with the export.lua in the files and add a new folder here /DCS-ExportScript/. The ikarus.exe HAS to be in the ikarus folder with all of the aircraft in it.

Thank you for updating the links. Currently, you have provided the following links: https://github.com/s-d-a/DAC https://github.com/s-d-a/Ikarus https://github.com/s-d-a/DCS-ExportScripts Can you please add the Ikarus.exe file link that Goldwolf mentioned in his REDDIT guide (See Below Part 1)? I cant seem to navigate to it from your github file structure? I have not found any mention of its need in your current installation instructions either? Part 1 - Ikarus.exe The downloads above do not include the ikarus.exe file. You have to download it also. It can be found here.

Just confirming, I have to create my own MonitorConfig.lua (C:\Eagle Dynamics\DCS World Whichever version\Config\MonitorSetup\to export things like the Shkval & ABRIS for the KA-50 correct? That is not handled through this software that I could find in the documentation I have read to date.Thanks,

I have been reading, also, some of the wiki info had broken links. Also, I could not find any navigation info to find the Ikarus.exe file? I appreciate the software, but the flow of instruction is on the side of ambigious. I am writting down the steps so maybe the instructions can be updated?

I only have the DCS folders created by the install,,, the one in the Programs folder, and the other in the Users/Saved games folder. I have not yet initiated Ikarus yet, I just started installing the files per all of the instructions I can find so far. I will continue work on it tonight and report back. Thanks

Goldwolf, I am slowing picking at the pieces to get this installed and running. In addition to the Ikarus instructions, I am reading yours as well in an attempt to merge the instructions together, so I get a proper install. In your REDDIT instructions, you state that you basically used the export.lua from the Ikarus files. So far, I understand that, then you go on to state the section I have highlighted with red letters, which I don’t follow. Can you elaborate further? Thanks. Part 2 - Export.lua After I could finally see the dials/panels etc for Ikarus, I started up DCS and none of the dials worked or updated. I updated the Export.lua as outlined (adding the code to it) but it did not work, so I backed up my old Export.lua and used the one from the download. This fixed it and now the dials updated correctly in DCS. I dont know why this made a difference, but it did. Also be sure to add the same export.lua and /DCS-ExportScript/ to the open.beta folder if you have one (in case that helps).

Goldwolf, thank you very much for providing that information. I browsed through it quickly, I recall some of the issues you spoke of. I look forward to giving it another shot via your procedure info. many thanks again sir!

I have not tried Ikarus for a year or more. I did struggle with its implementation and eventually gave up. I recently searched YouTube for a basic installation/configuration tutorial, but did not find one. Is there one available somewhere?

I love the new rotor sounds, incidentally, my sound breaks up alot now,,I cant explain it any better than its choppy, breaks up,, seems to happen most when I turn my head to look around.

I had been a long time Helios user for many years. There is a learning curve! I also dabbled into IKARUS a couple of years back. As I recall, I seem to remember the attraction to IKARUS was the more high fidelity graphics compared to Helios. I admittedly struggled with getting IKARUS running. At the time, it was not as intuitive as Helios for me. I have not dabbled in either for close to 2 years. With DCS updates etc, I found that Helios needed frequent maintenance. I just gave up one day as I am not as sharp as some of the other members that use it. I was dabbling into VR, but that is not working out for me. I am going to go back into Helios I think. It is a great piece of software, and is greatly appreciated,, You just have to keep up with it.Its outstanding once you have it dialed in! Good luck

Thanks, I mis read earlier in this thread that it would Gaff it up,, ,I mis read that,, thanks

So knowing it is likely to be fixed in the next update, in the mean time, as i understand it, there is no way to really know if its on or not? Correct?

AHHHH,,, ok,,, LOL

It seems you may have started a new thread for one that already exists? https://forums.eagle.ru/showthread.php?t=263208