What a Beta means.

[Leftenent]

We are all excited about the beta launch. For those of you who pre-ordered, you are already playing, for those of us who have not yet done so, it's only a day away.

I wanted to stress that this is a Beta of a full fledged game. It is our opportunity to play in order to give feedback about bugs, suggestions, etc.

This is NOT just an opportunity to play a game for free for a few days to see how awesome it is. Granted, that's a part of the sales appeal. BUT, as a gaming community, we want to see better and polished games.

Please give your feedback to EA. The link to do so is provided here.

Left

 

[LilShortstuf]

Fine take all the fun out of it... but unpolished games full of bugs like BC2 are the best! I mean I love scoping in only to zoom out and having horrible hit reg and C4 not working right and chat box lag and and and and...

Yeah you get my point.

 

[BetterDeadThanZed]

Yeah, some people have trouble distinguishing between a beta and a demo...

 

[Panzer1509]

Am I left out if Im not excited about BF3 and its beta at all?

Just another game coming out we all like. Why the fuzz >.<...

 

[Diezel]

Am I left out if Im not excited about BF3 and its beta at all?

Just another game coming out we all like. Why the fuzz >.<...

Because of the new frostbite engine, the level of graphics, and we are all huge battlefield fans.

 

[Panzer1509]

Because of the new frostbite engine, the level of graphics, and we are all huge battlefield fans.

Still doesnt get me excited about it... :bored:

 

[Mr.SaJoRa]

Still doesnt get me excited about it... :bored:

your weird then.

 

[overlord326]

Some people on the EA forums were saying that the HD 5770 didn't run bf3 well. I don't have any problems with it, I can't run it on ultra because the ultra is a bit buggy but i can run it on high or less.

 

[death180]

I still can't get into the beta, so a bit of a ripoff, but I guess I will just have to play the open beta with everyone else.

 

[Infektion]

theirs alot of people out their who got the pre-order but did not get into, the beta. Your not alone, just be glad they are actually holding an open beta for bf3, I say.

 

[bad_azz_campa]

theirs alot of people out their who got the pre-order but did not get into, the beta. Your not alone, just be glad they are actually holding an open beta for bf3, I say.

this is true

 

[Zubbs]

Are they still resetting stats and ranks after beta? If that's the case, I'm going to slow down playing BF3 then. I don't want to upset myself knowing I lost a lot of what I earned. Yea, they're not hard achievements or accessories, but six+ hours of playing on my time is something that should be rewarded. Especially if we give feedback about gun nerfs, bugs, glitches, etc. We don't get payed to find their flaws, only "licensed" video game testers.

 

[mad pistol]

Are they still resetting stats and ranks after beta? If that's the case, I'm going to slow down playing BF3 then. I don't want to upset myself knowing I lost a lot of what I earned. Yea, they're not hard achievements or accessories, but six+ hours of playing on my time is something that should be rewarded. Especially if we give feedback about gun nerfs, bugs, glitches, etc. We don't get payed to find their flaws, only "licensed" video game testers.

Nope, and here's why.

A beta is a chance to fix bugs and exploits as well as fix compatibility issues. It's also a chance to fine tune weapon balance and in-game mechanics. BF3 beta is a chance to see how the public will react to what they have created, and then "fix" the bugs and stuff people don't like. BC2 was the same way. If BF3's beta is anything like BC2's was, not all the unlocks are available. Therefore, to let someone keep their stats would be to grandfather in the unlocks, which means they may not get certain ones.

Stats get reset because there are final tweaks that are made to the game. To keep stats gives certain people an unfair advantage, even if they've already devoted many hours of their life to testing/playing the beta.


You have much to learn, grasshopper.

 

[Zubbs]

Nope, and here's why.

A beta is a chance to fix bugs and exploits as well as fix compatibility issues. It's also a chance to fine tune weapon balance and in-game mechanics. BF3 beta is a chance to see how the public will react to what they have created, and then "fix" the bugs and stuff people don't like. BC2 was the same way. If BF3's beta is anything like BC2's was, not all the unlocks are available. Therefore, to let someone keep their stats would be to grandfather in the unlocks, which means they may not get certain ones.

Stats get reset because there are final tweaks that are made to the game. To keep stats gives certain people an unfair advantage, even if they've already devoted many hours of their life to testing/playing the beta.


You have much to learn, grasshopper.

Lol, I kinda expected an answer like that. But it is true, and I understand. Thanks for answering my question. College books, here I come.

 

[RandyOglestein]

