Recommended Posts

What the hell? The generation went from strongest launch lineup ever to the usual hit and miss. So now its basically Killzone and Driveclub for PS4 day one. This is very disappointing from a gaming point of view.

 

One game doesn't kill the lineup, still the best lineup since consoles went 3D. I don't have time to play all these games anyway. 

Sure, I hate to see the game delayed, and would have bought it at launch if it was there.

 

But if it's not there, well there's to many other good games for me to play to care to much if it's not available. I don't have time to play all the good games anyway. 

Meh, no big deal. I wasn't going to get it for the PS3 anyway, instead waiting for the PS4 version, so this doesn't affect me in any way. And I would rather that they take the time to polish it off rather than do what almost every other team seems to do, release a half-baked idea with a day-one patch to clear up the bugs that make the game unplayable.

then explian the 2011 demo of it that had no console  tied to the game  the game is first PC then next gen including Wii U  and then current Gen 7th gen consoles   so  it is not gonna be a Port  unless you consider  a PC port to PC a port  then sure  

 

I just meant to say, if they have the game running on 360/ps3 in some way, they could surely provide settings for it to run fine on 4gb of ram.

In fact, I will damn near guarantee that this game will be pretty playable on 4gb of ram anyway, with some occasional stutter in certain instances. 

 

If it's a crap port than a high end CPU may be necessary even on low settings. Hopefully not. 

mATX Intel G41-chipset motherboards fall into this category if they only take DDR2 (example - ASUS P5G41-M LX2/GB - I have this mobo currently).  The CPU is Intel's Q6600 (not just x64, but quad-core to boot); however, the RAM is DDR2-800 (2GB x2).  If it took DDR3 (there *is* a DDR3 version of this board, with the same chipset) I would not be so *stuck*.  The issue is the type of RAM and the MCH, as 4GB DDR2 DIMMs, when they were available, have always been pricier than their faster DDR3 relatives - it makes more sense to change sockets altogether than to purchase another motherboard in what is basically a dead socket.

 

A setup like this really shouldn't be expected to play any new games, your pushing below "low end". 

What the hell? The generation went from strongest launch lineup ever to the usual hit and miss. So now its basically Killzone and Driveclub for PS4 day one. This is very disappointing from a gaming point of view.

Don't know about Killzone, but DriveClub was delayed not that long ago: https://www.neowin.net/forum/topic/1182865-driveclub-officially-delayed-until-2014-sony-confirms/

this is mad ! and to think of all the digital retailers selling pre-orders already ! glad I didn't pre-order..

I pre-ordered the ps4 before I knew when it would launch.. just because something gets delayed doesn't mean don't pre-order it.  I pre-ordered destiny.. I have no clue when it will launch.

  • 1 month later...

A setup like this really shouldn't be expected to play any new games, your pushing below "low end". 

IN whose opinion, sir?  Never mind that the same setup runs BF4 or even NFS Rivals (their x64 executables, no less) with little issue from the CPU end.

 

I'm not saying that this isn't old hardware - I stipulated that the setup is, in fact, DEAD (as in no longer manufactured) hardware.

 

However (and this has been my point, with this thread and the similar thread regarding NFS Rivals) it has taken exactly how long for x64 to be leveraged properly by a mainstream game?

 

Look at how long it has been since x64 has been in the mainstream - note that even Q6600 didn't lead that.

 

And despite how long it has been since merely the first x64 P4 (let alone Athlon64 and Opteron) the first x64 operating systems had to be given away.  (Note that I'm referring to Windows XP Professional x64 Edition - it was NEVER sold even via the OEM channel.)

 

The x64 application push came during the Vista era - to a whimper.  (Microsoft Office 2010 x64 was the first x64 productivity suite - and it was basically a yawnfest.)

 

x32 gaming didn't push RAM utilization - mostly because it can't.  (Even within an x64 based flavor of Windows, an x32 application - or x32 game - is limited to 4 GB of RAM.  Most gamers don't run even other applications - let alone other games - while playing a game; that means if you have even 8 GB of RAM - let alone even more - what is the rest of your system doing while you're gaming?  Typically, it's loafing - by force.)

 

Back when this motherboard was designed and built, x64 was an outlier - when it comes to gaming, it's still largely is an outlier.  How well will Watch Dogs be received - remember, unlike BF4 or Rivals, there is no x32 option whatever.

 

(Here's a rather surprising fact - Watch Dogs is the first game OR application to have a FLOOR greater than 4 GB of RAM; to put that in perspective, the floor for Watch Dogs is twice the recommendation for either the current RTM or beta of Microsoft SQL Server - in both cases, it's 3 GB of RAM.)

 

In a real sense, Watch Dogs is,  even among x64 games, a major outlier (by having no x32 option).  It's not Waterfox (the x64-compiled Firefox) or even Word, let alone Rivals or BF4.

 

While quite a number of us (and that includes me) would really like to say "It's about time!", how well the game actually acts when it releases will be the proof of that.

 

And even INCLUDING Watch Dogs, do you realize that the number of x64 games for Windows out there will still be countable on one hand?

BF4 can be forced to run on very low settings, and NFS is a bad console port so the bad resource usage (Where it uses too little) is to be expected (GTA4 had a similar issue, throwing more CPU/RAM at it didn't help)

I just meant to say, if they have the game running on 360/ps3 in some way, they could surely provide settings for it to run fine on 4gb of ram.

In fact, I will damn near guarantee that this game will be pretty playable on 4gb of ram anyway, with some occasional stutter in certain instances. 

 

If it's a crap port than a high end CPU may be necessary even on low settings. Hopefully not.

It's limited to hell and back on the 360/PS3 though, textures are very low res, you'd have simplified (and less) AI, etc.

I think this is just a case where due to higher specs on the next gen consoles, devs can simply code sloppy to take up as much resources with little to no optimization and footprint monitoring and reduction.

 

It isn't so much that the game features require these new specs and services, it's that they can throw stuff against the wall and see what sticks.

I suppose this could be considered a transition period? 64-bit will eventually be the common standard in PC gaming, this is just the early days of it.

 

Anyway, if you are part of the PC master race you need to expect (and are constantly demanding) the latest and greatest.

I think this is just a case where due to higher specs on the next gen consoles, devs can simply code sloppy to take up as much resources with little to no optimization and footprint monitoring and reduction.

 

It isn't so much that the game features require these new specs and services, it's that they can throw stuff against the wall and see what sticks.

 

Do you really believe that? You really believe BF4 on Ultra Settings, at 1080p, 60+fps doesn't require that? No dropped frames, screen tearing, or hiccups. Rather, it's because of sloppy code it won't run like that x32 on a i5 with 2GB ram and iGPU?

This topic is now closed to further replies.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • 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
      591
    2. 2
      +Edouard
      187
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      75
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!