MadKreator

I will add to this, that it wont break multiplayer IC, but it will get erased with updates so its best to use it with ovgme.. good thing with notepad++ is it will keep all the files you modified open, so if you don’t use ovgme, and it gets reset, its pretty quick to hop back in and redo the adjustments. I did that for a good 2 years before I messed with ovgme and figured out how to use it.

Just started using Helios. Everything is great so far, its awesome! Just curious what people are using for poll rate (how often Helios sends info to the export.lua) default is 30 times per second.What does this actually do.. Ive tried up to 180 and don’t notice any difference. I was trying to get rid of the gauges being kinda jittery. Is that just the way Helios is? Is it because of the difference in frame rates? ( main monitor is 120HZ, I average in the 80-90 range in dcs, but the Helios touchscreen is only 60hz).

I have exactly the same issue and couldn't find a solution. I've kind of learned to live with it, but it is a little frustrating. Hitman got it.. bind the zoom keys/ buttons to the right mpcd button 3 and button 4

Oh hey that’s a good idea! I will delete those bindings for “tgp view zoom” and bind the osb keys to the hotas instead and give it a shot! —update : that works perfectly! Exactly what I was looking for! Never thought of that, I guess I assumed the tpod view zoom function/keybind would be a mirror of the mpcd buttons. I suppose it wouldn’t hurt to have both mapped so you could have slow and fast zoom

I feel the same, autostart is a bit drawn out in the harrier. I learned too manual start it and its pretty simple actually, cuts the time down for sure, but id rather just hit auto lol

Track IR and Quest 2 work just fine on mine

I have exactly the same issue and couldn't find a solution. I've kind of learned to live with it, but it is a little frustrating. Yup I’ve learned to just deal with it as well, but it is kind of a bummer.

Been flying the harrier for the last couple months, love it! But.. for some reason when I zoom the TGP in and out when I tap the button for either, it zoom in like 6x then almost all the way in.. no matter how fast I click each button it acts like I’m holding the button down. No issues in any other aircraft, all mapped to the same buttons for zoom. Is there a zoom rate/ sensitivity in the av8b I’m missing? Anyone else have the same issue? I’ve tried other buttons but it doesn't seem to matter, I tap zoom and it just starts going.. sometime a little bit, sometimes it will zoom almost all the way in with one button press.

Ran into the same today, I was testing Helios on a larger monitor and the exported displays were all flickering.. same solution, I had vsync on fast response in nvidia for vr and sure enough, I turned it off and the flickering stopped! What is odd is that when it was turned on, when I ran Helios on my small external mfd monitor they didn’t flicker, only on the larger screen..

No issues at all here, with intel cpu, nvidia gpu. Win 11 has worked fine since release for me.

You can move it by editing a .lua file.. I have a single 49” ultra wide screen and have mine moved over so its within my view mid-screen. I made a post about it several months ago and someone responded with correct way to modify it…. Well I’m too dumb to figure out how to link it but I made the post Feb 24th of this year under View System Bugs forum section: titled “Comms Menu, move location on screen…semi solved”. ( still on the first page near the bottom) Halfway down the thread , member “ draconus” had the correct format for the .lua. Must be exactly like his format, with the number 500 repesenting how many pixels you want to offset it. You can see the file that needs edited in the screenshot I posted in the beginning. as for the OP, there may not be an easy way to move all of those to a different screen all together, if even possible.. I think dcs expects them to be part of the main “ center” screen. Although it may work the way I did the comms menu, but you would need to find the correct .lua file(s) and try it out.

3080, intel cpu, win 11, graphics drivers always the newest available and never had an issue here

Just tried Helios for the first time on my small display I use for my external mfd’s. Took a couple minutes of fiddling to get it going, but not too hard. It is awesome, that is all! Now to find a decent 24-27” touchscreen to mount under my main display Didn’t notice one bit of performance drop.( I’m sure a 1080 or 1440 monitor will ding a few fps) but all in all pretty impressive! I average in the 75-100 range on a 5120x1440, running re-shade, an external mfd monitor, track IR and most all graphics on high/ extreme, and dcs-ufc app on tablet so there’s room to spare. —tested with a non touchscreen 1920x1080 monitor and noticed no performance drop at all. mfd’s are plenty large on a 24” screen, not really sure why I didn’t try this years ago lol

In this forum section the first pinned post is the guide to do so. Follow it to the letter. Its not difficult but worth reading through the whole guide once or twice before following it

I ran a #50 and #30 on mine with 200mm extension. Tried the hard center cams and didn’t care much for them. I ended up shortening the 200mm extension and then machining a couple of my own and actually settled on about 65mm for my preferred sweet spot, with #30 singles on each axis. The 200mm with the two springs on each axis still felt really soft but I always had issues with the extension staying tight enough to the base. It would always loosen up and you could hear the springs rubbing, even with the rubber tubing around them. Since dropping down to the short extension I still feel like there is still plenty of throw in the stick ( I didn’t care for it with no extension), but haven had any connection issues since, no noise, nothing. Just silky smooth like it should be with soft center cams and just enough tension on the dampeners so when I pull the stick to full deflection and let go it gets back to center and stops without the stick bouncing back and forth a bunch. I did end up going through the whole base and found a few screws that weren’t as tight as they should be, just some food for thought if you hear and clunking or clicking noises. The gunfighter base should be dead silent.

