MagnumHB

1.1.1.1 had plenty of random disconnects as I recall. They just took longer to occur.

Well known issue. See: http://forums.eagle.ru/showthread.php?t=94724

Good news. Let's hope indeed.

Thanks for your diligence Tyger. Hopefully we'll get some feedback soon.

Let's get the core engine and multiplayer stable first.

Tyger, I was able to connect to Lynx with no issues earlier tonight at 6 PM EST, but I just got this same CTD when trying again at 10:15 PM EST. I believe the mission had been running about 2 hours when I tried to connect this second time. Looks like the next update can't come soon enough.

Where did you see this and what were you doing? SP or MP?

There was even an update post about it: http://forums.eagle.ru/showpost.php?p=1604355&postcount=2

I noticed that several missiles fired in an MP session seemed to fall infinitely after exhausting their fuel and missing their targets. I managed to grab a screenshot (attached) of a Sidewinder at around -90000 feet. My game soon crashed, with the missile at what I estimate to be about -100000 feet. I suspect this bug only manifests in MP, as I also tried to replicate this in an SP session, but was unable due to the missiles correctly exploding on impact with the ground. I believe this log is associated with the crash: # -------------- 20121114-032813 -------------- # C0000005 ACCESS_VIOLATION at 3FCFCFAE 00:00000000 00000000 00000000 0000:00000000 3FCFCFAE 0024EE10 0000:00000000 3FC940D4 0024EE80 0000:00000000 3FC927BE 0024EFE0 0000:00000000 3FC8925E 0024F010 0000:00000000 E8A38721 0024F0A0 0000:00000000 E8A38BEA 0024F0F0 0000:00000000 3FD6F4D9 0024F180 0000:00000000 3FD71DED 0024F1E0 0000:00000000 3FD899B4 0024F210 0000:00000000 3FD898A9 0024F270 0000:00000000 3FE108E8 0024F2E0 0000:00000000 3FE11D28 0024F7D0 0000:00000000 3FE1471F 0024F880 0000:00000000 774B652D 0024F8B0 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 7774C521 0024F900 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 Faulting application name: DCS.exe, version: 1.2.2.7204, time stamp: 0x509e53ae Faulting module name: DCS.exe, version: 1.2.2.7204, time stamp: 0x509e53ae Exception code: 0xc0000005 Fault offset: 0x00000000002acfae Faulting process id: 0x107c Faulting application start time: 0x01cdc216671a1975 Faulting application path: E:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe Faulting module path: E:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe Report Id: 528478eb-2e0b-11e2-a81a-1c6f65d54a89

I have an i5 2500k @ 4.2 and a 6950, and I have the same issue. In my opinion, this is one of the most critical stability issues remaining in the game at present for the majority of users.

Any word on possible fixes for the blue smoke, explosion effects, and general framerate for those of us that haven't had a chance to try it yet?

According to the relevant Wikipedia pages here and here, your father would have indeed been a part of the 354th Tactical Fighter Wing. The 354th TFW was then further broken down into three tactical fighter squadrons, the 353rd, 355th, and 356th. Without further information however, it's impossible to determine which of these individual squadrons he would have been assigned to. You would most likely be safe with a 354th patch for the entire wing though.

Use a little imagination, and it easily translates to Afghanistan. That's my plan, anyway.

Be sure to run the manual DCS Update in the Start Menu (again, if necessary). The current version (as of yesterday, anyway) is build .6288, and this issue is fixed as far as I noticed.

It seems like, at the very least, it fixes the mouse focus issue and the need to Alt+Tab at the beginning of a mission.

Those things are very useful for more complex and obscure bugs. However, this issue is easily replicated by simply dropping a CBU, as I said. If I were at home, I'd love to post a track, but I'm not. This issue appears in both SP and MP, and there isn't a game crash in SP, so most of those logs don't apply anyway.

I feel obligated to point out that even though the attitude in this thread got off to a bad start, the undeniable fact is that those weapons do completely destroy performance when used thanks to the new, not fully optimized explosion effects. Simply drop a CBU-87 and observe the ensuing slideshow. I would hate to see an obvious issue get overlooked due to a less than stellar forum post.

I've never particularly cared for this effect either. Understandable that it's not a priority though.

Thanks for the update c0ff. Can you report what updates were actually made in .6055 though, since nobody seems to know?

Kuky, this isn't about losing a frame here or there, it's about a reduction to unplayable slideshow levels in the worst cases. The simple fact is that by any reasonable standard of performance, these effects are not quite ready for the public spotlight yet. Of course we all want new features, but not at the expense of playability.

Did you not notice that the explosion effects received a massive overhaul when World was launched? Prior to that, A-10C and BS were using LO-era effects (or something derived from them), which while not as fancy, were far superior to what we have now in terms of gameplay.

I doubt it, or at least completely, because the CBU-87 was a problem in 1.2.0 as well. The new particle effects in World seem to be terribly optimized so far.

I'm with YoYo as well. The new World effects should never have made it into a public release in their current state. The impact on gameplay, particularly with the CBU-87, is just so unreasonably severe. Once the general framerate loss is resolved (in the very near future hopefully), I can see this becoming a user "favorite" issue to complain about.

Looks like Wags just edited his post to include this.

The last few releases have been in batches of multiple updates including patches and brand new betas and products. This is simply what people are expecting again. Most people, including myself, I think would be pleasantly surprised to see a patch for World and/or A-10C released earlier than FC3. That's just my read on the situation, anyway.