Deezle

I ordered mine probably within the first twelve hours, no tracking info yet.

With your system specs (namely your GPU and RAM), it's really hard to suggest going with higher resolution monitors. That said, I had inexpensive BenQ 1080p 27" triple monitors and I thought they were quite nice for the money and their bezels were really thin, but the triple screen setup and I have parted ways, and I've since gone with a single Ultrawide.

The default T0/T1/TV mappings are a bit wonky, this has been discussed since release. It really depends what type of switch(s) you're using. The default mapping for 3 position switches is intended for use with a 3 position switch where the center position is off (such as the boat switch on a WH throttle). This will not work with a 2 stage trigger, because when the trigger isn't pressed, it will default to the T1 position. And the other mapping option is for use with three separate buttons, one for each function. In the custom key mapping thread there are solutions posted for this. I really recommend everyone learn how to create custom keybinds in the .lua files, it adds great flexibility to the sim.

Sure thing. https://forums.eagle.ru/showthread.php?t=182373

Ongoing thread here https://forums.eagle.ru/showthread.php?t=180092 It works ahead and behind but if you're beaming the launcher I never get a warning.

Slow operation of the knob when bound has already been discussed, the devs seemed to be open to changing it.

I do notice TIR head movement seems a little smoother at 60+ FPS than lower levels, but never enough to bother me. My TIR doesn't work worth a damn if it's plugged into a USB hub though, tracking drops out constantly, regardless of settings, works fine plugged directly into my mobo.

I too had the washer (it's not really an o-ring) pop out after about 15 months of use. I'm luck enough to have some teflon sheet at work and a laser engraver. Really turns the WH into a smooth stick.

My previous setup was indeed 5760x1080, I know all about editing the view LUAs to get 160 degree max FOV. I think you've completely misunderstood what the slider tuning does. It's adjusting your "default" FOV to where you want it in the middle of your axis's range, so you can quickly move your zoom lever back to it's center position and get it back to where you like it, so you don't get any jitter from the pot by not being in the center. Near as I can tell, that's exactly what you want, however you keep dismissing it. The above picture of my rig is with 20min/160max FOV and my zoom slider in the middle detent, you can clearly see it's not zoomed in to 70 degree FOV. You don't *have* to limit your min FOV to get the middle of your zoom axis to an ideal FOV.

It's completely possible if he's talking about a toggle switch that holds an input when left on. It's basically how mine is set up, but for the first detent of my trigger. I can't remember if it was a default binding or one I made.

You can save the sanctimonious attitude for another time and place. The *only* time you *need* to modify the luas is for single viewport triple monitor setups to increase the max FOV beyond what they allow, as 140º is not enough. If all you want to do is change the default FOV to a value that's available from the stock luas, the slider tune method is a completely valid way to do that and many people are happy with it. If you *prefer* to do it another way, good for you, but it doesn't make you better than me.

I don't care what the math says, it works, and it works fine. If you want to reduce your ability to see enemies by reducing your min FOV to 110º, that's your boggle, everyone else wants that zoom. And this.

Are you using windows scaling? That was throwing off my Ikarus profiles.

Play and see if 16 is enough, in 2.0 multiplayer, I'd frequently max out my 16gb, it's even worse if you attempt to move vehicles with combined arms which causes a RAM leak and will eventually use all of my 32gb as well.

Shilkas are easy. I'd rather deal with those from 1.5nm than get within .7nm to kill a tank.

Perhaps because you use the triple viewport instead of a single viewport. Except for the Mi8 with it's FOV slider option, I had to take the FOV to 160 for all the other modules, default is 140 IIRC, and was certainly not wide enough. I do agree with you though, all modules should have an FOV slider like the Mi8. You can get around the integrity check by adding the view info for each aircraft to the server.lua file, but often servers are running missions that force you to use the server side server.lua (and often the host has no idea they're doing it) and it disables your mod. It's one of the reasons I went to a single ultrawide, triple monitors sucks online since the integrity check. A proper view like this was not possible with the default FOV all the way zoomed out.

People with three monitors. Do this, adjust it so the default position is where you like it. No lua editing required.

This seems to be reasonably accurate.

Unless the devs change something or make a separate viewport for export only that doesn't dance around with head movement, it's simply not going to work properly.

Ended up making a set of quick and dirty combat pedals for mine anyways. Not nearly as nice as Milan's concept but they're okay, and I could still buy his when they finally come out. Ignore the schmutz around the pedals, rudder pedals are a magnet for lint/detritus.

TrackIR aiming seems to be totally screwed up, and I notice the special option for it is missing. It sounds like there's a keybind for it now? Hadn't noticed that. EDIT: Sure enough, it's controlled with a keybind now. The reason it's not assignable to a joystick is they only put the commend in the keyboard default.lua. And once upon a time, unassignable commands were greyed out, so you didn't waste time trying to click on them, for some reason ED got rid of that feature.

I'm quite familiar with the A-10 and it's dead zones. I've done several tests against Iglas, out of probably 24 missile launches I finally got one single warning from a head on shot. Keeping the wings pointed at the threat results in silence. Either something is still broken or the detection envelope was severely reduced on purpose. Just tested it in 1.5, same result. Alerts from head on and directly behind, can't get any alerts from the side.

Any news on the modern style pedals? At this point I'm about to make my own.

I saw the last post in that thread and assumed it was fixed, but I just tested it and indeed, 3 months later and still broken. The MANPADS no smoke bug was indeed fixed however.

Just tested it in the latest 2.0 update against an Igla. It is NOT fixed.