GPatricks

You can position the MFDs to any addressable area on any monitor seen by Windows, so I would say yes, no problem.

I think you are possibly making it too complicated.. Once the program (Set) has been uploaded from the device in MMJoy (Load sets from device" tab), hit "Save Sets to file" so you have the original named/saved before you mess with it. Then select "Joystick axes" tab and then "Calibrate Helper" tab and simply Set Center , move the stick to all its extremes, then clik "Save Calibration". You WILL still see a slight movement in the X/Y/Z axis numbers and that's fine (my X/Y fluctuates about 6-8, Z (dont use it) is same). Check the "Joystick Buttons" Tab to be sure the DX functions are where they were from OEM (unless you want to change them, which you can do here also. I have attached two screens showing all my DX assignments. Once set just Save Set to device and also Save Set to file (named "After-Calibration" or whatever). Do NOT attempt to use Win10 to try and calibrate once the new mainboards are installed, it will just muck things up..

Why not use the racing fixture adapted to flight? For my "Next Level" stand its only a matter of the 4 bolts holding down my Fanatec Clubsport wheel (KB velcro'd in place) and swapping out rudder pedals for my TM T-LCM car pedals. And be sure to compliment your flight sim experience with the "other" F16 sim, each has its strong points.. and for WWII IL2 BoX is excellent. My MFD/Gauge screens are on long arms that move out of the way easily, ICP is velcro'd onto a heavy/adjustable Tablet stand..

Is there a list/spreadsheet for this and other abbreviated Start-ups somewhere?

I assume this was fixed in Helios.1.6.3425.0, no? The section of HeliosExport16.lua I have with the latest version is:

I use real switches via a PoKey 57U board for this, sending a CTRL+I for Pitch/UP (ALT Hold) and CTRL+P for Pitch/DOWN (ATT Hold). I have also tried the ATT Hold/AALT Hold options but the switch does not move in the sim. The switch works perfectly in the Options window when testing.. It does "wobble" for a second (in flight) when I hit my switch but does not change position. The mouse works fine, is this related to the issues reported here?

Lol, I started with Falcon 3! Still like BMS better as I play MP Campaigns but time will tell! Thanks for all your help, much appreciated!

Follow up as this was solved by derammo on his Discord Helios Support channel. So simple yet no idea where it may be documented, so in case you have this issue - "In the Interface dialog called "DCS Monitor Setup", click on the "plane and helicopter" on each of the extra monitors to turn them from "blue" i.e. included in the view of the sky to not blue" Works perfectly now, no idea when or how I clicked those to "blue" backgrounds but there it is!

You can see above and below what I get if I let Helios "Reset Monitor" to clear the errors in the Profile Editor. The DCS main screen uses the whole area (of 2560x2240) to display which puts parts of it on my Lilliputs.. The red lines on the bottom are added (the lines on the bottom were like yours before)/ and height is changed from 1440 to 2240... =============================================== _ = function(p) return p end name = _('Helios') description = 'Generated from compatible Helios Profiles' F_16C_EHSI = { x = 1968, y = 2049, width = 188, height = 184 } F_16C_LEFT_MFCD = { x = 0, y = 1440, width = 550, height = 550 } F_16C_RIGHT_MFCD = { x = 1968, y = 1440, width = 548, height = 549 } Viewports = { Center = { x = 0, y = 0, width = 2560, height = 2240, aspect = 1.14285714285714, dx = 0, dy = 0 } } UI = { x = 0, y = 0, width = 2560, height = 1440 } UIMainView = UI GU_MAIN_VIEWPORT = Viewports.Center ==========================================

Thanks man, that worked! Now I need to figure out what I screwed up to have the main screen extend down into my two MFDS... The Helios.lua seems to be correct but the main screen is running in 2560x2240 instead of 2560x1440 so it's the background in my MFDs.. now lol. This is how the Profile Editor sets the Monitor Setup, tried " height = 1440" but it throws an error and resets it.. If I set it at 1440 and don't run a profile I get the viewports (MFDs and EHSI) and all is well.. Helios.lua - _ = function(p) return p end name = _('Helios') description = 'Generated from compatible Helios Profiles' F_16C_EHSI = { x = 1968, y = 2049, width = 188, height = 184 } F_16C_LEFT_MFCD = { x = 0, y = 1440, width = 550, height = 550 } F_16C_RIGHT_MFCD = { x = 1968, y = 1440, width = 548, height = 549 } Viewports = { Center = { x = 0, y = 0, width = 2560, height = 2240, aspect = 1.14285714285714, dx = 0, dy = 0 } } UI = { x = 0, y = 0, width = 2560, height = 1440 } UIMainView = UI GU_MAIN_VIEWPORT = Viewports.Center

Saw a video where someone copied the gauges from a working profile and pasted them in a 2nd Helios Editor window with his new profile in it. As my "working" profile is a bastardized Cat. Zeen's "F16C_v1.1b" profile and all that works are the LMFD/RMFD/EHSI gauge Viewports I figured give it a shot. Copied the Engine RPM% gauge over, resized it. Copied the Nozzle Position gauge over, resized it. Copied the Fuel Flow over but all that copied was the 4 number window and no bezel, and it won't resize so it's too small. Reset everything so no errors and fired DCS up, everything worked perfectly! I'll keep plugging away but I still need a full size Fuel Flow, a Fuel gauge (to take Nozzle Positions place), a VVI, and an AoA gauge to finish up.... Here is where she is today.

Absolutely! They are setup the same as in the pic.. The other pic is where I am after copy/paste the gauges from Capt. Zeen's F-16 profile over to mine. Getting close but the Fuel Flow can't be resized so too small on LMFD and I can't get the Fuel gauge, VVI, or AoA guages... but RPM% and Nozzle work!

For BMS Falcon 4.35 (which moved to DX11) you currently need to use the included RTT extraction tool for MFDs, but can combine it with the easy to use YAME64 1.21 for other gauges. I believe once the U1 patch comes out you may be able to use YAME64 for everything again (as it was in 4.34).. Been a while since I was here, but now with Helios 1.6 and the new profiles available Helios does it all, no need for RTT at all on a strong system!

New to Helios and DCS from the BMS/YAME64 world. I can't seem to get the gauges to communicate with the gauges or MFDs displayed when placing them from the "F-16" images. There is no "F-16 Interface" listed to install. Failing that I installed Capt. Zeens' F-16 profile and removed all the gauges as it seemed to install a "DCS Generic impersonating F-16C_50" Interface Put the gauge images from the F-16 folder in place, still nothing. Added the "Additional Viewports" Interface and the placed the RMFD.RMFD, and EHSI from the "F-16 Simulator Viewports" folder in place, made sure all tabs (DCS MonitorSetup/Interface/etc.) had no errors and hopped in DCS World. The MFDs and EHSI worked perfectly (actually they work without invoking the profile at all) but still no input into the other gauges. I'm missing a step (or 2 or 10),please advise! This is where i'm at now...

OK, gave up on trying to get MonitorSetup configured and went bak to Helios. I installed the Capt. Zeen F-16 profile and removed all the images and placed the MFDs from under the "F-16 Simulator Viewpoints" tab into my two 8: lilliput monitors. Cleared all the errors in Display and Interface, saved, now I have perfect MFDs in sim but the gauges (shown above) I placed do not work. I added the EHSI gauge below the RMFD from under the "F-16 Simulator Viewpoints" tab and IT works perfectly. I want to add most of the gauges shown above but Zeen's profile and the gauges it uses are in .png format while the F-16 gauges are in .htpl formal, is there a way to get all Zeen's images into Helios, of help ne get the existing ones to function please?

OK, I installed the Capt. Zeen F-16 profile and removed all the images and placed the MFDs from under the "F-16 Simulator Viewpoints" tab into my two 8: lilliput monitors. Cleared all the errors in Display and Interface, saved, now I have perfect MFDs in sim but the gauges (shown above) I placed do not work. I added the EHSI gauge below the RMFD from under the "F-16 Simulator Viewpoints" tab and IT works perfectly. I want to add most of the gauges shown above but Zeen's profile and the gauges it uses are in .png format while the F-16 gauges are in .htpl formal, is there a way to get all Zeen's images into Helios, of help ne get the existing ones to function please?

OK, I installed the Capt. Zeen F-16 profile and removed all the images and placed the MFDs from under the "F-16 Simulator Viewpoints" tab into my two 8: lilliput monitors. Cleared all the errors in Display and Interface, saved, now I have perfect MFDs in sim but the gauges (shown above) I placed do not work. I added the EHSI gauge below the RMFD from under the "F-16 Simulator Viewpoints" tab and IT works perfectly. I want to add most of the gauges shown above but Zeen's profile and the gauges it uses are in .png format while the F-16 gauges are in .htpl formal, is there a way to get all Zeen's images into Helios, of help ne get the existing ones to function please?

OK, I have perfect MFDs now but the gauges I placed do not work. All that works are the MFDs and others (EHSI in my case) under the "F-16 Simulator Viewpoints" tab. Zeen's profile and the gauges it uses are in .png format while the F-16 gauges are in .htpl formal, is there a way to get all Zeen's images into Helios? So close yet so far...

Thanks for the reply Sharkfin! Does Helios really show your lilliputs underneath the main screen? - Yes, Helios picks up my setup directly from Win10. Main screen as the 3 monitor setup shown in my pics. I simply found the gauges I wanted to use and positioned/sized them to fit inside and below the TM MFD bezels. Perhaps you have to set up their position inside Windows right of the mainscreen, side by side (regardless of their "physical" position in front of you). Resolution should be 3760x1440 now. Then use the "reset monitors“ function inside helios. - I can try that, though Helios seems fine with the positioning as it is and I get no errors in "DCS Monitor Setup" tab. Status here is "Monitor setup files are up to date". Thing is I use YAME64 + RTT for extraction in the "other" sim and would rather not have to redo everything.. Also check if you already added the "Profile->Add Interface->DCS Additional Viewports Install the patches, go to the HELIOS "Interface Status" tab and see if there are any warning signs. - Went through again and there were no errors but one warning about SAVING the profile, saved it and warning is gone. Patches are installed. In your HELIOS "DCS Monitor Setup" tab, scroll down to the end and click "Save Profile". In the "DCS Monitor Setup File Output" portion of "DCS Monitor Setup" tab, click the configure" button. - Done, and no errors or warnings now. Then, (at least I had to) choose "Helios“ under the in-game monitor settings. - This was the KEY to not having a screwed up screen when going to 2560x2240 resolution, thanks! Unfortunately I am still getting no MFD or gauge data on Monitors 2&3! The sim is not communicating and I have no clue why at this point... EDIT: I imported Capt. Zeens F16 profile and removed all but the MFDs (under the F16 Simulator Viewports) then placed them in my two Lilliput monitors and they work!! Now to see if I can add the gauges I want and also try and find out the difference between what I built and what the Capt. did...

Trying to extract the R/L MFDs and a few gauges below them on two Lilliput 600x800 (Portrait mode) monitors. While I can get them positioned correctly in Helios they do not function in DCS (they are there but no MFD and gauges do not work). If I set my DCS resolution to 2560x2280 (2560x1440 + 600x800 below) the DCS screen covers the monitors and the menus are just about impossible to use due to the mouse not working on the buttons or the "ok" button is hidden in the center between the two MFDs.. Here is a pic of the setup... appreciate any help as both Helios and trying a modified Monitor setup to just get the MFDs will not work for me and i've reached "RTFM" saturation.

I should add a picture of the setup for clarity, this is while running Helios (with no extraction) -

I'm just trying to get the MFCDs and a few gauges to work on two 8" (600x800) monitors... Have them displaying but no connection to DCS so MFDs are black, gauges are inactive..

To bring this thread to life, is there an Interface for the F-16? If not, how do you get DCS to see the profile? I'm just trying to get the MFDs and a few gauges to work on two 8" (600x800) monitors... OK, I installed the Capt. Zeen F-16 profile and removed all the images and placed the MFDs from under the "F-16 Simulator Viewpoints" tab into my two 8: lilliput monitors. Cleared all the errors in Display and Interface, saved, now I have perfect MFDs in sim but the gauges (shown above) I placed do not work. I added the EHSI gauge below the RMFD from under the "F-16 Simulator Viewpoints" tab and IT works perfectly. I want to add most of the gauges shown above but Zeen's profile and the gauges it uses are in .png format while the F-16 gauges are in .htpl formal, is there a way to get all Zeen's images into Helios, of help ne get the existing ones to function please?

This is making me crazy, I have 3 monitors, two 8" Lilliputs with TM MFD Bezels and my main 2560x1440 monitor. The 600x800 (portrait) lilliputs are below the main, so the total resolution is 2560x2240. I've created a "DCSViper.lua" shown below. If I choose 2560x2240 in DCS Options I get a squeezed down main screen (guess is about 2560x1000 or so) with black above and below. Choosing "DCSViper.lua" does not display MFDs at all.. I also tried Helios, and while I can build the MFDs and they display, I get no data to them (MFDs are black, gauges don't function) so I figured try this method to at least get MFDs.. My lua - _ = function(p) return p; end; name = _('DCSViper'); Description = '3 Monitors - Left MFD on the left monitor, Right MFD on the right and Game on the center' Viewports = { Center = { x = 0; y = 0; width = 2560; height = 2240; viewDx = 0; viewDy = 0; aspect = 1.142857142857143; } } LEFT_MFCD = { x = 0; y = 1440; width = 600; height = 600; } RIGHT_MFCD = { x = 1958; y = 1440; width = 600; height = 600; } GUI = { x = 0; y = 0; width = 2560; height = 1440; } UIMainView = GUI

All set now, the Save Profile was missed after my last change I guess.. now I just need to get Helios to work with my two MFD monitors...