vredesbyrd 10 Posted September 29, 2013 You know what would be nice? - If BIS acknowledged this issue and made light of the fact that they are doing something about it.....maybe through some kind of feed where they give some small insight in to the issues they are actively working on? Just a suggestion. There are a lot of angry people who (thankfully for the integrity of the forum) haven't yet found their way here to kick off and moan - Although some have. I'll also echo something said earlier: Don't patch on a Friday. Share this post Link to post Share on other sites
docbrown 1 Posted September 29, 2013 patience... take a look at the feedback tracker. some tickets regarding physx crashes since 1.02 have been assigned and upgraded to high priority. its the weekend, take a deep breath and play outside. Share this post Link to post Share on other sites
l etranger 5 Posted September 29, 2013 (edited) Just parachute a group of AI many time, and you'll get the crash for sure. Or you can try out attachto an object and make the attached to collide with a physx object. Edited September 29, 2013 by L etranger Share this post Link to post Share on other sites
bvrettski 10 Posted September 29, 2013 This is incredibly bad...and extremely frustrating. How and issue like this can persist for so long (since Alpha) and not be properly addressed speaks volumes about the state of the game they released. Since the patch I am seeing half the players crash from the server at any given time and its definitely not mission dependent as I experienced it across the board on a half dozen different missions and servers. Congratulations all...and welcome to the real Arma3 beta test program...:( Share this post Link to post Share on other sites
chlywly 10 Posted September 29, 2013 Has been crashing for me every 10-15 minutes after last update, using GTX TITAN win7 x64 latest Nvidia BETA drivers. ---------- Post added at 03:28 AM ---------- Previous post was at 03:26 AM ---------- Another member of the ZiiP community thinks they may have tracked down the source of the crashes.It is anecdotal, but he has only crashed out due to the Physx bug when he has been in the proximity of an explosion, and from memory, I remember hearing or seeing explosions most times I've crashed out. In other instances, where I have not witnessed explosions, other members of the community in close to medium proximity have done and have immediate crashed out, along with most, if not all, of the players in that particular area of the map. I must point out, this is happening in Wastelands in Multiplayer - The same community member who has pointed to explosions has been on an invasion server for most of today without any crashes despite more explosions than a Michael Bay movie. I also played nearly an hour of SP last night after all the crashes made me give up with MP and did not have a crash. Sharing in hope of being helpful, and I've pointed out that the theory is based on anecdote - Refrain from throat jumping please :) I can confirm this, I feel like I've made myself including many others crash off of multiplayer servers from explosions caused by my Tanks.. Share this post Link to post Share on other sites
bvrettski 10 Posted September 29, 2013 Dear BI..I hope this helps. With a little analysis you will see a pattern forming... 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: 0x001521cb Faulting process id: 0x1060 Faulting application start time: 0x01cebbb7bd7a58d6 Faulting application path: G:\Steam\steamapps\common\Arma 3\arma3.exe Faulting module path: G:\Steam\steamapps\common\Arma 3\PhysX3_x86.dll Report Id: ad4f7c61-27ab-11e3-9717-50e549bcaffb 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: 0x000decc0 Faulting process id: 0x126c Faulting application start time: 0x01cebbb88c0fc1d4 Faulting application path: G:\Steam\steamapps\common\Arma 3\arma3.exe Faulting module path: G:\Steam\steamapps\common\Arma 3\PhysX3_x86.dll Report Id: 9b9a9bca-27b7-11e3-9717-50e549bcaffb 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: 0x00143d75 Faulting process id: 0x16c4 Faulting application start time: 0x01cebbc561a32181 Faulting application path: G:\Steam\steamapps\common\Arma 3\arma3.exe Faulting module path: G:\Steam\steamapps\common\Arma 3\PhysX3_x86.dll Report Id: 8af1c618-27d2-11e3-9717-50e549bcaffb Faulting application name: arma3.exe, version: 1.2.110.424, time stamp: 0x52440456 Faulting module name: arma3.exe, version: 1.2.110.424, time stamp: 0x52440456 Exception code: 0xc0000005 Fault offset: 0x00c92027 Faulting process id: 0x116c Faulting application start time: 0x01cebc55a4fa8e25 Faulting application path: G:\Steam\steamapps\common\Arma 3\arma3.exe Faulting module path: G:\Steam\steamapps\common\Arma 3\arma3.exe Report Id: e760a3c4-2848-11e3-975b-50e549bcaffb 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: 0xed8 Faulting application start time: 0x01cebc585f49f3a9 Faulting application path: G:\Steam\steamapps\common\Arma 3\arma3.exe Faulting module path: G:\Steam\steamapps\common\Arma 3\PhysX3_x86.dll Report Id: 88e49477-2853-11e3-975b-50e549bcaffb 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: 0x000decc0 Faulting process id: 0x448 Faulting application start time: 0x01cebc60ba1c49ca Faulting application path: G:\Steam\steamapps\common\Arma 3\arma3.exe Faulting module path: G:\Steam\steamapps\common\Arma 3\PhysX3_x86.dll Report Id: 35f43621-2856-11e3-975b-50e549bcaffb 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: 0x000decc0 Faulting process id: 0x3b0 Faulting application start time: 0x01cebc780fca1a9b Faulting application path: G:\Steam\steamapps\common\Arma 3\arma3.exe Faulting module path: G:\Steam\steamapps\common\Arma 3\PhysX3_x86.dll Report Id: 09ae6369-286f-11e3-975b-50e549bcaffb 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: 0x000decc0 Faulting process id: 0x1354 Faulting application start time: 0x01cebcb0a07f592e Faulting application path: G:\Steam\steamapps\common\Arma 3\arma3.exe Faulting module path: G:\Steam\steamapps\common\Arma 3\PhysX3_x86.dll Report Id: 8b5a7033-28b1-11e3-975b-50e549bcaffb 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: 0x000decc0 Faulting process id: 0x12c8 Faulting application start time: 0x01cebcbea12b209f Faulting application path: G:\Steam\steamapps\common\Arma 3\arma3.exe Faulting module path: G:\Steam\steamapps\common\Arma 3\PhysX3_x86.dll Report Id: 0d2a6c10-28b4-11e3-975b-50e549bcaffb This represents 2-3 hours of attempted play.... For more info and expanded definition see also "unplayable." Share this post Link to post Share on other sites
vredesbyrd 10 Posted September 29, 2013 patience... take a look at the feedback tracker. some tickets regarding physx crashes since 1.02 have been assigned and upgraded to high priority. its the weekend, take a deep breath and play outside. Well, working a 60/70 hour week as I do, I feel I deserve to make use of the expensive gaming hardware and games I have bought to enjoy in my down time. I feel justified in my annoyance that the game is broken during said down time - Should it have been broken during a week day, my impatience and irritance would be less so because I would have no time to play any way AND BIS studios would be immediately there to see the issues and fix them. Just saying - Some of us have to plan this stuff in and it's frustrating when something like this happens. Share this post Link to post Share on other sites
markocro 66 Posted September 29, 2013 also getting crashes physx3_x86.dll now but didn't had any since alpha, things i changed - bought new graphic card 7950 HD and change settings everything to max, i crash at every server Share this post Link to post Share on other sites
Austintatious 10 Posted September 29, 2013 "Arma 3 has stopped working" random intervals, not corresponding to anything I can tell... Sometimes in the spawn area with no fire of any kind. I have also been in HEAVY firefights with no crash. System. i7 3.5 not overclocked GFX 770 2 gig ( not overclocked) 16 gig 1600 ram all latest drivers. No mods or add ons of any kind. Running game at 2560x1440 with a mix of settings seeing around 30 fps during heavy demand ( 60 on light demand) Share this post Link to post Share on other sites
vredesbyrd 10 Posted September 29, 2013 I realise that I haven't posted my spec, which may be helpful: i5 2500k @stock 8gb DDR3 Corsair Dominator @stock HD 7970 Vapor X GHZ Edition 3gb @factory stock (1ghz/1500mhz) Share this post Link to post Share on other sites
bvrettski 10 Posted September 30, 2013 Please add your insight and documentation to the following feedback tracker issue: http://feedback.arma3.com/view.php?id=15107 Hopefully it will help them and illustrate the severity of the issue. Share this post Link to post Share on other sites
soppa 1 Posted September 30, 2013 (edited) Updated server to dev branch 1.03.110511 Shame there is so fev players using development version that its hard to test if they fixed it. You can find server with =Olut= or with hostname: arma3.olutta.org:2302 Edited September 30, 2013 by Soppa Share this post Link to post Share on other sites
Yoiink 1 Posted September 30, 2013 Updated server to dev branch 1.03.110511Shame there is so fev players using development version that its hard to test if they fixed it. You can find server with =Olut= or with hostname: arma3.olutta.org2302 I tried the Dev on your server saturday. That crashed as well. Has there been a new DEV build or something since then? Share this post Link to post Share on other sites
soppa 1 Posted September 30, 2013 yes, dev build exe date is today at 13 about 3 hours ago Changed Depots branches/development/buildid: 120173 › 120816 107411/manifests/development: 4891830478707643750 › 7432260934050688954 about 3 hours ago Changed changenumber – 293464 › 294367 Share this post Link to post Share on other sites
docbrown 1 Posted September 30, 2013 great to see BI acknowledge the issue, as seen in the dev build change log. 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 Share this post Link to post Share on other sites
Yoiink 1 Posted September 30, 2013 yes, dev build exe date is today at 13 about 3 hours ago Changed Depots branches/development/buildid: 120173 › 120816 107411/manifests/development: 4891830478707643750 › 7432260934050688954 about 3 hours ago Changed changenumber – 293464 › 294367 Sweet! Great server BTW! Share this post Link to post Share on other sites
soppa 1 Posted September 30, 2013 yep, no fix in 110511 Share this post Link to post Share on other sites
SASsnipey 10 Posted September 30, 2013 the OLUT server crashes aswell in dev build so back to normal mode for me Share this post Link to post Share on other sites
warlock1982ger 10 Posted September 30, 2013 Our Armajunkies.de Server crashes too! Checked 15 Servers and all have the same problem since the last Patch. Please fix it soon. Share this post Link to post Share on other sites
bvrettski 10 Posted September 30, 2013 At least we know they are aware of and working on this 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 :). Share this post Link to post Share on other sites
jurrasstoil 10 Posted September 30, 2013 It's really a weird thing to witness. Just played a few minutes of wasteland to kill some time and at one point the server went from 46/46 down to 10/46 in a single moment. Chat went mental with people getting kicked. Share this post Link to post Share on other sites
Hatchet_Harry 1 Posted September 30, 2013 i am hosting the armajunkies server. The server itself is not crashing. The players being kicked in waves, because they crash and battleeye kicks the player with the reason "no client response". If dazhog says they work with high prio on the problem and when they are able to reproduce the error, we have to be patient. It helps nobody to start a flamewar or shitstorm. Fact is: Pro: - The patch stopped the clientside laggs and gpu mem stutters - My servers are running more fluently since the patch - My game is running more fluently as player and needs less performance Con: - The developers were not able to test every hardware / software configuration and player situation - that is the real life You cant test everything in a developement environment. People who dont change things will never produce problems. People who dont change things will never make the things better. Share this post Link to post Share on other sites
Austintatious 10 Posted October 1, 2013 i am hosting the armajunkies server. The server itself is not crashing. The players being kicked in waves, because they crash and battleeye kicks the player with the reason "no client response". If dazhog says they work with high prio on the problem and when they are able to reproduce the error, we have to be patient. It helps nobody to start a flamewar or shitstorm. Fact is: Pro: - The patch stopped the clientside laggs and gpu mem stutters - My servers are running more fluently since the patch - My game is running more fluently as player and needs less performance Con: - The developers were not able to test every hardware / software configuration and player situation - that is the real life You cant test everything in a developement environment. People who dont change things will never produce problems. People who dont change things will never make the things better. May I ask something... When you see these people drop off... is it en mass or is it one at a time? I only ask to suggest that it might be something the server is sending out that is causing the clients to crash. Perhaps x group of players is sent a packet that causes a crash, and y , z groups are not sent this packet.... if that is the case, perhaps there might be a way to root out the issue and point it out to the Devs. if it is individually, perhaps you could still see what the server is sending and see if there is anything in common.... I am not expert, just thinking out loud, Ill stop now HAHA Share this post Link to post Share on other sites
soppa 1 Posted October 1, 2013 the OLUT server crashes aswell in dev build so back to normal mode for me Let me fix this, players IN =Olut= server crash too.. not the server itself ;) Share this post Link to post Share on other sites
Magebuss 10 Posted October 1, 2013 4 days of crashing. Plz keep us informed Share this post Link to post Share on other sites
