BTTW-DratsaB

Thanks Viper

SLI Works well, but... hmm there is indeed a lot of misinformation in this thread. I use GTX295 and run SLI. Within Nvidia driver 260.89 (and previous ones) there is a profile called "Digital Combat simulator: Black Shark". This also works with DCSA10, as the .exe's share the same name. You don't need to make a profile. I was having some problems with DCS:A10 when using the TGP or Maverick camera. The Image on the MFCD starts to go corrupt and "flickery" showing the terrain wireframe through the ground texture. (I would take a screen shop but it wont pick it up). I turned off SLI and the problem ceased. But... I lost massive amounts of FPS compared to running in SLI mode, particularly when the TV cameras where on and in Cockpit view in general. So SLI is making a big difference to this Sim. But we need to have the targeting cameras fixed so they don't cause this corruption. Question is...who is supposed to fix this? With these multiGPU issues you get the feeling that the devs (not just ED btw!) are like, "that's not our problem, Nvidia have to fix it in their drivers because xyz". And nvidia are like, "that's not our problem, the Game devs implemented something in a way that isn't compatible so they must fix it" etc. And poor Mr End User is like, "uhh we have been waiting for 2 years since release, can one of you get this fixed please?" :D I just hope some one can take note of this problem and get it fixed before the sim goes gold.

thanks for clearing that up!

have a look here mate http://forums.eagle.ru/showthread.php?t=62573 :thumbup:

Landing Tutorial So, I call Inbound to Batumi ATC and they reply "Fly heading 224 for 35, QFE, 29, Runway 13, to Pattern Alt" The landing tutorial then says, "As indicated by the ATC, the Batumi Pressure Altimeter reading is 29.88 inHg." and asks you to set this on your altimeter. Question is this, how did the instructor know it was 29.88 inHg when all the ATC said was 29? When the mission starts the pressure level is already set to 29.99 so I'm guessing the XX.88 part is quite important. Perhaps the ATC radio comms have yet to be fully finished? Its not really going to cause me any problems when landing, I would just like to know.

I guess so. Half way is easy to guess, so a bit less than that :D I knew it wasn't my imagination when I felt this indicator was missing, I remember it from the Lockon A10. I'm surprised they didn't combine it with the Flaps indicator for the "C".

Have you tried to ramp start with no controllers connected at all?

Post a track before you reinstall, that is quite a drastic measure for what is probably a basic problem.

I think the latest beta3 changes are to blame for difficulty reading the HUD. With Beta3 the Default Field Of View(FOV) was slightly zoomed out compared to Beta2. I have found this has made the HUD difficult to view/read. I know some people said they found the view in beta2 too close to the front, I did too, a bit too claustrophobic feeling. Maybe this is why they changed the default FOV. But what I felt needed adjusting was not the FOV but the actual seating position. The seat felt like it needed to be moved back an inch or so. Doing this would not affect the readability of the HUD as much as FOV changes. Also, too much adjusting of the FOV can lead to a fish effect when looking around which isn't very nice. But then again they know better than me what sitting an A10 might look and feel like.

heh heh very clever! thanks again Frederf and Dethmagnetic. I'm going to run through the landing tutorial again. I think have another couple of Qs relating to it that confused me. Hope mooshim doesn't mind me Hijacking their thread!

Thanks very much for that explanation Frederf. It helps with what I have read from the manual. I actually mucked up with what I was asking though :doh:. I was trying to ask how would you do an instrument landing at the airfields that dont have ILS or TACAN. But thanks again for taking the time to explain about the ILS approach. :thumbup: I will print it out and use it as a reference.

I'm having a similar issue, I have not tried disabling SLI yet. My issue is seeing a flickering terrain Wireframe across the ground when looking in the FLIR modes or the IR Maverick, do you get that? Haven't noticed building texture probs yet.

I was also wondering how you know what the ILS freq was for each airfield, so :thumbup: for this thread. I see though that only 3 airfields have TACAN or ILS capability. How do you do instrument landing at these airfields?

heh heh I'm surprised by people throwing around the "Simulation" analogy for this game, especially on this forum of all places :D It looks nice and is probably good for a laugh at a mates house, but I really couldn't enjoy it, given how used I am to playing proper racing sims.

I had an interesting experience where I was able to get into a UAZ and start the engine!... :shocking: then the game crashed.. hmmm I tried searching for other threads about this but no luck. Any one know if there is one?

nice pic I Stumbled upon

Dont forget the Quick Start manual Also, the quick start manual is really good (except for a few errors in the screens shots with labels). You can achieve a whole lot by reading that. It also makes diving into the full manual less daunting, it gives you a good reference point.

I downloaded and ran the Redistributable June version and installed. No error and sound working again. Thanks I recommend pointing people to that rather than the Web Setup which appears to have problems. http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=3b170b25-abab-4bc3-ae91-50ceb6d8fa8d

Like I said, I tried to update but it told me there is no need. Quote: "DirectX has determined that a newer or equivalent version of DirectX has already been installed already. No installation is necessary."

I just installed Beta3 on to a Beta1 + Beta2 patch installation. Everything seems fine except for an error message I have not seen anyone else report yet. I get the error when I go to load a mission, It starts loading and says "Can't init XAudio2. Please, update DirectX Runtime." I click "ok" and the game continues to load, but when I get to the cockpit I have no audio at all. I have tried to update DX but it says my version is the latest. I have Creative XFI sound card. Any ideas? DxDiag.txt

I would suggest Company of Heroes also. Absolutely amazing level of detail still astounds to this day. Also the amount of audio they recorded takes about as much HD space as a regular RTS lol.

Looks very useful and innovative! Thanks!:thumbup:

So far the profile is working ok for me, but I am only just starting to use a lot of the buttons so I may find something wrong yet. Pinkie switch is working fine for me, e.g. I can trim using it no problem. The only thing I had to change relates to this bit of Jack's instructions: For whatever reason, in BETA2 "A" is now "Autopilot" and "1" is "HOTAS Speed brake switch forward". So I switched both of these around I also don't think this step is needed as I believe that switch now works in BETA2

^ At the moment, that seems way too familiar :D:joystick:

Wow amazing video thanks, never seen anything like that. :shocking: