JustBeingReal said:
You know what shows this will work that easy? PC, just look at how highly complicated, different hardware specs can all run the same games, because developers and hardware creators support the tech in all of those different PC builds, they do not have to make ports of games for each hardware set-up, they just make sure hardware drivers are updated and take new games and program code into consideration. This hypethetical NX family of devices would actually be night and day simpler than this, because it wouldn't have anywhere near as many hardware set-ups. Nintendo's OS designers can easily just take all hardware specs into consideration and as long as each device is within a certain ballpark of the other(s) then this would work easily. Hell it's not hardware to disable AA, Tesselation, etc when you code a game engine to allow for that, which is the case for all 3rd party developers and their engines dating back to beginning of modern PC gaming. You think a 4K capable PC and a thousand other spec builds are getting unique ports? No, developers make a high end build of their game, that's the only one. End users choose their settings to make the game run how they like on their particular, unique PC build and the developer has built their game engine to allow for the settings to be tweaked. The only major difference in the hypothetical NX set-up is that it's way less complicated than PC, because NX only has maybe a few different specs, but they all use the same OS and all of the tech (just like in PC) is taken into consideration by Nintendo and their OS programmers. Sony didn't make anything like this, PSP and Vita, PS3, PS4, etc are all made in their own vacumes as far as their final OS goes, the OS of each weren't designed to run on a bunch of different devices and unify the library of games and the technical architecture wasn't really made to work seamlessly across all games for this kind of thing, proven by the fact that they all have different control inputs and the fact that developers have to port their games across them if they want to allow crossplay. Which isn't necessary in a windows or Linux, etc environment There's nothing magical about logical math equations and analysis of real world hardware that actually exists or real examples of this very thing that I'm suggesting. As for what I do, or what my experience is, I could say whatever I like, but the proof is in the pudding of the examples I give here. You haven't given a single example of why this couldn't work. Math and real examples disagree with you. |
This isn't how console video game development works. PC game development is actually a lot different than console development, and those comproimses that PC developers make to have scaling hardware settings by interfacing with APIs rather than the hardware itself means major sacrifices to performance. In doing so, You lose the ability to optimize for specific hardware specifications, something consoles can't afford to do given the fact that the hardware is weak to begin with. You see, console developers don't program a game to interact with the operating system, or even with APIs to send instructions to the hardware. The engines are built to interact with the hardware directly. Certain portions of the hardware are "roped off" that game engines do not have access to which the OS runs on, and the engines do interact with the OS for things like controller input, camera input, achievements/trophies etc. But for the most part, engines are programmed right "on the metal". It allows you to optimize specifically for that hardware, allowing developers to streamline commands, minimize processing times, work around bottle necks, and free up additonal resources to make other parts of the game better. It's why console games can look so much better and run so much smoother than on PCs with near identical hardware. In other words, it's a fundamental and critical part of console video game development.
Because you don't appear to know this, the rest of your argument completely falls apart because it's based on a flawed assumption. It's not less complicated for the hypothetical NX and more than PC development becoming more complicated if intel releases a new processor. It doesn't matter if you have 5 specs of 500 specs, not being able to optimize for one spec, and interfacing with an API or OS instead means you lose that performance advantage. That's why console video game developers don't do it.
Again, if it were as easy as you said, Sony could have just developed an OS or an API for the Vita knowing what the OS or API for the PS4 would be (or vice versa) and get near instant ports of PS4 games on the PSV. The hardware specs wouldn't really matter, would it? I mean it's "just" two diifferent hardware specifications" to design the OS the handle - what's the big deal, right? This is what Sony was aiming to achieve with the PSP and PSV, home console games seemlessly taken on the road and back to the console going from one device to the next. That was the vision. The hardware and OS was designed with that in mind. Why do you think Sony didn't take the approach you're suggesting? Seriously. If it's that obvious and that easy, then the engineers at Sony with decades of experience that should be more than capable of pulling it off. Why didn't they? Why did they take a different approach? And don't tell me they were "developed in a bubble" considering many of the people behind the Vita and PSP are the same people behind the PS3 and PS4. These devices were developed with the other in mind.







