14 replies to this topic

[Xaat Xuun]

it's only happen a few times, in the past years, but it is a strange

my LBX acting like UAC jam, if I am getting hit by SRM's. I just can not fire my LBX, got plenty of time to look (not glance) and see they are in fact cool down, and what feels like forever cool downed, even the the other LBX has cooled down, but they'll fire, just the first set still acting like they are Jam

I didn't know LBX's can jam, do they Jam ? is it possible, and I just was unaware

might be something I need to test with someone and see if I can recreate it happening

[Aidan Crenshaw]

LBXs are definitely not supposed to jam. Maybe you just don't get a response (muzzle flash, sound) although you fired the weapon?

[LordNothing]

it happens. the sound channels get used up, too many sprites and particles to render, so stuff gets skipped, but the shots should still be registering.

Edited by LordNothing, 11 March 2019 - 11:56 PM.

[Xaat Xuun]

okay hmmm

so nothing showing they fired, like the cool down indicator

Edited by Xaat Xuun, 11 March 2019 - 11:51 PM.

[Xaat Xuun]

okay just had a match, my LBX 's wouldn't fire at all, like they didn't exist, just had to stand still so the Piranha can end it faster.

jumped in testing grounds to see what's up, nothing wrong . . only having these strange LBX jam and this new one, while in a match
oh and my weapons group was all red, like if I was out of ammo, or no weapons any more

[Matthew Ace]

Perhaps you could upload a video and show us?

[Xaat Xuun]

yet not know how to record, I surely would

[VonBruinwald]

Was this Solaris or QP?

Experienced something similar on Solaris a few days ago with my LBX20 Cicada. Put it down to me and my opponent having about 500 ping between us. Never had it happen before.

[jiggyjiggy]

I had the same thing happen to me the other day. I was in my ON1-IIC-A with LB20X and 4xSRM6s, and it felt like my LB20X was just taking way too long to cooldown every once in awhile. Thought I was losing my mind. This makes me feel better.. I guess.

[Koniving]

Xaat Xuun, on 11 March 2019 - 11:26 PM, said:

my LBX acting like UAC jam, if I am getting hit by SRM's. I just can not fire my LBX, got plenty of time to look (not glance) and see they are in fact cool down, and what feels like forever cool downed, even the the other LBX has cooled down, but they'll fire, just the first set still acting like they are Jam

I didn't know LBX's can jam, do they Jam ? is it possible, and I just was unaware

They do -- but not in MWO (just a fluff/lore thing and is mech specific, not weapon specific).

It sounds like you're having a ping/connection OR lag issue.

Each time you want to fire, the client "asks for permission" to fire from the server.
The Server says yes.
You fire.

If you are unable to ask the server for permission... you can't fire.

If you create conditions to significantly increase your ping, you can jam the ability to ask permission, causing the "zoom" command to take up to 7 seconds in order to actually permit you to zoom in.

[Nightbird]

Sounds like your LBX got critted out.

[Koniving]

Similar things can happen to fire, movement and other aspects as well.

This is a server disagreement (Edit - wrong time index, fixed)
(Watch when the mechs stand back up. For something more subtle with the server authority permission system, watch where I shoot versus where I hit; that's an idea of how much of a delay is caused in this 'permission to result' sort of thing without HSR. Shoot WAY ahead of enemy right arm completely missing, hit enemy left arm and left torso.)

Now this isn't to be confused with desync, as then where you are and where the server says you are become two different things, and you can get all the permissions but...nothing works the way you think it does.
(Video is of a desync / packetloss)

Sadly I don't have a specific video for your issue, but I have personally experienced it (it isn't limited to LBX, any non-MG gun can do it.)

Now, there's also what Nightbird said. If they stopped mid-cooldown and became red; they're crit.

My response is if they are otherwise perfectly fine, still cooling down (but not stopping), etc...but flat out refuse to fire.

Xaat Xuun, on 15 March 2019 - 11:40 PM, said:

jumped in testing grounds to see what's up, nothing wrong . . only having these strange LBX jam and this new one, while in a match
oh and my weapons group was all red, like if I was out of ammo, or no weapons any more

Seeing this line: That's a crit.
Basically either your ammo got destroyed or your gun did.

If it looks like this, its critted-and-dead. Cooldown bar might get stuck as a bug, but basically its dead, Jim.

Edited by Koniving, 16 March 2019 - 09:48 PM.

[Xaat Xuun]

paper doll did not look like that, and still had armor and structure, but my weapons group looked like that but everything.

I know MG can crit, but not under a sec, on a fresh mech, @ 100%, though I suppose it is possible, but don't feel like it it happened that way.

I couldn't say if the fire group was like that the whole time, just something I didn't look at right away, it was when I realized, my guns were not firing at all, I looked, all ammo was there, but every thing was red, like no ammo, or blown away torso's , and they still had yellow armor when I decided to just stop moving, can't shoot back why bother.

[Xaat Xuun]

Koniving, on 16 March 2019 - 09:35 PM, said:

They do -- but not in MWO (just a fluff/lore thing and is mech specific, not weapon specific).

It sounds like you're having a ping/connection OR lag issue.

Each time you want to fire, the client "asks for permission" to fire from the server.
The Server says yes.
You fire.

If you are unable to ask the server for permission... you can't fire.

If you create conditions to significantly increase your ping, you can jam the ability to ask permission, causing the "zoom" command to take up to 7 seconds in order to actually permit you to zoom in.

