osram

@OldRavenNL For "all-inclusive" use, including comfortable MFD-display my recommendation for this purchase or upgrade is: Go as big and with the highest quality you can asap. Don't be like me and "upgrade" from unit to unit multiple times to still not be happy. Obviously touch, control, feedback. Is already amazing - But the last comfort/benefit is enough size to have those MFD's on the touch be your one and only. What I DON'T recommend at all are "portable"/notebook extension monitors at all. For this application things like the AOC 16T2 (1920 x 1080 Pixels, 15.60 ") are really BAD. Only 6 bit colour (awful!), the battery/hdmi/usb-c design will lead to frequent disconnects. Could have sworn some fella in here ordered a Hannspree? But who knows, maybe I can't even use a search-function anymore. Actually that size would have been acceptable as a very bare "minimum". Just the technical limitations/quality made it a no-go for helios and MFD's. But still; BIGGER is BETTER. In this case, for sure Viewsonics have nice, flexible angle-stands that can be compacted strongly for limited-space or "inverted" use. (Mine is cushioned and resting on it's top edge... while the stand is fully bound together and retracted, to fit under the top, main Viewsonic) I don't think any other Touch-Brand with often bulky or rigid stands, would have made this possible on such limited space. Using my extra 2-3 "tray" standing "desk" extension. Viewsonic Elite XG270QG (2560 x 1440 Pixels, 27 ") over an Viewsonic TD2455 (24", Full HD) Neomounts by Newstar @Goblin 1-1 What do you mean by BRT controls not "working" specifically? The Helios' profile "turn" function? Or can you turn the knobs in cockpit and/or helios but you don't see any results? I've been theorizing briefly about the possibility of a helios interface having an interruptive effect on actual cockpit functionality. It's actually possible, but would have to be almost "intentional" or with a very erratic implementation. I believe. Haven't noticed any comparable issues when using the profile so far. Please note that usually touch-screens at least have lower brightness and dynamics - so it can be different "ranges" you end up using to "calibrate" desired BRT, contrast, levels etc. There's usually a difference between in-game cockpit MPD image "dynamics" and exported ones. Potentially even missing "optimizations" regarding viewport exports and "brightness" etc on the DCS end. So depending on devices, quite a few things can play into it. Especially for the Apache in my experience; the "BRT" function of Left and Right MFD are extremely marginal. Even in-cockpit, you actually have to look real close to notice any difference from max. to min. What has a much larger influence/effect is the actual "VID" button. Even when it's not necessarily about "Video" display in the selected MFD. Also all knobs use the new "radial-precise" control method implemented with 1.6 I believe. You drag the radial "out" and turn it around with held, sweeping motion. Enables slightly "different" angles to be used on the fly, somewhat. And they just feel more precise and way faster than the classic modes. Should the output device or OS have issues with that type of control; They can easily be customized oneself in the right-hand properties panel, changing the "input-type" from "radial-precise" for each knob to your own prefernece or something more classic, then saving the profile in the Editor and restarting/starting it in the control center. Do they "turn" correctly or at all in both directions? DCS ◄ ► Helios. If you truly have "input/output" problems I'd be surprised. Unless you modified/edited the profile in some way. Are you using the hif.json lua-interface that came with my zip? The current one? Should that kind of issue be going on probably better to hit me up on discord so we can look into it. oze#2672

Thank you for your update. Albeit a rather disappointing one. I think internally the TEDAC continues to be rendered anyways IIRC. Initially my Helios profile had the TEDAC "uncovered". Don't think it was "frozen" either, might be wrong. But pretty sure I had TEDAC display while hot-switching from CPG to PLT seat. The KU and EUFD can render as transparent "overlays" at the same X/Y location. But that's just because they are simpler text "types"... and not really with 3D rendered capabilities like the usual MFD's/Video, I presume. I also suspect I'm having quite annoying Controller-Setup file corruption issues or so: My Store/Update function has worked at some point, but seems completely broken now. No matter if NAV/ATK phase etc. Doesn't seem to be reported much, i.e. quite rare and intermittent - But that's for another topic. Hot-Reloading/Switching MFD's for multiplayer/SP on exported viewports really should be a necessity IMHO. Thousands of people are sitting in their cockpits, zooming and goose-necking in super-unhealthy and uncomfortable body positions. Maybe sounds a bit exaggerated, but with modern MFD-focused modules... ED should actually recognize and promote/support the potential of things like Helios. It's ergonomics, interactivity and comfort. You can basically get a digitized "simpit" with comparable haptics and accessibility; At the fraction of money and time - of an actual simpit. With a 5-10 minute install - In most cases. Until VR matures in terms of Gear/Performance including haptic interaction or gloves, which will most certainly take at least a few long years to come. Can't even buy a properly convincing VR product that satisfies in terms of price, controllers, fov/display/resolution, comfort/usability, audio/glasses in it's current state. Let alone the required hardware. - This "path" and potential is the best bet, for sure.

