Page MenuHomeFeedback Tracker

Brief driver crash when hitting CAPS LOCK to talk in multiplayer
Closed, ResolvedPublic


Upon entering any multiplayer game, the first time I hit the "CAPS LOCK" button to talk, the screen will go completely black for approximately 5 seconds, then will resume to normal. All in game sounds and motions are still active and possible during this time.
P.S. This can be re-created at the main menu screen as well.

My config:
Intel i7 3820 3.6gHz
nVidia gtx 680
16 gb ram {F19120} {F19121} {F19122} {F19123}


Legacy ID

Event Timeline

siryates edited Steps To Reproduce. (Show Details)Apr 24 2013, 7:08 PM
siryates edited Additional Information. (Show Details)
siryates set Category to Multiplayer.
siryates set Reproducibility to Always.
siryates set Severity to Minor.
siryates set Resolution to Open.
siryates set Legacy ID to 2324937056.May 7 2016, 1:50 PM
Khan added a subscriber: Khan.May 7 2016, 1:50 PM
Khan added a comment.May 14 2013, 12:24 PM

Please provide us with your DxDiag info and your Arma 3 settings. Thank you

I have attached a file containing dx info. Please review, thank you for taking up my issue! Arma 3 settings to follow.

I have also included 3 screenshots showing my settings, I hope this is what you meant.

Khan added a comment.May 16 2013, 9:35 AM

This issue was processed by our team and will be looked into. We thank you for your feedback.

Please keep the issue monitored to see when it is fixed.

Unable to repro in actual version on Steam. Do you have still this issue?

Yes, the problem persists. I shouldn't really have flagged this as a multiplayer issue, as it will happen at the main screen as well, but oh well. I'm using Arma 2 keyboard/mouse presets if that helps at all.

Do you have still this issue in beta build? If issue still persist, please upload crashdumps to some free sharing service and write link here. Crashdumps you can find here: Arma 3 Beta: C:\Users\<Name>\AppData\Local\Arma 3\ Thank you.

MadDogX added a subscriber: MadDogX.May 7 2016, 1:50 PM

Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.

If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.