ruprecht

Couldn't you do it like this on the second head?

But in XP span mode, the sim sees only one screen yes? So you can span across both heads? This is what I mean: Then you zoom the centre view out really wide like the last pic in this thread: http://forums.eagle.ru/showpost.php?p=628924&postcount=1 And voila!

urze, thanks for your post. I wonder about what you've said here: from what I understand, under XP you can run main view and ABRIS on 2 heads fullscreen right? And a TH2G appears as a single screen on a single head right? So with 3 screens off the TH2G (on one head) and the ABRIS screen on the second head, it should be possible so long as all have the same vertical res? Sorry if I've misunderstood you, but I'm about to buy a TH2G and install XP_32, so I'm eager to get it right :) :thumbup:

Have you tried adding a second screen onto the second head for ABRIS/Shkval? Does it work with TH2G?

It does not, the DRM issue is still present in Win7. Best solution: trial the beta and spam MS incessantly about the ridiculousness of hurting legitimate use on the off chance that some users who are going to violate DRM anyway will be somewhat impaired.

I can't find any way for a unit to throw smoke on a trigger. This would be a very welcome addition to the ME. "Gator 1, target is a bunker 300m east of the bridge. Standby for red smoke, wait." "Gator 1, target is 30m north of the red smoke. Clear in hot, danger close."

See bold above. I'd recommend using the same vertical res for XP, as a) you can use fullscreen and b) you will not have the issues with the multiplayer screen that you will with asymmetric vertical res.

this "phantom monitor" nonsense needs to be done away with as well. And there seems to be deafening silence from ED on any issues to do with multimonitor. Is this because it's "too hard" or only applies to a limited set of your customers, or are you preparing a surprise for us?

Which OS? *edit* never mind. OK for XP you need to read the top section of this: http://vaaf.net/wiki2/index.php5?title=Black_Shark_MultiMonitors Post your monitorconfig file and I'll have a look at it. Cheers

MrTube, I have also flown a lot of F4 and the Viper is a big pussy to fly compared to the Shark. With the F16's automatic stabilisation you can set an attitude and it will hold it - it simply wants to fly. Not so with the Shark - like all helos it desperately wants to beat itself to death on the ground and you have to constantly convince it not to. It sounds to me like you're overcontrolling and thinking too much about it. You have to fly helos with your subconscious brain because your conscious brain is too slow. That sir just takes practice and a force of effort to stop yourself "stirring the pot" with the controls. I'd also do some reading on rotary wing aerodynamics as that can help to explain some of the secondary effects you're seeing. Every control is interlinked and changing one means you need to change another too. You shouldn't need to touch the throttles, just leave them in the "governor" position about halfway up. Good luck!

You need a dedicated cockpit setup then!

Unplug the screens, swap GPU heads, switch positions on the desk :) *high fives scatter* another successful mission buddy.

