Mobile Graphics > 360/PS3 in 2014


Recommended Posts

NVIDIA: Mobile Graphics Will Beat Consoles in 2014

Big words from one of the leading mobile chip providers, but NVIDIA estimates that the graphical power of smartphones and tablets will meet and surpass consoles in the next two years.

The Tegra manufacturer provided AnandTech with a slide comparing the graphical trends and performance of the different gaming platforms since the turn of the century, ultimately pointing out that a mobile system on a chip (SoC) would be at the same level of home consoles in 2013, and surpassing them the year after.

nvidia-slide.jpg

Source

Link to comment
https://www.neowin.net/forum/topic/1071717-mobile-graphics-360ps3-in-2014/
Share on other sites

I don't care if it has better graphics or not. It's as the previous neowin editorial. You get a visually appealing game, and since it has very clumsy controls, it isn't enjoyable at all.

Bingo. Inputs on touch screens aren't conducive to good gameplay. It's fine for simple games, anything else is, as you said, clumsy.

If you need an example just look at the Max Payne port for iOS. Virtual, on screen controls are terrible.

This graph makes the assumption that new consoles won't be released with improved graphics processing prior to 2014. Point made though, mobile devices are becoming qutie powerful as far as graphics go.

Actually, they have an averaged charting of where PC's and Consoles would be with the dotted lines. And if you look, the consoles are still ahead with that curve assuming another console with a similar technology leap is released.

Only so much you can do with better graphics if the input system can't improve.

Maybe I'm one in a thousand, but I'm more interested in PS Vita like platforms reaching console graphics, yet maintaining decent battery life. As the Vita seems to produce some decent graphics, what I'd like to see next is battery tech getting better, not so much mobile phones catching up to dedicated handhelds/'consoles' in the graphics department.

Smartphone batteries are bad enough at times as it is, I don't want to be playing cutting edge graphical experiences on my phone on the train in the morning for the battery to die by lunch.

Simple mobile games do it for me (especially puzzle), for anything else, I'd as I mentioned at the start of this post always prefer dedicated.

Nothing magical here at all. The console will improve in its next iteration and PCs have been improving constantly so the mobile platform will lag behind the current technology level of its day. It will improve iteratively though and have increasingly better performance over time.

The growth in console graphics performance isn't all that amazing really. The only thing this graph really proves is that there was no real demand for mobile gaming quality graphics until recently. It will be interesting to see what the sustained growth in graphics power for mobile platforms are over a longer period, such as the scale used to compare it here to consoles and PCs.

you guys are missing the point... they are going to have hardware faster then a ps3 in a tiny tiny little box. that's pretty crazy....

The issue I have is: why? I don't get what a mobile platform could possibly use that power for besides improving the visuals of the games which really isn't their primary function anyways. I know people pretty much pay for the latest and greatest anyways but they could simply optimize the current platform rather than upgrade the hardware (such as improving battery life). I'd rather have a phone that needs a charge once a week than one that can run Mass Effect 3 but dies at the end of the day.

The issue I have is: why? I don't get what a mobile platform could possibly use that power for besides improving the visuals of the games which really isn't their primary function anyways. I know people pretty much pay for the latest and greatest anyways but they could simply optimize the current platform rather than upgrade the hardware (such as improving battery life). I'd rather have a phone that needs a charge once a week than one that can run Mass Effect 3 but dies at the end of the day.

oh i agree with you and everyone else about the battery issue. but to me, mobile cpus/gpus/apus/*whatever*us have come a long way pretty quickly.

The issue I have is: why? I don't get what a mobile platform could possibly use that power for besides improving the visuals of the games which really isn't their primary function anyways. I know people pretty much pay for the latest and greatest anyways but they could simply optimize the current platform rather than upgrade the hardware (such as improving battery life). I'd rather have a phone that needs a charge once a week than one that can run Mass Effect 3 but dies at the end of the day.

Mobile gaming isn't the primary function of tablets, but PC gaming isn't the primary function of PCs either. Battery life has been steadily improving along with graphical power, so it's not like they're ignoring that issue.

oh i agree with you and everyone else about the battery issue. but to me, mobile cpus/gpus/apus/*whatever*us have come a long way pretty quickly.

I agree. I just hate that they've jumped into the gaming hardware bandwagon rather than pushing a more obvious form of optimization. My old phones would last days before needing a charge. New phones last around 10-16 hours. That's a huge step backward in terms of their actual purpose. There is so much technology available these days, phones with similar power to what they had 4 years ago could be streamlined to generate less heat and use less power.

Mobile gaming isn't the primary function of tablets, but PC gaming isn't the primary function of PCs either. Battery life has been steadily improving along with graphical power, so it's not like they're ignoring that issue.

PC's can be built with that as a primary function. Phones and other mobile platforms cannot (at least not yet). A computer does what you make it to do. A phone/tablet is what it is and the fact that the manufacturers are blurring their purpose means that they are going to become riddled with features and stuff they don't need, driving up their price and preventing the consumer from seeing productive improvements and price drops as quickly as we should.

I'm not saying that they haven't improved anything, they certainly have. But today's smart phones could be a lot simpler and have a much, much longer battery life than they currently do if the focus was to minimize power consumption in the hardware/software rather than to beef up the power.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • 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
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!