Helios Users- New CH-47F Profile V1.0.3

[MadKreator]

First release of my CH-47F Pilot profile. Please note you MUST have Helios version 1.6.6110.0005 minimum for all functionality.
Enjoy!
Go here to download---> https://github.com/HeliosProfiles/DCS-CH-47F-Profile-by-MadKreator37/releases/latest

User Files-->https://www.digitalcombatsimulator.com/en/files/3340914/

 

 

 

Edited January 4 by MadKreator

[MAXsenna]

Thanks for this! How large monitor did you use?
I think I need a couple more!!

[MadKreator]

22 minutes ago, MAXsenna said:

Thanks for this! How large monitor did you use?
I think I need a couple more!!

Single 24” touchscreen  monitor 1920x1080. Lots of stuff crammed in there lol Some controls are a bit small but most all of it is easily useable via touch. The huge mfd’s were the killer, building everything around 3 of them. Took a long time adjusting everything a few pixels at a time trying to find a good balance. 

[MAXsenna]

51 minutes ago, MadKreator said:

Single 24” touchscreen  monitor 1920x1080. Lots of stuff crammed in there lol Some controls are a bit small but most all of it is easily useable via touch. The huge mfd’s were the killer, building everything around 3 of them. Took a long time adjusting everything a few pixels at a time trying to find a good balance. 

Yeah, I gather. 24" here as well. only 16x10. I had the MFDs originally setup as 800x600, which was kinda perfect.

[MadKreator]

24 minutes ago, MAXsenna said:

Yeah, I gather. 24" here as well. only 16x10. I had the MFDs originally setup as 800x600, which was kinda perfect.

I wanted that range at first. Wanted them as big as could be but had to compromise. With a 16:10 you could prob enlarge some things a bit and rearrange. I tried to make it very “modular” so people could pick it apart easier and adjust to their liking or spread across multiplie screens. 16:10 is not a common size here in the US, I don’t think I’ve ever seen one to be honest lol Several years ago , installing CZ’s profile for the first time, I was thinking what on earth is a 16:10 monitor, that doesn't make sense

[MAXsenna]

1 hour ago, MadKreator said:

16:10 is not a common size here in the US

Well, it's a professional HP screen. My 30" is 16x10 as well. Also an HP Pro screen. It's for workplaces and not gaming.

[MadKreator]

5 hours ago, MAXsenna said:

Well, it's a professional HP screen. My 30" is 16x10 as well. Also an HP Pro screen. It's for workplaces and not gaming.

Oh okay. Then they’re  just not common in my scope of life then I remember going from perfectly square monitors a LONG time ago straight  to 16:9 format as the standard. 

[MadKreator]

@MAXsenna if you do want to toil around with adjusting the profile to fit your 16:10 screen better, there is the raw background texture in the images, you could size correctly and cut your own viewport holes out of. Or I could send the fully made background with no holes cut( if I saved that original)  that you could either enlarge or just copy a selection of part of the background and “extend” the background to fit the screen in a photo editor. Everything should be easily re-sizeable.. but as all re-sizing in Helios it will shift all of the components within each panel slightly so you would need to line them back up, or change their scale if they get skewed. If you feel like it, let me know. I have no problem posting the extra files on google drive. Been trying to get in the habit of saving every edit and not just deleting them. I’ve had to re-do one profile from almost scratch due to me accidentally moving an image folder and not copying it, then prematurely deleting it. A mistake I don’t EVER want to make again

[MAXsenna]

@MadKreator I'll have a look. I'm really torn now. I'm testing your profile, and it's very god. As always!
Currently in my own setup. I have all 5 MFDs as 800x600. While it's no space for the buttons, and other stuff at the same time. I might just get a couple of touch screens, and then they will be 16x9s

Sent from my SM-A536B using Tapatalk

[MadKreator]