I think part of your problem is the X= settings in your monitor config. I'm pretty sure you don't need to use a phantom monitor with XP. The way you have it, you have 3200 horizontal pixels left of your main display, which is why you can't see the multiplayer text. My notes below: Description = 'ABRIS and Shkval on the right and camera on the center' Viewports = { Center = { x = 3200; [b][color=black]-- this should be 0[/color][/b] y = 0; width = 1600; height = 1200; viewDx = 0; viewDy = 0; aspect = 1.3; [b]-- shouldn't this be 1.33333 ?[/b] } } Shkval = { x = 2400; [b]-- this should be 1600[/b] y = 0; width = 800; height = 1200; [b]-- or use 600 for correct Shkval aspect[/b] } ABRIS = { x = 3200; [b]-- this should be 2400[/b] y = 0; width = 800; height = 1200; } And for your options: ["graphics"] = { ["multiMonitorSetup"] = "shkval+camera", ["color"] = "32", ["heatBlr"] = 1, ["scenes"] = "high", ["water"] = 2, ["fullScreen"] = false, [b]-- you should be able to use true with XP one you get your numbers right[/b] ["visibRange"] = "High", ["aspect"] = 4, [b]-- why 4? shouldn't it be 3200/1200, or 2.66666 ?[/b] ["textures"] = 2, ["shadows"] = 3, ["display_mode"] = { ["avi"] = { ["bpp"] = 32, ["resolution"] = "640x480", ["full_screen"] = false, ["aspect"] = 1.333333333, ["height"] = 480, ["width"] = 640, }, -- end of ["avi"] }, -- end of ["display_mode"] ["effects"] = 3, ["lights"] = 2, ["haze"] = 1, ["terrPrld"] = "20", ["height"] = 1200, ["resolution"] = "1600x1200", ["civTraffic"] = 1, ["width"] = 4800,[b] -- should be 3200 (1600x2)[/b] }, -- end of ["graphics"]

pics!

cheers

OK - the first reply wasn't me :) Same sig block style, different names. Stick with 1600x1200 if your GPU can handle it. The aspect setting should ease much of your pain I would expect. Just change one thing at a time, fix the shkval aspect once you've got the overall aspect correct. Good luck.

Also note that the aspect at 1600x1200 (1.33333) is different to the aspect at 1280x1024 (1.25). Maybe that's causing you grief. *edit* you need to decide if you're going to run at 1600x1200 or 1280x1024 because the config is different for both. See Scatter's script: ... aspect = screen.aspect / 2; ... So your aspect (in options.lua) needs to be set to either 2.66666 or 2.5 depending on if you're using 1600x1200 or 1280x1024 respectively. Let us know how you go, and try to describe the results more fully. Cheers

@ advent: you mean like this? :D as far as I can tell, there is no other overlay directly exported from the sim other than left, right, centre, ABRIS and Shkval. That means that what you want to do with the extra instruments in the dead space isn't possible. But let's not hijack Quirk's thread eh? Quirk, I almost guarantee that you're missing something small - even if you're not a programmer, try and understand what the config file is trying to do. You will get it in the end, all of us that have done multimonitor have been through what you're going through. Keep trying. You've posted a number of images above, but you haven't actually said what is wrong with each of them, you've left us to infer that. For example, the first one (using Scatter's script) looks pretty close to me, you just need to fix your extreme zoom out level and change the Shkval height parameter to screen.height / 2 to fix the aspect. Also if your problem is that all of that is crammed onto one screen (it's hard to infer from a screenshot without your description) changing the aspect in your options to (total width) / (total height) instead of 1.33333 might fix it (in your case: 2560/1024 or 2.5). Please explain why each image that you've posted is not what you need? We need more info. Also note that you don't have to modify the existing monitorsetup files, you can create your own and call it banana_milkshake.lua for all the sim cares, so long as you select that file in the dropdown. Cheers

I found it in (root)/BlackShark/templates.bs (don't edit with notepad). The following should give you everything you need for an Eastern FARP, except for the FARP helipad and the FARP tent. Note that I haven't tested any of the functions (rearming, refuelling, repairs or comms), please advise if it doesn't work. Also adds 4x ZSU-23-4 for defence. [0] = { ["type"] = { ["FARP Nancy-Bird"] = "static", ["FARP DEFENCE"] = "vehicle", }, -- end of ["type"] ["groups"] = { ["FARP DEFENCE"] = { [1] = { ["long"] = 0, ["heading"] = 1.6233793884058, ["name"] = "ZSU-23-4 Shilka", ["lat"] = 0, ["skill"] = "Random", }, -- end of [1] [2] = { ["long"] = 2.280758167128e-005, ["heading"] = 0.017453292519943, ["name"] = "ZSU-23-4 Shilka", ["lat"] = -1.5561089129701e-005, ["skill"] = "Random", }, -- end of [2] [3] = { ["long"] = 4.450442127879e-005, ["heading"] = 4.7955302122731, ["name"] = "ZSU-23-4 Shilka", ["lat"] = 1.6914361222753e-007, ["skill"] = "Random", }, -- end of [3] [4] = { ["long"] = 2.2757215727531e-005, ["heading"] = 3.4330494480677, ["name"] = "ZSU-23-4 Shilka", ["lat"] = 1.5899625428473e-005, ["skill"] = "Random", }, -- end of [4] [5] = { ["long"] = 3.4916078855973e-006, ["heading"] = 0.043450895391531, ["name"] = "SKP-11 Mobile Command Post", ["lat"] = 7.4423499827336e-006, ["skill"] = "Random", }, -- end of [5] [6] = { ["long"] = 3.6365464068822e-005, ["heading"] = 2.5722794624891, ["name"] = "ATZ-10 Fuel Truck", ["lat"] = -1.2854836833665e-005, ["skill"] = "Random", }, -- end of [6] [7] = { ["long"] = 3.8932508622413e-005, ["heading"] = 4.321781936687, ["name"] = "Ural ATsP-6 Fire-Engine", ["lat"] = 1.0825254769697e-005, ["skill"] = "Random", }, -- end of [7] [8] = { ["long"] = 4.3630904587144e-005, ["heading"] = 4.2487413713839, ["name"] = "ZiL-131 APA-80 Ground Power Unit", ["lat"] = -6.6811530609057e-006, ["skill"] = "Random", }, -- end of [8] [9] = { ["long"] = 9.0337669331753e-006, ["heading"] = 2.5722794624891, ["name"] = "Ural-375", ["lat"] = -1.2516553784758e-005, ["skill"] = "Random", }, -- end of [9] [10] = { ["long"] = 1.8558282571801e-005, ["heading"] = 2.6344941491975, ["name"] = "UAZ-469", ["lat"] = 1.5223048214885e-005, ["skill"] = "Random", }, -- end of [10] [11] = { ["long"] = 1.5116430285622e-005, ["heading"] = 2.6344941491975, ["name"] = "Ural-4320-31 Armored", ["lat"] = 1.4715609516158e-005, ["skill"] = "Random", }, -- end of [11] [12] = { ["long"] = 1.2769970739845e-005, ["heading"] = 2.6344941491975, ["name"] = "Ural-4320T", ["lat"] = 1.3954451953846e-005, ["skill"] = "Random", }, -- end of [12] [13] = { ["long"] = 1.0813317519065e-005, ["heading"] = 2.6344941491975, ["name"] = "ZIL-131 KUNG", ["lat"] = 1.2939576111481e-005, ["skill"] = "Random", }, -- end of [13] [14] = { ["long"] = 8.575882813e-006, ["heading"] = 2.6344941491975, ["name"] = "KAMAZ-43101", ["lat"] = 1.1924701305843e-005, ["skill"] = "Random", }, -- end of [14] }, -- end of ["FARP DEFENCE"] }, -- end of ["groups"] ["names"] = { [1] = "FARP DEFENCE", }, -- end of ["names"] }, -- end of [0]

Has anybody hooked a Simkits USB instrument up to BS yet? I was going to get started on the code soon but if it's already been done...

OK latest: With the added RAM and an OC to 3.2 GHz (400x8 ) I get 17FPS on medium settings plus 2xAA 2xAF with all 4 screens running. I'ts aaaalmost enjoyably playable. I ran 3DMark06 on each of the GPUs to verify the x4 slot was holding up the 9800. Lo and behold: the 8800 Ultra (in slot 1) got 13,500 3dmarks, and the 9800 GTX+ (in slot 2) got 10,000. So yes, there is a definite bottleneck there. Solution: - new mobo supporting twin x16 GPU slots (this one? http://pcgogo.com.au/index.php?act=viewProd&productId=8128) - use Asus PCIe soundcard to free up more CPU cycles - maybe upgrade to Windows 7 64bit With that I hope to crack the 25FPS barrier. We shall see. Thanks for the help so far.

Adding in another 4GB of G.Skill PC8500 (for a total 6GB - I know that's more than Vista32 can handle, but it shouldn't hurt right?) tonight had 2 effects: - wouldn't boot windows with the existing OC parameters, so I'm back down to 2.4 GHz. - boosted FPS from 10 to 15 in 4-head low detail AND it's much less stuttery. So it seems even with 20% less CPU performance, I've still got a 50% FPS boost from the extra RAM. Plus I have at least 20% additional performance headroom with a new OC. The hunt continues...

OK a bit of research turned up some interesting snippets: - My mobo disables the PCIe x1 slots when the PCIe_16_2 GPU slot is in use. That explains why my PCIe sound card stopped working. 1 mystery solved. - While the PCIe_16_1 GPU slot supports x16, the PCIe_16_2 GPU slot only supports x4 (though it is physically an x16 slot). Maybe if I drop slot 1 to x4 (is this possible?) it might sync better? clues.... hopes rising.... *edit* Been trying to figure out how to limit the PCIe x16 lanes to x4 - according to this post http://www.tomshardware.com/reviews/pci-express-2-0,1915-4.html you need to tape the socket! Any better ideas before I try that?

Thank you all for your replies. OP states that I am using dcsbsaffinitytool to use all 4 cores :thumbup: That's not really the problem - post #3 describes the major issue. Quite :) Maybe as a last resort, but not until I've tested the performance with a borrowed one. Anybody in Brisbane got a TH2G for me to test? :music_whistling: Will do so, thanks. The major issue is the major FPS hit just by introducing the second GPU. I get 50FPS on low with the onboard sound with 2 screens on 1 GPU, or 25 FPS on low with onboard sound with each GPU running one screen. Yes the overall FPS would be improved by not using windowed, but it doesn't explain the difference introduced by using a second GPU. RAM is my next step. 4GB will be in there by this evening. And I hope I get it running too :) As above I can get 50FPS out of it with two screens if I use a single GPU. XP is probably a second-last resort. 'cause it don't work otherwise :)

Appreciate the thoughts GG. If that's the case though, surely there would be an outcry by all those that thought they were going to get increased performance running two GPUs? Yet commonly accepted wisdom is that adding a 2nd GPU gives you almost but not quite double the performance. I get half the performance by adding a second GPU. In the words of the Chewbacca defence: that does not make sense. It seems I'd be better off trying to flog my GPUs and getting a single quad-head 4850X2, but that's an expensive proposition with no guarantee of success. Surely this problem can be solved.