Hmm.Now I’m really curious. Makes me want to hook up my 4th monitor like that just to see what it does LOL

I don’t play in VR a lot but I have the WW Orion f-18 throttle and have no issues using it in vr. muscle memory is there with it so finding the right switches isn’t much issue. I think whatever you choose it will take some getting used to, but you may find the added benefit of having all the extra buttons on the Orion useful. However if you fly helis a lot, the gemini may be the way to go. Or get the handle upgrade later on. The f-18 Orion throttle is on sale now for $235 USD.

Just out of curiosity, why not just use them the way they work? Or do you use them for things other that dcs, where the display order makes a difference? Nothing wrong with trying different ways, of course, but if it works they way you have it setup in the first picture , why not stick with it?. I have mine stacked below my main screen with the left edge aligned on all three and it works.. IDK maybe DCS doesn't like that big open space between for some reasonAlso if you’re including monitor #2 in your total dimensions then the top of it will be the (y0) so your center screen will need to be offset down from that as its actual x,y starting point. So maybe try your center with x=0, y=480. Then add another 480 to your mfd y axes. Also make sure dcs is set to windowed mode in options( in case fullscreen was re-checked for some reason). even though you’re not using screen 2, maybe its playing hell with DCS since its in the windows monitor setup. Maybe you have to still compensate for it. In dcs maybe the total screen res needs to be 4520x2944 in the main options to get the correct aspect ratio as it is in windows

I see both sides of the argument as valid. But its hard to please everyone, that’s for sure. Maybe when these things are announced it might be good to tell all what stage the module is actually currently in, in development. Are basic renderings done, any flight systems, anything? Same for maps. That gives no promise of release date , but can give many some needed/wanted information, instead of being in the dark completely. Yes there’s a few photos attached to most and a teaser video maybe, but a line or two of “ we have this and this done currently” can go a long ways. Problems arise, just like with anything. The Apache got delayed for several months even when ED was confident enough to show a release date. Which for me was fine. But for some maybe not so much. I’m sure they got their share of backlash when something wasn’t delivered exactly when said. Realistically, depending on the size of dev team, at least a year or two would be my best guess before any actual release on any of these new announcements ( although SA/Falklands seemed to come fairly quickly, maybe I’m getting old and just losing track of time ) I wish it was sooner. Like hey this is just announced for release next month. Instead of a tease that causes endless pissing matches, then fizzles out with the occasional sarcastic comment about it here and there over the next, who knows how long ie. dynamic campaign, Vulkan, multi-core. We all want them, and we want them bad, but would we have been better off not knowing these things were in the works? Possibly

Half of my problem with speed was my track ir lateral movement is set too low so i can’t lean far enough to see all of the switches around the throttle and radio, ils and tacan controls lol I just had someone’s custom knee board pages installed a long time ago thats happen to have the procedure so i figured why not give it a go. I may map the needed switches to a page on the stream deck, then I can just burn through it. Or like you suggested, make a couple macros to do multiple things quickly

So for the hell of it last night I figured I’d learn the a-10 startup… well, that was about as easy as it gets lol took all of three attempts to memorize the things that need done, using a knee board checklist for reference. I can have most everything on and running before a fast ins alignment is done. As soon as the right engine is fully running and engine start light goes off, there’s only 5 more switches or so to switch and its ready to go. Of course startup still cuts into my planning/ load out time.. but it really is easy and actually a little bit fun

Just wondering if you’ve turned off full screen mode. When I did my multi monitor for external mfd’s part of the guide says to un check fullscreen mode. May not be necessary for 3 screen as the main view. And that the resolution in the main options is set so its the total width of all three in pixels and height of the tallest one? 2560x1440 + (2x)1680x1050 would be 5920x1440 in the monitor size in the main options.. just a couple ideas if you haven’t done those already. I know when I setup my external mfds, dcs was finicky about what order I selected the options. Otherwise It would make the displays all crazy and unuseavle until everything was set correctly. Wonder if its freaking out because the monitors are different sizes? note: I haven’t setup 3 monitors as main screens, only for mfd’s …just a couple ideas.

I don’t play in VR all that much, but I use a no name brand cable from amazon that says “Quest Link Compatible”. It is usb c on both ends and only tests around 2.8 as well, even though it says up to 5 gigs. Oculus software seems to thing that’s sufficient. I don’t seem to have any issues really until I crank the graphics and resolution up to high for the quest 2 to handle. Then it just sits there and does nothing. Also using windows 11.

+1

So I have external mfd’s setup now, but problem was there before I did that as well. The aspect auto configured when I manually entered the total screen size. Before this monitor I had an msi 3440x1440 widescreen and don’t remember ever having to mess with it until i got the 5120x1440.. possibly just a weird quirk with the ultra-wide. Maybe I will hook the 3440x1440 back up one of these days and see if there is a difference. I don’t mind having to edit it to be right, especially since I figured out how to use ovgme to just turn it on and off. I’ve been using the 49” monitor for 2 years now, so It doesn’t bother me. Every other graphic in the game is crisp and clear, just the HUD’s look like they’re from 1999 if I don’t modify them lol I’ll bet its just an issue with 32:9 aspect, since its not a very common size for people to run. on another note: if anyone reads this and is having the same issue, I’m happy to share my .lua settings for the 18,16 and av8b