Mallard of Death

Just wanted to say that I have found what the issue was. When you revert from 2.5 to 1.5.8, the game enables "Use Virtual Headset" option by default. In 1.5.8 it seems it's draining your power, which is strange.

No. I haven't been updating nothing. But I must admit that I experienced the same issue almost 2 months ago. Had 1.5.8 installed. Updated to 2.5 early February. Did not like the performance in certain areas (aforementioned TGP frame-tanking in densely wooded areas and abysmal loading times). Regressed to 1.5.8 and my previous performance issues have been miraculously resolved. Then, a week ago, I upgraded to 2.5 hoping it was optimized better. Saw that it was not [still a resource hog (no pun)]. So I regressed again to 1.5.8. But now, I have the same original issue. 49-51 frames per second in cockpit on the ground during takeoffs, and while looking at certain directions. The strange thing, those frame rate issues present in 1.5.8 are not present in 2.5, yet 2.5 has frame rate issues not present in 1.5.8... ED should just optimize 2.5

Actually did that before I posted this. In fact, I reinstalled fresh. Tried with new, fresh settings and was still getting slow downs. The funny thing is, it happens only when I look in a certain directions, and it's very noticeable in cockpit. Like I said: Ran a 1.5.8, upgraded to 2.5. Then rolled back to 1.5.8 and got slow downs.

Hi. I have been testing the 2.5 upgrade and have found it not to be to my liking (funky visuals, bad frame rate drops while using TGP and flying low over wooded areas), so I rolled back the 1.5.8 version, and I got with ~17% decrease in performance. Let me clarify: Before 2.5 upgrade, my 1.5.8 was working rather swell, but after I rolled back from 2.5, the 1.5.8 got performance hit; 49-51 frames per second, prior to solid 60.

Oh, I owe you guys an apology. I have made a mistake: it's R-60 missile, not R-73.

I am using a whopping 0 mods! And whatever the version the R-73 is, it's useless. "helicopter temperature sign is lower." No way! I thought the decoy flares are just a visual distraction, like a fireworks. "Try to launch your first missile closer" Umm, I get shredded by 2 Mi-24 then.

I fly with Su-25 (not T), I have 2 R-73 Air-to-Air missiles. I see two Mi-24. I fire my R-73 at one helicopter. 80% of the time the missile misses (Mi-24 deploys decoys). 20% of the time the R-73 hits, it doesn't even leave a scratch on the helicopter. Most of the time, I get shot down by a damn helicopter. I remember playing this mission 3 years ago without Mi-24 being titanium-plated. What gives? Help! Note: I am using 1.5.8 version, since 2.5 works horrible.

With all due respect, that which you describe is not modeled in 1.5.8. In 1.5.8. I just have to destroy the radar (there is a radar system + 3 launchers) and I can buzz over the launchers at will. I know what I'm talking about since I did testing with Su-25T in the mission where you have to destroy a Buk system, in both 1.5.8 and 2.5, respectfully.

Too late. I rolled back 1.5.8. I didn't like how my frame rate in 2.5 goes from solid 60 frames per second to 40 when I use TGP/shkval to spot the targets in distance. Also, get this: in 2.5, the BUK SAM locks on and shoots missiles at me even after I destroy its radar.

Atrocious optimization.

It does not work. DCS does not recognize Nvidia Control Panel tweaks.

Wow! 2.5 improved some performance issues I had, but overall, it works awful. From 60 fps it drops inexplicably to 40-44. When in the woods, it goes to 30! And TGP and shkval are frame killers. Is it because it's beta or just awful optimization, or both, hmm...

What happened? The last time I played tut ung bombs, it was there and worked like a charm; now this?! Give me a break.

Got it! And I survived!! It's tricky and risky but it IS doable.

Well, if you really must know, I'm agnostic theist.

How do I survive emergency belly landing on a field?

I hate to whine, but even after this last update, there's still no fix...

Yes, and they work. But that's not the point. The point is that Su-27, F-15C and A-10A are all glitched planes. Since I'm a pi*s poor fighter pilot, I can't play custom missions, let alone campaign with efficiency; I wan't to make my own 'padawan' missions to practice dogfight tactics. Note: You know what's strange? If you play one custom mission, they try to CREATE your own FAST MISSION, the log book will update with correct flight hours and landings.

And after this latest 3,2 GB update - still no fix! Thanks a lot ED. :(

OK, so after the last couple of patches (since Su-27 add-on) I've been (thoroughly) testing FC 3, and I've come to conclusion that pilot profile log does not update after you fly in your generated missions, or so called 'CREATE FAST MISSION'. Now, when you fly a mission that's found in the MISSION menu, your LOGBOOK does update with your flight stats: flight hours, landings and ejections. Don't get me wrong, I really like this simulation, and I'm not whining, I just want to see that someone else has noticed this rather strange issue. Note: This is the issue that afflicts only Flaming Cliffs 3 and not A-10C Warthog, e.g. P.S. Sorry mods, I know I've made a similar topic on Su-27 thread, but this issue affects Flaming Cliffs 3 birds.

Thank you sir for the reply. BUT, I have to disagree. Log time and landings were working fine, that is - the stats were being "logged". After the latest update it all went to hell... And as I said, DCS: A-10C Warthog log works fine... you can land and you can muster flight hours. It is Flaming Cliffs 3 that HAS that issue. I swear to God I'm not lying. Replays are broken since like forever.

OK, so I've figured out that this is FC 3 issue, and not A-10C Hog. Can I have confirmation from someone, please? I really dig FC 3, and new Su-27 flight dynamics are AMAZING!

Just finished testing Warthog module Landing log: check Engine shutdown: check Flight hours: check

After this last update, my mission logs don't/won't register my landings nor my flight hours. I'm stuck with my previous flight hours and my [previous] number of landings. But the strange part is when I land and taxi to park my bird, I shut down engines and electronics and the mission log registers engine shutdown??? I'm playing Flamin' Cliffs 3, testing Su-27 new flight model, and the flight model is good. I will try DCS: A-10C Warthog and test to see is this issue also affecting other DCS modules.

Gods, I know how you feel! I had some pretty awesome tracks, yet now, they are corrupted. Bummer beyond bumming.