Dauntless's recent Steam launch proved disastrous, thanks to some changes the developer made to the core gameplay, which we covered in more detail here. Phoenix Labs responded shortly after the controversy, but that original statement was largely seen as dismissive by the community. Now, Phoenix Labs has put out yet another response, this time responding to individual criticisms and laying out a detailed plan for the future of Dauntless.

In the response, Phoenix Labs starts off by apologizing to the community for the lost progression and disastrous Awakening update. Throughout the rest of the statement, the developer breaks down how it plans to address each of the criticisms, including the progression reset, monetization, and core gameplay changes. The most interesting take-away from Phoenix Labs's response is that the returning players will be rewarded with additional in-game resources—300,000 Rams and 5,000 Combat Merits as well as Peerless Aetherite, scaling based on how many weapons players had crafted before the update—to get them back up to speed in the new system. As of Update 2.2.0, dropping "early next year," players will also no longer have to re-do quests they had already previously completed in order to unlock all game modes and regions. Various challenges and monsters have also received reward drop buffs to speed up progression. Monetization changes include making the free battle pass for future seasons more rewarding, and Phoenix Labs also promised to re-evaluate the monetization strategy in future updates "to balance sustainability with fairness while remaining rewarding for players." As for core gameplay changes, Phoenix Labs has already implemented changes to armor perks, shield caps, and weapon buffs based on feedback, and it says that it will continue to find more ways to add diversity and depth to player builds in future updates.

Recent testing has revealed that latest NVIDIA App v1.0 software utility may significantly impact gaming performance, with benchmarks from Tom's Hardware showing frame rate drops of up to 15% in certain games when the new NVIDIA App is installed alongside graphics drivers. The performance issues appear to be linked to the application's overlay features, particularly its game filters and photo mode capabilities, which seem to affect system resources regardless of whether users actively engage with them. Gamers primarily interested in the app's video capture and optimization features can restore regular performance levels by disabling these problematic overlay functions. In the meantime, NVIDIA issued the following statement on its GeForce forums in the "Game Filters and Performance in NVIDIA App" thread:

NVIDIA Official StatementWe are aware of a reported performance issue related to Game Filters and are actively looking into it. You can turn off Game Filters from the NVIDIA App Settings > Features > Overlay > Game Filters and Photo Mode, and then relaunch your game.

Path of Exile 2 today released in Early Access on Steam and consoles, and, despite the game's $29.99 Early Access pricing, it has already managed to amass a peak player count of over 458,920 players on Steam alone. While this is undoubtedly good news for the developer and publisher, the increased server load has apparently already caused problems, resulting in excessive queue times to get into game sessions. At the time of writing, the game has only been available to play for a little over four hours, and the player count is only beginning to plateau now.

According to the Path of Exile X account, the development team has been hard at work trying to stem the bleeding, as it were. So far, the Path of Exile website has been down several times due to the high traffic, preventing players from claiming their Steam keys. Additionally, and somewhat hilariously, this outage has also affected the "Early Access Live Updates" site that was meant to be a resource for gamers to keep track of work the live service team was doing to try and deal with the high launch-day volumes.

The search for a new Chief Executive Officer (CEO) of Intel has begun following Pat Gelsinger's departure on Monday. And it is not exactly an easy role to be filled. The tech giant's board is primarily considering external candidates to lead the company through one of its most challenging periods. Among the potential successors is Lip-Bu Tan, a former Intel board member and semiconductor industry veteran. Tan, who previously served as CEO of Cadence Design, left Intel's board in August 2023 after disagreements with Gelsinger over the company's strategic direction. Despite these past tensions, Intel's board has reportedly recently approached Tan to gauge his interest in the position. The search for new leadership is extremely difficult, considering the requirements and massive problems the new CEO would face.

Coming at a critical moment for Intel, which has experienced significant financial challenges under Gelsinger's tenure, the new CEO would need to get the Foundry business to pick up and maintain a solid product roadmap. The company's revenue dropped to $54 billion in 2023, marking a nearly one-third decline since Gelsinger took the helm in 2021. Analysts project Intel's first annual net loss since 1986 this year, with long-term signs of recovery. Gelsinger's exit, which came after the board presented him with the option to retire or be removed, reflects growing impatience with the pace of his ambitious turnaround strategy. The company has appointed CFO David Zinsner and senior executive Michelle Johnston Holthaus as interim co-CEOs while the search committee works to identify a permanent replacement.

