Grand Theft Auto 5 Still Shows Significant Bugs, Even After the Long Wait!

We previously announced what everyone found out while trying to get Grand Theft Auto 5 running in 4K and ultra-high graphics settings. Well, the 14GB VRAM usage was not as it seems. It was just a big annoying bug!

Yes ladies and gentlemen, even after the long wait for the title to get released on the PC, it still comes out with easy-to-find bugs. A more detailed analysis reveals two things. The first is that the SLI configuration doubles the amount of VRAM available AND used, and the second is that the 8x MSAA seems to double the required VRAM based on the VRAM available.

The pic above shows the required VRAM used on a single GPU configuration using 2x MSAA. It’s acceptable, but still…

This one displays the same thing, but on a SLI configuration. Notice how the VRAM available and used gets doubled? The same 2x MSAA configuration is applied.

However, upping the MSAA to 8x doubles the VRAM required, leading to the 14GB VRAM usage as we previously reported. Even so, why Rockstar… why?

Are there more bugs in the latest Grand Theft Auto 5 title for the PC platform? Have you found any of them? Let us know!

Z97 and Z97M Anniversary Motherboards Announced by ASRock

ASRock has announced its Anniversary Edition of motherboards, the Z97 and Z97M, following the Pentium 20th Anniversary Edition G3258. One of the key features of the aforementioned motherboards is the “Pentium Anniversary Edition” technology, making overclocking easier for users.

The manufacturer is said to have specifically designed the motherboard with overclocking and Intel’s Pentium 20th Anniversary Edition G3258 CPU in mind, being able to access the Pentium Anniversary Boost by hitting “P” when turning the PC on. From there, the feature is said to help the user automatically overclock the CPU from 3.2 GHz to a maximum of 4.2 GHz.

In addition to the overall overclocking feature, ASRock’s Z97 and Z97M Anniversary Edition motherboards are said to provide even more kick out of the Pentium Anniversary Edition G3258 CPU. A clock speed of 4.5 GHz can be easily achieved, having a performance boost of 40%. However, users can also go for the 4.8 GHz limit, where an additional 50% performance boost should be noticeable.

[youtube]https://www.youtube.com/watch?v=5F1MIVXTBgw[/youtube]

Other features present on the motherboards consist of “Super Alloy” technology for the Z97 in order to provide more stability and reliability, along with Intel’s Gigabit LAN and ELNA Audio Caps. The Z97M is said to come with ELNA Audio Caps as well, along with various video outputs, such as D-Sub, DVI-D and HDMI, supporting a Triple Monitor configuration.

Thank you TechPowerUp for providing us with this information
Images and video courtesy of TechPowerUp

Google Invents Self-Fixing Problems? Is This The Future?

After some of you experienced or at least saw what happened yesterday with some of Google’s Services, the company officials expressed their apologies and released a statement explaining what went wrong, which inevitably caused the outage yesterday.

Ben Treynor, Google VP Engineer, posted a statement which points to a ‘bug’ in the system, the ‘culprit’ that caused the whole outage. He says that at 10:55 a.m. PST, an internal system that generates configurations for other key systems reported to have generated incorrect settings, which in turn sent out to other systems. Around 11:02 a.m. PST, the massive outage started and users reported they can’t access the Google services.

The current incompatible settings were basically telling the systems to ignore server requests from users, which in turn generated the error messages. About 12 minutes later, at 11:14 a.m. PST, the same system that generated the error instructions rectified itself and starting sending correct configurations. By 11:30 a.m. PST, all systems were back online and engineers started taking precautionary steps, from removing the source of the failure, to implementing new security measures for it not to occur a second time.

Some questions still remain though. If the bug hadn’t ‘magically’ repaired itself, at what timeline would we be looking at for yesterday’s outage? And how come Google’s Site Reliability Team did not find the error faster? I mean, we are all human of course, but isn’t Google supposed to be one of the top companies with the best team of engineers? It appears not.

Thank you Google Blog for providing us with this information