GregP

Glad to hear you found a solution. In general I've found that explicitly including both press and release functions does indeed lead to less problems (with a variety of sims, actually). So while your issue is slightly different from what I was talking about (pauses needed in programs other than TARGET, such as SST and MacroWorks), I'm glad that thread keyed you in to the solution.

The 1.1.0.9 patch introduced the really annoying change that controllers which sent commands from outside the sim (i.e. were not assigned using DCS's in-game options menu but instead passed key combo through utilities like TARGET) that included modifiers, had to have manual 'pause' commands added to their profiles, between the modifier and the key, in order for DCS to recognize both the modifier and the key. There was a discussion over here: http://forums.eagle.ru/showthread.php?t=77788 I haven't installed 1.1.1.1 yet, and don't really understand how it changed controller inputs, but I wonder if your problem has anything to do with above.

So it's possible to have say, 3 modifier buttons defined, giving you 3 independent shifted states? (As opposed to TARGET's I/O and U/M/D being dependent upon each other, i.e. 'Shift1 = I,U', 'Shift2 = I,M', 'Shift3 = I,D', etc.)

That's news to me, Rocky49, but welcome news. Will go update my post now. Thanks for pointing it out.

EDIT: CARD NOW SOLD I just got this recently for an SLI system but then decided to go with Crossfire instead, so now I'm selling it. It's the Zotac model: http://www.newegg.com/Product/Product.aspx?Item=N82E16814500199 I got it second-hand, but the original owner just bought it a few weeks ago and had basically never used it; I have the original box and everything that came with it. There's nothing wrong with it at all; I ran it in an SLI for about a week with no problems at all. I can do $430 shipped. I'd prefer Paypal, and I can mail the card out the day after payment. My heatware is here.

Yes, sorry, typo in the original ... just corrected. You can indeed create the DCS folder, I think by right-clicking and choosing 'new key' or whatever that first option is.

As I understand it, the typo is that StereoMemoEnabled REG_DWORD 0x00000001 (0) should be StereoMemoEnabled REG_DWORD 0x00000001 (1) i.e. there is no way to type in "0x00000001" but then have a "0" end up in the parenthesis. Looks like a simple typo. As for why it's not working on your machine, did you do a search in your registry for "Stereo3D"? There are at least two places in the registry where it appears, but only one might have a "GameConfigs" folder in it, and it's THAT one that you want to add the 'dcs' subfolder to. To make this process easier, I'm going to combine Rodney1111's two previous posts, condense, and fix the typo: --------------------------------------------------------------------------------------------------- 1) Run Regedit 2) Go to the address HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NVIDIA Corporation\Global\Stereo3D\GameConfigs\ I then found that there was no dcs folder. When I went to create the dcs folder it wouldn't let me because it said the folder already existed. I concluded the folder was hidden (with no immediately apparent option to unhide it). Apparently programmers hide their registry folders when they don't want people fiddling with their registry settings. A quick search of the net shows how to unhide reg folders. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder\Hidden\SHOWALL\ And make sure that you have CheckedValue REG_DWORD 0x00000001 (1) Once the dcs folder has been unhidden, make the data at above address look like this: (Default) REG_SZ (value not set) Link1 REG_SZ Launcher.exe StereoDX9 REG_DWORD 0x00000001 (1) StereoMemoEnabled REG_DWORD 0x00000001 (1) StereoTextureEnable REG_DWORD 0x00000001 (1) Note that you add the StereoTextureEnable and StereoDX9 values by choosing "New->DWORD" while you add the critical "Link1 REG_SZ Launcher.exe" bit by choosing "New -> Expandable String Value" (at least I think that was what I did not sure about that last one).

Yes, just sent them out this morning, sorry.