Microsoft's latest Flight Simulator 2024 just launched, and it already appears to be riddled with problems. When internally testing, we ran into some issues regarding long loading times and eventual errors without getting to the game. Additionally, many others confirmed that they were experiencing problems. Launched on 08:00 am PT on November 19, the simulator has faced widespread server infrastructure issues affecting player access. CEO of Asobo, maker of this Flight Simulator franchise, Sebastian Wloch, has released a public statement via video addressing the widespread technical issues that plagued their latest game release. According to Wloch, while pre-launch testing had successfully simulated concurrent player counts of 200,000 users, the actual launch revealed critical weaknesses in the database cache system that weren't apparent during testing.

Additionally, the negative reviews stemming from these issues have piled up. On Steam, the game currently has 2,865 reviews, only 500 of which are positive. The remaining 2,000+ are overwhelmingly negative, with many users not being satisfied with the gameplay and quality of the release. The game's infrastructure is powered by Microsoft's Azure cloud, which is also not good marketing for Microsoft as the Azure platforms should signal better infrastructure scaling and stability. While these issues should be cleared in the long run, the short-term consequences are turning the launch into a colossal failure, as gamers expected more from this release. Lastly, the alpha version of the game was notorious for the massive internet bandwidth hog, causing up to 180 Mbit/s load.

Supermicro shares took a big hit today when Ernst & Young quit as its auditor, making its stock fall over 30%. EY decided to leave because of their worries in July about how Supermicro runs things, shares information, and keeps track of its money. In August, Supermicro delayed its annual report as they were looking over internal financial controls following Hindenburg Research's allegations of accounting manipulation. Ernst & Young's letter to the Securities and Exchange Commission (SEC) about quitting says they can't trust what the company's leaders say anymore. They also don't want their name on the company's financial papers after discovering new information during their check. "We are resigning due to information that has recently come to our attention which has led us to no longer be able to rely on management's and the Audit Committee's representations and to be unwilling to be associated with the financial statements prepared by management."

Supermicro doesn't agree with the accounting firm's decision, and they say fixing these problems won't mean they have to redo any of their financial reports from 2024 or earlier. Commenting on this subject, Nathan Anderson, the founder of Hindenburg, said in a post on X, "As far as auditor statements go, E&Y's SMCI resignation letter is about as strongly worded as I have seen." According to The Wall Street Journal, the Department of Justice is currently looking into the company. Supermicro will present its first quarter fiscal 2025 business update on Tuesday, November 5, 2024, at 5:00 p.m. ET / 2:00 p.m. PT.

During its Q2 2024 earnings call, NVIDIA confirmed that its upcoming Blackwell-based products are facing low-yield challenges. However, the company announced that it has implemented design changes to improve the production yields of its B100 and B200 processors. Despite these setbacks, NVIDIA remains optimistic about its production timeline. The tech giant plans to commence the production ramp of Blackwell GPUs in Q4 2024, with expected shipments worth several billion dollars by the end of the year. In an official statement, NVIDIA explained, "We executed a change to the Blackwell GPU mask to improve production yield." The company also reaffirmed that it had successfully sampled Blackwell GPUs with customers in the second quarter.

However, NVIDIA acknowledged that meeting demand required producing "low-yielding Blackwell material," which impacted its gross margins. During an earnings call, NVIDIA's CEO Jensen Huang assured investors that the supply of B100 and B200 GPUs will be there. He expressed confidence in the company's ability to mass-produce these chips starting in the fourth quarter. The Blackwell B100 and B200 GPUs use TSMC's CoWoS-L packaging technology and a complex design, which prompted rumors about the company facing yield issues with its designs. Reports suggest that initial challenges arose from mismatched thermal expansion coefficients among various components, leading to warping and system failures. However, now the company claims that the fix that solved these problems was a new GPU photomask, which bumped yields back to normal levels.

According to a recently published help guide, spotted by the X/Twitter user @harukaze5719, NVIDIA has addressed reported stability problems users are experiencing with Intel's latest 13th and 14th generation Raptor Lake Core processors, especially the high-performance overclockable K-series models. In a recent statement, NVIDIA recommended that owners of the affected Intel CPUs consult directly with Intel if they encounter issues such as system instability, video memory errors, game crashes, or failures to launch certain applications. The problems seem particularly prevalent when running demanding workloads like gaming on Unreal Engine 5 titles or during shader compilation tasks that heavily utilize the processor and graphics capabilities. Intel has established a dedicated website to provide support for these CPU instability cases. However, the chipmaker still needs to issue a broad public statement and provide a definitive resolution.

