derammo

this is the F18 profile support channel https://discord.gg/wztGPqQ

outstanding! I can fix the Helios-provided interface for F-18, but Capt Zeen's module uses its own as you know. So he will have to fix that in his stuff. https://github.com/HeliosVirtualCockpit/Helios/issues/319

Unfortunately, there is currently nobody working on Phidgets for Helios. I think the old Phidgets 2.1 interface broke over time and anyway that API is deprecated by Phidgets. I did some stuff with Phidgets 2.2 for my own setup, but it isn't going to get released (no time to support more stuff.) So if someone was to join the team and maintain Phidgets support again, that would be great.

Capt Zeen's FC3 profiles have not yet been ported to 1.6. That's why his download page message says he will do those soon. I resolved the bug you filed by creating a version of the F15 profile that works with 1.6. https://github.com/HeliosVirtualCockpit/Helios/issues/318

PS: we now use context patches to edit the Lua files, so even minor tweaks won’t matter as long as they aren’t structurally changed, which they would not be in a re-packaging

Thank you for engaging. Helios support for doing viewports/monitor setups in Steam installs incoming :) https://github.com/HeliosVirtualCockpit/Helios/issues/295

FYI: You previously released at least one OpenBeta that had five “words” in the version number. I don’t remember the build number but it reported (in autoupdate.cfg) something with the format 2.5.6.5xyzw.1. Kind of like someone repackaged without rebuilding or something? Anyway, after we all fixed our parsing code to allow version numbers like that, it was all good. For our add-on tools (Helios in my case), that just means we will treat that build as the same version on Steam (since Windows version numbers obviously only have 4 segments.) Probably won’t be a problem, since the files will be close enough if it is just a respin. Just something I wanted to point out in case you were unaware that thing was shipped :)

lol, thanks! I'm an idiot. I didn't even check if you stamped the files :)

Does anyone know of a way to find / extract (with a program) the currently installed DCS version from a DCS Steam install? Obviously there is no autoupdate.cfg. It is stamped into the start screen, but apparently into the binary itself? At least I could not find it.

When you render to extra viewports ("viewport exports"), will it render to the resolution that is configured in DCS "Resolution of Cockpit Displays", or do you get some random aircraft device-specific resolution that is then stretched to the output viewport? Or does it actually render natively to the viewport size that is specified in the monitor setup without subsequent stretching? In another way of thinking: if you wanted to decide what size to make MFD exports for good visual quality, what size would you make them? Pretend you have whatever display size available that fits, so don't worry about that. Understanding this precisely has major impact on viewport export tech I am working on for Helios. It would be nice if someone has already done this research, so I don't have to do 1000 tests :)

I was actually thinking a clean way would be to wrap the device driver (with a filtering driver) and punt to another API. Like maybe feed vjoy. Then any old crap keyboard you have lying around could be a game controller with the maximum number of supported buttons (whatever that is currently in windows hehe.)

What you are reporting is very strange. Installing the ready-made 1.6 versions of profiles is actually way less complicated and I haven’t seen any reports of failed installs where the exports just don’t work. I would love to see the configuration that you ended up with when it failed, but I guess you have already deleted it? Do you have a backup of your Scripts folder from when you installed 1.6 profiles and it broke? In any case, I would love to help you install the 1.6 version of the F18 profile and see if it fails again, so that I can improve the product. Do you have discord? I hang out here all day helping people: https://discord.gg/qtvdVWc

The upgrade to 1.6.3104.0 is now released to all Helios 1.6 users. This is the maintenance release to address issues found during the first release. https://github.com/HeliosVirtualCockpit/Helios/releases/tag/1.6.3104.0

