SrSosio

Hello there. I'm having issues exporting the MPDs. I can export them fine with two separate monitor configs that I created with Helios, but I can't get a config to switch between PLT and CPG. See attached my config file. I always get the CPG seat, regardless of where am I seated, it doesn't switch with me. BTW, is it still required to replace those files in the zip file mentioned in the first post? I just did it just in case, cause I hadn't done it until now, but the result is the same. Apache.lua

Nope, now it only loads the CPG screens, for some reason, when I switch seats, nothing happens. See attached my helios.lua file Helios.lua

I think that may be my problem. I set this profiles a while ago and I don't remember how I did it, but I believe I can have all the modules in one file, instead of a file for each module, but I don't remember how to revert back to just using the Helios.lua profile file. I have this. I don't remember how to move my profiles to Combined: I'll keep trying Nevermind. I moved them to combined. I'll re-test now

Hi. I have a couple of Apache MPDs that I built, with two working LCDs. I created two different Helios profiles for the Pilot and the CPG. My expectation would be, from what I've seen Helios can do, to be able to switch from one another just changing the profile in the Helios Control Center, but I must be doing something wrong, because it's not working for me. I have these two profiles in the Monitor config in the setup: and they work normally if I select them from that dropdown list, but every time you switch from one another, it restarts the game. The Helios control center seems to not be able to change the profile in game. What am I doing wrong?

Hey, I don't know if this has been reported already, I hope I don't duplicate topics, but I have Apache MPDs with LCD screens. Find attached the monitor config I use to export the viewports. I've found a couple of issues with them, one general, the other, only happeing when the viewports are being exported: The general one is that I have the DAY/NT/MONO knob bound to a rotary switch, and although the mapping looks fine in the controls screen, and physically rotating it does have the desired action in the screen, the game knob doesn't actually move and it stays wherever it is. The export one, that works normally when I'm not exporting the viewports, but doesn't when I am is that the brightness knobs don't have any effect on the bright of the text, only on the background image (if you are in the TSD screen, for instance). Also, it only affects the brightness of the game screen, but doesn't do anything to my actual screens. The VID knob works fine both in the game and the actual screen. I'm not sure if this is something that is captured in a track file, but find it attached too, just in case. Thank you H_DCSAH64PLT.lua LastMissionTrack.trk

I don't think it's a bug, they just changed the AI situational awareness in the last patch. They can now see you through buildings.

So I used to have a lot of fun in combined arms, driving around in strykers, bradleys and lavs, killing and capturing zones. Unfortunately that is no longer possible thanks to AI vehicles seeing you through buildings and shooting at you the moment you show a leg around the corner. I hope this was not done on purpose and will be fix in a near patch. If it was done in purpose and there are no plans to adjust it, you've ruined it for me, and I think it would be unfair, considering it's a paid module.

You're way too nice John. I hope you enjoy them.

Finally found the problem. At some point I might have tried to place the stick backwards or something, but the female connector in the base was recessed and therefore not plugging in when I screwed the stick in the base. I've tested it and it works.

Thank you Hempstead. I actually just noticed this in my device manager under HID devices: So I think the base is actually ok. It may be the stick what's wrong, since I had a Winwing adaptor and when I reinstalled the original TM cable, I might have pinched or not properly plugged it. I'll re-check it and let you know.

I know it has been a while since this last reply, but I recently tried this and faced another issue: I have a monitor setup that consists in a main FHD monitor (1920x1080) and two small 1280x960 monitors below, so total resolution is 2560x2040. If I do the above the mouse in the main screen doesn't reach the top right half of the screen, so I can't even click on any of the menu options (instant action, campaign, etc...). Since the resolution of the 3 screens kinda has the shape of an L, it would seem as if that determined where the mouse can move around.

Can anyone at least confirm if the base should be detected without stick? I think it should, but a confirmation would be appreciated.

Hi Jarhead. That's in my mid term plans. Unfortunately time is scarce for me lately, since I just became a parent. But do not hesitate to contact me for ad-hoc help.

I tried that, but then something weird is happening. Looks like the resolution is preventing me from reaching some parts of the screen with my mouse. My screen setup for this test is like this but without screen 4: And in the main menu, looks like that's driving where the mouse can move, so I can reach the exit link in the right bottom corner, but not the instant action one in the top right.

Thank you both. Sorry I didn't reply earlier, I didn't receive a notification of the replies. I'll try that and let you know if it worked. I'm using a Pico 4, btw.

Hi. I have a TM WH and a WW Orion, and to be able to switch them easily, I modified both the base of the stick and the throttle to have a USB type B female in the front in the fashion of the WW ones. It worked perfectly fine since it's a very easy and straightforward mod. However, recently I changed my gaming setup and wanted to replace the type b females for type c. The throttle works perfectly fine, but I don't know if I accidentally bridged something in the stick, but now it's not recognized in windows. I would like to ask if anyone knows or is willing to test something for me before I try to troubleshoot the control board: - is the base recognized by windows if the stick is not attached (that should be easy to test by anyone who owns one). I assume it is, but I want to make sure I can test it without the stick. - a bit more complex one: is the control board recognized if I completely remove it from the base, just leaving the usb and the board connected? I need to check if there are shorted caps or burnt components, and if I replace any of them, it'll be easier if I can test it without having to put it all back together. Thank you

