derammo

Glad to hear it. Just to close on the previous question for posterity :) : The DPI thing is just an informational message and unrelated to the warnings or errors you are seeing. But it looks like you worked it out.

Helios currently doesn't have the ability to tell if you have different DPI values. It just always tells you that message that you should check (not that they are necessarily wrong.) I had thought this message would be there short term while we wait to implement it correctly, but then it got de-scheduled for a while. If your DPI values are all the same, then you can safely ignore the message.

I don't use any of these things so would not want to recommend something and then get questions about THAT free software also :) I just heard others talking there is better stuff now.

You should not be using the "2-monitor-FA18C" that's the monitor setup that came with Capt Zeen 1.4 profile. Ignore ALL the instructions from a 1.4 profile. Don't copy any mod. Don't copy any monitor setup. Don't edit the monitor setup. Just let Helios configure everything for you. It will tell you in the "Recommendations" in the Interface Status what your "Monitors" selection (usually "Helios") and "Resolution" should be in DCS.

PS: See my previous reply about writing code. However, if you don't mean something entirely custom and just want to make an ADI type thing, there are these (Capt Zeen specials, so you can probably get support on his discord server.) https://github.com/HeliosVirtualCockpit/Helios/wiki/Custom-Gauge https://github.com/HeliosVirtualCockpit/Helios/wiki/Custom-Tape

Some of the other export scripts (not Helios) must be wrong/weak :) In an export script, you are supposed to check if some other script ahead of you has already registered itself and then call it when you are done with your stuff, so everyone gets called. So you have to put the worst script first, because it won't call anyone else. Then you put the civilized scripts (TacView, Helios) etc at the end because they actually call the ones before.

Creating entirely custom controls is a matter of programming them in C#. It's not hard to figure out from the code how to do it. Then you either contribute them to Helios if you plan to distribute them or otherwise make a plugin for your local use. We are under strong GPL so if you do distribute it, you have to give us the source so everyone can use it.

IRIS isn't part of Helios. Helios cannot do this job, even though it probably should if someone who is a very good programmer wants to work on that. IRIS is redistributed (with permission) with Helios 1.4 for convenience, because BlueFinBima uses it. There are better tools out there now for this same job, but you can still use the IRIS that is included in the last 1.4 release if you want. https://github.com/BlueFinBima/Helios14/releases We might make an IRIS build available again with 1.6 also, depending on (again) if anyone does the work (scripting it as part of our build and upload process.)

It can hold a key down just like a keyboard. And also just like a keyboard, it cannot just send the key over and over. Hopefully you can get your DCS keybindings to do the the right thing with a held key. Attached is an example. Here's how to test it: https://w3c.github.io/uievents/tools/key-event-viewer.html hold_key.zip

That's a neat idea. Helios can send key strokes so you could do that. It can't currently create bindable axes in DCS (it is not a virtual joystick.)

Ah. You should wait for a Helios release that supports this plane. As far as DCS is concerned, this is a completely new plane, never mind the fact that most of it is a straight copy. But it does have its own files and Helios needs to update those to add viewport exports etc. It turns out that was relatively easy so I have completed that work (I think?). Like mentioned a few posts ago, the testers group (volunteers) has access to a build of Helios where we are testing this. I ported the existing Capt Zeen profile to run with the new aircraft, so at least something works. Now the bigger work will be for Capt Zeen to create an actual profile to match the A-10C II cockpit. But in the mean time, we should be able to use a quick port of the existing one so we can continue to play. There will obviously be some panels that don't actually exist in the plane, but at least we can play. What you have running right now is probably the A-10C profile and of course the viewports don't work because you don't have any viewport patches/mods in the files for the A-10C II. Those come with the next Helios release.

PS: I tried build 55847 and found no problems so far. Are you on latest Helios?

Every time ED changes the Lua files, I have to go and make sure out mods/patches work again for the new version. Until they add me to the private beta program, this means I will usually need a day or so to fix stuff up after OpenBeta. By the time things hit Release, they are obviously all done. But the leading edge will always be unstable as you know. I wrote the first version of A10C_2 support yesterday and it is currently in closed testing. If you are a technical user/programmer type, you are welcome to join my testers group on the discord to get access to unreleased builds.

I always appreciate more data. I would need the settings that you have for "Export Frequency" in the DCS interface for your Helios profile. And then just let me know what FPS you have without and with Helios exports running. But of course I don't expect you do that just for testing if you are using VR now :). Anyway, if you end up playing with Helios again, then I would love this data.

could not repro this issue with the patches... please reach out on Discord if you are having this problem hreich: finally was able to open your screenshot. Your patches appear corrupted or changed. There is an underscore missing in the name of a variable being matched. Were your patches hacked up?

If you are seeing significant performance impact from Helios 1.6 exports, please let me know by filing a bug here https://github.com/HeliosVirtualCockpit/Helios/issues/new or reaching out on Discord https://discord.gg/qtvdVWc

even if the interface for A-10C II isn't there yet, it should at least not break the viewport patch install. I am working on that now.

Helios 1.6.3304.0 is now pushed to all users via update notification. This build is required to fix a bug in the archive installer we are about to start using to install Capt Zeen profiles. release notes: https://github.com/HeliosVirtualCockpit/Helios/releases/tag/1.6.3304.0 download: https://github.com/HeliosVirtualCockpit/Helios/releases/download/1.6.3304.0/Helios_Installers.zip

Release 1.6.3302.0 is now "general availability" and is recommended for all users. This release has some features requested by profile developers and power users. release notes: https://github.com/HeliosVirtualCockpit/Helios/releases/tag/1.6.3302.0 download: https://github.com/HeliosVirtualCockpit/Helios/releases/download/1.6.3302.0/Helios_Installers.zip

WinWing: Did you resolve this? For Helios, I abandoned the "NextEvent" style of exports because of changes made in recent OpenBeta seemed to screw up the scheduling for very high update rates (like your 100Hz rate.) So now I just run on "BeforeNextFrame" with my own governor to limit the rate.

Seriously though, thanks for the pointer. I won't use it, but thanks. Anyone who wants to write the Helios plugin will need that library. I won't do it though. By the way, the only actively developed Helios is here https://forums.eagle.ru/showthread.php?t=282103

In case the Knobster developers want to write a Helios plugin for their COMMERCIAL PRODUCT, the code is here... https://github.com/HeliosVirtualCockpit/Helios :P

Release 1.6.3214.0 is now "general availability" and is recommended for all users. This is the release that adds Steam support properly. If you were previously using a workaround, please make sure to read the release notes carefully to clean that up. release notes: https://github.com/HeliosVirtualCockpit/Helios/releases/tag/1.6.3214.0 download: https://github.com/HeliosVirtualCockpit/Helios/releases/download/1.6.3214.0/Helios_Installers.zip

out of curiosity, would you have preferred to get a popup in Helios that makes you actually upgrade your Helios to a new build to get these patches upgraded? I decided not to do that because I wanted to demonstrate we can fix it without compilation, but maybe that wasn't as user friendly as just upgrading to a new build.

Sorry I should have posted here also. Here is the resolved issue, in case you don't use Discord. https://github.com/HeliosVirtualCockpit/Helios/issues/323