Jump to content

PE_Tigar

Members
  • Posts

    306
  • Joined

  • Last visited

Everything posted by PE_Tigar

  1. SoulJah - I stand corrected - it is as you've said it of course, I've mixed up the two. I got my CPL in the Czech Republic and it's exactly the same, TL is given in ATIS and seems that it's a practice in Europe. As ATIS in the US does not contain the info on TL, I'd guess that it's fixed at some value (like FL180?) the same way as the transition alt.
  2. Smokin Hole, I've got a CPL with IR, you don't have to explain to me which is which (BTW QNH is defined as local air pressure normalized to the MSL, but whatever). SoulJah - thx - I guess it would be great if ED could fix ATC to give us QNH rather than QFE, would be more useful. BTW - transition altitude vs. transition level - transition alt is variable, given by ATC, in thousands of feet - when climbing you change to QNE at that value. Transition level - given in the chart, you switch to QNH from QNE at that level. So when I approach say, Batumi, and the ATC dude gives me QFE it's pretty much useless - QNH would be much better, I have radio altimeter for getting the height above the terrain.
  3. I hate to sound hissy, but here's my experience with ATi/AMD (In the last few years I've repeatedly fooled myself into thinking that they offer better value for money - I admit being a dumbass). I've owned Radeon 9800, 2x4850 in CF, 5870 and finally a 6970 now. Here's my experience with chronic problems, with all ATI/AMD products I've used: - Terrible performance in FSX. Granted, it's abandonware, devs screwed up, but still it has a huge market behind it. Never improved, numerous reports 100s of people sent to ATI/AMD - nothing. - botched OpenGL support for Il-2 in most Catalyst revisions. Can be solved rather easily but still a nuisance. - in DCS, RoF etc. - need to tweak and re-tweak to get the performance right. HDR in DCS - off limits. Crossfire in DCS screwed up. - in Il-2:CoD - no AA. Again, the devs screwed up big time, but the fact of the matter is that nVidia offering is better supported or performs better. - X-Plane - mediocre performance all around. Random CTDs. Can't put a finger on it, but would expect better performance from high mid-range/top of the line cards I've been using. So, all in all, whatever the reasons, I'm done with them as they don't seem to notice the flight sims as a market nor flight simmers as customers. I do recognize AMDs offerings as technologically more advanced, but what good is it if their software support is so abysmal?
  4. Just one short Q about Qs :) - why are all ATCs in DCS world using QFE? I know QFE is normal in Russia but my impression was that QNH is the standard in NATO countries (maybe I'm wrong).
  5. 6970, 11.4 Catalyst here and have the same problem too.
  6. What my team finds itself doing a lot due to this is setting the NET settings on TAD to Group ID and Own ID as we want it (one group, and then Own IDs as per our plan).
  7. 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?
  8. 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.
  9. 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.
  10. 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...
  11. 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 :).
  12. 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.
  13. 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.
  14. 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...
  15. 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...
  16. 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.
  17. 004s? Out of curiosity, which aircraft did you work on with these engines and where?
  18. 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...
  19. 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.
  20. 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.
  21. @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.
  22. 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.
  23. 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.
  24. 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.
  25. 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 :).
×
×
  • Create New...