jonsky7

Edit, Just looked at both your files again, you were missing the first _ in the first line _ = function(p) return p; end; I have no idea how important that is mind. And on your later post with pictures, your CFG name doesn't match the one you have selected in DCS settings. 1. You have a very large display, but you have selected "1 screen" effectively I'm not super knowledgeable on how to set up a 3 screen properly but you probably want something like the below. That should fix the super zoomed in view. That is setting up 3 views, instead of 1 view stretched out over 3 displays. For 2560x1440 resolution x3, setting a resolution of 7680x2040 in the DCS setting page 2K.lua The viewDx and viewDy, are offsets to looking straight ahead. You'll notice the Left view has a viewDx of -1, and the right is 1 You may need to adjust these, I'm not sure what measurement they use (probably radians or something), so it will take a bit of fine tuning, or a bit more research into multiple display cockpit view. Needless to say that a more negative value of "viewDx" moves the camera left, and a more positive one moves it right. 2. The blurriness of the HUD in your picture simply looks like the HUD brightness is set too high, if you use the knob on the UFC, that should fix that problem. 3. I've looked to see what the Max Resolution actually means, most answers point to the amount of VRAM the GPU has that limits the amount of Pixels it can generate. When I've seen other people have an issue, part of the screen goes black, or has no output. So if you have the menu displaying on your MFD monitors, I agree that you are probably not hitting a limit. As far as I can tell, the Menu screen is rendering as 3D application, judging by GPU usage and power draw when sitting in the menu screen. I'm not sure why they are displaying a plain blue screen though. 4. You can absolutely try dragging you MFD monitors to under your "TVs" in windows and reconfigure the setup file. ( I can see you've already done that ) 5. Is your monitor "3" set as the Main Display in windows? For 4K Tv's 11520x2760 4K.lua

Are you using Helios? The default names for those MFD exports are LEFT_MFCD CENTER_MFCD RIGHT_MFCD I think I've heard Helios changes the names sometimes. If you are NOT using Helios, use the names as above. Otherwise. you may be exceeding the limits of your graphics card in 3D applications, are you running your TV's at 4K? More than 1 graphics card? The Max resolution of most graphics cards is 7680x4320

Hi, Just thought I'd share this mission that I made. It is a FULL mission, from cold and dark, a flight over the channel into France, and back again to landing. It takes about 1 to 1.5 hours to complete. You will need "The Channel" map, and WW2 Assets pack. Whilst doing some reading on the great Wooden Wonder, I came across this term "Siren Tour". Although I only managed to stumble across a few mentions of the term, it piqued my interest. An introduction to the Siren Tours is provided at the start of the mission, but as I understand it, they were raids of small bomber groups, going in with the main purpose of setting off air raid sirens and all that goes with it like heading to air raid shelters etc. I had the idea of maybe making a campaign, but creating just this one mission, with all the foibles of the DCS Ai and mission making, took a great deal of time. There is a scripted navigator who flicks switches and tunes the navigation radio. I did look into Ai voices etc, and some are used, but for the most part they are quite there yet with no way to infer emergency or panic etc. Available in user files section https://www.digitalcombatsimulator.com/en/files/3335873/ links to references of the term "Siren Tour" https://www.rafcommands.com/archive/09862.php https://www.rafcommands.com/archive/11386.php https://www.aviationclassics.co.uk/issue-10-de-havilland-mosquito/

The RWR is not exportable by default in any aircraft, which means it requires modification of game files. These files are in the cockpit scripts portion of the aircraft game files and are subject to checks for modifications by the "Integrity Check". If the server you are playing on has the option "Require Pure Scripts = Yes", you will be kicked for applying said modification. So whether that game file is modified by Helios, or manually, you will be kicked from servers requiring "Pure" scripts. Also, if the server has this option set to No, you will still see a red shield (Intergity check fail) when you leave the server and go back to the server list, or if you play a bit of single player and then go to the multiplayer server list. The workaround is to restart DCS. A few posts up you will find a list of the default exportable displays. Exporting any of these does not effect the integrity check and should allow to play on "pure scripts only" servers without being kicked. The solution is to either not export the RWR and play on any server you like, or do export it and find a server you like that does not require pure scripts. and beg ED to make the RWR exportable by default.

After having a brief look through the multiplayer server list, it looks like a few more servers have the option for "Require pure scripts" set to yes lately. Unfortunately when a server has this option set to yes, there is very little in the way of allowed modifications, if any at all. You should be able to still play on any multiplayer server where this option is set to "no", you may get an IC failed notification when you leave the servers, if this is still the case you need to restart DCS to reset the IC check.

FC3 has a different coding structure. Most of the files are locked away in encrypted files. There's an "aircrafts/common" folder somewhere. It may be in there but I'm not at my computer to check.

You could open the controls indicator, which IIRC is RCtrl and Enter. This brings up at small display in lower left corner showing control inputs. If it's moving about with no stick input, then your joystick might have a bit of jitter.

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