Recommended Posts

About damn time games started using the hardware! Sick of games being held back by 8 year old consoles. I bet AMD and NVIDIA also love this. For years you could run games extremely well with really old cards.

GTX460s aren't exactly new anymore.

I think it's clear that this is going to be a poor pc port, seeing as they easily have it running on 360/ps3. 

I'm all for pushing steep requirements (I have a SLI 760's setup) , I've been waiting for these new consoles for years to help give graphics the boost PC has been patiently waiting on.

But I think company's should still provide settings for older computers to run their games, or they will make PC gaming look even more elitist than it is currently portrayed. 

 

I'm fairly confident watch dogs could run on well under 4gb of ram if it was optimized correctly. Most top of the line games don't usually push more than 2-3gb of use.

 

DX11 and 64bit OS is fair enough though. 

 

Looking forward to this one.

  • Like 2

I think it's clear that this is going to be a poor pc port, seeing as they easily have it running on 360/ps3. 

I'm all for pushing steep requirements (I have a SLI 760's setup) , I've been waiting for these new consoles for years to help give graphics the boost PC has been patiently waiting on.

But I think company's should still provide settings for older computers to run their games, or they will make PC gaming look even more elitist than it is currently portrayed. 

 

I'm fairly confident watch dogs could run on well under 4gb of ram if it was optimized correctly. Most top of the line games don't usually push more than 2-3gb of use.

 

DX11 and 64bit OS is fair enough though. 

 

Looking forward to this one.

 

 

 

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  

it's time to kill 32bit and it's unreasonable 4GB limit.

 

Nothing unreasonable, it's just math, unless math are unreasonable?

The switch to 64bit for games would have happened sooner or later anyway, the 2Gb per process boundary and graphics memory adressing requirement have been pushing the boundaries for a while. Even blizzard had to compile a 64bit version of Wow to accomodate for some setups.

  • Like 1

The 4GB limit is probably one of the lesser of many reasons to move to 64 bit. 

Not so much.  Texture RAM on the GPU and audio is mapped to that 4GB, so you choke out your AI and other processes with it the more stuff you have.

 

It's the most important reason to move games to 64 bit.

It's about time some commercial software started taking advantage of all the power on users' desktops. Funny thing, all those x86-x64 systems with 8GB Ram that have been upgraded over the years to overpower poorly written 32-bit software would be powerhouses now...

I think it's clear that this is going to be a poor pc port, seeing as they easily have it running on 360/ps3. 

I disagree. Ubisoft games have a very good track record on PC and usually are well optimised. The fact that the specs are so high and they're making 64bit a requirement only shows how seriously they're taking it, as that will seriously limit their potential audience. While it's disappointing that it won't scale my hope is that the game will be all the better for those able to run it. To me it indicates that PC gamers are getting the full next-gen experience rather than a dumbed down X360 / PS3.

 

We'll see how well the game does but I still have high hopes for it. Ubisoft stated early on that the PC is the lead platform, which is a lot better than the contempt we get from Rockstar. I just hope it can live up to its lofty ambitions.

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!