Display an area on small display..

[RickJamesBish]

Is there a utility I can run in conjuction with my current SimappPro from Winwing, which runs my left and right MFD for F16, that will let me display an area of the cockpit on a 3rd usb display? My current setup is MFD with USB display on left, ICP Panet in center, MFD with USB Display on Right. I would like to add a 3rd USB display to the bottom below the ICP panel and have it show all the area as pictured in attached image.  null

Edited April 27, 2024 by RickJamesBish

[Scott-S6]

A few things. First, you don't need an application to export MFDs. Both Helios and Simapp cause more problems than they solve for MFD exporting, imo. Setup your viewport file properly and stop using them for that. Helios has nothing to do with the exported MFDs, EHSI or DED in the pic - all done simply by configuring the viewport file properly.

You can't export a piece of the cockpit like you're asking to do. What you can do is use an app like Helios to draw the gauges you want in the arrangement you want. It's not difficult at all. (the gauges aren't working in my pic because I no longer use them and have removed the helios interface, I still had the profile around though)

I would suggest considering if those gauges are actually useful to export. If they're strictly for eyecandy then fine but I have found that a large RWR is much more useful in the Viper and that's how I use the center screen in that aircraft.

Edited April 30, 2024 by Scott-S6

[MadKreator]

Removed my first response.  @RickJamesBish… @Scott-S6 is very correct!. You do NOT need Helios or Simapp to export viewports. Many, are available natively through dcs’ export api. You just need to create a monitor file accordingly( there’s good writeips and walkthroughs in the forums here). Helios can cause IC issues depending on how you use it when exporting viewports. But you most definitely don’t NEED it for basic mfd, ded , rwr exports etc. You will need it for exporting things like the gauges as those are user created and not a direct function of DCS’s exporting.  You CAN use Helios for exporting mfd’s ( like SimAppPro) if you aren’t comfortable writing your own monitor file.( although simapp already wrote you one) Where Helios and SimApp MAY start to conflict is if you have devices such as the WinWing MIP that uses is own scripts and export.lua to use the switches and knobs and such on say the ufc. With both software trying to send and receive device commands, it can get messy. Your  best bet would be to scrap SimAppPro if you don’t NEED its other functionality( delete its lines of script from the export.lua that it writes in there when you install it), keep using the monitor file it created for you, then use Helios to export things like the analog gauges

Edited May 1, 2024 by MadKreator

[Scott-S6]

Re IC issues - exporting any of the displays that don't have a viewport configured by default will cause an IC error regardless of whether it's done manually, by Helios or by simapp since they all do exactly the same thing in regards to viewports.

In the viper the two MFDs and the EHSI have pre-configured viewports and you simply need to add them to the monitor file - no IC implications. The RWR, DED and other indicators exportable as a viewport require you to edit the indicator to create a viewport and this will cause an IC fail no matter how you do it (since all three methods involve editing that indicator file) unless ED change the IC at some point in the future.

While I find Helios to be troublesome in a variety of ways and avoid using it wherever possible, IC check fails are not a Helios (or simapp) failing, they are unavoidable if you create a viewport for an instrument that doesn't have one configured by default.

Edited May 1, 2024 by Scott-S6

[RickJamesBish]

On 4/30/2024 at 4:28 PM, Scott-S6 said:

A few things. First....

 

Thanks for the response. Now that you mention it, Those gauges will likely not be that useful and I think I would like to put the F16 RWR in that location instead. I will give it a shot once I have an understanding of how it works.

[Scott-S6]

8 hours ago, RickJamesBish said:

Thanks for the response. Now that you mention it, Those gauges will likely not be that useful and I think I would like to put the F16 RWR in that location instead. I will give it a shot once I have an understanding of how it works.

The two MFDs and the EHSI have viewports configured already (if you want to display the EHSI then go straight to step two and add a viewport called "EHSI" to your monitor file). For any others, you need to add a viewport export to the instrument and then add that viewport to your monitor file. Here's how you do it (and the same method works on lots of other instruments that are a 2D display - doesn't work on 3D stuff like gauges). Remember to backup these files before you edit them in case you screw up and can't figure out what you've done wrong.

 

First you find the indicator file for the instrument. In this case it is: 

DCS World\Mods\aircraft\F-16C\Cockpit\Scripts\EWS\RWR\indicator\RWR_ALR56_init.lua

You need to add two lines to create a viewport. You can name it whatever you want but mine is called F16_RWR

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
try_find_assigned_viewport("F16_RWR")

Keep a note of these details as you'll need to do this again if you install an update. If you play multiplayer then be aware that this will cause you to fail an integrity check, no way around that.

 

Then you go to your monitor file in DCS World\Config\MonitorSetup\whatever_yours_is_called.lua (in the DCS config menu you can see the name of your monitor config file) and define where you want this viewport to be displayed. Use the same name you used in the previous step and adjust the XY position (remember the top left corner of a box drawn around all of your monitors is 0,0 and the point you define is the top left corner of the viewport) and size. These are my numbers and name, yours might be completely different.

--F16 RWR on center screen - working
F16_RWR =
{
    x = 2710;
    y = 890;
    width = 500;
    height = 500;
}

