jonsky7

Thanks very much for this, superb! BTW who are Eric and Patrick from the comments section, I'm nosey (curious) lol

But there is a relatively simple fix as far as I can see. Rather than allowing those files to be modified freely, if the team simply add the lines that we exporters add to the display's init.lua files and THEN lock them down. Ie For example, the A-10C RWR %%/DCS World/Mods/Aircraft/A-10C/Cockpit/Scripts/AN_ALR69V/indicator/AN_ALR69V_init.lua Add the lines dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("A10C_RWR") As long as each display gets its own unique name, I'm sure that will suffice. We are aware of the limitations of some exports of these displays. At this time nobody is asking for anything more than being able to export them as they are and pass IC.

Hi William I'm sure we can get this figured out for you. Can you tell us your setup? How many monitors do you have, what resolution are they, and how are they arranged in window display settings? A screenshot is always helpful And Where do you want stuff to display? If you've already had a go, you could upload your monitor config file and we can maybe check for errors. Cheers Jon

You can export the RWR but it will break integrity check. It requires modifying the init.lua of the RWR display indicator file. It's not a particularly good export either, as only the symbols get exported, the "crosshair" of the RWR is part of the cockpit panel texture. If you still want to go ahead and do it, the required info can be found here Save me typing it out again

Only other thing I can think of is your graphics' card maximum display resolution. This is quite often 2x 4k monitors ie 7680x4320 but it might be worth checking if you can't get anything to display on your monitor (2)

The viewport output name is usually in the indicator init.lua file of the display you are looking for. These are located in the aircraft's cockpit/scripts folder. eg DCS World/Mods/aircraft/F-16C/Cockpit/Scripts/Displays/EHSI/Indicator/EHSI_init.lua - in which you will find try_find_assigned_viewport("EHSI") or DCS World/Mods/aircraft/F14/Cockpit/Scripts/VerticalDisplayIndicator/Indicator/init.lua - try_find_assigned_viewport("F14_VDI") I have just confirmed that my EHSI export is still working with the name EHSI EHSI = { x = 2561; y = 370; width = 520; height = 520; } A really good tool for this is Notepad++ It has a "find in files" tool, you can use that to search for try_find_assigned_viewport (ignore the replace in files bit) Filters just filters only .lua files and directory will speed up the search, otherwise it WILL search your entire computer It will then display every file with that code in it. I know you didn't ask for this but...... A list of most of the default exportable displays A-10C, A-10C_2 LEFT_MFCD, RIGHT_MFCD AH64-D LEFT_MFCD, RIGHT_MFCD, TEDAC or CENTER_MFCD An entry for TEDAC in your monitor config file takes priority over a CENTER_MFCD entry, so if you have both, the TEDAC will be shown in the TEDAC position. AV8BNA LEFT_MFCD, RIGHT_MFCD F-5 RIGHT_MFCD F-14 F14_VDI, F14_HSD, F14_TID, F14_DDD, F14_ECMD, F14_UHF_ARC159, F14_VHF_ARC182 Pilot upper display, Pilot lower display, RIO lower display, RIO upper display, RIO right display (by right knee), Radio Freq displays x2 F-15E Front Seat LEFT_MFCD, CENTER_MFCD, RIGHT_MFCD, UFC. Back Seat OUTER_LEFT_MFCD, LEFT_MFCD, RIGHT_MFCD, OUTER_RIGHT_MFCD, UFC. F-16 LEFT_MFCD, RIGHT_MFCD, EHSI FA-18 LEFT_MFCD, RIGHT_MFCD, CENTER_MFCD JF-17 JF17_LEFT_MFCD, JF17_RIGHT_MFCD, JF17_CENTER_MFCD, JF17_CLOCK_WIN1, JF17_CLOCK_WIN2, JF17_RADIO, JF17_UFCP_1, JF17_UFCP_2, JF17_UFCP_3, JF17_UFCP_4 or LEFT_MFCD, RIGHT_MFCD, CENTER_MFCD, CLOCK_WIN1, CLOCK_WIN2, RADIO, UFCP_1, UFCP_2, UFCP_3, UFCP_4 (if you have JF17_LEFT_MFCD defined in your config file, the LEFT MFCD of the JEFF will be displayed in that position, otherwise it will be shown in the LEFT_MFCD position. The upper line here takes priority over the lower line, this enables you to have the display export a different size or location to the LEFT_MFCD position, helpful because the JEFF screens are not square.) Ka-50 and Ka-50_3 Shkval, ABRIS or LEFT_MFCD, RIGHT_MFCD (again, if you define ABRIS in your config file, the ABRIS will be shown in that position, otherwise it will be displayed in the RIGHT_MFCD position.) M-2000C VTB displays in RIGHT_MFCD position FC3 LEFT_MFCD, RIGHT_MFCD (can not be changed)

