On Sat I had it last map on EU more than 60 % of the time -killed the fun for me, I m not good even with a gun
![Laughing :lol:](./images/smilies/icon_lol.gif)
Moderator: Executive
21CW plays 8 hour battles and I've never experienced the glitch there.zorplex wrote:
Edit: I'm curious for those who are involved with other BF3 groups, (cM, EGO, LVL, etc.) has this happened during games on others' servers? I don't think there are many communities that play as long as GC does on Saturdays; LVL probably is the closest to amount of time of continuous playing. I might try to contact them directly and ask if they are aware of the issue.
You can't just increase the server's memory like that, most providers will put multiple game servers on a certain node and therefore increasing the server's memory would not only affect use but anybody on that node. Multiplay are extremely unlike to increase their memory like that and are even hesitant in formatting our server as well as per a request I sent out last Saturday after the euro problems.zorplex wrote:It's only happened to me on GC servers from what I remember, usually on the EU server. I've been searching the internets trying to identify what might be the cause but haven't found anything decisive. There are a couple different versions of the "No gun glitch". Some where you can shoot, some where you can not. Some that come back after entering and leaving a vehicle. Most of the results I've found were for console games though and usually due to a cache and/or disc read error.
I'm curious if the number of times the glitch has been experienced per server changes with geographic location. I.e. do EU players have it happen more on US servers and vice versa? If so, it has likely has to do with user latency. However, since it happens for multiple people at the same time and can happen again even after a user restarts the game (as happened to me last Saturday), it means it is likely a server side problem.
If the glitch occurs later in the day on servers (which it seems to do) I would guess it would have to do with either physical or virtual memory on the server having issues. If the glitch ever happened immediately after a server reboot, that would mostly disprove this theory. However, from what I can tell, the glitch usually appears after several rounds of no issues. There have even been a few cases where the server crashed shortly after the glitch started occurring (such as the Sharqi match either last campaign or the campaign before) This makes me think it's a memory leak of some sort. If it's inherent to the game's program, there is little that we the users can do to stop it. Perhaps upgrading the physical memory of the server could help, but if it's a memory leak, it will only delay the inevitable.
Alternatively, we could always reboot servers immediately prior to battledays and perhaps take a brake at 25% and 75% into the battleday to reboot the server and clear memory/cache. Hopefully this would stop the glitch from happening before we switch servers but rebooting and reorganizing would also take time away from the battle day so there is a trade off.
I really want this problem addressed ASAP though so if anyone has better ideas, I'd like to hear them.
Edit: I'm curious for those who are involved with other BF3 groups, (cM, EGO, LVL, etc.) has this happened during games on others' servers? I don't think there are many communities that play as long as GC does on Saturdays; LVL probably is the closest to amount of time of continuous playing. I might try to contact them directly and ask if they are aware of the issue.
I agree that this seems to be the problem.Robawillis wrote:(...)
If I recall correctly servers handle large maps by hoping that conflict is spread across the entire map not around a concentrated area. As soon as the number of events increases around a certain flag/location then it is put under large amount of stress. The only true way of fixing that would be to either get a provider which would give you an entire node to yourself or look at a dedicated box which we would have to forfeit our direct access to due to EA's stupid ranked server provider policy
You always had that amount of ping? It changes?mrBLUE9 wrote:After the high ping issues I had in the EU server on saturday I contacted my ISP and they came over today for a check-up, they also changed my modem for a more modern one. So, I just tested my ping again in the EU server and it's still above 350/400, which is unplayable for me, I normally hit 250 max. I tested other EU servers, including a Multiplay UK one and everything is normal. Does anyone know what may be causing these ping issues? I'm really bummed out because I will only be able to play in the US server.
I always had 230-250 too, just this weekend that it went up to 400 and it's still there.elchino7 wrote: Im from ARG and i normally hit 230-250, you being on Brazil (although depending where exactly do you live) should have a lower one.
Didn't play Bandar, so didn't experience the gun glitch on NA server, Sabalan pipelines was fine, maybe due to TA did something or because it was infantry only.archdirtydigger wrote:Extremely bad today. Had the glitch on both servers but on the NA: Bandar it got ridicoulus. for most of the last round I had no gun atall. It seemed to be contadious since guys spawned in on me and got the glitch.
This really needs to be fixed since it is killing the enjoinment of the game. In a bad way.