Recommended Posts

Yeah, I focused on that one, too. You know, the one that makes you wrong yet again, as we've been trying to point out to you.

I agreed with the tweet that I provided, not hiding that. That's why I posted it. But then that's why I also provided in my previous post a better encoded source that skipped the YouTube encoding (which deceased the quality of the image a bit), for much better quality for the likes of you and her.

Now prove me wrong in what? That the PS3 demonstrated version is far less detailed than the PC version, or what?

Because I never said the PS3 version is more impressive than the PC's one :blink:

LOL. Didn't know I'd wondered into a flame war. I do think the PS3 will look great but I also don't think that the PC is as powerful as people make out in practical terms. Sure there is a lot more horsepower but there is also several more times overhead than what you get with PS3 or Xbox 360.

I agreed with the tweet that I provided, not hiding that. That's why I posted it. But then that's why I also provided in my previous post a better encoded source that skipped the YouTube encoding (which deceased the quality of the image a bit), for much better quality for the likes of you and her.

Now prove me wrong in what? That the PS3 demonstrated version is far less detailed than the PC version, or what?

Because I never said the PS3 version is more impressive than the PC's one :blink:

No one here is debating with you that the PC version doesn't look better -- you get that, right? We're debating with you that it looks "like DICE didn't even try" with the console versions, and that the videos and screen captures you've been posting are indicative of what we'll see on our home television sets.

Also, your second video still does not take into account that the image has been compressed when it was broadcast, which you don't seem to be comprehending. Yes, the Youtube version was further compressed, but this is yet another recording of a compressed signal. You've seen the comparisons of a Blu-ray and a movie broadcast in HD, correct? You're going to face a similar issue here.

It wasn't filmed off-screen. It was a direct feed, just like the presentation of the tank battle in E3.

If it wasn't, the end result would be a lot of this: http://i.imgur.com/l2EnK.jpg

Do notice there's no camera in front of the screen to capture the so called "off-screen" footage. And if there was a camera behind Jimmy and the guys from DICE capturing the screen showing the game, we would see their backs as they're in front of the screen. So no, def. not an off-screen footage.

You assume they are filming it from the same screen.

It was already stated on the official Battlefield blog that it was filmed off-screen. And it's pretty clear that it was:

Battlefield 3 just made its public console debut! We went to New York to visit Late Night with Jimmy Fallon, where we played Battlefield 3 live on PS3 in front of the audience. Check it out below. Sorry for the ghosting and rasterizations -- this was filmed offscreen.

http://blogs.battlefield.ea.com/Default.aspx##

^ :rofl:

No one here is debating with you that the PC version doesn't look better -- you get that, right? We're debating with you that it looks "like DICE didn't even try" with the console versions, and that the videos and screen captures you've been posting are indicative of what we'll see on our home television sets.

Also, your second video still does not take into account that the image has been compressed when it was broadcast, which you don't seem to be comprehending. Yes, the Youtube version was further compressed, but this is yet another recording of a compressed signal. You've seen the comparisons of a Blu-ray and a movie broadcast in HD, correct? You're going to face a similar issue here.

honestly, i would be STOKED if they didn't try on the console versions. now the console players know how it feels to be a PC gamer for the last 5 or so years... being treated as the ****** child of gaming.

No one here is debating with you that the PC version doesn't look better -- you get that, right? We're debating with you that it looks "like DICE didn't even try" with the console versions, and that the videos and screen captures you've been posting are indicative of what we'll see on our home television sets.

Also, your second video still does not take into account that the image has been compressed when it was broadcast, which you don't seem to be comprehending. Yes, the Youtube version was further compressed, but this is yet another recording of a compressed signal. You've seen the comparisons of a Blu-ray and a movie broadcast in HD, correct? You're going to face a similar issue here.

The "didn't even try" referred to major missing details in the game (details on walls, on fences, buildings, people in front of you not to speak a few meters ahead of you (lod in general), lighting, shadows and etc.). Not the image quality and compression of the video itself. You can notice the lack of the details even with heavy compression.

And I know the PS3 is limited in power compared to the PC, but games before BF3 had those details perfected even in earlier builds (Advanced Warfighter 2 on the consoles for example. And that game was released back in 2007). And four months before the release, that can't be a demo of that early of a build, of a complete level that was already shown on different platform month (if not two) ago.

You assume they are filming it from the same screen.

It was already stated on the official Battlefield blog that it was filmed off-screen. And it's pretty clear that it was:

http://blogs.battlefield.ea.com/Default.aspx##

That only bring us back to the image quality of the video, and not the details in the game itself.

This is just unacceptable. Look at how horrible the graphics are in real-life!

You should turn on the deinterlace filter in your video player and then try again.

Early speculation is a waste of time.

The game will look great all around. The game will look best on a $2,500 PC, that is the advantage on throwing down g's on a gaming rig. End of story.

Don't like it? Too bad.

Yea but..

Gaming Rig - $2,500

Battlefield 3 PC copy - $60

60 Degree Console FOV - Negative 9,000....

Watch they will manage to screw it up some how.

all that video is doing is showing that a developer is actually taking advantage of the power of a current PCs instead of making a console port. MUCH respect to DICE for that. and that's still a ****ty video to make the comparisons. maybe everything it says is right, but look how muddy the PS3 coverage looks compared to the PC coverage...

I really hope the menu's and what not on PC are optimized for a mouse and keyboard and not a controller though...

I'd rather spend ?150 on a console to be honest..

Agreed. TBH I thought BF3 looked great on PS3 though it is pretty obvious that the PC looks really good if you have the specs for it. I'm more curious to see CoD MW3 vs BF3 comparison imo.

Put it this way, if I could afford it I'd be buying this for PC, along with every other game, because imo PC Gaming is much more enjoyable, in terms of gameplay.. the communities that form.. and the modifications that follow, but I can't so ?150 instead of ?1000 for slightly inferior graphics really doesn't bother me whatsoever.

In no way did I suggest spending money on a new PC just for one game, simply correcting the over exaggeration of the cost for a more than decent PC capable of running it on max. If you have a console and not a good PC for this game, just buy it for consoles. I find it silly anyone would lay down cash to get a brand new computer just for one game unless there's a bigger picture involved besides gaming purposes.

Agreed. TBH I thought BF3 looked great on PS3 though it is pretty obvious that the PC looks really good if you have the specs for it. I'm more curious to see CoD MW3 vs BF3 comparison imo.

Why? Just go look at any other CoD over the past few years and you're looking at it MW3...nothing to compare. BF3 on any platform will destroy CoD visually (fact).

Put it this way, if I could afford it I'd be buying this for PC, along with every other game, because imo PC Gaming is much more enjoyable, in terms of gameplay.. the communities that form.. and the modifications that follow, but I can't so ?150 instead of ?1000 for slightly inferior graphics really doesn't bother me whatsoever.

It won't just be slightly inferior graphics though. It will be inferior gameplay as well. Maps won't be as large and player count will be limited quite drastically too.

It won't just be slightly inferior graphics though. It will be inferior gameplay as well. Maps won't be as large and player count will be limited quite drastically too.

That doesn't bother me, wasn't it the same with BC2? I love that on console so.. don't see how less players can affect gameplay really, just the situations you find yourself in, not the handling.

Like I said, I'd love it on PC, but for the sake of saving ?850 on a console instead of a rig able to play it, then I'm OK.

This topic is now closed to further replies.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!