GregP

It does indeed look like that screen supports HDMI 2.0, so you could get the full 60Hz out of it with 900-series cards. If you're going to do it, I'd strongly recommend going SLI. I tried a single 970 at 4K and FPS rarely went over 40, and often dropped to the teens, whereas with 2 970s now I'm usually around 40-70. One thing I'd encourage you to do, though, is first research whether that model can properly do "4:4:4 chroma color" at 4K/60Hz. Check out the Nvidia 900-series forums for details on that. But bottom line is, if the monitor can't do it (despite what the manual claims) you're going to have color problems in games. As for response times, I'm not sure what my Panasonic has, but I have no complaints about it across multiple different games.

One 970 may not be enough, but I can verify that two certainly is. :) I'm running DCS at 4K/60Hz with SLI'd 970s, and even though I rarely see VRAM usage go over 3.5 GB (maybe lending credence to the card not being able to use all 4 GB), I'm generally able to maintain 40-80 FPS. As others have pointed out, yeah it sucks not having all 4 GB, but does it really make a difference? In my experience, at 4K, where SLI is really required anyway -- no, it doesn't.

Just wanted to note that mondaysoff's tips in post #4 still work perfectly in 1.2.14. Nice work!

This is a problem that has now screwed up pretty much all Su-27 skins, right? Because I too have been having this problem several weeks now. I definitely don't look forward to going into every single lua file and fixing it manually. Very frustrating when changes like this are made.

There are several buttons/switches/axes in the pit such as these that don't have entries in the control GUI yet, so I would imagine that Belsimtek simply haven't gotten around to it yet, but plan to do so.

Yes, great idea Devrim! All high quality mods here. Although even after having used every one of these at some point, I have to admit I'm still confused about how noise, trees and Ed's villages work, i.e. how to separate those files out such that you don't have to give them up if you later decide to switch to another mod. Maybe a discussion for another thread.

Congratulations on joining the club! I've had my Pana for a month now and absolutely love it. I too, though, struggled with getting optimal picture quality. I've tried many combinations of settings but still haven't managed to find what I would consider to be an ideal setup. Overall, it seems to me that the Pana just simply can't do deep blacks very well. For now I'm using the below settings, and rely on SweetFX to individually tailor colors etc. in each game I play on it. Picture Mode: Monitor Back light: 80 Contract: 85 Brightness: 0 Color: 80 Tint: 0 Sharpness: 0 Color temp: Normal Vivid color: Off Color remaster: Off Adaptive backlight control: Off Letterbox: Normal C.A.T.S.: Off Video NR: Off MPEG remaster: Off Resolution remaster: Off Caption smoother: Off Brilliance enhancer: Off Pro settings: Contract A.I.: Off Advanced picture: Game mode: On 4K pure direct: On Black level: Dark

This here is likely the cause. The MP mission itself sometimes has the creator's snapviews saved inside the .miz file, whether intentionally or not. Luckily if you're hosting the session, you can simply open the .miz using a zip application like 7zip and remove the responsible config file. But if you're joining a server that enforces integrity checks, chances are there's no way to override it.

I bought a DSD button box a few years ago for racing and loved it. In fact just recently I looked for a suitable button box on his site that would be good for DCS, but couldn't find any with true rotary dials. If he's thinking of making a more flight sim-useful box like that, I'd definitely buy one.

For years now I thought it had been firmly established that SLI/Crossfire simply didn't provide any performance benefit in DCS, and that it wouldn't happen until DCS 2.0. After owning AMD cards for the past 3 years (including trying Crossfired R9 290s about a month ago), I switched over to Nvidia recently with a single GTX 970. I just bought a second 970, did a quick takeoff-in-a-MiG-21 FPS test, and found the following: Single 970: 45 FPS SLI'd 970s: 64 FPS Not the doubling of FPS ideally expected, but a 40% improvement nonetheless -- not bad at all! In my quick test, I didn't see any graphics anomalies either. So, has anyone else had similar luck with SLI/CF lately?

So you fly the Mi-8 with a G27, eh? Now THAT'S hardcore. :)

These look incredible! Great job so far. Can't wait to try them out.

Hey everybody -- apologies for going AWOL from my own thread :) for over a month now. Like Chic and SDsc0rch, I sprang for the Panasonic TC-58AX800U a few weeks ago and am absolutely loving it. For those in the U.S., Best Buy carries them for $1999 but you can use the post office Best Buy 10% discount coupon (just ask for a moving coupon / address change packet at any post office) making my out-the-door price, for example, $1908. I was satisfied with the 30Hz limitation of the Seiki a year ago, but now that I have 60Hz, I'm ecstatic. It really does make such an incredible difference in DCS. As for FPS, with most graphics options medium high to high in DCS, I can maintain 25-60 FPS. As for TrackIR placement, this is indeed tricky; I had to move it from the top of my previously desk-mounted 55" to underneath my now wall-mounted 58". I've cludged together a simple solution that seems to work for now, but it ain't the prettiest -- see the [admittedly awful] second picture below.