If you are using "assisted" or "auto" start, do not touch anything until after the engines are idling at 1200rpm (the warmup part of auto-start). The auto-start sets the throttle to the correct position, if you are then moving the throttle you may be placing it in the wrong position.

I don't use VR so I haven't tested this personally, but I believe it is possible. 1. add this line to your monitor config file, apparently it can go at the very end under UIMainView, and GU_MAIN_VIEWPORT (if you have it) VR_allow_MFD_out_of_HMD = true 2. make sure "Use DCS System Resolution" is checked in the VR settings in DCS, won't work without this setting checked. 3. adjust the Monitor config file to place the MFDs in the desired position. Please report back if it works, and I'll add it to the main part of the guide. It would be helpful to others if you also make a note of any drawbacks. Cheers

Thanks very much, I haven't done a great deal of testing but I think I got it working with a slightly different method. I edited the targetdx128.tmh and removed the definitions for DX33 to DX64 (line 883 to 914) I think because like you say, they've added more buttons to the defines.tmh, so not as many are needed in the targetdx128.tmh file. targetdx128.tmh

Yes, somebody has taken the DCS-Export Script, which was used to export data to ikarus, and updated it for use with streamdeck. Which is nice, because I used the updated one to make panels for the Mosquito and some Heli's like I mentioned earlier.

Sorry, can you elaborate on this please? I've been using this for over 2 years now, I know I had to do something before to make it work, but now I don't remember what that was. Like patpat above, I've just installed windows 11, and used the latest version of the TM software. I'm getting the same error as above Compile Error: Identifier name expected in targetdx128.tmh at line 883 I made a shortcut to the script launcher that says "C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETGUI.exe" -r "G:\Saved Games\DCS\WarthogThrottleALLSwitchPos2.tmc" The WarthogThrottleALLSwitchPos2.tmc has a 2 in it because I modified it somehow, for one of the buttons I think. And now I don't know what to do....... please HELPPPPPPPPPPPPPP!!!!!!!

As the support for Ikarus ended well before the F-16 was released, there are no gauges for it unfortunately. The best you can do is use gauges that are available for other aircraft and re-purpose them, but that isn't easy really. The gauges are built within the software's code, so I have no idea how to add gauges or modify existing ones. I only really use the gauges when flying Heli's and warbirds. I have made my own profiles by using other gauges, The Mi-8 gauges can be used for the Mi-24 Spitfire gauges for the Mosquito etc For Jets I sometimes just use the LCD 8 segment displays, just to have a fuel meter or gear lights etc

Sounds about right. The only other thing to consider is that with core mods, sometimes other data in the file changes too. If after re-applying a mod after an update, things stop working as they should, that's probably the reason. Doesn't seem to happen too often with display/export mods, just something to bear in mind. I use notepad++ with a plugin called "compare". You open the original file, and the modded one in a new tab, hit compare, and it shows you where all the differences are, pretty cool.

Could you tell me how to do it from ME please?

Sorry, no you can't

