Recommended Posts

It actually started on January 28th 2010 and ended on February 25th 2010. I believe that's a full month.

it was definitely longer then two weeks. because i bought my slim when they first came out, ran through metal gear which was the only game i had at the time, and played the beta religiously because it was the only game i had that was MP on my PS3 :rofl:

it was definitely longer then two weeks. because i bought my slim when they first came out, ran through metal gear which was the only game i had at the time, and played the beta religiously because it was the only game i had that was MP on my PS3 :rofl:

Yes indeed. See here: http://blogs.battlefield.ea.com/battlefield_bad_company/archive/2010/01/07/bfbc2-pc-beta-update-fr-229-n-dice.aspx

It shows the dates I mentioned.

trag3dy should also take a look at this and this. :p

Yes indeed. See here: http://blogs.battlefield.ea.com/battlefield_bad_company/archive/2010/01/07/bfbc2-pc-beta-update-fr-229-n-dice.aspx

It shows the dates I mentioned.

trag3dy should also take a look at this and this. :p

wow that's an ownage going through one of the biggest threads in neowin history...

wow that's an ownage going through one of the biggest threads in neowin history...

It wasn't my intention to "pwn" him, haha. I simply used a certain skill of mine to remind him of something he once knew. :)

Anyway, I'm still a little disappointed at DICE. Either they're confident that the game won't launch with a lot of bugs or they really want to get it out before Modern Warfare 3. I have a feeling it has more to do with the latter than the former. A beta shouldn't last less than two weeks.

Crossfire 6870s, OCed. Should be interesting how close I can get to maxing this. My i7 960 and 12gb ram should cover the rest... but still. Hopefully I won't need 6990s in cross. Trying to wait until next gen of cards before an update..

Nowhere near, you need SLI 580s to run it in Ultra. The Quad Core, 6950 recommended specs are aimed at running the game in Medium.

There isn't that much of a difference...

http://www.guru3d.com/article/geforce-gtx-580-sli-review/6

Im not making it up im going off what the DICE employees on twitter are saying.

The Recommended Specs are for Medium Detail only and to run the game in ultra you need SLI 580s, one 580 wont cut it.

bkohn1 so would one GTX580 run it on ultra? Or do I need two of them?

zh1nt0 @bkohn1 2

http://twitter.com/#!/zh1nt0/status/116140729864159232

Judging by everything else they're saying even though they've made it I'm sure you'll have to take their hardware configuration opinions with a grain of salt. You won't need 580's in SLi unless they're working on next crysis 1 engine to bog your system down with that struggles to have stable 30+ for the next 2 years.

Pretty much there's 3 levels of hardware low, medium and high then standards/quality of play up to 30, in between and 60+ fps.

Let's say SLi 580 you'll probably have ultra @ 1920x1080 with 60+. If you have say i5 2500k + 6970 2GB you may get high/medium @ 1920x1080 at 60fps plus but you can also play ultra but at maybe 30-50 area which is still playable. It will go on like that.

What dice are doing is just looking at the hardware profile without technical details or specifics. They want quality of game so they'll chuck everything in highest fps range even if it reduces visual quality thanks to opinions of consolers who think fps matter on consoles so if it runs best at medium even with a i7 990X @ 4.2GHz 16GB ram and 2xHD6990's that'll be what they suggest.

This is all i've picked up on watching their recommendations on twitter.

The PC requirements sound ridiculous for medium. :s Hope it is based on trying to achieve massive FPS as Digitalx suggested.

Wonder how my 5830 will stack up. Has handled everything I've thrown at it so far. Will have to try the beta and see... not spending ?200+ on a video card.

Im sure i read on one of the DICE team twitter that the min/rec specs are aiming for 30fps.

The Alpha ran fine on my Quad i5 Sandybridge with 5850 but then tesselation and Destruction 2.0 werent enabled neither where high quality graphics. Hoping i can scrape by with my spec in high detail if i turn SSAO/AA/Tesselation off.

I don't understand - what's unique to this game? The weapons seem the same as from war games in the past 10 years, map are just different layouts from ones we've had for 10 years (if that makes sense).

I play Bad Company 2 but it's practically the same as the Medal of Honor: Allied Assault multiplayer from 2002 - same weapsons etc.

Enlighten me. I'm not being a douche, I need need persuading a little as I don't understand.

I don't understand - what's unique to this game? The weapons seem the same as from war games in the past 10 years, map are just different layouts from ones we've had for 10 years (if that makes sense).

I play Bad Company 2 but it's practically the same as the Medal of Honor: Allied Assault multiplayer from 2002 - same weapsons etc.

Enlighten me. I'm not being a douche, I need need persuading a little as I don't understand.

If you played Bad Company 2 and think that is was practically the same as MoH; Allied Assault, well also not being a douche, but you will never understand if you feel that way, as it is truly NOTHING like that game.

If you played Bad Company 2 and think that is was practically the same as MoH; Allied Assault, well also not being a douche, but you will never understand if you feel that way, as it is truly NOTHING like that game.

I've played them both a lot. Let's assume we're talking team deathmatch - the weapons are practically the same, the maps are similar (not in layout but in style). BC2 has destruction and a tank - but not much else is different to me.

I've played them both a lot. Let's assume we're talking team deathmatch - the weapons are practically the same, the maps are similar (not in layout but in style). BC2 has destruction and a tank - but not much else is different to me.

Well if you really have played both games a lot, I am not sure how you can say not much else is different, as destructibility and vehicles alone drastically separates the two games IMO. Also, Battlefield has never really been a Team Deathmatch game at all. It has always been a team objective based game. Also classes and squads play a huge role in Battlefield.

And technically, you can pretty much say all FPS's set with a realistic tone the weapons are practically the same, but technically the weapons are not the same at all in the two games being compared. One is a WW II based game and the other is a modern based game, so the weapons are not the same weapons at all really. But yeah sure, they are similar, any gun in any war based FPS ever made most of the weapons are similar, you pull the trigger and something fires out of said weapon.

Not even sure why I am trying to explain it to you, especially if you have played them both a lot as you claim and this is the decision and outcome you have come to. So it is really pretty simple, do not play the game if you feel that it has nothing for you. Trying to convince you otherwise is obviously a moot point.

Well if you really have played both games a lot, I am not sure how you can say not much else is different, as destructibility and vehicles alone drastically separates the two games IMO. Also, Battlefield has never really been a Team Deathmatch game at all. It has always been a team objective based game. Also classes and squads play a huge role in Battlefield.

And technically, you can pretty much say all FPS's set with a realistic tone the weapons are practically the same, but technically the weapons are not the same at all in the two games being prepared. One is a WW II based game and the other is a modern based game, so the weapons are not the same weapons at all really. But yeah sure, they are similar, any gun in any FPS ever made most of the weapons are similar, you pull the trigger and something fires out of it.

Not even sure why I am trying to explain it to you, especially if you have played them both a lot as you claim and this is the decision and outcome you have come to. So it is really pretty simple, do not play the game if you feel that it has nothing for you. Trying to convince you otherwise is obviously a moot point.

I just can't help but feel BF3 will feel and play very similar to BF2 and BF1942 but with posher graphics.

I just can't help but feel BF3 will feel and play very similar to BF2 and BF1942 but with posher graphics.

that's how i feel about the game so far, but to millions of people out there, i'm sure that's fine with them. Also in my mind this game doesn't exist to me because it's not on steam.

This topic is now closed to further replies.
  • Posts

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!