MadKreator

I’ve never got it to work either.. but I always have the tgp as soi so mavericks slave to to with china-fwd-long… Does the space stabilize only work with HUD as soi, I wonder?

Was having some issues yesterday too, they bore sight fine, but the new parallax thing is throwing me for a loop.. I boresighted on ground, targeted something about 6 miles away, ( as recommended to now try to bore sight 3+nm if possible) but when up in the air and lock something with the t-pod, manual handoff, the mavericks slave, but aren’t close to the point of the t-pod at all. Probably 1/2mile offset down and to the left, every time. Is boresighting on the ground the issue as opposed to in-flight? I tried several times yesterday, even re-boresighting in the air but to no avail. I should note I was using mav-h’s.. I did not try d’s, I usually only use d’s at night. Contrary to most I really like(ed) the TV mavs, they have been good up until recently it seems with the changes to boresighting. I will try to get a couple tracks together today, maybe someone can see something I’m doing wrong, although I’m doing everything the way I have always done in the past. —— never mind, It was me.. I wasn’t switching the mavs to PRE.. It definitely doesn’t work boresighting in VIS I’m a little rusty in the 16

Honestly for just mfd viewports, helios may be overkill. It can do that, sure, but is really designed more for exporting lots of viewports and touchscreen controls, gauges etc. Like the picture.. The George thing I would put in the same category as the kneeboard. Just lack of support, or care about Multi-displays. With the added 600 pixel height, dcs isn’t smart enough to know that that extra space below the main screen shouldn’t have anything rendered on it except mfd’s The game displays fine, where its suppose to but overlays seem to not speak the same language. Kneeboard not so bad since you can click and drag it but I can see George being quite frustrating, not being able to use it correctly. I have a whole set of other quirks and dumb issues using an ultrawide monitor, that shouldn’t be there

Yes it will break the Pure scripts required, like on hoggit. It basically edits the monitor setup and viewport export for you, but does it the same way as manually editing the files. MP seems to still have the bug where even if you pass IC but then back out of a server, then your IC fails. Same hopping from SP then into multiplayer too(seemed to happen when pure scripts was implemented, might be liked somehow)….besides the point… Helios will pass a server with Pure clients, but not pure scripts unfortunately. Hoggit was always my go-to relaxing MP and since I started using helios and the pure scripts was added I can no longer play on hoggit.. but I find myself on grayflag or flashpoint the most these days. TTI or 4ya if I want to chill and relax on MP. Your monitor.lua looks right to me. It seems DCS doesn’t seem to play nice with all monitor setups. I’ve seen other posts similar to yours. It would be nice if ED someday would really up the support for exports, mullti-monitor, widescreens etc. fumbling through code to get a built in function to work hardly seems like anything the consumer should have to do l

Ever given Helios a shot? It wont solve the George ai deal ( all multi monitor users probably suffer from it and the kneeboard being huge and half off the screen) because of the added height from the mfd’s, but it may be a bit easier to handle the monitors. Plus you can add the controls on screen to your mfd’s too if you want. Join Captnzeen discord for any help and support, there’s no great manuals for it, but its easy to setup once you know how( myself or the current helios developer will gladly help you through setup) There is an Apache profile too by the helios dev, so your mfd viewports and controls etc will be drag and drop to wherever you like them. Just a thought. DCS likes to funky things when you have a monitor arrangement it doesn’t agree with

I do both currently, save each profile and then copy the user input file from saved games to a second location. I lost all my map points on 4 aircraft one time… just once!… redundancy

Snap views and and view saving in general, don’t save the zoom level ever. Just re-centers. The reason I recommend the view zoom in/out slow on the hotas when you get it you can edit one of the game files to change the default fov(which gets overwritten each update) , but as of now there isn’t another way to save the default FOV where you want it unfortunately.

Would be nice when mapping controls and you “save profile” if it would save all controls for all your devices, instead of having to save each device/ column individually. Unless there is a way to do that already and I completely missed it

Number 5 on the number pad goes back to default view.. when you get the winwing setup, I highly recommend using two buttons or two directions on a hat and map them to “ view zoom in slow” and “view zoom out slow” didn’t know if you noticed in the controls setup there is a whole section named “hotas” thats basically a grouped list of everything that should/ would be good to, go on the stick and throttle… some things you don’t necessarily need( like MIDS 1 and 2). You still have to go through the pain of what really needs mapped but that section shows you about evening that should be in quick reach.. I will post you a screenshot of my hotas section if you want , just to give you an idea. Shipping is outrageous, I was going to order a new radio control plane the other day, until I got to shipping and it wad $190 plus a $60 “container offset fee”… for a balsa wood/ carbon fiber airframe that was USA domestic rate from GA to ID lol Once you get the controls mapped, click on each section, stick, throttle,keyboard, etc and save profile for each.. it wont save the entire profile, only each column individually, so name them accordingly just in case it gets wiped out

