osram

Yes. See @Fasu's test and feedback about using my Multiseat SwitchPit on older iPads as well:

Posted Sunday at 02:26 PM (edited) Potential workaround for multiplayer/MFD hotswitching. Thanks to @Fasu's relentless questions and some lovely, dynamic inspiration: At least for people who fly frequently together. When using my, or any switchable Helios Profile. OR possibly worth testing/documenting/sharing a Reshade render-order workaround mentioned by other users. Depending on how long it takes for an ED fix. Now that we talk about it; I haven't tested but should actually work: You could even only "export" one PLT and one CPG viewport in the monitor setup, only commenting out one CPG MFD side. You'd lose an MFD - but you could actually control both with a bit of practice. The partner could do the same but reversed. And then "hotswitching" in multiplayer after resetting the role/aircraft - Would actually be possible, if I'm not mistaken. Even if it meant to only have min. 1 MFD for full functionality. For most things it would actually be two fully functional MFD's. But if PLT for example agrees always to have left mfd PLT and right CPG. And his Co-Pilot friend, the left MFD CPG, and right PLT. It should actually work rather well without dcs restarts - With a bit of "agreements". (edited)

That's the nice thing about simpler/clear profiles or helios profiles in general. The functionality/visual elements are very separated/decoupled. So people can easily edit to their own needs and preferences. The question is for these "micro" time comparisons. Is switching between separate profiles really faster for the MFD issues, i.e. switching MFDs? You would have to load the other profile, re-setup to ensure it regenerates the monitor-setup file, re-save. Maybe even "verify", if it really wrote the file properly? While I keep the profile running - Keep the monitorsetup file open (to save more time if needed or switching more often) it takes me literally 3 seconds to "Ctrl + §" with VS Code two lines, for example. Ctrl + S. And then just start/restart DCS again. Again: The Helios profile and DCS viewports are decoupled. Not even a restart of the running profile is required. IMHO having two separate profiles just didn't feel preferable - Plus it's not only about the MFD's. By switching between PLT/CPG you change the entire "control-layout" and control "target" so to speak. So you can actually decide what to control or see (apart of main MFD's) - when switching seats in multiplayer, and more so hot-switching in singleplayer. You can even "control" the other seats functions without even switching the seat in-game. But simply flicking the switch of the SwitchPit to the other role. In multiplayer people can probably also switch to the "PLT" role rather easily, without restarting DCS or anything. (Maybe?) As I think the PLT in practice is less "MFD" dependent. He usually aims/shoots with his HMD and more visually anyways. Now that we talk about it; I haven't tested but should actually work: You could even only "export" one PLT and one CPG viewport in the monitor setup, only commenting out one CPG MFD side. You'd lose an MFD - but you could actually control both with a bit of practice. The partner could do the same but reversed. And then "hotswitching" in multiplayer after resetting the role/aircraft - Would actually be possible, if I'm not mistaken. Even if it meant to only have min. 1 MFD for full functionality. For most things it would actually be two fully functional MFD's. But if PLT for example agrees always to have left mfd PLT and right CPG. And his Co-Pilot friend, the left MFD CPG, and right PLT. It should actually work rather well without dcs restarts - With a bit of "agreements". See that's the kind of things you don't get when going for the "simpler", separate-profile route. None of us profile creators are happy about the MFD restrictions. We simply make the best of it, for now. Not having flown the Apache to great extent I'm not sure if there is any advantages to that in practice. But it's available. It's especially useful if someone is coaching, for example: The teacher can activate/edit to the MFD's of his student, and see what the student see's - And also take control if needed over his students seat. Had a very nice session that way with moneyshot helping me catch up a bit on the Apache, as a little "Thank You" for my work and time with this profile. And he does a truly excellent job. He's a natural - With deep understanding, calm voice and bringing things across in a clear/logical/technical mindset. You can even see what your partner types into the KU Keyboard Unit Scratchpad - As those MFD's are not affected by the bug/issue and inputs will overlay in transparency. Also - For me it doesn't make much sense to aim for a solution that (hopefully) becomes obsolete once ED fixes the multiseat issues. Afaik they acknowledged bugreports. the issue and I'm pretty sure they understand it's importance. It would mean I'd have to do part of the work twice and again at the end - Changing the entire structure/layout and solve a setup from moving from two separate profiles, to a single one. I am pretty certain, solving these issues as much as possible in a single profile; is the more elegant, intended and cleaner solution. It was nice to learn about panel functionality and panel-switching. There probably will be more panels to switch around separately/hierarchely inside of the two separate PLT/CPG panel "paths" or states, as well. It's kinda cool. And they should stay in their "saved" state no matter where you "panel" or switch... to. I really like it. It also shows neat little/big benefits people probably don't even expect.

You can also copy-paste the devices file into a new Notepad++ file, delete the beginning and all the empty lines. And the line-number will then tell you what device-number it is.

I am very happy to hear things came out well. I am sure the practical experience and feedback will help others save some time and find a good solution going down the same process as well. No need to be embarassed for anything. I was surprised by Helios' rather advanced capabilities as well at the beginning. In the Helios Control Center there is a retrigger "delay" setting in ms when you open it's addition options. Also Windows Touch screen calibration might have a setting by default that "rightclicks" on "long/held" press. IIRC that can interfere as well and I disabled it too, I believe. The "Filter" Pushbutton 4 has a wierd behaviour of not "deactivating" with the first click - it needs to be clicked twice. But seems like a DCS-bug. It happens when clicking with the mouse in cockpit as well. The TEDAC and space question is valid. But in order to use more space for the other MFD's you would have to "scale" those wider than high, non-uniform and stretched. Or lose space at the bottom area. So it's not really feasible or preferable for my design. The area could be used, but additional panel-switching might come... once room runs out. I will opt for a slightly "fresh" way of panel-switching compared to most classic profiles I saw. I believe at least. Also I preferred to keep instruments and things at the bottom, intuitively I guess or as a matter of preference; Touching things further up is farther, less ergonomic than lower area of the screen for my setup. So I guess that also lead into this decision subconsciously. Things grow kinda "dynamically", organically and from preference, taste and experience. I suppose. They can always change depending on functionality and depending where the "flow" goes. I guess it's a technical-design kind of thing. Inspiration and workflows. Current WIP as another sneak-peek. Glad you got things running well to enjoy Helios and DCS!

Hi I'm very new to helios working on a DCS Apache Helios profile that's been released in forums. I've been reading up on a lot about dcs-bios, dcs, helios, generic interfaces, helios lua-interfaces the past 1-2 weeks. trying to get my head around things. I've been wondering if there is any way of somehow getting a rotary switch to work similar to a three-way toggle switch with it's "on-on-mom" functionality. I got it working as desired with a 3-way toggle, i.e. "Off - On - Test" ... a Test position that acts, or should act more like a button with release, than an actual rotary position. I could just use the 3-way-switch and be done with it... but it's more of a question of how far arguments/parameters and maybe even basic aspects of functions can somehow be influenced and handled? Also this specific example also shows in the AH-64D code that "overlapping" {-0.0, 0.0} and {0.0, 1.0} array structures seem to be used to handle/trigger some more exotic states? Not sure if it's related to maybe achieve the result. From what I suspect much of the lua-interface functionality in dcs helios is based on warlords json "api" and work for dcs-flightspanels? he seems to be using a rotary switch for the first two positions, and then a regular pushbutton for the last "test". I don't think that's "compatible" with the basic lua-interface "schematics" I try to accomplish in this specific challenge. it's really challenging to find any examples and information about the "other side" of things. searched through the entire Helios16 git for things like "dcs.common.switch" to no avail. I guess it's due to functionality not really being handled in Helios but rather some other/existing dcsflightplanes or dcs-bios json/conversion, schematic or whatever. Another question is if "arrays" can be "sent/received" from the lua-interface json-interface. It seems like "future hybrid soft interfaces" might provide more of what I'm asking about. But yea afaik that only exists for the F18 so far.

I'm pretty sure I found it here: C:\Games\DCS World OpenBeta\Mods\aircraft\AH-64D\Cockpit\Scripts\AI\PrestonAI_page_common.lua Don't think I saw any more user-friendly/high-level, editable config or anything. Editing/testing is imho certainly not recommended without some basic programming experience and backup is strongly advised. We can try/test and look at it together tomorrow. Just hit me up on discord.

I'm glad to hear you got it mostly running: Another dude just got it running with Spacedesk as well; But it's rather Android I presume. In the "secondary monitor" thingy thread. He's been struggling in general for quite a bit, also due to not using my v. 0.0.4 completely.. for his latest tests. Asked him to possibly write a little guide to share once he "recovers" and has the patience. I speak English, German, French, Spanish... and a little bit Italian. Feel free to hit me up on Discord if you want to look at things over screenshare or voice. No problem, really. I hope you can enjoy. Yes: The CPG/PLT switch is rather essential and switches the whole "view" to the controls of the "other" seat. Can also edit your version or rather show you can at least switch the controls/seat before you start each separate profile. As a workaround, if that helps. PS: Have you tried "dragging" the switches or CPG/PLT switch up/down... with your finger? It's normally not meant to be a touch/click function.

Also: Your last three lines have one extra/obsolete UI = { ... } line? Not sure where that comes from, could be the issue? Try only having these 2 lines instead of the 3. Comparing to my file content. Edit: Yea... v 0.0.4 certainly works better, setup in a cleaner way and it seemed like that generated file was rather off. --- If you have some energy/patience after a while again. Would be interesting for people to know how you setup your spacedesk-app or whatever you use for the monitor-emulation. So other DCS people can enjoy "poorman's" tablet touch as well. Feel free to leave a feedback on the actual TouchPit thread about how (hopefully well) this profile runs despite smaller screen? It should do rather fine comparing to what I remember from more classic/stylized "cockpitish" profiles. I hope you can finally enjoy o/

Hit me up on discord; oze#2672 if you still have issues. it will probably be solved in a couple minutes. Much easier that way. That is a Behringer X-Touch Mini Midi/Audio device btw that can be used to control certain Apps and also DCS. Using python py2vjoy and vjoy midi can be used/converted as regular Joystick, buttons, axis etc. But requires some work and setup. Not done in 5min. but doable in 1-2h. I was wondering why it would take so long for someone to ask It's basically one of the best/cheapest "Sim" controllers for 50-60 bucks translating to dualmode... 2x8 endless encoder-wheels with LED indicators. 2x16 buttons. (momentary or modal)... and 2x+ fader/axis. Something actually no other "dedicated" purchasable sim device can do. at least not that I know of. and certainly not at this quality or price. I could even use the setup to control DCS with something like this. Just a "bit" large and "slightly" cumbersome at 10-12kgs. BUT... it would the one of the most expensive DCS "Joysticks" and rather cool.. for sure.

It's really hard to provide support in E-mail style through a forum. From what I understand you are running spacedesk and try to have 1 windows-monitor and two emulated/exported tablets being used through this helios-profile? Or is that just the idea to have 1 windows monitor + 1 tablet screen? if you want to somehow "split" or redistribute this profile it would have to somehow be done by editing the profile itself. which shouldn't be too much of a problem. but not by default. or maybe only if it's spread across two screens side to side, for example. if they somehow are set to "emulating" one single screen. no idea. the numbers you show me from the file look quite off tbh. here's mine for example with a 2506x1440 main/primary screen ontop of a 1920x1080 touch-screen in windows. you should get correct numbers generated to the file by simply performing a monitor reset AND saving, re-opening, simply ensuring that it sees something is wrong in interface status... for you to reconfig again) - so it can regenerate. however this would have to be performed with the tablet turned on. and also ensured to your solution to provide an actual-windows monitor "emulation". IF... I understood things correctly. Or are those 2-3 regular, fully fledged "windows monitors"? When it comes to tablets. This was never tested with this profile. And is a special setup. Plus you are asking for answers/support in the entirely wrong thread? I also provided my discord ID. if things don't work out. I am happy to test together. But not in E-Mail style for a rather complex topic/application with many unknown variables. i.e. your setup. here my current example with deactivated CPG MFD's. Helios/DCS should internally (Monitor Reset?) treat my example as 2560x1440 + 1920x1080. so a total of 2560x2520. For my screens setup side by side the full area you need to "envision" to calculate.. would be 4480x1440. (a small part is always lost/empty) And IF the bottom screen is the primary, afaik things would have to be possibly shifted using negative X/Y values. not certain. the "safest" is primary left and secondary right according to some more experienced people. but I had it running in all sorts of constellations, left/right and bottom/top with primary/secondary reversed but it can lead to wierd behaviour idd. some also say best to use primary left and secondary right for "best results" - even if it means they define it "wrongly" in windows. (resulting in wierd mouse movement to move across screen borders) - i prefer primary top, secondary bottom. and it works well. depending if you have a setup above or below eachother... or where the the "exported" MFD's should be positioned. using X and Y position. you will understand when you look at my example file. knowing and comparing with my monitor setup I described. normally the center viewport is your main screen. it doesnt need to be touched much, usually and pretty sure it should not be only 1920x1080? unless shifting to a secondary below or right with added X/Y values. dx/dy is only used for special three-monitor setups. where internal 2-monitor setups cannot be handled and extra shifting offset is needed to correctly position. for anything else. I'm happy to help in a discord voice/screenshare session etc. and for future. better in the proper thread ---- _ = function(p) return p end name = _('H_AH64D_Multiseat_SwitchPit') description = 'Generated from Helios Profile AH64D_Multiseat_SwitchPit' AH64_CPG_KU = { x = 720, y = 2080, width = 480, height = 60 } -- AH64_LEFT_CPG_MFD = { x = 80, y = 1520, width = 480, height = 480 } AH64_LEFT_PLT_MFD = { x = 80, y = 1520, width = 480, height = 480 } AH64_PLT_KU = { x = 720, y = 2080, width = 480, height = 60 } -- AH64_RIGHT_CPG_MFD = { x = 1360, y = 1520, width = 480, height = 480 } AH64_RIGHT_PLT_MFD = { x = 1360, y = 1520, width = 480, height = 480 } AH64_TEDAC = { x = 720, y = 1520, width = 480, height = 480 } Viewports = { Center = { x = 0, y = 0, width = 2560, height = 1440, aspect = 1.77777777777778, dx = 0, dy = 0 } } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center

