PE_Tigar

I second that, I think I've whacked several Bradleys and a (very unfortunate this one) HQ M113 but frankly, with no TGP in conditions like that I was firing at what would best be described as white blotches. Now I did realize I can change the loadout, so I'll probably restart the campaign with TGP in each loadout and see how that goes. And here are some other observations: I'm at mission 5, and the last three missions I've been flying alone - the rest of my flight just stays in the hangars or a couple of meters in front of them. It's rather unfortunate that ED obviously doesn't have airfield ops nailed down yet, hope that this will be solved soon. Also, although I've killed a number of (enemy and allied :/) ground targets, my A/G kills count both in campaign and in my log are still 0 (in mission debrief they're recorded correctly). Is this a known issue? Anybody else has it?

In Navigation mission I can't even get to that part, it gets stuck at the straight and level flight at 16k feet telling me to "Keep my speed at 300 KT" while I can only manage 280 IAS on that altitude with full throttle. BTW, maybe I should RTFM (didn't - seldom do even for the real planes :D), but seems to me that the autopilot is unable to fly to steering points or hold the flight path.

Actually, LASTE switch when operated activates "Elevator Emergency Disengage" switch to the "right" position. Possibly a problem with mapping or smt. Other bugs in the startup training mission: 1. Canopy close switch unserviceable (right click+hold doesn't close the cockpit). 2. Fuel truck stuck beneath the right flap. 3. Battery pwr switch highlight stays on. 4. The LASTE switch issue.

You're talking T/W in which conditions - AA/AG loadout?, full fuel/no weapons? Because, obviously, if you have a much lighter a/c, its t/w will go down much more steeply with any loadout. From what I heard from actual Gripen pilots: - vs. Luftwaffe Phantoms it was not even funny - vs. Rafale - good in turn, can't keep up in the vertical Otherwise, much praise for the bird, it has many other good sides to it that can't be evaluated by performance figures only, like simplified maintenance, great level of autonomy, able to operate from improvised strips etc...

The one good reason to close the crossfeed would be to isolate a ruptured tank or a ruptured fuel line. I don't know how the real Ka-50 SOPs go, but in large jets crossfeed is usually closed, unless there's significant fuel imbalance. I don't know why, probably not to loose all the fuel if there was a large leak in fuel lines on one side. To me it seems that there are two things to consider - whether you want to keep the fuel balance and have to do another task when the fuel tank is ruptured or the engine shut down (on by default, xfeed clsd when tank ruptured) or you want to continuously check for fuel imbalance, but have more safety for the ruptured tank scenario (xfeed clsd, open only when needed). In large jets it makes sense keeping it closed, because there's seldom such imbalance that requires actually opening the crossfeed. Again, I may be wrong, because I know it only in theory, haven't got any type ratings yet :).

Pirate and the original poster - which brand graphics cards do you use? I have 2x Asus 4850s and have had overheating problems with the older one - BIOS flash solved the issue.

FWIW, I've been running Win 7 64-bit for several months now and had little or no problems after ATI has published an officially supported graphics driver. And it's in RC stage still, there's quite a bit of time for improvements until the release in October... Looking forward to testing that 64-bit executable.

After 10 hours spent on a real simulator (with 20 kg forces on controls), I'm inclined to say that the hydraulic force feedback may really be the best thing for a good simulation if it's able to produce the same forces as you encounter in real aircraft. Unless, of course, you're simulating an F-16 and other airplanes with tensometric sidesticks, control forces there are not an issue. Bottom line, for simulations of non-FBW aircraft this will be a great thing. Oh, and sturdiness etc. - two thumbs up for that! Never was a fan of planned obsolescence...

Stop using antivirus software. I've been using PCs since 1994, building PCs since 1998, never used antivirus software, never had a virus. My main problem in my work PC is the centrally managed antivirus, it's intrusive and blocks completely random stuff left and right...

All three things listed should help, but the most critical (and it costs you nothing to try with Win7) is the OS, second thing is the new mobo, the soundcard - don't bother, X-Fi PCIe will work as well as Asus one, under the assumption that the new mobo is able to push all the PCIe bandwidth available.

004s? Out of curiosity, which aircraft did you work on with these engines and where?

Found the explanation - it has something to do with OpenGL support in Win 7. For nVidia users there's a cure, search for OpenGL 3.0 beta drivers from nVidia, that should do the trick for you. Nothing like that exists for ATi :(. One Hz difference doesn't do a thing, I managed to force 60Hz through the Catalyst Control Center, didn't help. The OpenGL thing is in known issues of the ATi Win7 beta driver, should've read the notes earlier...

I think I got a couple of errors like that, and if I recall correctly it was UAC-related. Try setting "Run as Administrator" option in the compatibility preferences for both the launcher and the game .exe itself and turning off UAC.

That's strange, must be some mysterious graphics setting that we're not aware of. What kind of monitor do you have? My Samsung for some strange reason is working on 59 Hz and I can't get it to stick to 60 Hz. Just weird.

@Lobo_63 - thanks mate, this is what I needed, I had crackling and sound distortion in DCS:BS also with official drivers for my ZS @Zaelu - do you have ATI graphics, W7 64-bit? I'm using the same workaround, and it's annoying as hell.

Well, since those certain conditions include mist/fog/precipitation and OAT below a couple of degree C (common in the Caucasus), and you say that EKRAN can't be relied upon 100%, we do need OAT indication then.

Ah yeah - skimming, my bad, I sincerely apologize. My TIR SW crashed once so far, but I'm a danger-lovin Win7 beta user, I kinda expect it with no official support. All out of ideas then. If it was me and my PC I'd be reinstalling the OS and the rest now, I'm pretty impatient when it comes to issues like this.

Nobody mentioned an obvious, though frequent omission - did you try and update the game support in TIR4 Pro software? I had to do it with mine to start working.

I guess it's all different between helos, large turbine airplanes and small GA, but I'm flying (GA airplanes) a lot in marginal VFR with a lot of haze and low clouds in wintertime and let me tell you, I am very much paying attention to the OAT gauge. That said, though, what would really help would be an explanation of how the EKRAN knows when to tell you to turn the de-ice on. If it's just interpreting the OAT input then we don't need the OAT gauge. If there is a separate ice detection system then again, we don't necessarily need it - it feeds into the EKRAN. This is in the sim. In real life, I wouldn't fly combat missions in icing conditions without an OAT gauge operational - even if it's "just" a backup. Of what kind that ice detection system would be, I wouldn't know, I'm in ATPL training now and never heard of such a system, but we're mostly focused on B737 Classic and A320 family for systems, and they have pretty rudimentary ice detection equipment. A320 has basically a small rod with a light shining on it, visible from the cockpit. Funny thing is that the light is in MMEL and you can't fly with it inop :).

Okay, got it to work. I installed 8.12 vista driver (manually, first removed catalyst drivers, then through the device manager, automatic installation won't work). Now I have more or less usable GUI, though it does flicker when in full screen and when I'm moving the mouse around. So I guess it's Catalyst after all... zaelu, I also lost the activation, same thing here bro... ah what can you do, you pay for not paying attention... EDIT: Installed the Win 7 preview Catalyst - and no change (but the GUI is not white anymore). And the GUI flickering gets worse if I turn off Aero! Plain weirdness. Catalysts are flaky, guess I'll be buying nVidia next... @Lobo - thx for the link, Jesse's util works like a charm!

As a budding CPL/IFR pilot myself, I'm amazed to see the job that Eagle did on RNAV and ADF modelling, as well as on the avionics and turbine engine management. Such a shame I won't be able to put much of that to work in real life :). Otherwise I'm enjoying it greatly!

Same here. I guess it's the vid drivers, I've tried 8.12 for Vista, ATI Win 7 beta and the ones that came through the Windows Update. Same thing. Tried disabling the Aero (both through the shortcut options and manually) - same thing. The game itself runs great otherwise, and the Multiplayer GUI works well. Weird, but my instinct tells me it's ATI's fault, their drivers are flaky as hell. Some specs: C2Duo something something (round 2GHz) R4850 512MB 4GB DDR2 800 all on Win 7 Beta 7000 etc. Oh, and can somebody tell me shortly how to set the process affinity so as to increase the FPS? Thanks in advance :).

Off the top of my head, J-35 Draken has been sold to Austria, Denmark and Finland. I can't recall any Viggen sales though, and Austria also used Tunnans.

The NATO-compatible export version is made in cooperation with BAE Systems, who handle all the NATO-exclusive equipment. But for Venezuela it wouldn't be an option I guess.

Wrong--sold to Czech Republic, Hungary and South Africa already.