Search the Community

Hi, I would like to get gauges of mosquito to my small display with Helios but it seems that there's no existing interface for Mosquito? Is that true or have I mistaken as there's interfaces for so many rare planes?

Коллеги! Еще совсем недавно, иметь много мониторную систему было сложно. Но нынче, ограничением является не сколько стоимость, как место, где этот 2-й , а то и 3-й монитор поставить (или просто неудобно...). Но, ИМХО, есть неплохой и достаточно дешёвый способ, . Особенно это актуально , в связи с переходом на 2,7 и Вин10, в которой достаточно много "плюшек". Одна из них это использование вместо 2-го огромного монитора. на 22" использовать для вывода дополнительного рабочего стола планшет или смартфон. Для этого: 1. Скачиваем программу на РС и девайс. Мне больше всего нравиться это приложение, https://spacedesk.net/ , в отличии от других, она позволяет пользоваться подключением по USB практически так же, без потери скорости (как на Wi-Fi ). 2. Вывод экранов (МФ и т.д. можно настроить штатными средствами DCS (профили, по умолчанию, приложены в клиенте или написать свои). 3. Использовать приложение Helios 1.6. Профили под монитор 22" http://www.captzeen.com/helios/index.asp . Штатными средствами приложения профили конвертируются под Ваш формат. Учебники (в основном по версии 1.4.) в стиме https://steamcommunity.com/app/223750/discussions/0/154642321537076529/?l=czech Но . есть проблемы, именно с написанием профилей открытого доступа, под себя, для редактирования и т.д. именно под модуль F-16. В забугорном разделе есть разработка от mcmike (F-16Profile), без вывода экранов. В целом , программа Helios 1.6., интересная . Предлагаю желающим обсудить в этой теме непонятки по данной теме, а так делиться профилями и советами.. С уважением..