OK, so you've got a fairly easy setup to work with; basically you just change your resolution from 1920x1080 to 2720x1080, because you'll be 'virtually' placing the USB monitors to the right of your main screen, i.e. in Windows' display properties screen, you're going to drag the USB screens to the right of your main monitor. Then you need to tell DCS that your entire screen space is the new render area. Then you create a multi-monitor lua file that tells DCS where to render the MFCDs; then you download SoftTH, drop the single DLL file into your DCS directory, and put a SoftTH config file in there with it (I could create both config files for you pretty quickly). And that's it! MFCDs exported to the USBs. Since you'd now be running a larger render area, you would likely see at least some small FPS decrease, but given that you're only running a single screen right now on a 6950, I doubt it would be significant. If the above sounded complicated, it's really not ... I could easily step you through the entire process, and once you figure out how it works, it's pretty simple.

Mike, In DCS I had them running using the free SoftTH utility. The main restriction is that you can't be using Nvidia SLI or AMD Crossfire, by aside from that, it's pretty flexible. What specifically is your setup? How many monitors and video cards, and what kind? Once I know that I can quickly figure out how it would work. BMS I'm not sure about ... I know guys have been extracting the MFDs, but I don't know how, specifically.

EDIT: SOLD I bought these new from a vendor in Korea last year, and was using them to export MFCDs in DCS: A-10C with TM MFDs overlaid on top. They're absolutely perfect for that function, but I no longer have a need for them since I've started using Eyefinity and Helios. They have a resolution of 800x480 and connect through a single powered USB plug or two unpowered plugs. Free DisplayLink drivers run the monitors, and I've never had a problem with them, as they continue to regularly update them. I'll mention that one of the monitors has two slight scratches: one about 1/2-inch long on the lower left, the other about an 1/8-inch long in upper right. Both are just cosmetic scratches and there are no dead pixels. It was hard to take good pictures of them because the flash really exaggerates the scratches but you can see from the one where it's plugged in that the lower left one is not visible when the monitor is on, while the upper right one is only slightly visible. I'd like to sell these as a pair, as they really do make perfect MFDs. I paid about $225 last year, and I see that on eBay now they're going to about $190 a pair if you include shipping. I could sell them for $140 shipped, a $50 discount. I prefer Paypal, and I'll send them out the day after I get payment, to anywhere within the lower 48.

I have not tried LOFC2, no ... in fact I don't think I even have it installed anymore. I guess A-10C and BS are technically different engines (DCS) so perhaps that explains the difference.

Oooookay, finally got it sorted! I just couldn't leave it alone. Turns out I was doing the wrong (or maybe half of the correct) registry change: the main one to do is this one, with this one may or may not being needed. Once I got that fixed, my tests went as follows: 1920x1080 resolution: single GTX 580, no 3D: 29 FPS single GTX 580, 3D: 19 FPS two GTX 580 in SLI, no 3D: 37 FPS two GTX 580 in SLI, 3D: 28 FPS And in particular, 3D using SLI did not have any problems. Image quality looked the same to me as with one card. I'm using Win7-64 with 285.79...have you tried that set yet? Maybe it's a driver issue you're having.

Gave it another try tonight; first of all I realized that I was wrong earlier -- I did in fact do the registry change to get it working the first time. But for some reason, doing it again now doesn't work -- no matter what I try, even in single-card mode, I can't get 3D working again. I'll keep at it but I'm stumped. Yeah, the RAID I run just for data backup; I've had way too many data losses over the years and it's an easier alternative (usually) to doing regular manual backups. 70, eh? Man, I'm 35 and have been simming for over 20 years, and thought *I* must be one of the veterans by now. :) I guess it's all relative. I'll give 3D some more try this weekend; I'm planning a full day of DCS testing ... switching out my new GTX580 3GB SLI setup for a Radeon 6970 Crossfire setup; I'm determined to ... err, determine which one is better for multi-monitor gaming in DCS once and for all. Happy holidays to you too, and thanks!

lazduc, I'll try that out as soon as I can. I attempted to run the test last night and then (unrelated) my Nvidia RAID setup got corrupted, taking the entire rest of the night to correct itself, thereby locking my machine down. BTW my normal resolution in DCS is 5960x1080 (3 27" plus 100 pixels bezel compensation between each monitor), with everything on high (except for Civ Traffic low, Water and Shadows medium), MSAA2x, TSSAA, HDR, cockpit shadows, etc. BUT, for 3D, I'd run just my center monitor at 1920x1080.