Are they still resetting stats and ranks after beta? If that's the case, I'm going to slow down playing BF3 then. I don't want to upset myself knowing I lost a lot of what I earned. Yea, they're not hard achievements or accessories, but six+ hours of playing on my time is something that should be rewarded. Especially if we give feedback about gun nerfs, bugs, glitches, etc. We don't get payed to find their flaws, only "licensed" video game testers.

They also said that the stats wouldn't carry over because there was some issue with carrying them over. Not just because it would be unfair, but the programming wouldn't allow it apparently.

 

[Leftenent]

I think stats SHOULD be reset. This is a beta, as Mad Pistol said. It's an opportunity to fine tweak and locate bugs. Playing the beta, whether you report bugs or not, helps locate these and test servers under load.

A Beta is not a demo, or free look at a game. Thus any activity in said game should be zeroed.

 

[CrushedDiamond]

If need be I can take everybody's bug/glitch findings etc and make a full report/database. It's what i'm good at ha ha.

Thru findings many people have found perofrmance loopholes/bugs in programming that have been confirmed to being worked on by DICE.

Also to inform you this IS a old build it is not up to date hence why features that were announced (Commo rose, newer knife animations, damage maps) were now gone, and a lot of bugs like damage ramping were reported by DICE to be already fixed in another (retail based) build. So when you do report a bug do not get upset if they say nothing, more than likely its already fixed in their internal build. It's a new fad in my industry to do it this way instead of (old school) fixing it within the current build the public has access to. Trust me it works wonders in the office ha ha, it allows us to tweak things while not damaging what could be good code. When McKesson (company I work for) was working on (GW2) Social networking site IE: (Battlelog for GW2) We were given a chance to play in house a build of their game before gamescom 2011, We found about 100-150 (rough estimate) bugs/glitches and performance black holes. Many of those bugs we we're told they already knew about and were fixed in another build. In the end it allows them to prove again and again in the designing/programming process what EXACTLY causes the bug. [Ex: Say a gun in BF3 bugs out in the beta, if they changed it in THAT build and it's gone but comes back again its twice as much work to go back and try to recreate the whole issue vs. let's change it and stress the bug in another internal build and if it's fixed it's fixed]

There's some industry insight for you guys :thumbup1:

Seeing as how this is a "PC first made" game we need to show them that the community cares about their work and not shun what I consider a responsibility in a beta player. They are very much going against the grain for a shooter by not doing another money grabbing console port. So please report anything and everything you can even if it's little.

 

[Zubbs]

If need be I can take everybody's bug/glitch findings etc and make a full report/database. It's what i'm good at ha ha.

Thru findings many people have found perofrmance loopholes/bugs in programming that have been confirmed to being worked on by DICE.

Also to inform you this IS a old build it is not up to date hence why features that were announced (Commo rose, newer knife animations, damage maps) were now gone, and a lot of bugs like damage ramping were reported by DICE to be already fixed in another (retail based) build. So when you do report a bug do not get upset if they say nothing, more than likely its already fixed in their internal build. It's a new fad in my industry to do it this way instead of (old school) fixing it within the current build the public has access to. Trust me it works wonders in the office ha ha, it allows us to tweak things while not damaging what could be good code. When McKesson (company I work for) was working on (GW2) Social networking site IE: (Battlelog for GW2) We were given a chance to play in house a build of their game before gamescom 2011, We found about 100-150 (rough estimate) bugs/glitches and performance black holes. Many of those bugs we we're told they already knew about and were fixed in another build. In the end it allows them to prove again and again in the designing/programming process what EXACTLY causes the bug. [Ex: Say a gun in BF3 bugs out in the beta, if they changed it in THAT build and it's gone but comes back again its twice as much work to go back and try to recreate the whole issue vs. let's change it and stress the bug in another internal build and if it's fixed it's fixed]

There's some industry insight for you guys :thumbup1:

Seeing as how this is a "PC first made" game we need to show them that the community cares about their work and not shun what I consider a responsibility in a beta player. They are very much going against the grain for a shooter by not doing another money grabbing console port. So please report anything and everything you can even if it's little.

I almost didn't read that massive blog of a paragraph, but I did, and I'm happy I did. Thanks for informing us (or just me) about how that process works.

One thing you said was to possibly create a report proposing all the bugs the clan members found. Should we, as dedicated PC gamers, make a thread dedicated to finding bugs and reporting them? Like one specific bug I can think of currently is the reticules on any sight attachment to disappear over smoke (maybe even fire).

 

[Panzer1509]

well this sucks

 

[DEPUTYDAWG8025]

Still doesnt get me excited about it... :bored:

Maybe thats cuz your an Operation:X guy Not a Battlefield Division guy.