Seemed like a promising resolution. I tried it out, however rather works for more classic modules, I suppose. Multiseat or i.e. AH-64D probably somewhat works differently, possibly with 1-2 extra "layers" and functionalities. Tried adding the init files to all sorts of "screenspaces" disabling general for both the PLT MFD's for example - while editing the viewporthandling for general and inside cockpit in multiple variations as well. All to no avail.

That's an interesting option I haven't heard about yet @Devrim- Let us know how it turns out. Obviously. Multiseat TouchPit is the one and only. The only way! @OldRavenNLWelcome to the darrrrrkkk... side! I hope you're enjoying the cozy shadows. I haven't tried much with this yet. But afaik an option might be to disable the in-game cockpit-rendering entirely. If things don't "work" in unexpected ways. It should have a positive effect to at least not cost too many extra fps. @ChrischanSince you have quite a noticeable difference - Would also be a good occasion to test and let other people know. Maybe following these indications. (As usual I'd always backup any files before testing and editing)

I might be mistaken but sounds like you do not use PLT and CPG MFD's on the same X/Y position and monitor. So this is not exactly what this actual issue is about. When trying to use the same X/Y position I'm pretty certain just renaming the PLT MFD's is not enough. As the CPG ones always take priority with their default/internal names. Hence they need to be renamed uniquely as well. In order to be disabled selectively/manually, to become manageable via commenting/uncommenting at least. I find the fastest way is to just leave the corresponding monitor-setup file open in VS-Code for example (or whatever the Notepad++ Shortcut/Equivalent is...) Just click + "Ctrl + §" (European) to comment/uncomment those lines, Ctrl + S. And start/restart DCS again. Literally takes like 3 seconds. No need to restart Helios profiles, for people who use mine, Bunny's or anyone else's. Those two are rather decoupled as well. Pretty sure that's faster, more "ergonomic" AND safer over renaming/overwriting or moving actual files around. Especially as multiple files with the same internal DCS/module name (inside) can lead to multiple, identical entries with the same name in DCS system/video "profile" select. Certainly not recommended for the average user. Nor is to usually what anyone would want to "manage". I just move BAKs/Copies away into a separate folder, if needed. Anyone up to snuff with the AH-64D bug reports etc.? Like are you sure ED is not aware of this issue. Or that a bug or hopefully WIP/planned feature/resolution is not currently planned by ED? Not even on the F14? Is ED even aware... like what's the status?

