Trainzak

Is it even possible to aquire lock onto target near maximum range of Maverick? I always struggle with slewing around target waiting for lock, which comes somewhere half of the range bar. How am I supposed to attack SAM then? I would be dead three times before I could lock Maverick and shoot him down! I also tried setting SPI via TGP and then slewing MAV to the current SPI, but it doesn't make any difference, I still have to slew around, it doesn't lock to the target at all. Also, which type of Maverick is easier to lock onto target in perfect visibility? Infrared or TV?

Looks like the only possible solution is wait for the open beta of 1.2.6. I hope it won't take too much time, because I really want to finish my Black Shark campaign and start new A-10C campaign... Now I can only sit and wait.

It began with DCS Huey. Now you want DCS C-17 and soon we'll have DCS Cessna 172.

My personal guess of upcoming modules for DCSW: 2013: Mi-8MTV2 2014: MiG-21Bis A-10C Warthog 2 Flaming Cliffs 4 Hawk 2015: Black Shark 3 F/A-18C F/A-18E 2016: Flaming Cliffs 5 Eurofighter F-15E I believe there's quite big chance that it will look something like this... :smilewink:

I'm waiting more than a month just to start playing single player campaign, and have something as a reference in debrief and in the logbook. No, I don't think that this obvious bug that is affecting 100% of players and 100% of playtime shouldn't be covered in the hotfix.

Do you have some insider information, or you're just guessing? :)

What do you think? Can we expect DCS Autumn Sale around 20th September? I'm really considering buying FC3, but the price is a little bit high for me... So tell me - should I buy now or should I wait? :helpsmilie:

When the price was increased? I didn't even notice.

I would also prefer some DCS level simulation of a modern russian jet (or bomber). It doesn't have to be Su-27SM, it could be something that ED can reproduce. Although I'm looking forward to Project 18, I would also like see a nice aircraft with red star.

If I recall correctly, there used to be nickname of current pilot in the initiator field, now there is only "Player"... Maybe it's one of those issues.

It seems that all development is focused on Steam now. But I still can't understand why developers are so blind and constantly overlooking most obvious bugs... Really, can someone tell me how long I should wait to be finally able to play singleplayer missions and campaigns? Is this a forum or just a place to complain with no consequent action? Is there even some kind of user support?

Same here, I'm VERY dissapointed. :thumbdown:

The issue remains even after applying today's hotfix! This is starting to get ridiculous...

I'm quite modest, I would be OK with announcement of 1.2.5 update 4, which would finally solve "No kills in debriefings" problem...

I don't get any kills even when mission starts in air. And even if I did, it's not satisfactory solution.

Wags in the last weekly update stated, that Update 3 would be the last update for 1.2.5. Do you plan to fix this issue in another hotfix, or shall we wait couple of weeks for 1.2.6?

Sure, but it's similar to those I have posted before: # -------------- 20130813-091959 -------------- # C0000005 ACCESS_VIOLATION at F350C3F0 00:00000000 00000000 00000000 0000:00000000 F350C3F0 002FF2C0 0000:00000000 ?QueryEditor@viLight@@QEAAPEAVLight@Graphics@@XZ()+0 400FA7F3 002FF3E0 0000:00000000 401014D4 002FF480 0000:00000000 F00E6026 002FF4C0 0000:00000000 ?open_fire@wGun@weapons_gun@@IEAAXXZ()+86 F00E62E9 002FF4F0 0000:00000000 ??4wShellGroup@@QEAAAEAV0@AEBV0@@Z()+C9 F00E2CE9 002FF530 0000:00000000 ??1?$wActivityGroupEnvelope@VwShellGroup@@VwShell@@@@UEAA@XZ()+299 F3988561 002FF5C0 0000:00000000 F3988A1B 002FF610 0000:00000000 401B4FE9 002FF6A0 0000:00000000 401B7A9D 002FF700 0000:00000000 401CDC84 002FF730 0000:00000000 401CDB5B 002FF760 0000:00000000 40262A28 002FF7D0 0000:00000000 40263FDE 002FFDD0 0000:00000000 40266C2B 002FFE80 0000:00000000 7726652D 002FFEB0 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 7739C521 002FFF00 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

The patch was released yesterday and doesn't solve this problem.

Irrelevant note... Selected country have no influence to counted kills in debriefing at all...

I can confirm that random crashes are still present in 1.2.5 update 3.

In 1.2.5 Update 3 still no kills in debriefing when clicking at "My victories", although it should be fixed, according to changelog!

Probably he's referring to this: http://forums.eagle.ru/showthread.php?t=110684 (I get a "score" at the end of the mission, but no kills) Just tested and I have still no kills in the debriefing, and no kills at logbook.

New update 3 for 1.2.5 just came out, I presume that memory leak hasn't been fixed yet, right?

+1 This should be the highest priority as it totally ruins Single Player experience.