Your monitor setup file generated by the profile Editor should be: H_AH64D_Multiseat_SwitchPit.lua when using "separate" DCS monitor setup mode. Also that name needs to be used in DCS system/video settings. The lua monitor file should also contain AH64_Left/RightPLT/CPG_MFD etc. entries. for the TEDAC and KU as well. Is that the case?

I wanted to shout out a big thank you for Bunny Clark's hard work! I only started diving into the creator's side of DCS Helios around 1-2 weeks ago and the AH-64D is my first Helios profile. Even though I started with Capt Zeen's Generic Interface, which helped me learn some basics, I had to migrate to Bunny's interface due to 200 Pushbutton-Limit and two-seater multiplayer. His interface also helped me understand some new/unexposed parameters and arguments. And with the switch to lua-interface and more research I got to learn more dependencies and workflows. So I added/extended the NVS switch data, as well as switching around some on and off states as my mode-selector buttons were already in the "opposite" positions from the generic way of things. I hope it doesn't look bad netiquette or a shameless plug. But all of these profiles stem from our current MFD-render challenge and interface, be that bunny's lua or another: Thank you once again for your hard work and accelerating our progress along the way. I am sure preferences and tastes differ in the user-base for all sorts of profiles and directions. The more the better. I hope this additional, more visual/streamlined flavour of a Helios-Profile. Plus the detailed installation explanations and handling, dcs-update, helios-profile-update etc. described in the readme.pdf of my helios profile release. Also somewhat give something back to the community. Should the direct topic-link bother anyone - Let me know and I'll remove the link. The whole MFD, and manual-profile handling and best practices are explained in full detail. Even if you happen to not try or use my profile. Maybe read up on the readme at least. It should explain everything. Please note that my version of Bunny's Lua interface JSON is slightly modified and not interchangeable. (Just in case) Changelog: v 0.0.4 - Extended LUA interface and profile with NVS switch - Added IHADSS PLT Video Panel - Added Master Warn/Caution Indicator/Push-Lights for PLT & CPG - Added Armaments Panel for PLT & CPG - Implemented transparency and cut-out panels for custom background color and reduced contrast/eye-strain Coming soon: INT/EXT Lights panel, CMWS panel, COMMS panel etc. What to do after a DCS-Update? Usually you only need to re-copy/replace the MFD init files in instruction step 1.4. What to do after TouchPit Update from 0.0.2 onwards? Preferably ignore or delete as v 0.0.3 onwards uses a separate profile and lua-interface without “mods” file and folder. What to do after TouchPit Update from 0.0.3 onwards? Just re-copy/replace your new DCS.AH-64D.hif.json: Helios_AH-64D_Multiseat_SwitchPit_v_0.0.X\patch_files\interfaces\DCS.AH-64D.hif.json to: C:\Users\YOURUSERNAME\Documents\Helios\Interfaces and re-copy/replace your new: Helios_AH-64D_Multiseat_SwitchPit_v_0.0.X\patch_files\profile\AH64D_Multiseat_SwitchPit.hpf to: C:\Users\YOURUSERNAME\Documents\Helios\Profiles\AH64D_Multiseat_SwitchPit.hpf Don’t forget to re-open/re-save in Helios Editor and complete pending configs and setups. As usual all of these instructions can also be found in the current readme provided. Enjoy!

