Polo

Downloading updates... 84.4/1361.7MB @ 105.2KB/s Should be going to bed now but suspect tonight's going to be :joystick:

Not sure if you've found it yet, but you can hit Ctrl+Enter (the old combo that brought up the controls position layout in BS2 & A10C) and it will bring up the Radar in one MFD and the controls position layout in the other. Unfortunately not yet possible to get the RWR up as far as I know. Formski

Might just add my experiences, given I'm running a 6990 as well. My setup is Eyefinity with 3x24" at 6048x1200 (bezel corrected) and two 8" VGA LCDs with Thrustmaster MFDs. Using SoftTH to transfer the MFD images to the LCDs (basically I setup a renderarea of 6648x1200 and stacked the 2 600x600 images on the RHS of the main display) I'm getting between 15-30 based on inspection. With SoftTH Crossfire is disabled so I'm basically running a 6970 2GB here, O/Cd to 950/1400 (i.e. O/C 6970). From what I remember most graphic settings are on maximum although visual distance is set to Medium with 2xFSAA, TSAA and MFDs at 1024 every frame. MSI shows the GPU usage at between 95 and 99% most of the time. Given these frame rates are similar to Vlerkies' at 1920x1200 with over 3x the amount of rendering I'd suggest there is something in the engine giving the AMD cards issues. Of course this is all totally (un)scientifically proven! Formski

Hi AJ, Have responded to your PM about this issue. Formski

Are you sure that your PC is actually outputting a signal to the subwoofer? I'm using an Auzentech X-Fi Forte (modified Creative Labs X-Fi) and I needed to go into the sound card software and setup a crossover for the bass to the subwoofer and the BG2 for it to work. In the end I plugged the BG2 into the front speaker output on the sound card as it also works for headphones, whereas with headphones on the X-Fi there is no subwoofer output. This is with a Logitech Z5500 5.1 system, so the earlier model of what you are using now. Also ensure you turn the BG2 volume up as well. I keep the cutoff filters on and set the cutin frequency to minimum. Formski

I often find I need to hit Keypad-/ or Keypad-* (the zoom in & out keys) before the Warthog Throttle zoom will work correctly. Formski

My HP Laptop (DV6 I think) has an option in the BIOS to toggle the function keys so that they output F1, F2 etc. rather than the Wireless on/off, screen brightness etc. Otherwise you might be able to get F12 by pressing the 'Fn' key down near the Control and Alt keys, along with the F12/Wireless button.

I've been using this mod for a few months and it works very well. Only issue I've come across is that many of the allied flight calls are not being heard, although the subtitle appears on-screen. Easiest way I find to reproduce is to create a fast mission and when you start flying the allied flights/choppers etc. start calling in 'Ford 2-1, enemy armor detect at bullseye 352, 15 miles. This text appears but the radio call doesn't. Funnily enough the call 'Ford 2-1 is rtb at 1200' works fine. Removing the ModMan patch brings all the audible radio calls that disappeared back. Formski

Also turn off HDR in DCS A-10C if you haven't already. Seems to be an incompatibility between Crossfire and HDR. Formski

Just to add to this - Once you start to F-Pole Dive. You want your altitude to be under your opponents so that when he beams you your radar isn't looking down and loses lock. I find that this help the pK of my shots in somewhat (anecdotal evidence only) This also applies to all BVR shots from either side (SU27/33/MiG29/F15) Formski

From what I can tell that is the case. It means you can determine the landmark to use when you get there. I'm finding that campaign missions don't reveal too much in the editor, so the surprises are still surprises. Formski

Hi all, Am running Black Shark 1.0.2 using Eyefinity (5760 x 1200) While in-flight everything works fine, the single player GUI appears as a 2-screen wide window rather than full screen. The location of the GUI changes horizontally as you go through different screens and the vertical alignment with buttons is not quite right. Is there a fix to this? Formski

Hi S77th_RYKE, Unsure about the fishbowl effect - it's happening here too and it probably is related to the hack Kegetys has released. However i find it more annoying than when the smoke trails and land mass disappear. Would love to find a tidier solution however, which probably means ED need to look at and fix this in-code. FYI in options.lua I have ["width"] = 6060, ["height"] = 1200, ["resolution"] = "6060x1200", and with borderSize = 150in softth.cfgthe screen border is about right. Formski

Hi S77TH-RYKE, FYI I'm running 3 x 24" at 1920x1200, but prior I had 1 24" at 1920x1200 and 2 19" at 1280x1024 With borderSize and SideExtraWidth: From my experience the borderSize is the entry that adds in the borders/bezel management. On my current setup I use 150 and everything (almost) lines up properly. SideExtraWidth is the difference in resolution between the central monitor and the sides. On my current setup of 3 x 24"s I use 0, whereas on my old setup I was use -640 (1280 - 1920) So now my softth.cfg simply has in it: BorderSize=150 sideExtraWidth=0 and on my old 1920x1200 centre with 1280x1024 sides I used: BorderSize=150 sideExtraWidth=-640 With the whole fishbowl effect (i.e. sides being stretched) I don't think there is a fix, as this is due to the mathematics/optics of using a single camera with wide Field of View. The only way out of this would be to use the 3 monitors option in FC2, but this introduces other issues and also kills frame rate. Formski

