Loz Helios profile in full or windows mode?

[sobe]

It has been awhile since I looked at this issue and before I screw up my setup, I would like to verify if you run Helios (with the Loz profile that includes the MFDs) in full screen or windows mode?

 

Thanks

[Gadroc]

Windowed mode. Helios draws over top of the MFDs drawn by DCS. If DCS is in full screen Helios can't draw on top of it.

[sobe]

Thanks for the answer from the expert. I hope all is well with you and your family.

[cichlidfan]

I hope all is well with you and your family.

 

@Gadroc Indeed. I hope you, and yours, are having a good New Year.

[sobe]

Gadoc

When I looked at my game options, I noticed that the full screen option box was filled so I unchecked it. However, please note that I have obviously been playing the A10 C with Loz's profile in full screen for sometime with no apparent issues. Interesting.

[Gadroc]

Newer versions of DCS World automatically fall back to window mode if you have specified a resolution higher than the primary display.

[Gadroc]

Thanks for the good wishes guys. Been a very very busy year. Starting to get an itch for working on the pit, so hopefully you'll see more from me regularly.

[agrasyuk]

Good to see you back Gadroc.

[Capt Zeen]

Welcome back, Gadroc!

[CrackerJack]

I see that with 1.5 you still have to run in Full Screen mode to enable SLI which is a real bummer! I guess I can't have my Helios and SLI together :-(

[intx]

I am trying to run Helios on my Windows 10 machine. I have DCS set to windowed mode (Full screen unchecked). When I run the my Helios profile from Helios controller, I see my profile on the second monitor. When I start DCS, the second monitor goes dark. I have even tried to running Helios after DCS has started. I cannot get Helios to stay on top (from a z-level aspect). Am I forgetting something?

[cichlidfan]

Not that I can think of. I will be curious to find out the solution/cause?

[intx]

Call it Helios newbie blunder. Somehow the "Stay on Top" setting was turned off on the 2nd monitor portion of my profile. Fixed my problem right away...

[Fakum]

I am in the process of doing a real fresh build to solve some key binding problems. My 1.2 version and use of Helios has been superb! Unfortunately, it has been many years since I installed Helios and I recall having to install files from Peter P which did some over writing to files in the DCS root directory that helped with all the export files. What I want to know with Beta 1.5 and Alpha 2.0, and now Windows 10. Are those files like the ones we installed from Peter p still needed and if so, compatible with the latest DCS versions? Should those older files be allowed to overwrite the new version files? I have been searching the forums for sources of info on how to do a clean fresh install, but there are tons of hits when doing searches, and most do not help with mu question. Thanks for any input.

[sobe]

Fakum

Are you by any chance referring to PeterP's radio menu mod that allowed you to have the radio lines appear in the Loz profile where the gauges are located? I know of no other PeterP mod for the Loz profile.

 

I have been using your Rev 5 profile for the A10-c. Do you have a later version? Did you apply the radio fix by Capt Z to your profile?

Edited December 16, 2015 by sobe
new last sentence.

[Fakum]

No, its something else, for the Ka-50 & A-10C (in cockpit on or in cockpit off) something like that,, I will need to go thru my notes

 

EDIT: I'm on the trail, but have not found the file link yet, It's Peter P "Preset Files MFCD in cockpit on/off" (something to that effect), this file, to the best of my recollection, eliminates the need to edit all of the export instrumentation, so that you can just add/edit them in your monitor config.lua

Edited December 16, 2015 by Fakum

[sobe]

Fakum

What about:

I have been using your Rev 5 profile for the A10-c. Do you have a later version? Did you apply the radio fix by Capt Z to your profile?

[Fakum]

oh,,, I somehow overlooked that? Anyway, I do believe I have updated that. i will check tonight

[Fakum]

Sobe, here is my latest with the radios fixed, again, I may have some keybindings that don't match yours but I believe the radio keybindings are what were listed in the instructions,,,

[sobe]

Fakum

I know that it is probably impossible, but I would like to know what key bindings you thought were a problem with Loz and what you changed.

 

I use Capt z's export file together with PeterP's viewport names and have never had any export issues other than the radio buttons, which are know fixed.

 

I may try to learn the Huey next so is your revision 27 the latest version of your Helios profile?

 

I sure wish I understood Helios better, but it is so confusing to me.

Edited December 16, 2015 by sobe

[Fakum]

Hmmmm,, I'm not really certain how I can possibly find out what keybindings I changed in all these profiles, but I can show you what keybindings that are changed from the default keybindings from each module. Every time you change a key binding from the default one or even add a binding where there was none, a file is created called a "diff.lua"

 

e.g.C:\Users\YOURNAMEHERE\Saved Games\DCS.openbeta\Config\Input\A-10C\keyboard

 

you can open these files and see the name of the command and what the default keybinding was, and what it was changed to.

 

I have attached my latest UH-1H Helios Profile ( but I think I only used it in version 1.2? not sure if I made it for 1.5, but its possible)

I also attached the keyboard diff.lua files for the A-10C & Huey. I converted them to Word Document so you can read through it better. If your not familiar with it, when you open the file. Scroll down until you come to the 1st "Name" Line, above that line you will see the new key command. Foe example, when you open up the A-10C file, the 1st "Name " line is :

 

["name"] = "Throttle Left Up",

When you look above that you will see

[1] = "RAlt",

That is the modifier I used in the command, the next line above that to look for will be the "Key" line

["key"] = "Num+",

 

This indicates the key command I set for that name function, below the name you will see "Removed, it also has Key and Reformers, what you see there are what were the default keys that I changed in DCS. Hope this helps

 

EDIT: Standby, cant get the word docs to upload?

Edited December 17, 2015 by Fakum

[Fakum]

Try this

[sobe]

Fakum

Thanks for the diff files and I have reviewed them. One question-did you make these key changes in the game controller column AND also in Helios or just the former?

[Fakum]

The changes I made, and that is shown in the diff files is for the keyboard. So I made the changes in the game options as you would typically. With that being said, if any of those commands that are listed in the diff file are used in Helios, then you will know what key bindings I set as they are shown in the diff file. Any commands for Helios are what they come with as default if they don't show up in the Diff file. I hope that makes sense?

[sobe]

Fakum

Sorry but this part does not make sense: "With that being said, if any of those commands that are listed in the diff file are used in Helios, then you will know what key bindings I set as they are shown in the diff file. Any commands for Helios are what they come with as default if they don't show up in the Diff file. I hope that makes sense?"

Do you mean that the diff file contains your changes and if those changes effect the Helios profile, then you made similar changes in Helios? For example, I don't believe Loz has the seat adjustment in his profile so that didn't effect Helios. However, he did have the up/down selector on the UFC in his Helios profile and you changed commands in your diff file?