181 replies to this topic

[Direwolfe72X]

9erRed, on 27 March 2014 - 05:10 PM, said:

Greetings all,

First, thanks for the advanced notice and opening up the test servers so we can actually test the stuff for the 15th patch.

- Now for everyone else, you do realize that the test servers are a separate entity from our normal environment.

- And the Dev's could actually drop in as a group outfitted in all Clan Mech's, for quite the Aprils fool joke on us.

~ just saying...

9erRed

If they drop in as Clan Mech's randomly from now to June it would be awesome, I don't care if I lost every match!!!!

[cSand]

Deathlike, on 27 March 2014 - 01:52 PM, said:

I seriously wish EVERYONE READ THE SPOILERS, as it details that what we should have expected on April 1st IS NOW MOVED to April 15. More letter designations from M to Z AND hitreg strangeness will continue until April 15.

Lol

people QQ about LRM changes, crying for PGI to put changes on a test server before they run it

They do so (granted it was more of a side effect, but with good reason - a database migration isn't exactly copy>paste) allowing people to test the new changes

More QQing ensues

I like you man but... you need hobby or something (that isn't QQing )

[Deathlike]

cSand, on 27 March 2014 - 08:32 PM, said:

Lol

people QQ about LRM changes, crying for PGI to put changes on a test server before they run it

Well, I've complained about part of the LRM changes, but the part you quoted was specifically about rather important changes (I've still yet to get to Z, but I've gone as far as S in the targeting alphabet).

Quote

They do so (granted it was more of a side effect, but with good reason - a database migration isn't exactly copy>paste) allowing people to test the new changes

More QQing ensues

I'm not bothered with the database thing. One would actually hope it's for those multi-regional servers that people have been clamoring for, but I don't think anyone is bothered about the downtime. It's wondering what kind of progress has actually taken place in its stead.

Quote

I like you man but... you need hobby or something (that isn't QQing )

My hobby is to give a damn about things that I care about. Otherwise, if you prefer having the bar set lower, then don't be surprised someday when things eventually become a bigger, preventable mess...

[fluffypinkbunny]

Der Kopfsammler, on 27 March 2014 - 12:05 PM, said:

I wish they would add a Mech detail overview window to the UI BEFORE we chose to buy the mechs... not after we buy them, so we dont have to keep alt-tabing to search for that third party site just to check that specific Mech's details... :/

if you buy from the mech screen (not the shop, at the top of the mech screen it says owned, or purchaseable.) change the drop down. You can see mech detail

[ebea51]

As great as all this is - and it is - moving hit effects server side will not fix the hit registration issues.

For us high ping players (I am Australian and play on average with 280ms), all it means is that now not only will we get no damage registration where we are aiming, now we will also get no hit effects where we are aiming.

We would rather play with no hit effect but have our damage register!!!


Please help your SE-Asia and Oceanic playerbase!

[maxmarechal]

what about premium time while servers are down?...

[Mahws]

You'll get it back, it's in the spoiler in the first post:

Quote

Premium time will be credited back to users impacted by these downtimes and we appreciate your patience while we do the work necessary to build the foundation for future updates to MWO.

[LiGhtningFF13]

... and again I'm patiently waiting!

[Shiro Matsumoto]

No new Mech? or Map?

[MFZ]

InnerSphereNews, on 27 March 2014 - 09:55 AM, said:

Wave 1: Monday, March 31st @ 10 PM PDT - April 1st @ 10 AM PST (Est. 12 hours)
Wave 2: Tuesday, April 1st @ 10 AM PDT - 12 PM PDT (Est 2 hours)
Wave 3: Friday, April 4th @ 10 AM PDT - 12 PM PDT (Est. 2 hours)

I assume the PST is a typo? Certainly not PDT, then PST and then PDT again ...

[Jeffrey Wilder]

My goodness, the stupid lag is back again.

[BLOOD WOLF]

maxmarechal, on 27 March 2014 - 11:38 PM, said:

what about premium time while servers are down?...

go back and re-read.

[C E Dwyer]

Koniving, on 27 March 2014 - 11:41 AM, said:

Know how you lead a target to hit it when it's fast?
Do that with SRMs, but... lead to hit the air in front of the target instead of leading to hit the target.
Alternatively, aim to hit the target and chain fire.
Watch things shred in seconds.

SRMs when fired in bulk cause a number of 'checks' to see if you hit, warping the target for host state rewind in such a way that causes bad detection. Add to this that the server runs on 100 frames per second so anything between 0.01 and 0.02 seconds is lost (which can happen on weird angles especially with lots of missiles causing some to fail to register). Chainfire reduces the checks, allowing much more accurate registration and reduces the chances of between-frame-missile-loss.

Alternatively, by the time the server gets to the checks, the enemy is actually ahead of where you think they are and fired at. While the missiles fly right past the target (client-side effect), massive damage visually erupts all over it. Sometimes with missiles just whizzing right by a Jenner or Commando without even touching it, I'll get many component destructions and a kill message.

Take your pick to make them work until PGI gets around to it. Chain fire or aim for the air ahead of faster targets.

Players. Try this. If it works for you, throw a like on this post to endorse it.

My own ping is between 60 and 120.
You may need to aim ahead even with chain fire if your ping is worse, and farther ahead than described with the all at once lead ahead to "hit air" in front of enemy method.
If your ping is lower, you should not need to aim much ahead at all.

It works and I do requently remind srm haters that it is the slowest moving weapon in the game.

However there is something seriously screwy about srm's so its not all unjustifed complaining, give you an example from my own experience. start of the comp last weekend.

I'm in a stalker crimson straight I know there is an atlas coming down the tunnel, so I go support the hunchback and the raven,who had it targeted who flee's from it and i'm thinking your all mine now buster as I'm walking down the side entrance.

I have it at 80 meters, I gleefully let fly with Asrm12 at its CT nothing registers, I'm huh wtf back it up with laser fire i'm a bit disconcerted by now as my babies have never let me down before, but I give it a chainfire to the RT and again nothing happens, I'm crap, this is the first time this has ever happend before and ts happend twice to a dead cert, so I start backing out and fortunately a JM has joined me, but I'm hurting.

Now the Atlas stays put, trying to take avoiding action as I'm joined by a third and I'm at now about 150 meters its side on, I let fly with my srms determined to get in another go and this time at longer ranger with a more difficult 'moving' target they hit the atlas and destroy it.

So as a big fan of SRM's and a lot of the complaining is because of poor target leading.

SRM's do have problems, they do need a HSR fix and I do think they need a slight speed buff, and each time I fire them now I'm thinking of that atlas and are the buggers going to register

Edited by Cathy, 28 March 2014 - 04:07 AM.

[Jeffrey Wilder]

Jeffrey Wilder, on 28 March 2014 - 03:27 AM, said:

My goodness, the stupid lag is back again.

Frankly, anything above 400 ping is totally unplayable. I wonder how PGI tested 500 ping and says it's ok

[Jeffrey Wilder]

Jeffrey Wilder, on 28 March 2014 - 04:14 AM, said:

Frankly, anything above 400 ping is totally unplayable. I wonder how PGI tested 500 ping and says it's ok

BTW, I have no problem surfing the internet. In fact, even downloads work well. The only problem is bad ping so I suspect it's the server yet again.

[Atreides76]

Damocles69, on 27 March 2014 - 10:39 AM, said:

Please just fix SRMs.

Seconded'ed.

[Ngamok]

Shaedow, on 27 March 2014 - 08:30 PM, said:

If they drop in as Clan Mech's randomly from now to June it would be awesome, I don't care if I lost every match!!!!

I asked Paul during one of Impailer's twitch streams if they wouldn't mind trolling us in like mid to end of May till June 17th by dropping in clan mechs against us. Didn't remember if he was keen on it or not.

Jeffrey Wilder, on 28 March 2014 - 04:22 AM, said:

BTW, I have no problem surfing the internet. In fact, even downloads work well. The only problem is bad ping so I suspect it's the server yet again.

I had a ping of 27 last night /flex.

Atreides76, on 28 March 2014 - 05:12 AM, said:

Seconded'ed.

I killed someone with SRMs last night /gasp. My buddy Greystoke was running aroun in a Stalker with 2x ASRM4 and 2x ASRM6s and killing people. Oh noes. They work, just don't mass fire at people and don't face hump people.

[SweetJackal]

Shaedow, on 27 March 2014 - 08:30 PM, said:

If they drop in as Clan Mech's randomly from now to June it would be awesome, I don't care if I lost every match!!!!

I will fully admit to being a critic of PGI and calling them on trying to pull a lot of garbage over us, wool over our eyes saying "it's for the best."

But if PGI used the larger hours in the test environment to not only test but also hold an event like this then I'd be impressed.

Jeffrey Wilder, on 28 March 2014 - 04:22 AM, said:

BTW, I have no problem surfing the internet. In fact, even downloads work well. The only problem is bad ping so I suspect it's the server yet again.

Might not be your ISP or the MWO server but rather how you are routed to the server. You go through a lot of 3rd party property to get anywhere on the web and neither you, your ISP or the service you are using (in this case MWO, PGI and IGP) has any control over them.

Also, to my knowledge there are only servers located in US/NA so playing from across the ocean would kill your ping times compared to localized web browsing or video streaming.

Ngamok, on 28 March 2014 - 05:59 AM, said:

I killed someone with SRMs last night /gasp. My buddy Greystoke was running aroun in a Stalker with 2x ASRM4 and 2x ASRM6s and killing people. Oh noes. They work, just don't mass fire at people and don't face hump people.

Once more, SRMs are a weapon where your mileage may vary that have plenty of factors as to if they will work properly. It's not that they consistently fail to register for everyone in the same situations it's that they are incredibly unreliable as to when they hit and when they don't. Some people don't try launching 22 tubes of SRMs at once and don't facehump people and still get these problems.

Still, large volleys and being point blank with the shortest ranged weapon that weighs more than a ton should not have any effect on Hit Reg.

Some people will find ways of having them be reliable and work for them, and kudos to those people. But just like those experiencing Simulation Sickness from Cockpit Glass (WHICH STILL HASN'T BEEN FIXED MIND YOU!) just because you do not have a problem with it doesn't mean it isn't a constant problem for other players.

Edited by SuckyJack, 28 March 2014 - 06:40 AM.

[Roadbeer]

MFZ, on 28 March 2014 - 02:11 AM, said:

I assume the PST is a typo? Certainly not PDT, then PST and then PDT again ...

That's what happens when someone tries to get cutesy instead of just saying "Pacific Time". Sure, PDT/PST is quicker, but if you get it wrong, someone's gonna call your ass out on it

[Redshift2k5]

Ngamok, on 28 March 2014 - 05:59 AM, said:

I asked Paul during one of Impailer's twitch streams if they wouldn't mind trolling us in like mid to end of May till June 17th by dropping in clan mechs against us. Didn't remember if he was keen on it or not

They cannot "surprise drop" in clan mechs without patching the clan mechs to everyone's client.

They cannot patch anything to everyone's client without it being immediately found, exported, and on display (The achievement list was publically in the installation weeks before being implemented)

The Mad Cat would be out of the bag the second someone finished patching.