I can verify that Nvidia 3D Stereoscopic does indeed work with DCS. I recently bought an Acer HN274Hbmiiid 27" 120hz monitor that came with Nvidia 3D Vision glasses, and I gave 3D in DCS a try (64-bit version 1.1.1.0) with the 285.62 drivers. It works, and is pretty damn cool, but of course kills FPS, dropping it by half. Over the weekend I added a second video card to my system, so I suppose I ought to give 3D a try again and see if my FPS is more acceptable. I don't see myself actually playing DCS in 3D, though, because then I'd be stuck with a single monitor again instead of the triple-screen setup I prefer to use. I may not have time to play with it until the weekend, but I'll report back when I do. BTW I didn't need to do the registry hack to get it working in DCS, it just worked.

Try enabling vertical sync in the graphics options? Kinda sounds like a screen-tearing issue.

Excellent, thanks! Exactly what I'll need when I finally cough up the money for my own 10" touchscreen. The CDU is the last remaining item that I'd really like to have for my cockpit.

:) Well here's what happened, specifically ... I got up on Saturday morning with the fairly large project on installing 1.1.1.0 and getting all my customizations back in place (snapviews, controller configs, texture mods, etc.) which took a few hours. Rather than plug all my controllers in, load all their profiles, don the TrackIR headset, turn on VAC, etc., I decided to just start up the 'takeoff' mission and see how framerate was. And along with this shortcut was not bothering to turn my speakers on. So, when I found that 'esc' got rid of the briefing screen, and there were no other messages on screen, I just assumed I was truly 'in-game' and ready to take off. Of course, I never actually tried to take off ... which, in retrospect, would have been a good idea. :) Me? Really? Some config files, yeah .... but in general I'm much more a consumer of mods and the like than a producer.

Ugh ... how embarrassing ... I've just realized that I was never actually truly starting the mission. I did my tests with sound off and didn't realize that even after pressing 'esc', the game was still paused. Doing the requisite unpausing drops me back down to 21-22, as before. Off to go hide sheepishly in the corner now ...

So .... almost two hundred views and not a single "hey, me too!"? Not even from SoftTH users?

I don't know if this has something to do with my triple-screen setup or what, but I consistent gain an extra 25% FPS as long as I don't use the 'unpause' method of starting a mission! After lots and lots of trial-and-error to solve a separate problem I was having, I came across the following, although I have absolutely no idea why this works: In 1.1.0.9, on mission start, you are forced to 'unpause' the game to start the mission. On a simple sitting-on-the-runway test mission I use, my FPS would be 21. In 1.1.1.0, on mission start, you have the option of 'unpausing', hitting 'Esc', or clicking on the 'fly' arrow. If I 'unpause', I still get 21, just like in 1.1.0.9. But doing either of the two latter options in the same test mission gives me 26 FPS! Additionally, the 'auto-zoom out' "feature" (an annoyance to me) only occurs in 1.1.1.0 if I 'unpause' the sim -- not if I do the other two options. Does anyone know why ED changed the mission start options in 1.1.1.0? AFAIK this wasn't mentioned anywhere in the patch notes. And why should this have any effect on FPS?

That's the file where I define all my commands. I didn't attach it before because at least some of the commands I use are not DCS defaults -- I've redefined a few and defined a few that previously did not have key combos assigned yet. I've attached it here for your convenience, but note that you'll have to cross-check this list with what your particular install of DCS has for each command (in-game). The vast majority should be defaults though. (Note that I've changed the file extension to txt so that the forum will let me upload it -- remember to change it back to ttm) DCSA10Cv2.txt

