derammo
-
Posts
298 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by derammo
-
-
3 minutes ago, rurounijones said:
It looks like we can no longer export the RWR for the Mirage to a separate Monitor since this requires modifying those lua files. The Radar export works.
Please get RAZBAM to update the RWR luas so that it can be exported.
In fact, just allow people to export all the instruments as they please in the M2K. Basically replicating this userfiles pack: https://www.digitalcombatsimulator.com/en/files/2317118/
Yes I suggested a similar thing in the DCS Discord. Helios and other tools (like that user files pack) pretty much all just add the same viewports and give additional plane-specific names to the MFDs and such. If it was possible to coordinate with all the third parties to make these changes to the aircraft as shipped, that would eliminate a lot of the mods and patches, but not all of them.
Another class of changes we need to make with exported screens (especially on the Hornet) is to change the graphics settings so the exports are actually legible, which degrades the cockpit views and so can't be done by default. The only answer I see for that is to separate those graphics options from any that were involved in cheating by putting them in separate files.
I am not hopeful we can get enough coordination for either of those. It's not a trivial problem with so many parties involved.-
6
-
-
I am the developer of Helios' viewport patching and monitor setup functionality, and I can tell you with certainty that we can't work around this IC. So really the only way we will end up with a working solution for IC servers is if Eagle Dynamics can back out this change. This is OpenBeta, where they try out stuff. It doesn't HAVE to be released this way.
So we really need them to change course on this and come up with something else to do, like for example moving whatever parameters were involved in the cheating to another file that can be controlled, or something like that. But clearly someone on the dev side had some reason for locking this down, maybe they themselves are a PVPer who does not use extra screens or a cockpit build. Clearly they were not aware of what would happen with this change. Who knows... but that's why we have OpenBeta, right?
So let's maybe just document what the effect is, including your stories and anecdotes and so on, but without burning any good will we might have? I'm worried about the degree of hatred in this thread, and whether this will make it less likely that we get what we want. BIGNEWY has been really responsive and has been collecting the data about what the effects on various mods are to take back to devs. So let's give them some time to try to come up with something?-
21
-
-
Hi. I am the author of Helios patching functionality, and I posted my notes on this problem here:
That thread says it is where BIGNEWY is collecting a list of valid applications and mods that should have been allowed.
On my post there, I attached a diff of all our changes that we make, but just in case people don't read patches, this is the list of files we change:
Mods/aircraft/A-10C/Cockpit/Scripts/AN_ALR69V/indicator/AN_ALR69V_init.lua Mods/aircraft/A-10C/Cockpit/Scripts/CDU/indicator/CDU_init.lua Mods/aircraft/A-10C/Cockpit/Scripts/CMSC/indicator/CMSC_init.lua Mods/aircraft/A-10C/Cockpit/Scripts/CMSP/indicator/CMSP_init.lua Mods/aircraft/A-10C/Cockpit/Scripts/DigitalClock/Indicator/DIGIT_CLK_init.lua Mods/aircraft/A-10C/Cockpit/Scripts/MFCD/indicator/MFCD_left_init.lua Mods/aircraft/A-10C/Cockpit/Scripts/MFCD/indicator/MFCD_right_init.lua Mods/aircraft/A-10C/Cockpit/Scripts/UHF_Radio/indicator/freq_status_init.lua Mods/aircraft/A-10C/Cockpit/Scripts/UHF_Radio/indicator/preset_channel_init.lua Mods/aircraft/A-10C/Cockpit/Scripts/UHF_Radio/indicator/repeater_init.lua Mods/aircraft/A-10C_2/Cockpit/Scripts/AN_ALR69V/indicator/AN_ALR69V_init.lua Mods/aircraft/A-10C_2/Cockpit/Scripts/CDU/indicator/CDU_init.lua Mods/aircraft/A-10C_2/Cockpit/Scripts/CMSC/indicator/CMSC_init.lua Mods/aircraft/A-10C_2/Cockpit/Scripts/CMSP/indicator/CMSP_init.lua Mods/aircraft/A-10C_2/Cockpit/Scripts/DigitalClock/Indicator/DIGIT_CLK_init.lua Mods/aircraft/A-10C_2/Cockpit/Scripts/MFCD/indicator/MFCD_left_init.lua Mods/aircraft/A-10C_2/Cockpit/Scripts/MFCD/indicator/MFCD_right_init.lua Mods/aircraft/A-10C_2/Cockpit/Scripts/UHF_Radio/indicator/freq_status_init.lua Mods/aircraft/A-10C_2/Cockpit/Scripts/UHF_Radio/indicator/preset_channel_init.lua Mods/aircraft/A-10C_2/Cockpit/Scripts/UHF_Radio/indicator/repeater_init.lua Mods/aircraft/AV8BNA/Cockpit/MPCD/indicator/MPCD_init.lua Mods/aircraft/F-16C/Cockpit/Scripts/Displays/DED/indicator/DED_init.lua Mods/aircraft/F-16C/Cockpit/Scripts/Displays/EHSI/indicator/EHSI_init.lua Mods/aircraft/F-16C/Cockpit/Scripts/Displays/EHSI/indicator/LCD/EHSI_LCD.lua Mods/aircraft/F-16C/Cockpit/Scripts/Displays/MFD/indicator/LCD/MFD_LCD.lua Mods/aircraft/F-16C/Cockpit/Scripts/Displays/MFD/indicator/MFD_left_init.lua Mods/aircraft/F-16C/Cockpit/Scripts/Displays/MFD/indicator/MFD_right_init.lua Mods/aircraft/F-16C/Cockpit/Scripts/EWS/RWR/indicator/RWR_ALR56_init.lua Mods/aircraft/F14/Cockpit/Scripts/RWR/Indicator/Pilot/init.lua Mods/aircraft/F14/Cockpit/Scripts/RWR/Indicator/RIO/init.lua Mods/aircraft/F14/Cockpit/Scripts/UHF_Radio/Indicator/Main/init.lua Mods/aircraft/F14/Cockpit/Scripts/UHF_Radio/Indicator/RemotePilot/init.lua Mods/aircraft/F14/Cockpit/Scripts/UHF_Radio/Indicator/RemoteRIO/init.lua Mods/aircraft/F14/Cockpit/Scripts/VHF_Radio/Indicator/Main/init.lua Mods/aircraft/F14/Cockpit/Scripts/VHF_Radio/Indicator/RemotePilot/init.lua Mods/aircraft/FA-18C/Cockpit/Scripts/IFEI/indicator/IFEI_init.lua Mods/aircraft/FA-18C/Cockpit/Scripts/Multipurpose_Display_Group/AMPCD/indicator/AMPCD_viewport_cfg.lua Mods/aircraft/FA-18C/Cockpit/Scripts/Multipurpose_Display_Group/AMPCD/indicator/BAKE/AMPCD_bake_init.lua Mods/aircraft/FA-18C/Cockpit/Scripts/Multipurpose_Display_Group/Common/indicator/BAKE/MPD_common_bake_init.lua Mods/aircraft/FA-18C/Cockpit/Scripts/Multipurpose_Display_Group/MDI_IP1556A/indicator/MDI_left_viewport_cfg.lua Mods/aircraft/FA-18C/Cockpit/Scripts/Multipurpose_Display_Group/MDI_IP1556A/indicator/MDI_right_viewport_cfg.lua Mods/aircraft/FA-18C/Cockpit/Scripts/TEWS/indicator/RWR_ALR67_init.lua Mods/aircraft/FA-18C/Cockpit/Scripts/UFC/indicator/UFC_init.lua Mods/aircraft/FA-18C/Cockpit/Scripts/fonts.lua Mods/aircraft/Ka-50/Cockpit/Scripts/ABRIS/ABRIS_init.lua Mods/aircraft/Ka-50/Cockpit/Scripts/ABRIS/BAKE/init.lua Mods/aircraft/Ka-50/Cockpit/Scripts/SHKVAL/BAKE/init.lua Mods/aircraft/Ka-50/Cockpit/Scripts/SHKVAL/SHKVAL_init.lua Mods/aircraft/M-2000C/Cockpit/COM/COM_GreenBox_init.lua Mods/aircraft/M-2000C/Cockpit/COM/COM_init.lua Mods/aircraft/M-2000C/Cockpit/FUEL/FUEL_init.lua Mods/aircraft/M-2000C/Cockpit/PCA_PPA/PCA_BR_init.lua Mods/aircraft/M-2000C/Cockpit/PCA_PPA/PCA_UR_init.lua Mods/aircraft/M-2000C/Cockpit/PCA_PPA/PPA_init.lua Mods/aircraft/M-2000C/Cockpit/PCN/PCN_BR_init.lua Mods/aircraft/M-2000C/Cockpit/PCN/PCN_UR_init.lua Mods/aircraft/M-2000C/Cockpit/RWR/RWR_init.lua Mods/aircraft/M-2000C/Cockpit/VTB/VTB_init.lua Mods/aircraft/SA342/Cockpit/NADIR/init.lua Mods/aircraft/SA342/Cockpit/RWR/indicator/init.lua Mods/aircraft/SA342/Cockpit/Radio/Indicator/FM/init.lua Mods/aircraft/SA342/Cockpit/Radio/Indicator/UHF/init.lua Mods/aircraft/SA342/Cockpit/TV/Indicator/init.lua Mods/aircraft/SA342/Cockpit/WP1/init.lua
There are also some other changes made by users or profile authors, such as viewports for the Viggen.
-
10
-
-
It appears that viewport export changes are no longer allowed:
- we need to rename exported viewport names like LEFT_MFCD to make them unique across aircraftIt appears that adding viewport export calls is no longer allowed:
- we need to export things like RWR that are not exported by default
This affects all Helios users (approximately 2000 DCS users, we don't track users exactly) and all cockpit builders who use additional displays for things like RWR.
Helios also changes rendering settings in fonts.lua and across several instruments files (MFDs and such) to make exported viewports look legible on the F/A-18C. I can see that this could be considered an IC violation, so I would say this last part is optional but really convenient.
[edit: attached a diff of changes made by Helios against a recent DCS release, for example]-
16
-
3
-
-
-
Regarding my availability and a bunch of questions on here I never answered:
You might have noticed I never read this thread (or any threads on this forum) any more. That's because I don't visit this forum in general.
I still answer questions on Capt Zeen's discord:
https://discord.gg/KHmkTXe
or if you have real technical Helios questions, on my discord:
https://discord.gg/Ypj7aURIf you are on Zeen's discord, you will have seen the announcement that I am currently asking the community to support Helios development by joining my patreon. I will post another update towards the end of the month to let you know if I had to wind down my involvement with this project in total. In the meantime, please seek support on the discords instead of here.
-
Please read my comment again. I never said DCS should access the track IR curves. I said I would apply the inverse curve to those axes in DCS.
-
On 12/23/2020 at 4:07 AM, Pilot Ike said:
I thought there was an option to DISABLE them, can't find it anymore.
I removed them with TamperMonkey. Here's the script:
// ==UserScript== // @name no lights // @namespace http://tampermonkey.net/ // @version 1.0 // @description it isn't the 1990s // @author You // @match https://forums.eagle.ru/* // @grant none // @require http://code.jquery.com/jquery-latest.js // ==/UserScript== (function() { 'use strict'; $("#lights").css("visibility", "hidden"); })(); -
3 hours ago, Chriscache said:
There is nothing
I just checked it. The post is still there.
-
I am not trying to track where I am looking. This isn't what the HMCS does either. It should point to where my HEAD is pointing, not my eyes. And that is exactly known from TrackIR if I apply the inverse curve of the one applied in the TrackIR software to map from real head rotation to virtual head rotation.
PS: One thing I agree is that it would not be mathematically precise. We would not be putting in our screen geometry and seating position etc. to solve for the exact position. Just use manual curve editing to get it right in a few spots and interpolate. That would be way better than what we have now.
-
Agree with this request.
The HMCS X/Y displacement from center should be an axis that can be bound. We could then bind it to the TrackIR rotation with an appropriate curve for our environment. I realize this ignores translational head movement, but it would at least allow us to match the spatial feeling you get with TrackIR and have it feel like the HMCS is tied to our head.
Yes, I know it is a significant work if the current implementation is just a static overlay. But it is pretty much the only way to make this work. Your head has to deflect a small amount for TrackIR, so making the HMCS static isn't gonna work. -
Will the a10c2 be supported as an option for cockpits and will the capt zeen a10c profile work for it?
Didn't you already discuss that on the Discord?
-
Hello,
I am trying to control a virtual joystick (vjoy) using Helios.
A button pressed via touch in Helios should e.g. simulate the virtual DX button 1 in the virtual joystick.
Is that possible?
It is not. I decided supporting anything involving vJoy was not worth it. I don't want to deal with a kernel driver signed by a random person being installed on people's computers.
For DCS applications, we have always been able to do everything we want by just sending cockpit interaction (via Helios' DCS interfaces) and keyboard bindings (via Helios' Keyboard interface.)
That said, there is nothing stopping anyone from writing a Helios plugin interface to talk to vJoy if they want. I just did not want to be the one who has to maintain or support that :).
-
If I add a Falcon BMS 4.34 viewport to Helios 1.6 the viewport properties has a "Patch Required" checkbox.
What exactly is this? Is this a patch for Falcon BMS or a patch for Helios?
Any help would be appreciated.
Unfortunately, those viewports are only for DCS
https://github.com/HeliosVirtualCockpit/Helios/wiki/Simulator-Viewport
-
I know people have complained about this a while ago. Is there any fix to make the exported viewports brighter?
Please file a lot of bugs against DCS aircraft about this :). It is DCS that renders the viewports and we (Helios) have basically no control over it. I did some Lua hacking for the F/A-18C to bump up the brightness (these changes of mine are already automatically applied when you configure Helios 1.6.) But it is not generally possible for me to fix that for the other planes. So please file bugs/enhancement requests against all the planes where it doesn't work well. It requires code changes by the plane developers.
-
Bit of a weird question
is it possible to make a generic cockpit up that will work with any aircraft? So that I can have all the custom ones but when I’m flying one that dose not have a custom pit I can still have the basics? Ie, altitude, speed, bearing, rwr, mfcds etc?
Here are some links to study:
NOTE: doesn’t work in Multi Player if the server is blocking the use of the LoGet... functions
https://github.com/HeliosVirtualCockpit/Helios/wiki/Simulator-Viewport
(There are generic Simulator Viewport objects for the generic names for MFDs etc. that exist in many aircraft)
So you will get SOME stuff for SOME aircraft, depending on the whims of the different DCS aircraft developers and MP server settings. Have fun.
-
What's wrong with this picture? I just installed Helios 1.6 yesterday and it was working fine until 5 minutes ago. For some reason the Control Center starts minimized to the taskbar. And when I click on it I get only 1/3rd of it's window. I can drag it around and click on the buttons I can see, but how do I fix the window to be the correct size??
[ATTACH=JSON]{"data-align":"none","data-size":"full","title":"HCC windows bugged.png","data-attachmentid":7123218}[/ATTACH]
I think someone else mentioned this but nobody filed the bug. It looks like StartMinimized is broken.
1) please file a bug https://github.com/HeliosVirtualCockpit/Helios/issues/new
2a) if you are able to do some simple editing of an XML file, open the file Documents\Helios\ControlCenterPreferences.xml and change "StartMinimized" value from "True" to "False"
2b) if you don't know how to edit a file like that, then just delete the file Documents\Helios\ControlCenterPreferences.xml. You will reset all control center preferences to defaults and also reset the "what was my most recent profile for each aircraft" list.
3) Don't use "Start Minimized" until you get a new Helios release with a fix
-
Hi,
I wonder if anyone can help me solve this problem?
I am trying to setup a DCS Hornet UFC export profile i have on a remote laptop with a touchscreen connected in order to send the UFC keypresses to my desktop PC that has DCS running on it. So far no problem with the laptop/touchscreen side, the profile works and when i press the UFC buttons on the UFC they are recognised (they derpress etc.) The problem is i do not seem to be able to get the keypresses recognised and active in DCS on the Desktop PC. I have the keypress receiver installed on the desktop and have configured the pots etc to match with the Helios install on both systems.
I just have no idea where to go from here to get the touchscreen keypresses active in DCS when i'm in the Hornet. Unfortunately i can't use the more conventional method of connecting the touchscreen to my desktop system, i've tried but it just doesn't work.
Any help at all would be very much appreciated, i have been working on this for a few days now.
Thanks.
Hi. I didn't write KeypressReceiver (inherited that from 1.4) but I can help you figure it out if nobody else answers your question. https://github.com/HeliosVirtualCockpit/Helios/wiki/Ask-derammo
-
-
Running Helios 1.6.3308.0 with YAME64 1.2.1 and if I create a Helios button directly over a YAME64 touch point then tapping the Helios button also taps the YAME64 touch point even though it is running behind Helios.
Is there any way for Helios to prevent touching through to the YAME64 screen in the background?
Any help would be appreciated.
that doesn't sound right. Can you file a bug/issue please at https://github.com/HeliosVirtualCockpit/Helios/issues/new and provide some screen shots in it?
I don't think windows applications are supposed to get mouse clicks if an application on top of them already handled it...
-
I keep getting this: Main screen is 27" 1440 monitor 2nd screen with helios is 22" 1080 touchscreen.
It is telling you in the Recommendations what to do.
You generated a monitor setup using Helios (to make sure if matches the profile) and then you didn't select that monitor setup in DCS Options. Follow the Recommendations shown right there in your screen shot.
-
@BIGNEWY read the posts by Desert Fox and others. It's not that this needs more tweaking. It's that these changes are actively bad. The old site was ugly and antiquated looking, sure. But at least it wasn't actively violating every principle of UI and UX design.
-
3
-
-
Thanks and a big sorry is in order. I was using the wrong files and have now set things up using only Helios 1.6 and FA-18C Ver.3b. I now have my second monitor displaying the MIP and all of the displays and gauges display properly, but my main cockpit display is stretched to two monitors and the displays are transparent (pics attached). I have also included my settings page if required. If you need more information, please don't hesitate to ask and I will send it ASAP.
Thanks Again,
Wayne
in helios profile editor open the “DCS Monitor Setup” UI and de-select the airplane icon on the second screen, so it isn’t blue any more
-
I have the A-10C thing figured out and all of the DDI/AMPCD/UFC/RWR/IFEI are all working now, but the rest of the gauges and switches are not. I am using the 2_monitors-FA18C in the Monitor setting instead of the requested Helios setting in Monitors. When I use Helios and have the Main Instrument Panel (MIP) on my second monitor nothing goes there as it should. Instead, my main display is extended to the second monitor that is covered up with the Helios cockpit MIP. How do I get this corrected or what do you need to figure this out?
Thanks Again,
Wayne
Like I said above, don't use a monitor setup that isn't the one that Helios wrote for you.
If you want to change the layout or arrangement, you can move the viewport rectangles around in the Helios Profile Editor and then select "Configure" again in the "DCS Monitor Setup" interface in your profile.
If you write your own monitor setup file or use a random one you downloaded (2_monitors-FA18C) then Helios (and I) cannot help you. Getting that file correct by hand is up to you and it is pretty difficult, which is why Helios does it for you now.
Helios 1.6 - Official Thread
in PC Hardware and Related Software
Posted
You may have better luck getting community support on the CZ Discord, which has a channel for people creating profiles.
https://discord.gg/KHmkTXe
#creating_your_profiles