Am rather new to DCS but can't cope with my tinkering inclinations (see my systems specs in my signature). Have a 4 screen T shape setup with the following specs. Please disregard the 2520 in the 7680x2520 Resolution as it did not come into play when using my initial 3 camera (7680x1440) setup. Started using a plain vanilla DCS 3 Camera (7680x1440) view (pic 1) but missed the cockpit info provided by Helios. PIC 1 "3 camera" view So I moved into Helios (pic 2). Problem being: Helios starts rendering the pilot position way too far forward and it also distorts the HUD (because of the FOV it assumes I have based on being 1 giant 7560x2520 T shape display) PIC 2 Helios view - with far forward pilot position and distorted HUD So after tinkering for a while and facing the expedient of recognizing myself as a complete idiot for not being able to adjust Helios' FOV (solving the pilot position and HUD distortion problems) I decided to move into a Frankenstein by using a 3 camera 7680x2520 view ALONG with a stand-alone Helios (see pic 3 below). Now the problem is that the RMFCD does not renders at all. PIC 3 with 3 separate cameras and Helios running along (outside of DCS) as per CaptZeen instructions. Everything works fine but (lovely FOV, 3 separate cameras, nice HUD, nice Helios info) BUT the RMFCD does not render at all, as you can see in the pic below. Went through most of the posts here provided by CaptZeen, @jonsky7, @klem, @Hiob, @hansangb, @draconus, @MAXsenna and other good fellas out here but could find no solution to this problem. Any thoughts on why the RMFCD might not render when using my "3ScreenF18f.lua" profile in DCS along with Helios outside of DCS? Am including below a detail of my .lua file in DCS in case it could be of any help (edited w Notepad ++) _ = function(p) return p; end; name = _('3ScreenF18f') Description = 'Configuration with 3 identical monitors each with its own camera' Viewports = { Left = { x = 0; y = 0; width = 2560; height = 1440; viewDx = -1; viewDy = 0; aspect = 1.7777; }, Center = { x = 2561; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 1.7777; }, Right = { x = 5121; y = 0; width = 2560; height = 1440; viewDx = 1; viewDy = 0; aspect = 1.7777; } } FA_18C_CENTER_MFCD = { x = 3593; y = 2136; width = 363; height = 344; } FA_18C_IFEI = { x = 2969; y = 2193; width = 526; height = 205; } FA_18C_LEFT_MFCD = { x = 3095; y = 1640; width = 391; height = 369; } FA_18C_RIGHT_MFCD = { x = 4074; y = 1640; width = 389; eight = 367; } FA_18C_RWR = { x = 4308; y = 2160; width = 182; height = 182; } FA_18C_UFC = { x = 3556; y = 1471; width = 457; height = 259; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center --[[ also you can use "displays" table to perfectly match you configuration . it is generated by DCS automatically. displays table is contains information about all currently attached displays for example my setup is : displays = { [1] = { x = 0, -- note : x == 0 and y == 0 is always mark primary windows display y = 0, width = 1920, height = 1200 }, [2] = { x = -1440, -- mark that secondary display is on left side of primary display y = 0, width = 1440, height = 900 }, ... for all displays } screen table also contain x, y members which mark top left corner of DCS window note about fullscreen : directx doesn't allow fullscreen applications with resolutions more than primary display can handle, so multimonitor presets in DCS will fall back to windowed mode if fullscreen initialization failed ( this info also will be printed to dcs.log) for reconfigure viewports setup for each unit type independently you can declare here function function reconfigure_for_unit(unit_type) --unit type is string with unit name if unit_type == "A-10C" then Viewports = ... define new Viewports table -- also you can define cockpit displays viewports here RIGHT_MFCD = ... define new RIGHT_MFCD viewport else Viewports = ... define default for others RIGHT_MFCD = nil -- remove for others end end --]] Also, am including a detail of my Helios frofile (again, running outside of DCS) just clarification purposes: _ = function(p) return p end name = _('Helios') description = 'Generated from compatible Helios Profiles' FA_18C_CENTER_MFCD = { x = 3593, y = 2136, width = 363, height = 344 } FA_18C_IFEI = { x = 2969, y = 2193, width = 526, height = 205 } FA_18C_LEFT_MFCD = { x = 3095, y = 1640, width = 391, height = 369 } FA_18C_RIGHT_MFCD = { x = 4074, y = 1640, width = 389, height = 367 } FA_18C_RWR = { x = 4308, y = 2160, width = 182, height = 182 } FA_18C_UFC = { x = 3556, y = 1471, width = 457, height = 259 } Viewports = { Center = { x = 0, y = 0, width = 7680, height = 1440, aspect = 5.33333333333333, dx = 0, dy = 0 } } UI = { x = 2560, y = 0, width = 2560, height = 1440 } UIMainView = UI GU_MAIN_VIEWPORT = Viewports.Center Thank you very much for any support you guys can provide.

It would be helpful to have a built in tool rather than LUA manipulation and the FPS issues associated with trying to get exports onto a 2nd screen with medium grade gpu's (Currently have a 1070ti). Currently I have been using Helios to run a virtual cockpit while I fly and have done the usual steps to get the MFD's and what not exported to my 2nd screen. However I feel that there is a definite FPS hit to my setup from having to have a resolution of 2560x2520 (Main screen is a 32" 1440p screen and cockpit is run on 24" 1080P touch screen). It would be helpful to have a baked in way to handle exporting Cockpit MFD's and other scopes (radar, RWR in Particular) that would not have a huge hit on FPS especially given the scarcity of higher end equipment as of recent. I know that MFCD existed but that program hasn't been updated or supported in some time and so there is no other options than the current LUA manipulation method.

Good day, I have a touch screen I want to use for Helios. However, I seem to have a Windows problem. If you do not want to set the touch screen as primary monitor then there is, supposedly, a windows tool to set it as a touch screen. It is called calibrate for pen and touch input. This is missing in my windows version and I wondering if anyone know how i can install it, or use it? How do I get windows to recognise my touch screen without setting it as the primary monitor? Cheers!

All Switches and Gauges are working, bitte the export to the Displays i.e. DDIs does not work. I use Helios 1.6.... It would help to know which Files have to be where. I guess that the Files are not at the places where they have to be. Looking forward for your help. Andy

Hi all I've an F18c home cockpit and my UFC and IFEI Good morning all, I'm building a homemade F18c cockpit and want the UFC and IFEI to look like a super hornet However, I would like to know if it is possible to retrieve data from the simulator and display them via Helios when this data is not offered in the drop-down menus in Helios. Example: I would like to collect the amount of fuel in each wing to display it. But this possibility is not offered by Helios. Thanks in advance

Helios response time on switches and secondary instruments is so slow. Instrument needles look like there stuck sometimes. All displays( RTT I suppose) are working flawlessly. I just started getting into DCS and I am a little out of my element. Any suggestions? I am on newest version.

The Thrustmaster MFCD is too expensive, and is not for A-10. the price of industrial touch screen in China is acceptable, about 600RMB for each(≈86$). So I separate the MFCD for Helios for A-10c2 and make two virtual MFCDs. I set the touch screen resolution 768*768, main monitor is 2560*1440. Thanks to the Helios, it is a amazing and great sofeware. put the custom folder into *:\username\Documents\Helios\Images\Capt_Zeen\A10C\ and the A10CII_v1.0-3.hpf into *:\username\Documents\Helios\Profiles A-10c2-virtual MFCD.zip

Ive been using Helios for a few years now for f18,f16,f14 and have no issues getting the MFD's to show up on my 12" screen. Lately Ive been learning the warbirds, mainly the P47 and well Im trying to display some of the gauges on my 12" screen. Some gauges I had no issue getting to work like the Altitude,manifold Pres,Rpms but I cant get the speed to work right. Its displaying almost 100 mph slower than in game. I tried to use Capt Zeens P51 profile to reverse build that gauge but no luck there either. Anyway know what Im missing here or how to correct this? Also another question. With helios and using my profiles I built for the MFD's in modern modules I do not need to use the Helios Control Center. I just start the game and any module I load up with MFD is automatically loaded. This isnt true when flying warbirds and trying to use the gauges, I have to use Control Center to get the gauges to display. Is that just the nature of Helios or am I also missing something here? In DCS settings I have my monitor profile set to my current profile that is set for 4 screens and works automatically for any mfd profiles I setup in Helios without control center, like I said same isnt true for the P47 gauges. Again any help would be great. Thanks.