User Details
- User Since
- Oct 2 2013, 4:51 PM (585 w, 4 d)
May 10 2016
Perhaps I should clarify it doesn't seem to be ALL workshop files, it just seems (?) to be selective content which triggers it. I've still got quite a few others items/missions installed but the screen/map flashing now seems to have stopped.
I didn't uninstall everything, but systematically worked backwards from my most recent installed workshop files (as the problem was a recent one for me) until the flashing bug stopped.
Good hunting Bohemia!
Ditto re. the unsubscribing to (some) Steam Workshop missions to solve the problem... in my case I pinned it down to this mission by ffredyk [CZ] -
http://steamcommunity.com/sharedfiles/filedetails/?id=278701081
Perhaps some boffin could take a look (with the above mission by Dixon) to find out what causes the larger problem. NB The problem reoccurs if I resubscribe to this particular mission.
Thanks for chasing this up guys.
I've also used (successfully) many mods, but only with this latest update has the regular flashing screen problem occurred exactly as described elsewhere. For the record I'm using a non-default profile as I don't use my steam ID as my in game Arma name.
As with others is happening frequently to myself and friends in MP, sometimes as individuals, but now more often affecting groups of players simultaneously e.g. during squad play, though not everyone in game. A common pattern is the crash appears to happen during moments of major in-game activity, and (as noted elsewhere) nearby explosions often seem to be involved, suspect they may even be a trigger?
For what it's worth I also changed from Win 8.1 to Win 10 a month ago and since then my joystick has worked perfectly (i.e. as before when I used Win 7).
My X52 Pro stick and CH Pro pedals are permanently plugged in so I haven't (wanted to) test the unplugging issue.
Hope this helps (or partly reassures) anyone thinking about moving to Win 10.
Re. 'Slow' responses to control input as noted above. I found this elsewhere but you could try disabling any alterative input commands (eg for keyboard) used for the same manouever e.g. my own 'rudder' pedals were very sluggish in yawing until I removed the alternative twist-stick rudder control from my stick. Might be irrelevant re. the above, but it worked for me.
Good luck all.
Well for what it's worth those personal, rough test results are in... with Win 8.1 my CH Pro Pedals, X52 Pro Stick and TrackIR5 all appear to work happily with DCS, Rise of Flight, Take on Helis!!!, Elite Dangerous, MS Flight Sim X and X-Plane 10. But sadly not on Arma3 (the only game I really actually really play). Found an odd wrinkle in that A3 often -though not always- seems to accept my pedals IF I unplug my joystick before playing, but the same trick doesn't appear to work if I unplug my pedals instead.
It seems many of us are hanging on for Win 10 -which is at least imminent - though many of you have been waiting rather longer than myself. Well good luck guys, see you on the other side!
[Apologies for duplicating this earlier in the BI forums by accident]
Ditto above... played Arma3 since launch for many hours (Win 7) with CH Pro Pedals, X52 Pro and TrackIR5 - no problems and good times.
Just updated to a new PC (Win 8.1) and get instant loss of all but TrackIR when in SP and MP but otherwise nothing else different on my setup except for OS - well except new PC has significantly better spec than my old one.
Earlier posts seem to indicate Win 10 may be okay... is this what we are now hoping and waiting for?
NB Steadily trying same combination of peripherals with other flight games just for heck of it... for the record 'Elite Dangerous' is fine on my box with Win 8.1 (I will test others e.g. DCS, ToH, Rise of Flight etc.) BUT sadly it's Arma I really play full time.
This still appears to be true and regardless of relative position (higher, level or lower than AI) and also at varied distances (<50m to >300m). The AI usually sees through grass before the player can see them - this even when using very low stances and if 'sneaking' or 'hiding' near AI patrols.