You need to remove any viewport mods that you have installed either by copying in files or via a mod manager like OVGME. You obviously have a modified CMSC_init (most likely copied in from Capt Zeen’s monitor config mods from the previous version.). All that is no longer necessary, so please just remove any viewport mods or perform the DCS repair to reset to the files as they are released by Eagle Dynamics. Helios 1.6 expects your DCS files to be “clean” around the parts of the files where it wants to put in modifications for your viewports. You can install other mods and modify files, but not exactly where it wants to insert the viewport names etc.

correct. Helios 1.6 currently doesn't scale the monitor setup correctly if you have multiple different display scaling / DPI values on your different displays tracked here: https://github.com/HeliosVirtualCockpit/Helios/issues/151

Thanks for reporting this. I agree the code as it was in 1.4 and also in the first 1.6 release wasn't very good. That's why I added a feature to preserve Export.lua when possible, even if you don't use Helios to manage it. https://github.com/HeliosVirtualCockpit/Helios/wiki/DCS-Interface#exportlua-generation You can have this feature now by upgrading to https://github.com/HeliosVirtualCockpit/Helios/releases/tag/1.6.3104.0 or you can wait a few days and it will be pushed to all users.

1.) No. Profiles are just documents in your Documents\Helios\Profiles folder and Documents\Helios\Images folder. Anything written to the DCS folders will be written by Helios, no need to use OVGME unless you have other, unrelated mods. 2) Nothing happens. Helios will detect DCS overwrote some files and patch them again. Sometimes DCS changes too much and you will have to wait a couple of days while we push out some new patches to fit. But hopefully that will be very infrequently.

Helios has always had a Phidgets 2.1 interface but I think it rusted / decayed a bit. I don’t know if it currently works but it’s in there. I wrote my own Phidgets 2.2 interface as a plugin. It is not currently distributed but I am open to collaboration.

The second release of Helios 1.6 is available. This is the "immediate follow up" release to roll up bugs that were discovered during the first release. Right now it is marked as a pre-release so that it does not push automatically to all users. If you want to help out, please install it and make sure it works well, before I set it to push to all users in a few days. https://github.com/HeliosVirtualCockpit/Helios/releases/tag/1.6.3104.0

You don't have to do any of that yourself. You no longer download scripts either in version 1.6. Each profile will come with any export module that it might need embedded in the profile. Helios will guide you through configuration and install the files for you. Here's a video showing how you install a Helios 1.6 profile. If you need more help, please join the Helios Support Discord, because it is much easier to answer questions there: https://discord.gg/qtvdVWc

Yes, with a tiny amount of work. You would need to at least configure the exports in Helios Profile Editor. The video I linked in my previous post shows this step. This is required because 1.6 actually takes control of the export scripts again, since it is now compatible with Capt Zeen modules. So you would reuse the exact module file you were using, but let Helios take over the main export scripts. Alternatively, you can configure Helios 1.6 to not write the Export.lua file at all (in "DCS Export.Lua Output (Advanced)" settings section for the DCS interface.) I don't recommend that, because then you are running the old export scripts and not getting any of the new features. But of course if you really want to do that, that's fine too :) ---------------------------------- Einigkeit und Recht und Hornet

If you mean Capt Zeen profiles, then I recommend upgrading to his 1.6 profiles. They add new features and fix lots of bugs. If you mean your own 1.4 Profiles, then yes they will work. However, 1.6 will tell you to configure what export scripts to use, so it can inter-operate with other profiles and so it can make sure everything is installed correctly. This video demonstrates how to do that: If you have a completely custom export.lua, then you need to tell 1.6 not to generate export.lua at all and just use the one you have. Sorry for the tiered answer, but there are several cases.

1.6 is an upgrade against 1.4. So it is not a separate product. In other words, it is also the next version of 1.4, so installing it at the same time is not supported.

Please see this thread for information about Helios 1.6, which adds many new features and usability improvements: https://forums.eagle.ru/showthread.php?p=4437499 And yes, this one upgrades correctly :)

Please see this thread for information about Helios 1.6, which adds many new features and usability improvements: https://forums.eagle.ru/showthread.php?p=4437499