From my experience (and that's all it is!) I couldn't get LO:FC running at a good speed with maximum settings on my old Q6600, even overclocked to about 3.0Ghz. It did make a frame rate difference compared to 2.4 though - I had all settings at maximum except shadows all planar (the new video card shading bug) and object density/range(?) set to medium. I'm now running an i7 920 at 3.3Ghz and can finally run at 1920x1200 at max settings. Formski

A question for those using multi-monitor in Vista... I've setup a dual monitor setup (LHS is a 1920x1200 with the forward view, RHS ia 1280x1024 with ABRIS and Shkval combined) but because I'm trying to keep the aspect ratios of the ABRIS and Shkval there is a section of the screen that is not drawn on by these instruments. Is it possible to clear this so that the background and previously drawn items don't show? (i.e. the loading screen or radio comms text) FWIW it's an ATI4870 X-Fire (not that it matters here) setup with one monitor on each port and running in windowed mode.

Hi Celo63, You're right with the three monitors for separate ABRIS and Shkval (or you can merge both ABRIS and Shkval onto one monitor in a two monitor setup) With the three external views it means that there is three monitors with one of the views (front, left and right) on each. Basically a Matrox TripleHead2Go type setup.

The same as the second monitor. This is because KA-50 centres the overall 'canvas' in such a way that there is equal amounts on the LHS of the centre monitor as there is on the RHS. The Win X Move program earlier in this thread can probably help solve this, plus maybe there is another config somewhere in the LUA files that set the initial coordinates of the window. Now if ATI will just allow 3 monitor CrossfireX I'll have the equivalent of Triple Head 2 Go without the box... :thumbup: One other thought I tried (and failed) - with my second monitor I have the ABRIS and the Shkval setup in such a way as to keep their aspect ratios close to what they should be. The end result is screen space not used. Is there a way to fill this with the camera image? I tried but couldn't get it to work properly. Formski

Comms Text Has anyone run into the issues of communication text not appearing on-screen? I've setup my two screens - my 1920x1200 24" LCD on the LHS for the camera and my 1280x1024 19" LCD on the RHS for the ABRIS/Shkval (i.e. have expanded the window to 4480 pixels wide so that the LHS 1280 pixels are not showing anything) The radio menu appears over the ABRIS which is the LHs of the 19" I suspect the communications text is showing up in that first 1280 pixels which I don't have anything showing. Is there a way to move it? Formski

I've received this response back from ATI Support: Solution:Thanks for the information. I have passed the problem along for investigation. Further, I would suggest all that are affected with this problem fill in the Catalyst Crew Feeback form. Lots of feedback will give the problem more importance with the software engineers. Formski

I've got the same problem on my HD2900XT under Vista Home Premium 64 bit, but it is happening with both Catalyst 7.8 and Catalyst 7.9. I've logged a support ticket with ATI to see what they can come up with. For now I'm using 'All Planar' till it can be sorted out. Formski

Following up - can anyone please post up the square 1024x1024 or 2048x2048 files for those of us with 1.6 aspect wide screens? Thanks, Formski

Just to add to this list I uften use www.staticice.com.au when trying to track down items and good pricing. Also the Cougar is a very good HOTAS setup - been running mine for just over 12 months unmodded and am very happy with it. Formski

Yeah, I'm running a Crossire setup using 2 X1900XTs - picked up the master card for less than half what the original XT card cost me! :thumbup: I haven't noticed any issues running Crossfire in any games (except Medieval 2 won't start when Crossfire mode is active) and the SuperAA looks, well, super! This is all on an Opteron 175 at 2.93Ghz using the latest Catalyst drivers (7.1) Formski

Beat it Beat the Campaign AWACS Kill Mission this morning (in 1.12a) After taking off the first stop was the MiG29s - I shot at one with an AIM7 which he dragged out. This guy then continued extending and I suspect went home. The second MiG traded an R73 with an AIM120 from my wingman and both went down. After continuing along the steerpoints and chaffing a few SAM launches I came across two contacts at 37000 (nicely contrailed) which I assumed were the SU27s. Bugged them both in TWS and sent three AIM120s at them (one got two because I hadn't bugged them both early enough) which sent them defensive. One went down while the other started shooting after my missile missed. Got a lock on the last one and used the remaining AIM120 to kill him. At this point the A50 was heading away and dropping altitude, so I killed him with the last AIM7. Have to say the F15 is great for knowing what everybody is doing (read TWS), but lousy for actually interfering with it, because you're in range of everything before your missiles become effective. Formski