Actually, now I'm thinking it may be modeled correctly; at least, consistently with what the manual states: p. 59, discussing launching on AOJ locks: "If the entered target range is longer than the range of the chosen missiles for this altitude, then missile launch requires either that the entered range is manually reduced with [RCtrl--] until the "ПР" symbol appears, or that launch authorization override is enabled with [LAlt-W]." So I take that to mean that using the Radar Range axis lets you get down to 10.0 km, but if you want to launch on an AOJ lock and can't get the missile to launch because its range is less than 10.0 km, you can 'trick' the missile into launching by saying that the estimated range is now less than 10.0 -- as low as 2.0. Seems a bit redundant though since we already have Launch Authorization Override.

I've noticed that in the 1.2.11 open beta, when you assign 'Radar Range' to an axis, the range will only vary from 10.0 to 150.0. But when you assign that function to a button ('Target Specified Size Decrease/Increase') the range can vary from 2.0 to 150.0. I've tried this on multiple controllers and different axes, so am quite sure it's nothing in my control setup that causing this problem.

Yeah I get weird behavior after jumping into a MiG-21 too, for example if the plane I'm jumping into is in afterburner, the afterburner graphic and sound never turn off, even though inside the cockpit I can see that I've disengaged it.

As a point of reference, at 4K, switching from an R9 290 to a GTX 970 makes almost no difference whatsoever in FPS. :) But I did it so that I can use a 60Hz 4K TV finally, not for any actual performance improvement.

EDIT: SOLD! Bought this back in February, but recently switched to a GTX 970 so don't need it anymore. I'm the original owner, and I've had no problems with the card whatosever, it's in perfect condition. I'm selling it for $225 shipped anywhere within the US.

EDIT: SOLD! I bought this monitor a little less than 3 years ago, and have used it as a 3D monitor with the TriDef 3D drivers for playing Skyrim, The Witcher 2, Dishonored, etc. It's an incredible monitor, and if you haven't played any games in 3D, you're really missing out! Just recently I swapped out my AMD cards for Nvidia cards though, and as this monitor's 3D is really meant to work with AMD cards, I don't have much use for it anymore. It still goes for $480 minimum online, although is fairly hard to find now. Amazon's page for it is here. I will note that my monitor, like most S27A750D's, has the 'DisplayPort disconnect' issue. I've never even once had it happen while in-game, but once in a great while it'll happen when on the desktop. The solution is simple: just cycle the inputs until you get back to DP, and it's fixed. I've never considered it a serious issue, as it's never impacted by use of it. But presumably this was the reason this line of monitors was discontinued. Even without 3D, it's an outstanding monitor: fantastic colors, 120Hz refresh rate, very sharp text. It also comes with one pair of active shutter 3D glasses. I'm selling it for $230 shipped anywhere in the US, and would prefer Paypal payment. It's in perfect condition, no problems whatsoever, and I've taken very good care of it. It's been my secondary monitor for the past year, so hasn't even really gotten much use during that time.

FWIW, in my takeoff mission, this method worked to get one of the two dials on RH to work, but would not fix the second. Or 'takeoff from runway', it seems.

Here's working sections for Radar Low Altitude Filter (assuming that Filter Off would be middle position of 3-position switch, even though it's not like that in the actual MiG-21 cockpit), Navigation Lights (assuming user only wants Nav Lights Max, Min and Off), and RSBN Mode: --Alternate Navigation Lights {down=device_commands.NavLights,up=device_commands.NavLights,cockpit_device_id=devices.LIGHTS,value_down=0.99,value_up=0.0,name='Alternate Nav Lights Max',category='Lights'}, {down=device_commands.NavLights,up=device_commands.NavLights,cockpit_device_id=devices.LIGHTS,value_down=0.33,value_up=0.0,name='Alternate Nav Lights Min',category='Lights'}, --Alternate Low Altitude Filter {down=device_commands.RADARlowAlt,up=device_commands.RADARlowAlt,cockpit_device_id=devices.RADAR,value_down=1.0,value_up=0.0,name='Alternate Low Altitude Antenna Tilt',category='Radar and SPO'}, {down=device_commands.RADARlowAlt,up=device_commands.RADARlowAlt,cockpit_device_id=devices.RADAR,value_down=0.5,value_up=0.0,name='Alternate Low Altitude Filter',category='Radar and SPO'}, --Alternate RSBN Mode {down=device_commands.RSBNmode,up=device_commands.RSBNmode,cockpit_device_id=devices.RSBN,value_down=1.0,value_up=0.5,name='Alternate RSBN Mode: Descend',category='Avionics'}, {down=device_commands.RSBNmode,up=device_commands.RSBNmode,cockpit_device_id=devices.RSBN,value_down=0.0,value_up=0.5,name='Alternate RSBN Mode: Landing',category='Avionics'},

Same problem here, but in a simple SP mission I created starting from a runway takeoff.

As far as other keybinds that would be nice to have, I'd like to request the following: Radar Lock Cancel (CM52) ASP Angular Correction Knob (CU25) Radar Low Speed Target Mode (CM50)

jjohnson241, I just verified myself that what you suggest does indeed work.

My lucky day -- not only does the MiG-21 manual finally come out, but I talked myself into paying $35 for a bound B&W printout (as opposed to the $140 FedExKinko's wanted to charge for full color) ... but then when I went to pick it up, they said they'd made a mistake and printed in full color! So I paid $35 for a beautiful full color manual. No complaints here. :)