WD on the write-up. @Bunny Clark Couldn't bother anymore tbh after all the variations/guides we both attempted to try and explain. Hopefully with this it becomes more concise and clear. Just adding my own monitor-setup (with different names and setup to Bunny's - do not "combine" or "mix"), as a practical/visual example. This below is the only way you can have the PLT MFD's ACTIVE/Displayed - When you want both PLT and CPG MFD's located/defined at the same X and Y position of your screen, GUISE. By commenting out your CPG MFD-names and restarting DCS. (After following Bunny's exaplanations file/viewport modifications, obviously) As indicated by Bunny - Currently DCS multiseat issue. This will not enable you to hot-switch MFD's while changing seats or anything. Just to get the selection of PLT vs. CPG under your control. Rather surprised it's not acknowledged by ED. No feature planned etc.? Thought heard something bout F14 hot-switching planned? No? -.-

I just wanted to thank you @Asto and confirm that this fix finally works for a 2560x2550 total resolution with my helios profile running on the secondary/second and lower 1920x1080 touch-screen. Below a 2560x1440, windows-primary monitor also correctly setup the way described. I've told Sobe a couple hours before you that he's missing GU_MAIN_VIEWPORT, but he didn't catch my discord-PM after we briefly looked into this. Sobe... Sobe... Sobe. Tststs. Had been manually/fiddling and trying around inside the function and also inside "non-VR only" before. The positioning off center with the X/Y and -1 to 1 grid is clear as well. I could only get things moving when running primary screen only. And IIRC not from directly changing the compass/weap positions from inside the function, but at the "non-VR only". Had suspected some difference potentially between what's called "Additional Viewports" in Helios, and it's (potential) DCS-equivalent. (Possibly) Basically two monitor-setup ways and differences leading through the viewports function, and another one that does not. Maybe also combined vs. "separate" MonitorSetup - In Helios terms. But I wouldn't know, maybe that's just a Helios thing. And has no equivalent in DCS. But ye - Rather hard to "diagnose" with other's descriptions without sight. Or often not seeing the resulting changes/position oneself despite trying. With the second screen covered with the DCS export.

Also keep in mind that the "zoom/fov" selected defines your slew-speed. Regarding your cursor/slew keeping moving - I noticed yesterday since I can finally fly the Apache a bit - That using modifier shift-keys or Hotas-Buttons to multiply a mini-stick to/from HOCAS cursor or slew/track the cursor keeps slewing unless the mini-stick is fully released before releasing the modifier key. And probably also the "other way round" for the other functions, if modified in different order. I think the modifier key can also "interfere" with and interrupt the hocas-cursor or track-slew input in other ways I think I haven't noticed in other modules and not sure are reported. Or maybe I noticed the second issue and is a virpil-thing, but not the first so far I believe. At least using a Virpil Mongoose CM3. Yet again in other modules we don't often have double-assigned/shift-modified mfd-cursors and regular slewing. I suppose, so it's hard to say. IIRC also be careful about first and second detent for weapon fire and lasing; I think they are somewhat "reversed" for their "safety/override/yolo" function. i.e. like only 1st detent laser being the one that does not require correct parameters, while it's 2nd detent for the weapons release. (or the other way round) Correction: For the LHG weapon and LRFD trigger second detent as CPG I have set Second Detent for both. And those are most certainly the "yolo" versions, as I didn't have any issues since. However IIRC I think those had issues when being modified as well. Also ensure that your LMC, linear motion compensator (?) function is not accidentally enabled/disabled. When on you will see short, perpendicular lines at the end of the cross: That one will certainly keep moving even if you release your mini-stick-input. By design.

Haven't watched the replay. But just in case - Sure it's not the "other" MFD's just being "frozen" from sitting in the wrong seat and missing a visual refresh/update? Especially when it's "not doing it all the time..." Then it's somewhat "expected" behaviour in the sense of current MFD/Viewport PLT/CPG exports.

And want to know what the biggest irony is in all of this? Has to be the "irony-banger" of 2022, I guess. I literally out of curiosity - Just clicked your profile/post-history... and randomly clicked somewhere inside. And there you go: Exactly that specific problem and Question by @Leg2ion- Once again. But within the A10-C-II. Instead of AH-64-D. Exactly same problem. In Multi-Displays. Once again. Awesome! It couldn't get any better. PS: if you need further explanations and handling instructions. Activate signatures, Click my Signature, Download my Profile-ZIP. It's all explained for you there - In full detail. And most certainly in that and many more "sibling" threads. Exactly THAT was the topic at hand. Topics and Issues that were explained in full/detail countless times... Being explained and answered once again. Just in a different "folder" and "category" so to speak. Because of overlapping topics, splliting or merging things where they maybe shouldn't. Or maybe some sort of "pin" with cleaned-up, concise explanations/mini-FAQ for people about the most frequent issues/question, or some other alleviation might help. You're the perfect, personified example as suspected; and yet didn't even notice what the problem is. But opted to talk down to people repeatedly answering exactly your kind of questions. Awesome You sir, truly made my day. Nevertheless - I'd smile, have a small laugh WITH you and have a little pint with you, IRL if we happened to stumble into eachother. Alright? Toning down even subtle/indirect negativities/provocations can truly help wonders. And sometimes as for myself, maybe it's not even meant that way or by purpose. I know, m8. You have a good one.

Oh we got a really funny and mature one here. It is about the repeated questions lately since myself and others got rather involved with Helios, DCS, Multi-Displays and Viewport exports for the AH-64D. Even created detailed explanations and handling-recommendations for some of the core MFD export and multi-display issues atm. (Also helping people outside of forums) I don't really count hours, but that's aside of providing a fully-fledged and tested touch-profile for the DCS community with at least 100+ hours in about two+ weeks due to learning and first-time use. So that people people can fly the AH64 in an (imho) actually playable/enjoyable manner. Without cockpit-clickery. Almost off the very first few days. What have you provided for the community so far? Other than talking irrelevant things and engaging with people in a rather negative manner. Due to your own, potential weaknesses and insecurities, maybe? This was a perfectly valid thought and question, on a rather basic, structural and "technological", typical 'knowledgebase' and 'userbase' level. Maybe I could have worded the question more diplomatically or in a better way? Yes. But at least I tried with a few edits. But I guess you fail to captivate that entirely or prefer to make it childish, off-topic and personal, for some reason: What you mention is never what I truly intended, seriously hinted at or the core part of the question and topic. Or maybe you have personal issues with things like "empathy". Right? Did you somehow feel addressed? That statement is perfectly correct nowadays: People who work in tech, if not most branches notice that kind of problem since quite a "few" years. Might be that you are quite a perfect example. Somehow. If you approach random people with pure negativity and mockery. Expect some direct responses. Even if it's just "Online". Think about that for a second or two. Or don't. Whichever you prefer; Really.

That makes sense. Thank you for your reply, transparency and work, BN. Have a good one

No offense. It seems like it's a new category. How is this different enough from "controllers" and "profiles"? Can I post my Helios profile in here as well now, or some of us answer questions and "maintain" it in two 'main-categories' now? After all: It's a "Multi-Display" profile? We will probably get the same or "different" same questions about Multimonitor, PLT/CPG-MFD-Export-Issues etc. in two different main-categories now. Should we answer them in parallel here as well? I don't mean to offend anyone. Really - Just think "categories" and "structures" are a very delicate thing and often not even possible to do right when trying one's best at the very start - while also having the information/knowledge that changed over "time". One, or rather multiple people can repeatedly explain over multiple threads from different POVs and in different words. In PDF, or .docx or whatever fancy colours and formatting, or even in black-and-white - about the current issues with PLT/CPG "Multi-Display" exports. It still seems to not help enough for some. People even looking forward to "Youtube Videos" of the issue, nowadays. For an issue that should easily be explained in TXT - Or at least resolved... in a Text-Editor. It's the CURSE of modern tech and civilization. Communication, empathy, time, trust and patience are at an all-time LOW. While complexity, challenges and confusion are HIGHER than ever before. The new "Multi-Display" Category really doesn't help here; Imho without meaning to offend anyone. Merge into "Controllers/Profiles/Display"? Maybe? Or maybe someone can provide insight or different viewpoint/argument. I know it's never exactly "easy", sometimes not even possible to solve everything perfectly.

v. 0.0.5 has been released! (File-Download, SwitchPit or DCS-Update instructions in initial Topic-Post or included installation readme) 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

I understand the situation or reasoning. But I don't think that's the problem, tbh. Unless someone maybe didn't properly calibrate, has a hw-issue or different firmware-version, possibly. I have the exactly same CM3 without any deadzones whatsoever and I'm pretty sure it works as described. But maybe I'm wrong about the "regular", intended functionality and design entirely. Would probably help to check how the mfd-switch via cursor is supposed to work exactly. No time to check the manual or wags videos here again though.

I'm not quite sure why I put myself through these wierd things no one else probably would care about.. but I just can't stop. send HALP! Haven't looked into other profiles at all, actually. But I'm pretty sure this will become one of the most sophisticated covered, lit APU-pushbuttons in Helios history. (maybe?) it features multi-layered transparency and is truly decoupled/functional with underlying helios txt labels. and all of this to flick a little cover up and down, and have a little button light or unlight. I'm even forced to make a bad visual design decision in order to justify all of this work - and move the APU txt unnaturally close to the cover-button so maybe a handful of people notice the cover-lid transparency cutout, and some APU txt pixels "shine" through. (Apologies in advance)

I'm not an expert on the exact behaviour on cursor/screen switching in the AH-64D. But I have the CM3 as well. Someone mentioned to "press twice" for cursor-handled screen-switching. What they probably rather meant is "release and re-input", imho. But it seems to work normally. I'm not sure why you'd normally have to deadzone any VKB or virpil gear. In most cases it sits deadcenter, no need to calibrate. At like 12 to 15/16 bit resolution. The one thing I noticed though, I believe "modifier keys" can somehow interfere with the CM3 mousestick. Even if they are not used/pressed but defined for other "layers". Even momentary ones. They will make the ministick movement "interrupt". That's some possibility I'd exclude for sure. In any case with regular VKB/Virpil firmware calibration that is setup once... you can just move the cursor to the MFD-edge. Release the cursor/stick and push to the edge again... and switch MFD's that way. At least I thought that's the way it's meant to work.

You probably just need to perform a "file ► monitor reset" in the helios editor and ensure warnings/reds in monitor setup interface (interface status) get reconfigured using each interface's respective cog-wheel. also the DCS monitor/video system settings require to have the same "monitor setup" file generated by the profile. Preferably "separate", not combined. that's what I test against. And delete "extra" copies of monitor-setup files as they can create problems and multiple entries in DCS system settings. All of this should be mentioned in installation instructions; if more complicated/time-intensive issues remain - hit me up on discord. I can't just "make" the MFD's bigger. as with physical limits making them bigger will require some sort of extra space that has to be taken somewhere else. However the profile should be more or less editable "easily". At least with some explanation, maybe. So since I'm currently still finishing the regular desktop version, I can sadly not do these "mobile" or two-tablet modifications myself. (if they are even possible) But if you are going for it, and want to clean it up, i.e. document (if needed) and share. (Whenever or IF you ever feel like it ) Just an idea. Also any other sensible alternative/Version or preference is possible. Yes - But I can't do them all. They have to come from the community/users. More than happy though to assist so they can be brought back into my main profile thread (with credits obviously) so others can profit. Take your time

current fully functional wip sneak-peek:

We all gotta benefit from opportunities right? Yeah I know how it can be - Take it easy, bud. Taking care of oneself with appropriate/serious measures should usually help. The profile would probably have to be split into two "monitors" to export onto two separate ipads, I suppose. Haven't tried. But should be doable looking at the profile and trying stuff out. Feel free to hit me up and/or follow up with guides/results or an actual split-up profile within the TouchPit thread should you be somewhat patient/technical. I don't mind helping/co-operating for such an idea. Obviously only if that's something you'd enjoy - and only when fully recovered., obviously Just a thought. Get well soon, m8 - And enjoy the profile once done.

All good m8. It's basically a DCS viewport-export issue. Helios folks are just some of the more affected and involved with this right now.

All of this was discussed to it's fullest extent in at least two threads; I even created detailed explanations about the issue and handling in the installation instructions of my AH-64D helios profile. It's a missing DCS feature for multiseat or bug. Whichever you prefer. From what I saw there might be ways defining render-order with reshade mentioned by others. But yea, didn't have time to test or use it myself. Nor is that much of a problem; Even if hot-switching the MFD's would be nice. Vanilla you need to use new, unique names and comment out, i.e. disable the CPG MFD's as they will always be rendered by "default" otherwise. Current WIP sneak-peek:

Very happy to hear you enjoy It's a pleasure. Me alegra oir que puedan disfrutar. Es un placer. This time I'm trying to actually complete most "essential" or rather the "core" components of the cockpit for PLT and CPG for the next release, so people and myself don't need to update for smaller increments - I simply released these last versions quickly so people could actually fly with the essentials in an enjoyable way. EXT Lights for the PLT is finished. EUFD should be finished for PLT/CPG soon. Pilot CMWS is semi-done, but a bit more work required to manually extend to the lua interface. I'd like Engine controls in as well for the next release. Not sure if I forgot anything. Think that's about it atm. Shouldn't take forever, but still needs a bit of time. Hard to say. Coming soon (TM) I guess.

Just a quick "aggregation" of @hreich's test/feedback with Spacedesk on Android in another thread: ----- Just a quick guide-ish post for using tablet for second 1920*1080 touch screen...After setting up everything per guide from this post: ". I am using free space desk app from this post https://www.spacedesk.net/ to have my tablet act as second screen on which i see extracted MFDs and using tablet for button presses..Because small-ish 10" size of tablet, buttons are kind-a-small but it's a good poor's man panel with different helios profiles for different modules in dcs...Its working quite good, and if your tablet is fast you can get fine results..All the setup in spacedesk is automatic, you only have to install server version on pc, and one client version on your tablet...Then after launching and entering ip address of your pc on tablet app, your screen will automatically change to two screen setup...