60 replies to this topic

[Mister Blastman]

State rewind is state rewind. How can it only effect some weapons but not others? Sounds like monkey coding to me.

[Mister Blastman]

How is it not the same?

How they describe it works is precisely how it works in Half Life / Team Fortress 2. If say a PPC impacts at co-ordinate x,y,z @ 1:44:32 gametime, the server then rewinds to that state to confirm the mech being in that position the client claimed it to be when it sent the hit registration request to the server. If it matches up, the server tallys a hit and then sends confirmation to all client connections so their clients can register that hit on their end.

It should work the same for every weapon type.

[Mister Blastman]

I'm not a game developer either but I do have a bit of coding experience so I do understand quite well how the logic works.

Maybe he can clarify as I'd like to know.

[Broceratops]

Mister Blastman, on 04 March 2013 - 05:54 PM, said:

State rewind is state rewind. How can it only effect some weapons but not others? Sounds like monkey coding to me.

regardless of where you aim, it rolls a d20 to determine if you hit

[Mister Blastman]

Broceratops, on 04 March 2013 - 06:33 PM, said:

regardless of where you aim, it rolls a d20 to determine if you hit

LOL. If only it were like that.

Wait. No, no we don't want that. ;P
IB QQ but I want TT discussion.

[Fooooo]

Mister Blastman, on 04 March 2013 - 06:32 PM, said:

I'm not a game developer either but I do have a bit of coding experience so I do understand quite well how the logic works.

Maybe he can clarify as I'd like to know.

He already did in that quote posted.

Because ballistics have
1. A travel time,
2. Are checked on the server differently to lasers (hence the delay when firing ballistics generally)

Because of the travel time, they cant use the exact same code that is being used for lasers, they need to add another "layer" so to speak, to handle that. (which is said in the post is not complete yet, but if we are lucky, it may come out with the first part....or at least very soon after)

It needs to rewind, then "run" the ballistic trajectory + mech forwards in time (the blue box in the CC post) etc instead of just grabbing the x,y,z location of the end of the ray instantly without running the mech forwards (the blue box in the CC post) like they can from a hitscan weapon....afaik.

If they just let ballistics use the same thing the lasers are going to be, then weird stuff would probably happen with ballistics.

Edited by Fooooo, 04 March 2013 - 09:13 PM.

[Ngamok]

VEightFreak427, on 04 March 2013 - 12:51 PM, said:

Finally. I will look forward to all of the whiny light pilots after this is implemented. No more god mode for you.

Need collision to be back in too.

[Jetfire]

Been loving the Jenner's lately, nobody seems to have a hard time hitting me, if they get the chance to pull the trigger. Lots of 350+ dmg matches, feels pretty good.

[Vahnn]

As a Jenner pilot, I can't f*cking WAIT for this patch. Bait 3L, Spider, Commando into range of my teammates, engage in "circle of death" duel, fake him out and ram into him at full speed.

[Walk]

As a good light mech pilot, this change will effect me in no large way.

[Pierce Rossignol]

When they institute this for ballistics, wasting a Commando is gonna be like sand-blasting a Dorito.

Once they bring back collision damage along with this I'll be drop-kicking Lights into the Out Of Bounds zone.

Edited by Pierce Rossignol, 04 March 2013 - 07:32 PM.

[Rocdocta]

as an aussie jenner pilot i cant wait for this patch to come out. i am sick of chasing other light mechs and doing damage (so i thought) and it is basically unscathed. it should not take literally 4 minutes of blasting the rear armour of a raven with 4 MPLs to wreck it. i am ping 350+ vs ping 50...cannot wait to start doing more effective damage! and Hey! give us an aussie server!

[Star Colonel Mustard Kerensky]

Inb4 nothing changes.

[Owlfeathers]

Yay! Perhaps now my Raven 4X will be able to kill the swarms of 3Ls that always seem to be around.

[mekabuser]

the thing is, there are still going to be very good light pilots that will absolutely ruin your day if you dont ID them as a threat right away, and then know how to deal with them..

With all the improvements past and present, their numbers will be much less though because all the pseudo good light pilots will be gone... Which is all really anyone was asking for...

When collisions come back, the light pilot experience gets amped up another 20%, but i think thats what most of us in the light brigade are looking for anyways...

[raptorak]

I play with 257-350 ping with oftentimes bad packetloss from Beijing. This is a particularly pathetic effort I recorded:

This netcode fix will mean that all high-ping players ought to think about abandoning ballistics and ppcs until those can also be improved, since we will all have to relearn lasers to hit certain bodyparts rather than some mysterious point in time ahead of the mech. This is the easy part. The hard part will be aiming the lasers, and then still compensating for lag-shield with ballistics/pccs.

Still, the netcode fix is definitely a step in the right direction, but my main concern is that the random warping left/right/forward/backwards before I take a shot disappears (or maybe it is when others shoot at me), because that is the worst thing.

What low ping players will probably notice is that lasers that appear not to be hitting them, or lasering the arms, will infact be often be cutting directly into their CT, so LPBs fighting HPWs should expect to take a lot more damage than before and thus compensate accordingly.

Personally, in other games, I have tracking skills with a lightning gun in Q3 or the nova colt in Tribes Ascend that would make a 3L weep. Enemy mechs used to glow red hot from laser-fire but took no damage whatsoever before I found out about lagshooting.

So good luck, 3L pilots, because I have a settle to score with all of you.

Edited by raptorak, 04 March 2013 - 10:04 PM.

[Mister Blastman]

Wow Raptorak. I feel for you man. Let's hope this patch gives you some hope.

Edited by Mister Blastman, 04 March 2013 - 11:27 PM.

[Rocdocta]

@Raptorak...AH ha ha ha! I have the same drama in australia. i cant believe it when i am on an enemy mechs rear for a couple of minutes firing and then i have done 20 damage...4 MPL the whole time!! And then i see idiots on my own team typing "lead him noob!! leading means fire in front! You a sh@te jenner pilot!" Are you serious? copping rubbish from fools with a ping of 50 and i am on 350...almost makes me wait until beta is over on 2024 when they get the asia servers running.

[Mister Blastman]

Well I'm not sure... but I wonder how say Valve handles state rewind with rocket launchers. Hmm. Well, the server in MWO already knows when an order to fire is issued on an AC because of the delay we experience. From there it is just a matter of keeping track on the server itself where that projectile goes versus where the enemy would be.

Dunno, we'll see. State rewind will be far more useful for things like SRMs, PPCs and ACs as those are what will really smash apart light mechs.

I must admit though, I don't have much trouble at all shredding Ravens with a UAC 5 as it is right now.

[JadePanther]

Hann Solo, on 04 March 2013 - 01:02 PM, said:

I just want to see the next excuse you guys all have for why I shred you in my Raven. Better come up with a new one.

I think it's gonna be bad for ravens..

Check out the new cicada video.. I like the part where 4 ML's to the rear of a raven make him goo boom like they should...

No more of this OMG how many alphas can a damn raven eat.