Yes sitting in these profiles and then as lovely "climax" in dependencies/updates and thinking through the actual install-instructions after hours of learning and solving little problems... I felt like I had missed one part to better explain. This should now be mentioned and emphasized with detailed explanations and a screenshot. I really hope you didn't lose too much time @Fasu! My apologies for that. I'm not sure if the Touch-Input over Duet you mention are profile are Helios related. Duet is Apple/iOS specific. My feeling or limited recollection somehow tells me it might be caused by iOS "security" restrictions. At least that's what I would google/research for to get more insight or exclude, possibly. Also a test with "Spacedesk" and an actual Android output device might at least partially "exclude" the cause being Helios/Profile. If possible? Even if obviously the setups, config and "flow" is two completely separate things and not necessarily indicative. I was running DCS Helios Spacedesk to cheapo Android Huawei P30 Lite for sure around 6-9 months ago. IIRC low-end Samsung Galaxy tablets as well. Complete with visible MFD's, Touch-Functionality, very decent/acceptable latency and everything. (Samsung Galaxy Tab A7 (2020) (4G, 10.40 ", 32 GB, Dark Gray)) Actually this very profile at least for touch-control and visual-feedback on proper "hand-eye-coordination" should perform surprisingly well due it's usability and spacing-focused, simplistic design. (Even if bigger MFD output advantage is always desired) Try any Android device with Spacedesk. -> No matter how small. Even if it's just a test. If you have any technical issues or questions in that regard you want to share in a co-op session. Hit me up on discord tomorrow and we can take a look. (If you tried everything else thoroughly and feel it could help) For today however I've had enough of sitting in Helios. You lads have a good one. Lemme know how v 0.0.4 looks and feels to you in practice. Edit: Chrischan's point is also very valid. The disconnect, or loss of touch-issue happens a lot on non-dedicated, not fully fledged touch-displays. Even a portable, battery-supported AOC 16T2 (1920 x 1080 Pixels, 15.60 ") with it's annoying and crappy USB-C/HDMI and touch-disconnects, for example.

Multitouch Switchpit v 0.0.4 has been released! (File, SwitchPit or DCS-Update instructions in initial Topic-Post) Changelog: v 0.0.4 - Extended LUA interface and profile with NVS switch - Added IHADSS PLT Video Panel - Added Master Warn/Caution Indicator/Push-Lights for PLT & CPG - Added Armaments Panel for PLT & CPG - Implemented transparency and cut-out panels for custom background color and reduced contrast/eye-strain

Multitouch Switchpit v 0.0.3 has been released! (File in initial Topic-Post) NOW with full keyboard unit and complete Multiplayer support. (Additional testing & feedback still welcome) Changelog: v 0.0.3 - Migrated the profile to more modern and robust LUA interface -(Enables simpler installation, management and running green/yellow) - Removes pushbuttons limits and enables full multiplayer support - Added Keyboard Unit Coming soon: Additional Cockpit controls/elements

Thank you very much: I am happy if people enjoy a very streamlined and comfortable, usability/clarity-focused profile. Will probably see to migrate to newer "lua-interface" based workflow soon. With this kind of modern and multiseat module the current, internal 200-pushbutton limit is actually exceeded: Especially in multiplayer. Only started more intensive and focused endeavours into Helios profile creation about a week ago: After the leveraged button-limit I will finish off the keypad-unit and the other most important or desired cockpit-controls. Should be coming soonish, I presume. The rough/"slow" start and getting to know things in Helios should hopefully be over the peak now. current WIP sneak-peek:

You sure it's not just the module/vehicle name missing in "HeliosExport16.lua"? i.e. No actual connection in the Helios setup? Or did you confirm that iPad/Duet simply does not support "touch" somehow? Would be interesting for others who have iOS over Android to try.

Thank You Correct: a 24" Viewsonic touch-screen. But can also be useful for people to just have on a regular, secondary screen. (For enlarged MFD views, without straining our necks on track-ir and zoom so much. or maybe mouse-controls etc.) You should try Helios. It's amazing. It can be linked via WLAN or in some apps even on USB, if your device has "true" USB-C hdmi/video out. Or just network tethering? My first attempts with Helios and touch-screen tests were running successfully on a tiny Huawei P30 Lite. Also on some Samsung Galaxy tablets. Might even be able to split two helios/dcs-monitor tablets onto two separate tablets, side by side. By editing an existing profile and moving things around. There's only a handful of apps to "mirror" your windows/helios screen via WLAN etc. Don't quite remember the names, but you should be able to google and get it running with basic tech-experience. One popular one is "duet" afaik. The other one working well for me was involving to run a "server". To connect to via your Android... From a security POV and management thereof I didn't like it too much. But for a gaming machine it worked very well. Edit: Went to check - The one I tested rather successfully was "Spacedesk". Needs to be an App that emulates actual Windows "Display Output", IMHO. So that your Android is basically an extra "Windows Monitor". Not the usual stream- and casting stuff. No warranties etc. given. Wouldn't recommend leaving those apps running/installed on sensitive/critical work-machines or so. IMHO the bigger the better for DCS helios as a screen, or preferably touch screen. I'm not sure if Apple/iOS is favourable: IIRC they disabled some of the screen "streaming" stuff for "security" reasons. The usual stuff; I'd try on Android, tbh.

Still flying the Apache or other modules with "clickediclick" mouse-clicking in your cockpit? I'll be honest with you: Can't fly DCS without Helios touch anymore. Try out oze's AH-64D profile! And Helios in general! You will LOVE it! I proudly present my very first DCS Helios Touch-Profile for the DCS AH-64D Apache. This profile will easily save you at least 335+ keybindings/functions and provide proper hand-eye-coordination, visual control and feedback. Please read/follow detailed instructions in the readme.pdf provided. Based and extended on Bunny Clark’s AH-64D LUA interface 04.04.2022 Profile Version: 0.0.5 DCS Version: 2.7.11.21408 2.7.11.22041 Helios Version: 1.6.5200.0001 30.03.2022 Profile Version: 0.0.4 DCS Version: 2.7.11.21408 2.7.11.22041 Helios Version: 1.6.5200.0001 20.03.2022 Profile Version: 0.0.3 DCS Version: 2.7.11.21408 Helios Version: 1.6.5200.0001 (v 0.0.2 was based and extended on Capt Zeen’s generic interface) Sources: http://captzeen.com/helios/index.asp http://captzeen.com/helios/creating_helios_profiles/#/ https://forum.dcs.world/topic/286561-apache-profile-using-helios-for-a-second-monitor/ Created by: oze (oze#2672 on Discord) No distribution without consent Feedback and suggestions are welcome For help/support and Helios Discord community: https://github.com/HeliosVirtualCockpit/Helios/wiki/Get-Help Capt Zeen's Profile Support Discord https://discord.gg/S63KqxC Special thanks to <3: Bluefinma, CaptZeen, derammo for Helios, it’s extension and interfaces Sobe and wheelchock for answers, daily community-help and moral support Bunny Clark for exposing the AH-64D arguments/functions in his lua interface Known Issues: - TEDAC “Filter” Pushbutton B4 requires to be clicked twice for deactivation (Probably DCS-internal bug) - Slight Ghosting/Duplication of in-game Cockpit TEDAC display due to viewport-exports (DCS-internal bug) - KU Keyboard Unit brightness control knob controls both CPG/PLT (Probably DCS-internal bug) - DCS multiseat modules currently do not support positioning the PLT/CPG MFD’s on the same X/Y position: - Rotor Brake “lock” is apparently not yet implemented and was therefore disabled in the profile as well. Refer to step 1.7 to switch the MFDs between PLT and CPG with a quick file-edit and DCS-restart. Controlling all PLT/CPG elements is switchable with the PLT/CPG switch and works globally without edit/restart within this one profile. Changelog: v. 0.0.5 - Added Wipers for PLT/CPG (very important) - Added CMWS for PLT - Added Open/Close canopy for PLT/CPG - Added Ext Lights for PLT and Int Lights for PLT/CPG - Added switch/toggle-panel functionality and Engine section for PLT - Added EUFD for PLT/CPG v 0.0.4 - Extended LUA interface and profile with NVS switch - Added IHADSS PLT Video Panel - Added Master Warn/Caution Indicator/Push-Lights for PLT & CPG - Added Armaments Panel for PLT & CPG - Implemented transparency and cut-out panels for custom background color and reduced contrast/eye-strain v 0.0.3 Migrated the profile to more modern and robust LUA interface - (Enables simpler installation, management and running green/yellow) - Removes pushbuttons limits and enables full multiplayer support - Added Keyboard Unit Coming "soon" (won't be rushing this one): COMMs panel, FIRE Extinguish Panel, Jettison What to do after a DCS-Update? Usually you only need to re-copy/replace the MFD init files in instruction step 1.4. What to do after TouchPit Update from 0.0.2 onwards? Preferably ignore or delete as v 0.0.3 onwards uses a separate profile and lua-interface without “mods” file and folder. What to do after TouchPit Update from 0.0.3 onwards? Just re-copy/replace your new DCS.AH-64D.hif.json: Helios_AH-64D_Multiseat_SwitchPit_v_0.0.X\patch_files\interfaces\DCS.AH-64D.hif.json to: C:\Users\YOURUSERNAME\Documents\Helios\Interfaces and re-copy/replace your new: Helios_AH-64D_Multiseat_SwitchPit_v_0.0.X\patch_files\profile\AH64D_Multiseat_SwitchPit.hpf to: C:\Users\YOURUSERNAME\Documents\Helios\Profiles\AH64D_Multiseat_SwitchPit.hpf Don’t forget to re-open/re-save in Helios Editor and complete pending configs and setups. As usual all of these instructions can also be found in the current readme provided. What to do to Update to 0.0.5? Follow previous indications where applicable, redo Step 1.2 and steps indicated after 1.4.1 or just replace/reinstall all indicated installation files. (Might be easier/simpler) Enjoy! ---------- Make sure to check out @Devrim's amazing monitor to touch display conversion and upgrade path! Well done. It is a new, very economic path to provide touch functionality to your old, used or spare standard monitor. Potential testing/workarounds/instructions and feedback for switchable PLT/CPG MFD's of this profile via potential "Reshade" render-order (search on forums) is welcome and will be included and obviously accredited if anyone wants to contribute. Helios_AH-64D_Multiseat_SwitchPit_v_0.0.5.zip

http://www.co-optimus.com/ http://www.destructoid.com/

uhm... so... where are those drawings? i dont see anything.. anywhere within this thread.

that grumann would be an amazing 2-seat CAS alternative to a ka-52 we will never see. other than that i would say: su 25 t would be amazing when fully modelled. amazing firepower, FLIR... SEAD.... 16 vikhrs. yay!

funny how this got moved to: ED Forums » English » Reality » Chit-Chat » DCS World or Helicopter World makes no sense at all.

Well. I'm glad some people like Pharao, and actually many of my DCS friends, see the problem with unfitting types of aircraft... ... Others apparently don't. Even though it is perfectly obvious that flying or buying modules someone dislikes is not mandatory. Resources and time still had to be "wasted" on the creation thereof. It's kinda cool to fly around with some historical stuff for enthusiasts, sure. Even I bought the P-51, just to support ED (Like many other modules, actually). Nevertheless I don't see how it helps the general fun and scenario within multiplayer though. It's simply out of scope. Cannot be integrated in a nice, modern multiplayer map, i.e. "battlefield scenario". There is no need to "defend" your beloved historical aircraft. I like that kind of aircraft too... I just believe those should not be the main focus. Many people are just waiting, barely playing DCS... hanging out. In hopes of a new modern aircraft to pop up in order to have some fresh multiplayer stuff to get into with their friends and online-buddies. And it is critical to be modern aircraft. What good is it to have a couple of P-51 dogfighting with some FW190 on specialized multiplayer servers. If many others are actually waiting to finally get back into the full scale modern battlefield with new modern content/modules? As Pharaoh stated before: I believe it is absolutely critical for ED to take steps in the right direction. The direction can only be things which contribute to the already amazing modern battlefield stuff. In order to have that full mp-immersion, with all sorts of modern.. competitive aircraft. Even flying a KA-50 or SU-25T at low speed/altitude to sneak through the threatening dogfights going on above, in order to reach and destroy the next targets on the subsequent waypoint is so much fun. With a bit of luck you actually have some teamplay, teamspeak and fighters covering your rear in order to win the mission. Throw in some CA-commander stuff in there.. and Voila. You have an amazing MP-experience. Even on a non-coop map. That's what DCS is and should be about. What good is it to make a couple extra bucks with the sale of WW2-content, if the active playerbase to be seen on servers actually shrinks? For my part I will be holding back on "charity" module purchases, unless we are actually seeing modules which help the modern era multiplayer problem. And actually contribute to that part of DCS. Contribute to it's core: Modern PVP or Coop multiplayer. I know that within my own community many people have a similar attitude and dissatisfaction at the moment. Once the multiplayer improved, we can start looking at the sidedishes and extravaganza. Vegetables. Stuff like WW2 content or random aircraft which have no real role or "place" in larger multiplayer scenarios. Just to reiterate: I'm not against that kind of aircraft. I just hope that ED is mainly focusing on modern content in the near future. Since, imho, only that kind of content will have a true impact on increasing multiplayer fun. That's what a game should be about. Simulator or not. Fun & Multiplayer.