37 replies to this topic

[T0RC4ED]

Im going to sit here and complain that i wont be part of the beta because its not likely I will be home in time

[Aegis Kleais]

The vast majority of people just want to play, and if they do provide feedback it will be unconstructive and next to of no use to the developer.

I plan on putting in enough hours not only towards entertainment, but trying to do things that (once I understand how they are supposedly implemented) see if I can break them or cause an issue.

Anything to help out.

[Vodkavaiator]

I am going to drink vodka whilst playing and then report my results.

It should allow me to find and forget most of the bugs that are there.

[Sym]

Prosperity Park, on 24 March 2012 - 12:09 AM, said:

I will:

• Try to escape the maps;
  
• Search for unfair or glitchy camping sites/practices and report;
  
• Look for clipping problems with models and environmental features;
  
• Test how the different weapons cause different kinesthetic effects on my Mech/cockpit and how they affect gameplay;
  
• Check which weapon(s) exhibits the best boating profile, optimize my boat(s), then report why I came to that boating conclusion;
  
• Test heatsink thresholds and find the optimal dmg/time profiles for each weapon system I have time for;
  
• Try to crash the game with joint team missile boating;
  
• Determine the number of teammates and circumstances needed for reproducable joint-alpha-one-shot-kills with various loadouts;
  
• Examine the friendly-fire/booting system for abuse potential or accidental bootings;
  
• Compare a 3rd party communications program to in-game communications tools;
  
• Burn holes in Mechs with my lasers.

Now this is Beta testing! +1 for you my friend

[Hades Serpent]

I'll send in bug reports or thought-out suggestions.

To those deriding the "freeloaders" (seriously? everyone playing this game will be a freeloader until they pay for something), remember, every system can benefit from some stress testing. The open beta will serve as a good way to see how well their servers hold-up under heavy load, as well as answering the question "do we have enough hardware? too much?".

[Karl Streiger]

I would test the hit zones. Some past games had great problems with hit zones.
For example Vulture, DireWolf, Catapult, Jenner, Hellbringer where auto kills when you know how in MW2. The StoneRhino had real problems with the arms. you lost them first no matter where you aim at. Seldom last longer as some seconds.
In MW3 where Shadowcat, Direwolf and MadCat in most cases auto kills.

[DarkTreader]

I'll probably do the same with this as I do at work every day -

Check the artwork for texture issues, fubar'd polygons, etc...
Check the terrain for holes
Check the collision on EVERYTHING (you'll know it's me because I'll be the only one with an Atlas that's flashing red from the hips down... 2 minutes after a drop.)
Crunching the numbers on weapons, armor, ammo counts, weight, heat, and any other info I can get my hands on to test balance
Testing the actual usefulness of the non-weapon selectables (modules, NARC beacons, C3, etc...)
Looking for 'sploitz in the Command View (Can I just spam 'Rally here!' over and over on top of a 'Mech for points?)

Eventually, I might even get up to testing what happens when I shoot another 'Mech!

[AlanEsh]

Dlardrageth, on 23 March 2012 - 12:11 PM, said:

I would hope they would just account-kick people from beta who don't send in a weekly "progress report" to be evaluated by PGI. But that is probably the HR-focused me thinking there. Sadly I expect more like 90% of beta players being freeloaders just playing without contributing anything. Apart from the occasional biatching/whining ofc. As usual these days.

Your progress report idea isn't normal for an Open Beta. Sure open beta will put more eyes on the game to find problems, but more importantly it will give them much more realistic loads for the servers, match maker, and it will let them compile and evaluate a buttload of mech performance stats they couldn't determine in the much smaller Alpha and Closed Beta stages.
So the 90% who just log in to play are doing their part too!

[Sidewinder619]

As a former game tester for Sony and Hands On Mobile in in San Diego, the more players that log on and stress the servers the better - the online component - front end, text, sound, graphics etc and actual gameplay do need to be tested - At Sony we watched clever players in Socom 2/3 do all sorts of things to get off maps, use collision on objects to get pushed into other objects, use smoke grenades to break collision, claymore jump to buildings, crash the games with light sticks, etc. There will be bugs present - some not even seen at launch - however one hopes that all severe issues that crash the game, etc are addressed. You can see my credits on such titles as Gameday 2004, the original Killzone, Socom 2/3, Killzone Liberation for PSP, Neopets for PSP etc.

Sidewinder 619 aka Dwight G

[Kaemon]

I'll make a forum post trying to define a BETA checkoff sheet for new players who haven't been in one before ....no one will read it.

Then I'll try to get some ideas together to create a BETA Bug/Fix form people can use so issues are easily captured in a repeatable and easily read format...no one will use them.

Then I'll write a post of the most prevalent issues in BETA and the current comment (if any) on them from the devs....no one will comment.

So basically it'll be just like work...HA!

Edited by Kaemon, 27 March 2012 - 07:58 PM.

[CW Grayson]

I would just log in and try to play the game. Trying out glitches, usefullness of weapons etc. comes normally by that, maybe because i'm the "jäger-und-sammler" type anyway I was in the beta for X3:TC and just from normal playing i got some bugs. Of course, posting those needs also be done.

[Nik Van Rhijn]

I will run around like a headless chicken yelling "X is OP", "Y is nerfed" and other such useful items.

[DarkBazerker]

If any other game asked me to be a tester for them for free I'd told em no. On the other hand being that we are talking about MWO I will gladly test it for free, being that i just cant say no to any MW game! aside from mechassault

*holds out hand for beta key*

[Kanatta Jing]

Well one of the most important things about beta testing is the load test.

A bunch of people in one match playing the game in a big scrimmage and making a ton of lag.

[Maxtac Jurai]

My unit will bring upward of 50 people onto servers simultaniously, working together to test the regidity of coms and unit CnC, developing group tactics and testing the gameplay modes for optimal success. I suspect while that is going on, we'll find a few holes in the maps (this happened in MW4 - one of our guys was a mapper for that, so he was dead keen to find them), look at object collision (a big prob in MW4 - looking though walls and mountains was rife), testing heat scales vs weapons (and hopefully not finding the catnap bug that as in MW4), optimal loadouts, and a myriad of other points.

I echo others' comments about just getting a LOT of people out there playing, and seeing how the hardware and code stands up. That's as big a test as anything I mentioned above (an no less important). We don't want the servers going down, or the sofware locking up after a 12 hrs PA is coming to a head, now do we?

House Jurai likes to win, fair and square. As such, we WILL be reporting anything that looks like and exploit, and we hope that the devs will listen. THAT will make a great game. And that's what we all want, after all, right?

Tai-shu [HJ]-Maxtac Jurai
"diamondo no hitomi"
Warlord of The House Jurai

[Anvil Dragon]

Since I am unlikely to be contacted for the initial Beta, digging up a Dieron District Gymnasium pennant an cheering from the sidelines seem my most likely option.

Go Team!

[Archtus]

I would do my best to find every single exploit.bug/glitch possible for scouting.

And report it about three days later.

Goasl 1:Glitch into a building, find it has no view/collision data from the inside, and scan/scout/NARC opposing mechs from the comfort of the nearest office building.

[Aegis Kleais]

Beta Issue #00000

Title: No Download Link Exists for Beta
Status: Verified
Keywords: download, impatient, gimme, jonesing
Reported: 2012-04-09 12:48:04 PM EST by AegisKleais™

Product: MechWarrior Online
Component: Installation
Version: 0.03.2a
Platform: Windows PC

Importance: Critical
Assiged To: Kyle Polulak