This is what mine looks like as far as the EHSI is concerned LEFT_MFCD = { x = 5130; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 6210; y = 360; width = 825; height = 825; } EHSI = { x = 2561; y = 370; width = 520; height = 520; }

Not sure about Helios but I find that Ikarus update does update pretty much real time. Are you having an issue? At 0.05 it should be updating the instruments 20 times per second If you set them both to 0.01 that should be 100 updates per second

Yes, If you go into your monitor config file usually located in Saved Games\DCS\Config\Monitorsetup there is an entry at the bottom that says UIMainView = Viewports.Center The UIMainview sets the boundaries for the Main menu, F10 map, Mission editor, and the dialogs that appear in game. You can change it from the above to something like UIMainView = { x = 0; y = 0; width = 2560; height = 1440; } and limit the boundary to either one of your monitors. If you have absolutely no idea what any of that means, you might want to have a read of this thread

For Ikarus, if you go to your DCS-ExportScript folder, mine is in Saved Games/DCS/Scripts, but you may have been able to choose the install path, I don't remember. Open the Config.lua At the bottom there is a section with the title "Other", there is two values there called (line 36 and 37 for me) ExportScript.Config.ExportInterval = 0.05 ExportScript.Config.ExportLowTickInterval = 0.5 and the above are their default values. I have adjust the lowtick value to 0.1. Ikarus uses two different update timings depending on how important each "export" is. Decided by whoever wrote the scripts for each aircraft. The most important instruments should be updating every export interval, or 0.05 seconds Things like engine instruments, navigation instruments etc The rest use the low tick interval, Fuel tank contents, panel lights, switches and levers etc I assume this was done to lower the amount of CPU resource Ikarus uses.

Sorry, I haven't used Helios, so I don't know what it does when you make a profile with it. I did fancy it at one point, as I use the now not supported Ikarus to put gauges in my cougar displays when I'm flying Heli's and warbirds. Captain Zeen's profiles looked good, but no warbirds unfortunatley. Eg, in the Mosquito I have this, and the gauges are inside the TM Cougars, it uses the gauges out of the Spitfire section of Ikarus

If you're interested MAX, you can now configure your exports by aircraft type in your monitor config file. As an example: In the A-10A, which has a Right MFCD, you could export it to a position we'll call 1 Then when you jump into the Su-25T, which also uses Right MFCD, you can export it to position 2 Which would mean you wouldn't have to load separate profiles for each aircraft. See in the guide linked above for further info. it looks something like..... _ = function(p) return p; end; name = _('JB by type'); Description = 'JB by type'; Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 2560/1440; } } function reconfigure_for_unit(unit_type) if unit_type == "A-10C" then LEFT_MFCD = { x = 5130; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 6210; y = 360; width = 825; height = 825; } elseif unit_type == "Su-25T" then LEFT_MFCD = { x = 5130; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 2560; y = 360; width = 1720; height = 1080; } elseif unit_type == "A-10A" then LEFT_MFCD = { x = 5130; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 6210; y = 360; width = 825; height = 825; } else LEFT_MFCD = { x = 5130; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 2560; y = 360; width = 1720; height = 1080; } GU_MAIN_VIEWPORT = { x = 0; y = 0; width = 2560; height = 1440; } UIMainView = { x = 0; y = 0; width = 2560; height = 1440; }

You seem to have modified the ViewportHandling.lua, and this is fine if you only play single player. If you want to play multiplayer, you will need to follow the guide step-by-step and do this same alteration to the ViewportHandling-resize.lua file instead!!

Did you set the aircraft group skill option to "player" or "client" ? I think it needs to be on client. I didn't see them mention it in tutorial as the aircraft was already placed.

You can move the kneeboard anywhere you like with some modification. See this thread, scroll down a bit till you see the title about moving the kneeboard.

I believe you cannot occupy the second seat in a multicrew aircraft until the first seat is occupied. So the pilot must be in the aircraft before the navigator can join. The pilot will then get a message saying something like Diego wants to join your aircraft Accept Deny (buttons)