Never has crashing pissed me off more, game crashes, server crashes. A game where progression means so much and is so satisfying, and then you lose it fucking all. I've now unlocked the compensator for the M416 3 times, and I have to unlock it AGAIN..
[QUOTE=Zar;42775803]Never has crashing pissed me off more, game crashes, server crashes. A game where progression means so much and is so satisfying, and then you lose it fucking all. I've now unlocked the compensator for the M416 3 times, and I have to unlock it AGAIN..[/QUOTE]
For future reference in regards to client crashes: If you don't reconnect the server saves your progress and uploads it at the end of the match. So if you are having a good game then get booted, just don't rejoin.
[QUOTE=Raidyr;42775824]For future reference in regards to client crashes: If you don't reconnect the server saves your progress and uploads it at the end of the match. So if you are having a good game then get booted, just don't rejoin.[/QUOTE]
No shit, I can't just rejoin a server that dies and begins on a new map. I guess this means don't play any map at all? I heard it doesn't always workj. it sucked so fucking much losing 17.000 xp, and 3 unlocks.
[editline]6th November 2013[/editline]
i mean play on any server at all
[QUOTE=codemaster85;42775772]except BF4 is expected to be very clumsy with optimization because just look at it. somehow the graphics for ghosts went down from blops 2, and runs even worse.[/QUOTE]
"Clumsy with optimization" is a laughable understatement given the current state of affairs.
[QUOTE=Raidyr;42775859]"Clumsy with optimization" is a laughable understatement given the current state of affairs.[/QUOTE]
apparently not when there are plenty of people able to play the game with different kinds of hardware. it could be even worse and be like bf3's launch. also you missed my point completely with how ghosts looks like shit yet is having framerate problems with all consoles and PCs.
R6 update: Fixes most common server crash
R7 update: fixes most common server crash and some minor fixes
I'm confused...
[QUOTE=codemaster85;42775916]apparently not when there are plenty of people able to play the game with different kinds of hardware. it could be even worse and be like bf3's launch. also you missed my point completely with how ghosts looks like shit yet is having framerate problems with all consoles and PCs.[/QUOTE]
Actually plenty of people on different kinds of hardware can't play the game because of the constant client and server crashes. When they do get in they have to contend with a battery of bugs that range from annoyances to literally gamebreaking.
But honestly I'm really not interested in having a pissing contest about which unfinished military shooter came out the least unfinished. In fact I'd be happy if we could go a year without the resident Battlefield thread turning into CoD hate circle jerk echo chamber every November.
Actually on topic: How the fuck do I get 50 marksman ribbons? I don't even like sniping.
[editline]6th November 2013[/editline]
[QUOTE=Red_Bullet;42776286]R6 update: Fixes most common server crash
R7 update: fixes most common server crash and some minor fixes
I'm confused...[/QUOTE]
Even more confusing is that servers are still crashing. Getting better though.
What we really need is a client patch for these crashes and something to fix whatever the fuck is wrong with their hit detection to simultaneously cause people to be unhittable while at the same time allowing seemingly one shot kills.
Jesus why are you guys arguing about CoDvsBF again? We're through this shit since forever, drop this, it's bad for you.
[QUOTE=Zar;42775262]MOTHERFUCKERS THEY DIDNT FIX SERVER CRASHING.
I JUST HAD THE BEST GAME OF MY LIFE, 46/10 BY DRIVING AROUND A TANK, I THINK I HAD A 20 KILLSTREAK THEN THE SERVER DIES FUCK I UNLOCKED SO MUCH STUFF AND LEVELED UP[/QUOTE]
I'll just wait a week or two before carrying on my MP career. Too many problems right now.
If you were my friend and gave me money for BF4, I would make DAMN SURE THAT'S WHAT I USED IT FOR! Shitty friend.
Knife him and take his dogtags...having no BF4 is driving me insane...
[img]http://i.imgur.com/yR61iUN.png[/img]
I had a feeling they rushed it because of COD
Kind of a dick move for him to post it anyway, but it's nice hearing what's going on from the inside.
He's totally right about how everything DICE says gets misinterpreted, misconstrued, and used against them. Just look at how many people still perpetuate the "mod tools are too hard so they won't ever release mod tools" myth, and then cite the very posts that explicitly state that's not the case to support their arguments. DICE has always been burned when they try to explain what's going on, so I completely understand their silence on the matter, disappointing as it may be.
[QUOTE=Skela;42775522]Gave my friend the last of my money to pick up a copy of this while he was in gamestop, bought me COD Ghosts instead and some League Of Legends RP Cards for himself with the remainder.
What.[/QUOTE]
Return the game ASAP and talk to your friend about it firmly about it
[editline]6th November 2013[/editline]
Like I'm curious to know why he got that instead
[QUOTE=Why485;42776657]Kind of a dick move for him to post it anyway, but it's nice hearing what's going on from the inside.
He's totally right about how everything DICE says gets misinterpreted, misconstrued, and used against them. Just look at how many people still perpetuate the "mod tools are too hard so we won't ever release mod tools" myth, and then cite the very posts that explicitly state that's not the case to support their arguments. DICE has always been burned when they try to explain what's going on, so I completely understand their silence on the matter, disappointing as it may be.[/QUOTE]
How is it a dick move to have an insider's perspective? He admits that the game was rushed, but it's always nice to have a how and why.
I think he was referring to how the DICE guy preferred he didn't post their conversation directly, which he said he wouldn't do but did anyway.
[QUOTE=Bloodshot12;42776808]I think he was referring to how the DICE guy preferred he didn't post their conversation directly, which he said he wouldn't do but did anyway.[/QUOTE]
Oh, yeah. My mistake.
[editline]6th November 2013[/editline]
While I'm Page King might I mention how I despise whoever came up with the marksman ribbon.
[I]"Yeah, let's just reward people for camping WAY back and get headshots, I'm sure that will encourage people to do teamwork and accomplish the objective. No way this could backfire at all."[/I]
[QUOTE=StrawberryClock;42776742]How is it a dick move to have an insider's perspective? He admits that the game was rushed, but it's always nice to have a how and why.[/QUOTE]
It's actually pretty silly. There should be automated tests performed [i]every[/i] night that would catch crashes and bugs. DICE has money, they have EA, and they have time to get this shit done.
For those that are not in the software world, automated testing goes something like this: fake server setup, with fake players. Input is sent to the players+other stuff, and the result is then compared to the expected result. Each test is then marked as a pass/fail (sounds are a bit more difficult to test, but the code that runs those sounds should still be hit).
[QUOTE=Foda;42776967]EA has the money DICE deserves, EA owns DICE, and they are given about 80% (at best) of the time they need to get the shit done that EA commands them to do.[/QUOTE]
ftfy
[QUOTE=StrawberryClock;42776742]How is it a dick move to have an insider's perspective? He admits that the game was rushed, but it's always nice to have a how and why.[/QUOTE]
I think he meant that "posting the whole conversation, including the part where the QA guy kind of asks him not to publicly post the conversation but rather use the points made to explain things" was a dick move, but he was kind enough to censor stuff, AND include the fact that the guy actually said that it wasn't an official statement but a QA guy
everything in the dude's answers is exactly everything I and others have been saying and I'm glad he gave it more perspective about just how many man hours went into player experiences vs how much time QA could have ever hoped to log over the course of the game's entire development, in just [i]one hour[/i]. I know people think QA testing is so simple as just playing the game but it took a number of days of public gameplay for someone to pinpoint the particular rifle and silencer as a definite cause. Take into account how many hours had been logged by how many people before a competent person even realized it was the cause and reported it
[editline]e[/editline]
wow newpage
Anyone willing to buy this for me if I give them Fallout New Vegas Ultimate Edition on Steam, Payday 2 and Space Engineers?
[QUOTE=Foda;42776967]It's actually pretty silly. There should be automated tests performed [i]every[/i] night that would catch crashes and bugs. DICE has money, they have EA, and they have time to get this shit done.
For those that are not in the software world, automated testing goes something like this: fake server setup, with fake players. Input is sent to the players+other stuff, and the result is then compared to the expected result. Each test is then marked as a pass/fail (sounds are a bit more difficult to test, but the code that runs those sounds should still be hit).[/QUOTE]
I'm not a programmer but that sounds like BS tech you'd hear about on a CSI show and I want to make a snarky comment about how we should just program a program that programs the game for us
[QUOTE=Why485;42776657]Kind of a dick move for him to post it anyway, but it's nice hearing what's going on from the inside.
[/QUOTE]
I kinda feel dirty reposting it, yeah, but I think it's justified. First, it's the very conversation that took place, now it can't be twisted. It's DICE QA guy honest and personal perspective, clear of all sensationalism there could've been. The guy who posted it made a good job ensuring that, I don't think he really backstabbed anyone.
I believe it's completely okay to post it. It does more good than harm, it somewhat clears QA team from recieveing all of the unjust flak.
I'm getting so fucking frustrated at having my multiplayer character decide to rush forwards and not let me stop or look in a different direction or crouch or anything five times every minute, and the lag, and the random crashes, and fucking hell it's just so fucking annoying
Some bugs and glitches will slip through the cracks obviously. In fact, the two most frustrating ones, client and server crashes, are to be expected and are the most forgiveable. They are taking too long to fix them of course but when you release a game to the public, the amount of hardware configurations it's put through explodes exponentially. Anyone who expected a game like BF4 with all of it's moving parts to have a perfect launch is kidding themselves.
What I don't understand is how the reproduceable bugs got in, or more specifically, how so damn many of them got in. The reference to the silenced Spas 12 I think is supposed to be a tip off to how the QBU88 bug got in but even then, how did these horrendous netcode issues get past QA? Did they just not test it outside of an office connection? What about ground deformation under Obliteration bomb sites? At no point during their test sessions did anyone ever blow up a tank, C4, or drop a cruise missile to create a crater and make planting impossible?
The emblem editor really needs more layers. 20 is just so few to do something really good.
Not sure if anyone knows, but if I buy the PC version at GameStop, is it just a download code for origin? I recently got a job there, so I'd like to take advantage of my 15% employee discount :v:
[QUOTE=Hellohmhello;42777400]The emblem editor really needs more layers. 20 is just so few to do something really good.[/QUOTE]
40 is the max if you have premium.
[img]http://i.imgur.com/qMS5Or7.gif[/img]
Not mine
Really surprised at how bad the netcode is in this compared to BF3. Getting shot through walls every time I play all of the sudden.
LSAT is now my new favorite sniper
Sorry, you need to Log In to post a reply to this thread.