The instability is often attributed to the very high frequencies and performance the K-series Raptor Lake chips are designed to achieve, which are among the fastest processors in Intel's lineup. While some community suggestions like undervolting or downclocking the CPUs may help mitigate issues in the short term, it remains unclear if permanent fixes will require BIOS updates from motherboard manufacturers or game patches.

Update: As the community has pointed out, motherboard makers often run the CPU outside of Intel's default spec, specifically causing overvolting through modifying or removing power limits, which could introduce instabilities into the system. Running the CPU at Intel-defined specification must be assured with a BIOS check to see if the CPU is running at specified targets. Intel programs the voltage curve into the CPU, and when motherboard makers remove any voltage/power limits, the CPU takes freedom in utilizing the available headroom, possibly causing system instability. We advise everyone to check the power limit setting in the BIOS for the health of their own system.

The Professional Gamers League (PGL) showcased its newly upgraded tournament rig specification prior to the kick-off of their (still ongoing) CS2 Major Copenhagen 2024 esports event. As reported, over a week ago, competitors have been treated to modern systems decked out with AMD's popular gaming-oriented Ryzen 7 7800X3D CPU and NVIDIA GeForce RTX 4080 graphics cards, while BenQ's ZOWIE XL2566K 24.5" 360 Hz gaming monitor delivers a superfast visual feed. A hefty chunk of change has been spent on new hardware, but expensive cutting-edge tech can falter. Virtus.pro team member—Jame—experienced a major software crash during a match against rival group, G2.

PCGamesN noted that this frustrating incident ended the affected team's chance to grab a substantial cash reward. Their report put a spotlight on this unfortunate moment: "in the second round of a best of three, Virtus Pro were a few rounds away from qualifying for the playoffs, only for their aspirations to be squashed through no fault of their own...Jame experiences a graphics card driver crash that irrecoverably steers the round in G2's favor, culminating in Virtus Pro losing the match 11-13. Virtus Pro would then go on to lose the subsequent tie-break match as the round was not replayed. In effect, the graphics card driver crash partly cost the team their chance at winning an eventual $1.25 million prize pool." PGL revealed, via a social media post, that officials are doing some detective work: "we wish to clarify the situation involving Jame during the second map, Inferno, in the series against G2. A technical malfunction occurred due to an NVIDIA driver crash, resulting in a game crash. We are continuing our investigation into the matter." The new tournament rigs were "meticulously optimized" and tested in the weeks leading up to CS2 Major Copenhagen 2024—it is believed that the driver crash was a random anomaly. PGL and NVIDIA are currently working on a way to "identify and fix the issue."

To all Dragon's Dogma 2 players. We would like to update you on the status of the following items, about which we have received numerous comments from the community. To all those looking forward to this game, we sincerely apologize for any inconvenience.

Regarding Frame Rate
A large amount of CPU usage is allocated to each character and calculating the impact of their physical presence in various areas. In certain situations where numerous characters appear simultaneously, the CPU usage can be very high and may affect the frame rate. We are aware that in such situations, settings that reduce GPU load may currently have a limited effect; however, we are looking into ways to improve performance in the future.

Systems running on older hardware could be excluded from upcoming public versions of Windows 11—the recently released preview/insider build (26052) has introduced all sorts of new features including "Sudo for Windows", an improved regedit, and hidden beneath the surface, an AI-flavored Super Resolution settings menu. Early partakers of version 24H2 are running into instruction set-related problems—Windows operating expert, Bob Pony, was one of the unlucky candidates. Microsoft's preview code seems to require a specific instruction set to reach operational status—Pony documented his frustrations on social media: "Using the command line argument "/product server" for setup.exe, BYPASSES the system requirement checks for the Windows 11 24H2 setup program. But unfortunately, after setup completes then reboots into the next stage. It'll be indefinitely stuck on the Windows logo boot screen."