The first line which starts "--" is a comment - this is me reminding myself what it is, which screen it's on and whether I've finished adjusting it. Once it's where I want it I add the "working" suffix. You don't need to have this comment line at all but it's a useful thing to have when you come back to it later and can't remember what you were doing, especially if you get part way through setting something up.

 

Do note, the RWR export is just the stuff that's drawn on the screen in green - it does not include the fixed lines and circles which are part of the 3D model. If you want those you'll need to have something draw them (helios can do this, for example). Because of this, it's blank if the RWR is turned off or not detecting anything. Therefore, be sure to find a mission where you immediately have a bunch of radar sources around you to jump into to test the size and position.

 

The other one you might want is the DED. That's in DCS World\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\DED\indicator\DED_init.lua

 

And remember to share a pic of your setup!

Edited May 2, 2024 by Scott-S6

[MadKreator]

@RickJamesBish As a pro helios advocate .. to accomplish the same as Scott suggested with the RWR and DED, since the core file must be modified to “allow” that viewport to be exportable, which will break IC anyway, Helios can also do that for you if you aren’t comfortable modifying files yourself. It will add “patches” which is mostly adding the “dofile” to the proper cockpit scripts, the same way as you would do it manually as Scott suggested. But when it comes to placing and sizing the viewports it will be just dragging and dropping and sizing with your mouse to the screen you want. Again since either way will break IC and block you from MP servers with “pure scripts” enabled.
As Scott mentioned too, if you want the rwr rings or anything like that then you would need to use something like helios anyway.  if you decide to just stick with mfd’s then just stay the way you are now…. If it ain’t broke, don’t fix it
 
There isn’t a right or wrong way, but there is options. Some people like using helios, some prefer to do it manually. The choice is yours.

[Scott-S6]

19 minutes ago, MadKreator said:

There isn’t a right or wrong way, but there is options. Some people like using helios, some prefer to do it manually. The choice is yours.

There's a right way and way that routinely breaks itself... 

But seriously, a lot of the people needing help with exports are using helios or simapp (especially simapp, it's rubbish) and that's what's causing the problem. It's an okay stop gap if you're not comfortable with the lua edits but there's really nothing difficult about lua edits or working out viewport locations. You'll very likely end up doing that sooner or later anyway so, personally, I'd say learn how to do viewport exports natively and just use Helios for drawing gauges. Then when Helios gets abandoned (again) or you get fed up of the odd performance issues it causes you can ditch it and your viewports will still work just fine.

Edited May 2, 2024 by Scott-S6

[MadKreator]

12 minutes ago, Scott-S6 said:

There's a right way and way that routinely breaks itself... 

 maybe I’m a lucky one . I’ve been using Helios for several years ( not as long as when Gadroc dropped it initially) and developing profiles for the last couple of years and I have never had the slightest issue with it. Performance or stability-wise ( obviously very system dependent). I will wholeheartedly agree that learning to mess with DCS scripts, writing monitor files, even using mods, is almost a must to get the most out if dcs. Even if a person doesn’t ever learn to write/ script or code. A basic understanding of what it’s trying to do can be invaluable, even a basic monitor setup. I exported displays for a long time manually. But once I found helios and using a single touchscreen for all the aircraft controls I was hooked! The current dev is very good and is very dedicated to it. It may disappear someday but I will ride the wave until that day comes!… or until VR/Mixed reality takes a big step forward. I’m just a sucker for the best graphics possible and seeing my actual controls.

[Scott-S6]

17 minutes ago, MadKreator said:

I’m just a sucker for seeing my actual controls.

We're definitely on the same page there - physical controls, no keyboard and no clicking the virtual cockpit. In my pic above you can (just) see 3x streamdeck XLs. Between that and all of the physical switches/buttons in my pit I can run everthing and rapidly switch between aircraft. This is what my Viper profile looks like.

Edited May 2, 2024 by Scott-S6

[MadKreator]

1 minute ago, Scott-S6 said:

We're definitely on the same page there - physical controls for everything, no keyboard and no clicking the virtual cockpit. In my pic above you can (just) see 3x streamdeck XLs. Between that and all of the physical switches/buttons in my pit I can run everthing. This is what the Viper profile I use looks like.

Streamdeck are great! I use an XL but with just game functions( f keys, briefing,rearm, comm menu, pause, ff, etc). I run the DCS-UFC app along side as well, for certain aircraft. You can never have too many controls. Clickable cockpit is a cool concept but I absolutely HATED looking down and zooming in and out, using the mouse to do  everything. I like VR for free flight here and there or MSFS where the same 5 buttons controls every aircraft

[Scott-S6]

1 minute ago, MadKreator said:

Streamdeck are great! I use an XL but with just game functions( f keys, briefing,rearm, comm menu, pause, ff, etc). I run the DCS-UFC app along side as well, for certain aircraft. You can never have too many controls. Clickable cockpit is a cool concept but I absolutely HATED looking down and zooming in and out, using the mouse to do  everything. I like VR for free flight here and there or MSFS where the same 5 buttons controls every aircraft

I do find it a bit annoying that they don't function without the app though. For what they cost they ought to be smart enough to have a config pushed to them and then operate autonomously (like virpil or realsimulator controls do).