Recommended Posts

Finally got the update just now, first thing I checked was if the Resume games quickly option is still considered Beta. It is. Remaining disabled for now.

So far Forza (when in a race) is the only game that has had any issues and all that would happen is the game would reload basically.

Depending on when you last played AC4, there has been a title update recently, I launched at AC4 yesterday to get greeted with a 2.3GB update or so.

 

http://forums.ubi.com/showthread.php/827736-Title-Update-4-Multiplayer-Patch-notes?s=2d982acfcd209241c348b704c6949f62

 

Hrm yeah I wondered that but that list doesnt seem to mention anything, I suspect the size will be preloading some DLC textures etc but no idea.

Auto updates means I only really notice the notification saying it was patched.

Performance updates could mean a number of things but if games look better in the end who's to complain? I bet we'll see more of a update to overall performance with the March update before Titanfall.

Has anyone noticed other things like boot times being quicker or apps/games loading faster etc? Those are some of the things that benefit from "performance" improvements.

It would be nice that if the March update really does improve the way developers use the esram and it does give a huge performance boost like it is rumoured to give they would be able to patch their current games to improve the resolution like on the PS4 with ghosts and AC4.

What about 24hz Bluray voice sync fix? Anyone test a Bluray at 24hz yet?

For me this was fixed a few weeks back with an update to the Blu-ray player app. I've turned 24hz back on and it seems to work without issue now.

Apparently there is a black screen bug with the latest update but this fix might help. Just posting it for future reference; don't think anyone has reported running into it here.

 

Xbox One update - how to fix the black screen problem
 

MS should fix the battery power indicator on the 360! Even tho it's got it, it's wrong. LIke I can recharge the batteries and the thing is flat even if 3 bars are showing. It never gets to 1-2 bars before the controller starts playing up

 

This topic is about Xbox One...

 

Check Xbox Support for that problem.

MS should fix the battery power indicator on the 360! Even tho it's got it, it's wrong. Like I can recharge the batteries and the thing is flat even if 3 bars are showing. It never gets to 1-2 bars before the controller starts playing up

 

I think that's an issue with the battery rather than the OS. How old is it?

Apparently there is a black screen bug with the latest update but this fix might help. Just posting it for future reference; don't think anyone has reported running into it here.

 

Xbox One update - how to fix the black screen problem

 

 

I had this exact problem - I was playing AC 4, and had this issue. After several forced reboots, it came back up and has been working fine ever since.

I had this exact problem - I was playing AC 4, and had this issue. After several forced reboots, it came back up and has been working fine ever since.

 

I had this trying to play the Titanfall Beta, just unplugged the console and went back later.

Apparently there is a black screen bug with the latest update but this fix might help. Just posting it for future reference; don't think anyone has reported running into it here.

 

Xbox One update - how to fix the black screen problem

 

Had this in AC4 as well but I put it down to using a different monitor from before (I changed not long before the update) but I turned it off then back on and all was fine. I didnt do those instructions as such.

Had this in AC4 as well but I put it down to using a different monitor from before (I changed not long before the update) but I turned it off then back on and all was fine. I didnt do those instructions as such.

 

 

I had this trying to play the Titanfall Beta, just unplugged the console and went back later.

 

 

I had this exact problem - I was playing AC 4, and had this issue. After several forced reboots, it came back up and has been working fine ever since.

 

Good thing I posted it then, hopefully it comes in handy for anyone in the coming weeks. Did you guys comment on the issue? I think I must have missed them.

 

Hopefully the March update fixes it for good, but at least there is a workaround in the meantime (Y)

Good thing I posted it then, hopefully it comes in handy for anyone in the coming weeks. Did you guys comment on the issue? I think I must have missed them.

 

Hopefully the March update fixes it for good, but at least there is a workaround in the meantime (Y)

 

No like I said I initially put it down to an idiosyncrasy of the monitor I was using, that monitor has in the past gone black as well when using Dual DVI via PC. After rebooting the xbox the problem has not reoccured.

No like I said I initially put it down to an idiosyncrasy of the monitor I was using, that monitor has in the past gone black as well when using Dual DVI via PC. After rebooting the xbox the problem has not reoccured.

 

Ah ok understood. I've had the same problem you described on 360 and PS3 in the past when I've switched displays. I believe it's because of the preferences / display settings not adjusting correctly. There's a hidden boot up process on PS3 and 4 I think, but not sure X1/360 have anything similar.

 

Glad you got it sorted either way.

Good move. Think there was some people on Neowin disputing it even existed!

i know you're talking about me(by the way i agreed there was an output bug with a certain colorspace setting,just that its not a sharpening filter)

just found this funny, thought id share. from DF today

It didn't solve the problem anyway: while games such as Dead Rising 3, Killer Instinct and Call of Duty appeared smoother and more natural this way rather than using the scaler, forcing 720p output didn't seem to entirely disable the unwanted filter. A close look at edges on a pixel level showed that the sharpening effect (halos around objects) was still present, just operating with a significantly lower intensity.

lol, so it has nothing to do with the upscaler. its still present on native output. how can this be? native 1080p games don't have this issue. dun dun dun,its not a sharpening filter. its a colorspace bug in 720p mode. it only looks worse when upscaled because the image goes through some algorithms. I've said this repeatedly, on a full rgb display, it doesn't happen.

Do Gamers' Hangout regulars want pinned topics to discuss the OS updates for X1 and PS4 or would you prefer individual topics for each update?

 

We used to have official topics but the OPs didn't keep them up to date. Wouldn't be much use indexing the updates ourselves even now, as wiki does that already, but you could talk about most wanted / wish list features etc.

 

If not we can close this topic and start a fresh one for the March update.

Do Gamers' Hangout regulars want pinned topics to discuss the OS updates for X1 and PS4 or would you prefer individual topics for each update?

 

We used to have official topics but the OPs didn't keep them up to date. Wouldn't be much use indexing the updates ourselves even now, as wiki does that already, but you could talk about most wanted / wish list features etc.

 

If not we can close this topic and start a fresh one for the March update.

New topics would keep things more organized instead of one massive thread that could end up being 20+ pages long at least.

New topics would keep things more organized instead of one massive thread that could end up being 20+ pages long at least.

 

That is my personal preference too but I wanted to get some feedback from the rest of you :)

 

We can just have an "official" topic for each big update. As the generation goes on these patch topics don't reach 8 pages for small improvements anyway.

This topic is now closed to further replies.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • 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.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!