Jump to content
Sign in to follow this  
Feerless

Arma 3 Crashing Like Crazy

Recommended Posts

I've been playing quite smoothly multiple sorts of missions past week, until today, playing both custom made missions and other missions, we had crashes (or performance issues, but mostly crashes) as soon as certain vehicles exploded.

Share this post


Link to post
Share on other sites

Is there any official statement on when this might get fixed? Why not rollback to previous "stable" v. until this CF gets sorted? For the future, i really hope we wont see to many of these friday-patches....

Share this post


Link to post
Share on other sites

I'll add what I've noticed: Myself and 4 others hook up in Multiplayer (makes no difference whether a vanilla MP map or a scenario from workshop).

Regardless of who hosts the game, 25% of the time blowing up a vehicle (or having your own vehicle blow up) often causes one, two or all of us to crash. The crash is usually not to desktop...but a frozen screen. Ctrl+Alt+Del to desktop reveals the "Arma 3 Has Stopped working" dialog. Also, when only one or two players crash the other players all note that an ingame message says something about the player being kicked because of a "Steam Ticket" failure of some kind.

Only one player in our midst didn't crash. He has Nvidia card and changed the setting from auto-select to cpu.

Edited by Digital_Aura

Share this post


Link to post
Share on other sites

Since the patch a crash every time after ten minutes or so... not good at all!

Same here, me and my pal on teamspeak seem to crash out at the same time. noticing a lot of battleye kicks as well.

Edited by KrIxXuS

Share this post


Link to post
Share on other sites

I'll be on a server and BAM suddenly half a dozen, or a dozen, etc. people all get disconnected at the same time. When asked, all of them crashed. Crash in this case defined as a frozen screen which forces you to Ctrl-Alt-Del upon which you see the "ArmA 3 has stopped working" message. It's a serious pain in the arse.

Now, to test a theory I have, I shall now attempt to summon the Lord of the Bugs.

*Waves hands over the keyboard, infusing it with magical power*

*Dwarden, Dwarden, we summon thee in an attempt to seek help from you, the almighty tired/raggedy man who appears from nowhere in an invisible box, like The Doctor of ancient folklore. When we find ourselves in times of trouble, we the people come to you. Seeking words of wisdom, help us please.*

Share this post


Link to post
Share on other sites

Same here, since the patch I crash with frozen game. It always hits multiple Players on the server at the same time. The only common event we could find was a helicopter crashing.

I never had a crash before and I am playing since Alpha. So it must have something to do with the last patch.

Share this post


Link to post
Share on other sites
Same here, since the patch I crash with frozen game. It always hits multiple Players on the server at the same time. The only common event we could find was a helicopter crashing.

I never had a crash before and I am playing since Alpha. So it must have something to do with the last patch.

We have noticed it happening on invade & annex, as soon as there is an explosion with a chopper with people in it alot of players get kicked at the same time (5-10 players), ive had this also 2 times on 1 evening, guy drove a truck in a chopper resulting in the chopper to blow up and kicking everyone in or around it.

2nd time was a in air explosion by a AA missle kicking everybody in the chopper.

Send with Tapatalk.

Share this post


Link to post
Share on other sites

This is the general error that i get. Along with many others it is an issue with the Physx3_86.dll. Most of my crashes happen right after an explosion of a vehicle or large shell within close proximity. I know many servers whos admins have stated this is the cause of the crashes.

I am running 12gb DDR3 GSkill ram

AMD FX8350

Radeon HD 7850

MSI 890FXA-GD70 Mobo.

Faulting application name: arma3.exe, version: 1.2.110.424, time stamp: 0x52440456

Faulting module name: PhysX3_x86.dll, version: 3.2.4.1, time stamp: 0x5164246f

Exception code: 0xc0000005

Fault offset: 0x000dedb7

Faulting process id: 0x14c0

Faulting application start time: 0x01cebe6e3bc4801f

Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe

Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Arma 3\PhysX3_x86.dll

Report Id: e446e567-2a65-11e3-89c3-6c626deac992

Share this post


Link to post
Share on other sites

Yes, myself and others on a server have all crashed at the same time when there was a large explosion nearby.

Share this post


Link to post
Share on other sites
Yes, myself and others on a server have all crashed at the same time when there was a large explosion nearby.

I checked the 1.03 build last night. No crash on mp even with 10 vehicles exploding while using scope. here's hoping hotfix happens soon.

Share this post


Link to post
Share on other sites

There is no fix everyone. If you want to speed up the process send BIS your rpt and dump files as Dwarden already stated.

30-09-2013

EXE rev. 110511

Size: ~26 MB

We are working on investigating the frequent MP crash related to PhysX. It’s proving hard to find and involves external libraries. We hope to be able to hotfix 1.02 if we do find it soon.

Note: Scenarios now show the map briefing even when no briefing.html (outdated method) is present

Increased Independent Ghillie suit weight and capacity to resolve issue with Spotter not having a Claymore

Firing Drills: map briefings disabled where they should not be

Added: Missing radio track

Sound: Improved MP 3D sound playback

Fixed: Campaign menu did not refresh when getting back from a scenario

Sun lens flare occlusion tweaked

Protocol messages have different visualization than narrative messages

Fixed: Occlusion queries when using PiP

http://forums.bistudio.com/showthread.php?149636-Development-Branch-Changelog/page14

Found this in the feedback / issue tracker...as it relates to the crashing/ physX issue:

dazhbog (developer)

2013-09-30 16:39

Hey guys, we got your crash reports and we were able to reproduce the issue in our environment. It's obviously the biggest priority for us at the moment and we will deliver a fix ASAP.

Thanks for your patience :).

01-10-2013

EXE rev. 110573

Size: ~604 MB

We have finally found more useful debugging information for the main branch MP PhysX crash. We are still hoping to hotfix it once we have a confirmed fix.

Fixed: Slammer accelerating too fast

Fixed: Slammer should have 5 forward gears

Fixed: Scorcher jumping sometimes

Improved: Varsuk driving physics

Improved: Physics setup of Panther

Tweaked: 120mm cannon firing effect

Fixed: Conversation wasn't terminated fast enough after one of the participants died

Cinema border function is now spawned (can be also ‘called’ by designer)

Fixed some discrepancies between vest models and their capacities.

Introduced some diversity amongst vest types in their weight and capacity.

Independent diver has an adjusted outfit

Several bug fixes for Altis

Entering Offroad from the back no longer results in teleporting to the front

Fixed: http://feedback.arma3.com/view.php?id=14519 (Treat yourself was not localized)

Fixed: Development build indication in the main menu

Tweaked: Protocol chat messages are a bit lighter

Fixed: Binoculars were invisible in inventory

Chat messages use narrative visualization instead of protocol

Share this post


Link to post
Share on other sites

This thread is a classic example of how NOT to report problems and get a resolution. First, it just opens you up to people spending their own personal time telling you that it's only your problem and not one with the game. That's without any adequate information to make that allegation. Second, and most importantly, there is a Feedback / Bug Reporting system in place where you should submit (or add to an existing) bug report.

There are a lot of us experiencing the PhysX3_86.DLL crashes, and there are multiple bug reports on it. BIS has made the statements first that they were investigating it (and that it was a high priority) and second that they had been able to duplicate it (which is the first step to developing a patch). None of those things happened because of this thread.

Share this post


Link to post
Share on other sites

Thread Cleaned Up.

@all please post constructively when replying.

Thanks

RK

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×