Hi everyone. I have 2 apache MPCDs with lcds on them. That makes 3 screens (including the main monitor). I have the monitor config properly working when I load the game in 2D, the mpcds are properly exported. However, if I load the game in VR, they are not exported. My intention is to fly in VR and use reality mixer to see through my googles for the irl mpcds. Does anyone know what am I doing wrong? Thank you

I'm selling my own DIY Apache collective in almost perfect condition. The only minor issue is the nose attitude switch gets stuck a bit in the up position and you have to help it back to center, but it doesn't impact the game experience at all. Gearbox and shaft are aluminum, the grip is 3D printed. Although it is very nice and perfectly working, you can still notice it's a DIY 3D printed project, so don't expect plastic injection mold finish. Jettison and chop covers will be included (not installed in the pictures), but only in white PLA. You can paint them yourself if you wish. Counterweight not included unless you pick it up, for obvious reasons. Email me at mpavillard@gmail.com for inquiries. It's better than PMs, as I don't always get notified. Shipping from Spain. Selling it for 150€ + shipping

Hi. I just assembled the sim seat in the subject and added my winwing throttle to it with the provided hardware. However, I would like to be able to quickly/easily remove it to use a different input, say a collective, for example. Does anyone know if there is already a solution for that, whether it's an off the shelf one or a DIY one?

I tested joining a CPG seat directly and it didn't work either.

Ok, got it to work a bit better, but still need some more help: I've separated the two output files and with that I've managed to load the pilot's screens properly. I do need to change the monitor setup in DCS every time I want to switch from one to the other (and therefore restart the game), but I think I can live with that. If I switch to the CPG monitor profile in DCS, I need to restart, but the mfcds display the cpg's ones as expected, even when the mission loads you to the pilot's seat. However, I now have the issue that the TEDAC monitor does not show up. This is how the CPG monitor setup looks like (remember, TEDAC is on screen 4): And this is the CPG profile: _ = function(p) return p end name = _('H_DCSAH64CPG') description = 'Generated from Helios Profile DCS AH64 CPG' AH_64D_LEFT_MFCD_CPG = { x = 0, y = 1080, width = 1280, height = 960 } AH_64D_RIGHT_MFCD_CPG = { x = 1282, y = 1080, width = 1280, height = 960 } AH_64D_TEDAC = { x = 2048, y = 0, width = 768, height = 768 } Viewports = { Center = { x = 0, y = 0, width = 1920, height = 1080, aspect = 1.77777777777778, dx = 0, dy = 0 } } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center Do you think if I join in directly as a CPG role (in a MP server, for instance) it will properly display? I'm not sure if I can test this right now as I would require another player on the pilot's seat. I'll see if I can ask someone.

Resolutions are ok, I think. And yes, the cpg viewports are first in the file. I'll paste the contents of the file later when I get back home. I'll also test doing separate profiles instead of combined. I'll let you know the results of the different tests. Thanks for the help

Sorry, it's a bit complex to explain and I think I didn't do a very good job in my first post. I'll try to be more concise: Monitor 4 is the TEDAC display. The one you can see in my desk. It's a diy device I built. I want to be able to unplug it and store it away leaving only the main monitor and the two mfcds (also diy devices with screens) when I just want to to fly pilot. Even if I don't remove the TEDAC, I set up two profiles, but when loading a mission, which as you can see in the picture (not the screenshots), loads in the pilot's seat, but the mfcds loaded in my screens are the cpg's. I think I may need to not combine profiles if I want to be able to remove one of the screens Regards

Hello there. I just downloaded Helios as I have a setup like the one attached, but I'm having problems getting it to work properly. I created two profiles for the apache, one for the pilot, one for the CPG. The pilot one looks like this: Screen 2 and 3 are the left and right MFCDs respectively, and screen 4 is the TEDAC. As you can see, screen 4 is not used in the 4th screen for the PLT profile, but it is in the CPG profile, as I want to be able to remove the TEDAC when I'm flying as a pilot (I mean fully remove it, so the monitor configuration in that case would change). In any case, I save it like that, but when I load a mission, it starts by default with the CPG MFCDs even if I'm in the pilot seat (see attached picture), and I'm pretty sure I'm in the PLT profile because the 4th screen doesn't turn on. So I'm getting part of the two profiles. CPG profile looks like this: Also I'm getting this message all the time, both in the editor and the control center, which I don't know what means: What am I doing wrong? and how do I use the Helios Control Center? Do I need to keep it open all the time? should I be able to switch profiles without closing the game?

Selling a DIY Apache TEDAC and MPDs that I built for someone who wanted for VR, so it has no backlight nor LCDs, but the buttons are all fully functional. The person don't want them anymore (at least for now), so if I find a buyer for them and afterwards he wants them I'll build more. MPDs are 1:1 (approximately) in size, the TEDAC is just a close enough to play replica. The size of the screen is approximately 6.4" x 6.4" I am aware that there is only one picture of the TEDAC and it's not very clear, but I have it packed and I would rather not to un pack it if it's not absolutely required. If you want to see more pictures and the build process, you can see it here: Ah 64d Tedac The MPDs have some of the buttons with marks in order to be able to identify where you are just by feel. We can discuss about LCD versions, as I build them myself, but I would have to build them from scratch and time is not something I have a lot lately, so expect some lead time delivery. If you are interested in pricing, I strongly recommend you contact me via email, since for some reason I don't always receive notifications from the forum and if you PM me, it may go unnoticed for a while: mpavillard@gmail.com Shipping from Spain