since this LBX debacle happens more frequent, been keeping a eye on things, I believe it is the "ask for permission",(as you call it)
just had it happen with a laser/LBX build, and the lasers wouldn't fire, not crit (yet) and they were cool down, but just would not fire.

*Sigh* damn, now I know what it feels like to be last one pick for the team, need to find a way for the server to like me more, so I can be picked first
I've had the lasers fail before, but been a while

[Koniving]

Xaat Xuun, on 17 March 2019 - 12:30 PM, said:

since this LBX debacle happens more frequent, been keeping a eye on things, I believe it is the "ask for permission",(as you call it)
just had it happen with a laser/LBX build, and the lasers wouldn't fire, not crit (yet) and they were cool down, but just would not fire.

*Sigh* damn, now I know what it feels like to be last one pick for the team, need to find a way for the server to like me more, so I can be picked first
I've had the lasers fail before, but been a while

Spoiler

By all means you can. But it would be strange if it is isolated to one weapon type. Though that type does generate 2, 5, 10, or 20 projectiles simultaneously each with an individual trajectory (so perhaps?).

There's four things that can affect you and the server: 1) The server itself and its current state. 2) Ping to the server (yours AND theirs; the more erratically changing the worse it gets). 3) your physical distance from the server (if you're in North America and playing on an EU server, you're open to more issues). 4) Your ISP. 5) Your connection method (wifi / wired). 6) Your computer.

1) The server... Its running at 100 fps (though from having seen a server crash, not every server is linked; for example in one match in 2013 fourteen players got the boot at the same time, 6 from one team and 8 from the other (in quickplay for 14 players to instantly disconnect at the same time as a deliberate act is pretty much impossible).. so there is evidence that either A) the server hosting those players crashed, but it didn't stop the match as the one the rest of us were on was still up or B ) as a way to prevent a crash a server hosting all of us suddenly dropped a bunch of players.
Sadly we don't have a definitive understanding of the server structure and how it handles players.

What we do know is a bit of how the server authority works (as it is why cheating isn't as bad as it is in most free to play games)... its also why PGI is terrified to do some of the most basic things, like slowdown when traversing through deep water and actual variance in gravity.

2) Ping is crucial as the game's lag compensation makes estimates and anticipations based on it. For example your location and where the guy shooting at you sees you isn't the same thing (as you may have seen in that first video). This is why sometimes while watching a play, you'll see them shoot and completely miss but their bar says they are hitting, and to them they are hitting and even leading the target...but that isn't what you see.. you see them not only missing but trailing behind the target. Fun, isn't it? HSR does a lot to try and keep from ruining the illusion for us. A ping of up to 250 still functions fairly well, but once you hit like 399, yeah that's a 7 second wait to be able to "zoom in." And if your ping is completely erratic you'll see all kinds of strange behavior as the game keeps trying to compensate for it.

If ping is your issue, the fastest way to find out is try to zoom. If this only happens during combat, the issue may have some ping-like traits, but its not directly the ping...

3) Physical distance: Basically if your connection has to be sent over seas, there's probably no wires directly hooking you up meaning your stuff is probably getting sent to space and back down to their server on the other side of the world... This isn't necessarily the cause of your problems but it can make them worse.

4) ISP. This one's self explanatory, if your ISP can (and will) throttle your connection speed if you reach a certain limit...time to ditch 'em.

5) Wifi is interesting. For example depending on where it is relative to other devices such as microwaves you might notice some interesting behaviors. I've also noticed a certain offbrand chinese TV's remote would mess with my wifi by disconnecting it any time someone pressed the volume down button (you won't believe how long it took for us to deduce what was doing it). A hardline connection is obviously better... but its not just about your wire or wireless, check the stuff outside the house too. Had some strange behavior for a long time after a Spectrum contractor came out to hook up our connection. Then we moved out for about a year and moved back, and this time Spectrum's own staff came out. The cable used wasn't up to spec and the way it was hooked up was kinda shoddy too, they redid the whole thing and my connection speed nearly doubled.

6) Computer: Unlike most games, MWO is Extremely processor heavy. Worse it makes very poor use of multi-core systems. Some users do a boatload of tweaks to try and get around it for better performance, but the simple fact is: if your processor isn't up to par when combat gets intense and all the explosions flush around you, something's gonna give. A queue to generate 10 to 40 individual projectiles at once + explosions, smoke, etc., from 1 to 4 LBX...well that might be a thing.

Anyway, if you're having a legitimate issue with the weapon not firing due to any connection issue between you and the server, the fastest way to find out is to try to zoom (because for some damn reason the client has to ask for permission). If the game responds instantly, it isn't any issue related to connection. If there's a delay, how long of a delay will tell you something.

For some more fun ones...

When the server and your client can't agree... although this was happening to everyone so it was a server issue.
What's going on is the server repeatedly tries to correct our positions and is having a hard time accepting changes in position.


This one seems to be a discrepancy in the map versions (it was fixed soon after I reported it). The game map says I can do this... the server's non-rendered version says I can't, so when I try to go over it the server's like "You can't." But then my Client says "I can." And the two argue. What's really fun is when you can get the two to argue and the correction loop that follows keeps raising you into the sky. Don't have a video of it but its damn fun.

Beyond those network factors, I've got this in case if the problem's just a lot simpler...

Make sure the mouse battery is charged if you have a wireless mouse? I've also noticed that some mice with multiple buttons won't let them function at the same time. A cheap ONN mouse for example had that issue, so I went and got a larger mouse which let me use all the buttons at once (great for multi-group setups). So now I have a gaming mouse that I hide when I'm not home and an everyday use mouse.