Most likely, but I will say, unless you have that exact stick, I wouldn’t worry too much about how the exact aircraft hotas is.. Use it for a starting point and as you progress your knowledge and find the things that are most important for you to have on there, don’t be afraid to change them up. I have a vkb stick that is not a replica of anything, just a stick with lots of buttons, so I try to have the same round-about functions in the same locations for each aircraft, just so its a bit more natural. It can take a longtime during the learning process to figure out what things are most important to access quickly. For the hornet, radar cursor/tdc, TGP controls( fov and zoom) , weapon firing, cage/uncage, trim, countermeasures, a/a weapon select, nws/undesignate, radar elevation are some of the most important functions imo. Gear, flaps, master arm, a/a, a/g mode, general controls are better left off. Speed brake is one that is common on hotas setups for adjusting speed quicker, but it something you could leave to a keybind to make room for more important things especially when starting out. When you become a more aggressive dog fighter, you may find the speed brake to be something you want to have quickly available. There’s tons of you tube videos on the hornet, the training missions are very lacking on most aircraft. They’ll give a quick rundown but there’s much more to learn about each system. Your first module in dcs is a long process. Full of fumbling, and cussing frustration and button mashing lol Once you get it down though its a great feeling! And most of the concepts apply to other aircraft. Your second, third, fourth module will be much easier to get the hang of( aside from your brain learning new controls). You can always make one button ( or more) on your hotas a modifier( like holding shift, ctrl, alt) so you can have many more functions. Setup all your controls for main weapons deployment and target searching, use a modifier with each for other aircraft functions as you see fit. Maybe your trim hat switch can be modified to also be your missile select hat too. Or your nws/ undesignate, can double as cage/uncage for mavericks etc etc

Trying to not sound terribly ignorant, but what is MAC? Never heard of it.

Does it break IC doing it in individual aircraft? I do similar to remove the on screen mfd’s in the viewporthandling.lua.. it will do it for all aircraft but breaks ic right away in MP

Most use SRS Radio plugin. Some servers use Discord. I don’t think I’ve seen any public ones use the built in VOIP

Oh I just zoomed in… use either * or / on the keyboard number pad.. or like i do with an extra hat on my throttle, bind “view zoom in/ out slow” in the view section of controls. It wont save the position when you restart unless you modify some .lua files, thats why I put it on a hat, so I can change it wherever I want on the fly

Not quite sure what you mean. Can you post a screenshot? Or PM me on the Captnzeen discord and we cam run through it.

I just have a quest2, I don’t do much vr but the civil sim I like to play only in vr, I will turn on dlss and try different resolutions, I never really messed with it. I would be more than content if DLSS just got rid of the shimmering objects in DCS. In 2d or VR, but I’m not sure it works like that (if it replaces anti-aliasing).

I had a similar experience in that civil sim, DLSS may have performed slightly better, but the visuals on gauges and things were much worse than running with dlss off with TAA. In 2d it was not as big of a factor. I think DLSS with be great for the right system but maybe not for everyone. Time will tell.

That was my first thought as well. We will have to wait and see, but I’m keeping my fingers crossed!

Awesome, thank you! We’ve been fighting it for days lol I had no idea about a hard limit in the GPU. This is kind of what we were thinking, that somewhere its exceeding a max allowed resolution but didn’t know where. When he dropped the res down to 7680x1440 and re-centered in the monitor setup manually, the blank area split evenly between both sides of the monitor.. yes he was losing 880 pixels exactly.

I believe dlss was just stated as coming later this year. My best guess would be MT-new game engine -dlss-Vulkan- DC. But what do I know lol

I like this idea +1

About all you can do in dcs to feel faster is zoom the view out to a wider fov, or fly in vr, it always feels faster imo since you have that depth perception… or just fly closer to the ground

Trying to help someone in the helios discord, he had triples setup 3x 27” monitors, running just fine. Changed the center monitor out to a 34” and now even though helios is calculating the total size correctly, when he runs dcs it cuts off about 15-20% of the farthest right screen.. Any had any issues with running triples with a different sized center monitor? I’m kind of at a loss. ( the pixel count differences don’t seem to match up to what is being cutoff visually) monitors are 2x 2560x1440 and 1x 3440x1440

If they do, I would suspect it wouldn’t be until the new game engine is out, and possibly DLSS and Vulkan implementation. DCS really needs those core updates before anything changes graphics wise, however it would be a nice option to have it supported for those that can use it.

Just hopped on with my quest 2 for the fun of it (I only play in pancake usually). Previous to the recent patch, and after I got my 4080, it stayed pegged at 90 fps 9-10ms frametime even playing some a-10 missions ( nothing really heavy). Didn’t change one setting and now my fps is all over the place, even in free flight on caucuses, it bounces all over from 90 to 60, to 75, to 45, to 53, to 80 etc etc. even on fresh restart of pc and headset. About 3 minutes of that was enough to put the headset back in the drawer for another 6 months…pancake it is!