@MAXsenna I will definitely agree it’s nice having those mfd’s / cdu very large. At least in this aircraft, they’re really the bread and butter of the whole thing. When I was first making parts and only had the mfd’s, cdu and rwr, I was perfectly content. You really don’t NEED much more than that. The only part of the profile that bummed me out was there was no way for me to pull the engine rpm data for startup purposes. I would have liked to have them shown in a text box to know how long to hold the starter switch. My only option was to cut a chunk of the overhead panel to hide when the starters switch was flipped, that would show part of one of the mfd’s. Then requiring someone to have the inst page pulled up on that mfd. But then that would have over complicated things in a few ways if it wasn’t used exactly as I envisioned. So people can either count to 12 or 13 seconds or just look at the mfd in-game lol 

[MadKreator]

@MAXsenna could do a little test when you get some time and see if you have issues with the power levers, either doing a cold start and or while it running? See if the helios controls move through all 6 positions as well as the in game ones moving through each position and the gates? Bluefin says they’re not working right for him as I used a different control than what he did in the toolbox and the one he designed for the Apache.. They seem to work fine for me, not sure why they would be mis-behaving for him.

[MAXsenna]

@MAXsenna could do a little test when you get some time and see if you have issues with the power levers, either doing a cold start and or while it running? See if the helios controls move through all 6 positions as well as the in game ones moving through each position and the gates? Bluefin says they’re not working right for him as I used a different control than what he did in the toolbox and the one he designed for the Apache.. They seem to work fine for me, not sure why they would be mis-behaving for him.

Absolutely! I use my Warthog now, so it'll be a little different I guess!

Sent from my SM-A536B using Tapatalk

[MadKreator]

2 hours ago, MAXsenna said:

Absolutely! I use my Warthog now, so it'll be a little different I guess!

Sent from my SM-A536B using Tapatalk
 

Okay,  I got to the bottom of it. I built my Engine Condition Levers with the special options in game set to " levers move through detent gates". Bluefins originals use the default option of using the detent gates... so if they don't work for you, for now just change the special option to the other one. I'll have to decide whether to remake them to suit the default special setting and do a new profile release, or just add to the notes/ readme that people need to change the special option... neither is ideal lol 

[MAXsenna]

@MadKreator  Aaaaaah! That make sense. Had to change that setting. Didn't work well with the axis on my Warthog. Now it's a perfect smooth operation!
Just need a 3D printer so I can get myself some new detents.

[MadKreator]

16 minutes ago, MAXsenna said:

@MadKreator  Aaaaaah! That make sense. Had to change that setting. Didn't work well with the axis on my Warthog. Now it's a perfect smooth operation!
Just need a 3D printer so I can get myself some new detents.

I’ve had several 3d printers. And now use an “entry level” AnyCubic Kobra 2 Pro, and it just flat out works. Use their slicer, put filament in, run an auto level and get the z offset set and never touch it again, just print. Easiest one I’ve ever used, and goes pretty fast too. -dont use their filament though, it’s garbage lol Creality hyper series prints really nice , so does 3d Solutech brand. ( both are on the cheaper end of the market)

[MadKreator]

17 hours ago, MAXsenna said:

@MadKreator  Aaaaaah! That make sense. Had to change that setting. Didn't work well with the axis on my Warthog. Now it's a perfect smooth operation!
Just need a 3D printer so I can get myself some new detents.

Not that you use the engine levers, but I/we have decided it’s best to change the profile to the levers that use the detent system ( dcs default setting). Bluefin re-made them and they will work with either option. Not going to do a new profile version, just change the one thats there. So all install previous to today will have the “smooth” lever action, needing the change in special options and after I merge the new branch later on, the profile will use detents ( that also match the toolbox control). And I will deal with the flak and explain to people case by case if they have issues

[MAXsenna]

Not that you use the engine levers, but I/we have decided it’s best to change the profile to the levers that use the detent system ( dcs default setting). Bluefin re-made them and they will work with either option. Not going to do a new profile version, just change the one thats there. So all install previous to today will have the “smooth” lever action, needing the change in special options and after I merge the new branch later on, the profile will use detents ( that also match the toolbox control). And I will deal with the flak and explain to people case by case if they have issues

Roger!

Sent from my SM-A536B using Tapatalk

[MadKreator]

*Note about Engine Control Levers added to initial post

[Mikkey]