He continued to narrow in on the source of blame: "Windows 11 Version 24H2 Build 26058's setup (if ran in a live Windows Install) now checks for a CPU instruction: PopCnt." The Register provided some history/context on the SSE4 set: "POPCNT/PopCnt counts the number of bits in a machine word that have been set (or different from zero.) You might see it in cryptography and it has been lurking in CPU architectures for years, pre-dating Intel and AMD's implementation by decades." It is believed that Microsoft has deployed PopCnt as part of its push into AI-augmented software features, although a segment of online discussion proposes that an engineer has "accidentally enabled" newer CPU instruction sets. Tom's Hardware marked a line in the sand: "PopCnt has been supported since the Intel Nehalem and AMD Phenom II (microarchitecture) era—14 years ago—so compatibility won't be an issue for any modern systems. The only users that will be affected are enthusiasts running modified versions of Windows 11 on 15+ year-old chips like Core 2 Duos or Athlon 64." Bob Pony's long-serving Core 2 Quad Q9650 processor—a late summer 2008 product—was deemed unworthy by the preview build's setup process.

During launch-weekend, Payday 3 had a peak of concurrent players (CCU) across all platforms of 218,250, and a peak of 1,347,510 unique players (DAU). Starbreeze Nebula currently has 3,794,172 registered users. Payday 3 matchmaking infrastructure has not performed as tested and expected. Matchmaking software encountered an unforeseen error, which made it unable to handle the massive influx of players. The issue caused an unrecoverable situation for Starbreeze's third-party matchmaking partner.

A new version of the matchmaking server software was gradually deployed across all regions leading to improved performance. However, a software update made by the partner during late Sunday again introduced instability to the matchmaking infrastructure. The partner continues to work to improve and stabilize Payday 3's online systems.

A member of the amusingly named and low populated r/4090Burning subreddit has reported a strange incident where the PSU side of his 12VHPWR connector had melted. Shiftyeyes67k shared his equipment's plight two days ago and included two photos with his story: "Started noticing a smell coming from my PSU (be quiet! Dark Power 13 1000 W) recently that smelled like burnt plastic. Decided to swap it out and noticed that the 12VHPWR cable was burned...From everything I've read this generally happens to the connector on the GPU side so I'm wondering if anyone has seen this yet?" His feedback shows that the relatively new connection standard has ongoing reliability issues, even though most 16-pin connector problem cases have affected beastly GPUs such as NVIDIA's GeForce RTX 4090.

The be quiet! Dark Power 13 1000 W PSU has native support for the 16-pin cable standard, and no type of adapter was used in Shiftyeyes67k's example. Tom's Hardware reported on this sole incident recently, and a be quiet! representative responded to the article's content (updated today): "This is a unique case and we already have reached out to the customer to learn more." The company statement continues: "As our brand is known for highest quality standards, we treat this seriously and have initiated an investigation." be quiet! recommends that any customers experiencing similar issues should contact their support team directly. Tom's Hardware has attempted to get a comment from NVIDIA about the latest problem, but "an Nvidia spokesperson said we may not hear back for a few days due to a company closure."

Microsoft Surface Pro X owners are reporting that their hybrid detachable tablet computer's in-built (front and rear) camera systems have stopped working - user feedback has been popping up on Reddit and the Microsoft Support forum this week. Unfortunate users of the flagship Arm-driven device have attempted to restore normal operation via driver reinstalls, but to no avail. Windows simply displays an error message that states "0xA00F4271<MediaCaptureFailedEvent> (0x80004005)" when the Surface's camera application is launched. A reddit user (Wapitiii) posits that an expired security certificate is the route cause for this issue, which seems to affect all Pro X units.

A couple of crafty Surface Pro X owners have resorted to rolling back their system clocks to May 22 (2023), which seems to restore the camera app's functionality, but this workaround could have potential downsides with online authentication and security checks. A redditor has been in touch with a "support representative, and they confirmed it is a known issue that Microsoft is currently working on." They have suggested another placeholder measure: "The only way to fix it immediately is if you do a full system reset which deletes all applications and files. He said doing a reset that retains user files does not fix the problem. He advised waiting a few days to see if Microsoft puts out a fix versus doing a full reset unless the cameras are needed immediately." The company is currently engaged in its own Build developers conference, where (ironically) announcements have been made about improvements intended for business devices (such as the Surface Pro X) - hopefully Microsoft's engineers can get onto solving this problem, once festivities are concluded.