Anybody else noticed this curious-looking file? \Mods\mod_plane_sample.lua local world_id = CurrentModPlane -- set up numeric id CurrentModPlane = world_id - 1 -- set up numeric id for next mod aircraft my_custom_plane= { Name = 'Wunderluft', DisplayName = _('Wunderluft'), HumanCockpit = false, Picture = "Su-25.png", Rate = 40, Shape = "Su-25", shape_table_data = { { file = 'su-25'; life = 32; vis = 3; desrt = 'su-25-oblomok'; shadow = 'shadow4'; fire = { 300, 2}; username = 'Wunderluft'; index = world_id; }, -- su-25-oblomok { file = "su-25-oblomok"; fire = { 0, 1}; }, --[[ { --destruction_shape }, { --various pieces }, { --etc } --]] }, WorldID = world_id, mapclasskey = "P0091000025", attribute = {wsType_Air, wsType_Airplane, wsType_Battleplane, world_id,"Battleplanes",}, Categories = {}, ------------------------- M_empty = 10099, M_nominal = 12750, M_max = 17350, M_fuel_max = 2835, H_max = 10000, average_fuel_consumption = 0.4895, CAS_min = 64, V_opt = 180, V_take_off = 72, V_land = 68, V_max_sea_level = 292, V_max_h = 271, Vy_max = 60, Mach_max = 0.82, Ny_min = -3, Ny_max = 5.9, Ny_max_e = 6.5, AOA_take_off = 0.192, bank_angle_max = 60, has_afteburner = false, has_speedbrake = true, main_gear_pos = {-1, -2.009, 1.352}, nose_gear_pos = {2.808, -2.15, 0}, tand_gear_max = 0.577, tanker_type = 0, wing_area = 30.1, wing_span = 14.35, thrust_sum_max = 9856, thrust_sum_ab = 9856, length = 15.36, height = 4.8, flaps_maneuver = 0.2507, range = 1250, RCS = 7, IR_emission_coeff = 0.69, IR_emission_coeff_ab = 0, wing_tip_pos = {-2.7, -0.611, 7.18}, nose_gear_wheel_diameter = 0.754, main_gear_wheel_diameter = 0.972, brakeshute_name = 4, is_tanker = false, air_refuel_receptacle_pos = {0, 0, 0}, engines_count = 2, engines_nozzles = { [1] = { pos = {-3.793, -0.391, 0.716}, elevation = 0, diameter = 0.6, exhaust_length_ab = 8.631, exhaust_length_ab_K = 0.76, }, -- end of [1] [2] = { pos = {-3.793, -0.391, -0.716}, elevation = 0, diameter = 0.6, exhaust_length_ab = 8.631, exhaust_length_ab_K = 0.76, }, -- end of [2] }, -- end of engines_nozzles crew_size = 1, crew_members = { [1] = { ejection_seat_name = 9, drop_canopy_name = 34, pos = {3.029, -0.092, 0}, }, -- end of [1] }, -- end of crew_members fires_pos = { [1] = {-3.084, -0.595, -0.112}, [2] = {-1.003, 0.189, 2.237}, [3] = {-1.618, 0.175, -2.408}, [4] = {-0.82, 0.265, 2.774}, [5] = {-0.82, 0.265, -2.774}, [6] = {-0.82, 0.255, 4.274}, [7] = {-0.82, 0.255, -4.274}, [8] = {-2.87, -0.596, 0.754}, [9] = {-2.87, -0.596, -0.754}, [10] = {-1.573, 0.145, -2.172}, [11] = {-1.924, -0.04, -1.934}, }, -- end of fires_pos -- Countermeasures SingleChargeTotal = 128, CMDS_Incrementation = 32, ChaffDefault = 64, -- PPR-26 ChaffChargeSize = 1, FlareDefault = 64, -- PPI-26 FlareChargeSize = 1, CMDS_Edit = true, chaff_flare_dispenser = { [1] = { dir = {0, 1, 0}, pos = {-3.677, 1.012, -0.859}, }, -- end of [1] [2] = { dir = {0, 1, 0}, pos = {-3.677, 1.012, 0.859}, }, -- end of [2] }, -- end of chaff_flare_dispenser --sensors detection_range_max = 0, radar_can_see_ground = false, CanopyGeometry = { azimuth = {-145.0, 145.0}, elevation = {-50.0, 90.0} }, Sensors = { RWR = "Abstract RWR" }, HumanRadio = { frequency = 127.5, modulation = MODULATION_AM }, etc...

I too have been thinking of getting something like the 720s for use as a CDU; what has been your experience using that? I seem to come across a lot of reviews that say the touch precision is lacking.