@MadKreator thanks for the excellent Chinook Helios profile!
I'm using Helios for the first time and all the devices and buttons work fine, but I can't see the image on the MDFs. What am I doing wrong?
Thanks for the advice.

[MAXsenna]

2 hours ago, Mikkey said:

@MadKreator thanks for the excellent Chinook Helios profile!
I'm using Helios for the first time and all the devices and buttons work fine, but I can't see the image on the MDFs. What am I doing wrong?
Thanks for the advice.

Have you saved the profile? Have you installed the patches? Have you selected Helios as your monitor file in DCS settings and set the complete resolution manually, (this is what I always forget to do. ). 

Take a screenshot of your DCS settings first.

Cheers! 

[Mikkey]

Thanks MAXsenna. I have Chinook profile saved and without errors on Interface status page. DCS version is 2.9.8.1214MT and Helios 1.6.6110.0005. In DCS I set Helios as monitor, but I don't know how to set manual resolution and at what values. 

I have three monitors. Monitor 1 I don't use for DCS or Helios, Monitor 2 I use as DCS main monitor and I want use monitor 3 for Helios.

Thanks.

[MAXsenna]

9 hours ago, Mikkey said:

but I don't know how to set manual resolution and at what values. 

In the DCS settings, top row, just punch in 1920x2280. Yeah, I didn't know I could do that myself.  

You have correctly chosen Helios I see. In Helios to correctly write the file. Make sure you have selected both screens, but de-selected screen 3 for the GUI. I'm not at home, or I would have posted a screenshot. 

[Mikkey]

Thanks for your help Max!

I managed to set Helios at least to the state that the right MFD works:). But the left and middle MFD and other displays doesn't show anything. The buttons on them work but they don't show the image on them:(.

In the Helios editor, I have everything green in "Interface status",  the setting in "Monitor setup" is on the picture, and in DCS I have the resolution set to 1920x2280.
What else should I set, or where am I doing something wrong, so that I can see the image on all MDFs?
Thanks.

[MAXsenna]

Hi @Mikkey This is great! You're almost there. By default, RIGHT MFD, is defined in the Chinook already. That's why it works. Seems you have placed all the other displays correctly, and the RIGHT MFD display in correct place. Now, close DCS. In Helios, click profile, add interface, choose "DCS Additional Viewports".

 

Click "Install patches". As you can see, I have already done so. This must be done after EVERY DCS patch!!!! It will then populate all modules you have Helios profiles for, with correct/missing export capabilities.

Click the DCS Monitor Setup tab, and on the bottom right. Click the button that is missing from my screen, and just click ok in the next window. Press "LCtrl+S" to Save the profile, and boot up DCS! Enjoy!

Edited October 12, 2024 by MAXsenna

[MadKreator]

@Mikkey so sorry I just saw this. Your post didn’t ping me for some reason… Everything looks right. But for some reason, like @MAXsenna said, it looks like the “patches” are not installed correctly. In the interface status tab, even if its all green, go to the gear icon by additional viewports and click it to open the tab, then revert them and reinstall. Especially after a DCS update ( I usually revert before updating).. You shouldn’t have to go to the profile menu—>add interface—> dcs additional viewports, that interface should already be in the profile when its installed… ( you can see in the little menu “profile explorer” at the top left which interfaces are already there) .. Also with the patches, it’s a universal setting across helios, you don’t NEED to do it per aircraft. Revert and Install in any profile will do … check in DCS Monitor Setup tab in the chinook profile, at the bottom and make sure the profile is configured in the “Combined” section, in order to use “Helios” as your monitor.( assuming it is as the right mfd worked).

also at the bottom of the DCS monitor setup screen , even if the profile is in “combined” click the - symbols to move it to “separarte” then click the + to move it back to “combined” the click the configure button again if it asks, sometimes its buggy…. Again I’m assuming it wrote the monitor file correctly because the right mfd showed up in the correct spot and in the monitor setup preview all the pink boxed denoting viewport locations are correct… 

I’m with Max.. it looks to be something wrong with the install of the “Patches” in DCS Additional Viewports

Edited October 16, 2024 by MadKreator