Since update 2.08 Arma is messed up! First of all, dedicated servers (not public ones) cant be updated to the newset version, resulting in a red cross in server browser.
Then there are all kinds of bugs going on, also on official servers: sounds are way off, too loud and cracked, like doubbled, inside buildings horrible.
Rifles are shooting bursts when mouse is pressed only once. Guns fire wrong ammunition, rifles sometimes appear to fire phalanx munition!!!! They also fire when not even carried, laying on the ground. Triggers on public servers seem to fire too late or not at all. VON is broken on public servers.
Description
Details
- Severity
- Major
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Category
- General
Public servers. Server browser.
Event Timeline
On our dedicated server about 90% of missions that were all playable last week, are since the 2.08 update unplayable; as in after about 3 to 4 minutes into the mission all players lose connection at the same time. The dedicated server does not appear to have crashed & is still running, but players have to disconnect & re connect to try a different mission.
Some sort of major de-sync problem??
Same here, red chain, loosing connection on mission start.
I figured out the server steam update is not updating to 2.08.149044 but only updates to 2.08.148892
I figured out the server steam update is not updating to 2.08.149044 but only updates to 2.08.148892
149044 is profiling branch. Many of the bugs were already fixed on there
Thx dedmen, figured that out on sunday, the thing is that if using main branch on dedi server and local machine, server browser still says "different version" with red cross and looses connetion very soon. Hopefully main branch is updated to .149044 very soon. And btw: profiling branch still got t. he rifle firing in bursts bug until firing mode is switched.
The difference between a dedicated server & client seems to be a missing 0, as in Dedicated server is 2.8.148892 & client 2.08.148892
So 2.8 & 2.08 is that what's causing the problem? which is still happening today. Tues. 15th 23:00z
Same Wed
Yay! Steam update 13:30 today 16th seems to have fixed the problem. Nice one!
I wonder if it was a typing error with the missing 0?
I wonder if it was a typing error with the missing 0?
it was not, it was actually a parsing error inside steam that was triggered by our missing 0 (which is intentional)