4 ms·
The PS3 had OpenGL. Nobody used it because it was vastly slower than libgcm. The PS4 has OpenGL. Almost nobody outside of indie-land has even looked at it becau
by eropple 12y ago
The PS3 had OpenGL. Nobody used it because it was vastly slower than libgcm. The PS4 has OpenGL. Almost nobody outside of indie-land has even looked at it because there's no reason to when libgnm is right there and you still pay a significant performance vig, in an industry where you do not get the luxury of ignoring performance, for an only marginally better API. The Xbox One, on the other hand, does provide what appears (I don't have access to any of these consoles, I just know a lot of game devs who like to drink) to be a complete DX11 implementation...and it's plagued with perf issues you don't see on a PC because the assumptions of the API don't map to the actual hardware--which, I understand, the lower-level constructs of DX12 will address.
The future of non-indie game development seems very much to be going towards hardware: Mantle, Metal, libgnm, DX12. If you're on a console, you can afford to actually develop for the console. If you're not, you don't matter. (Indies don't care, but few people care about them, so that tail wouldn't wag the dog. Nobody cares about Steam Machines, so I don't know why you'd bring them up.)
- shmerl 12y agoThe fact that OpenGL on consoles has poor performance is the fault of console manufacturers, not of OpenGL itself. Also, their release schedule results in outdated hardware in comparison with regular computers. I.e. developers are forced into mentality of writing on a very low level to squeeze performance from a dated spec. More frequent updates could solve this situation and that's what Steam Machines aim to change as well. There is no valid reason why OpenGL can't be made to perform well on consoles except the lock-in mentality which plagues consoles market.
- eropple 12y ago> There is no valid reason why OpenGL can't be made to perform well on consoles except the lock-in mentality which plagues consoles market. Oh sure. Lock-in mentality is the reason. Never mind that Apple is doing Metal and AMD is doing Mantle because of defined, demonstrable issues with higher-level abstractions, both GLES and DX11 respectively. Certainly never mind that DX12 is shaping up to provide the same sort of low-level primitives as Mantle/libgnm/Metal. No, they're just hissss lock-in hissss. Can't possibly be because, like, it's a better option, can't have that. Like, do you know how many calls you have to make to accomplish stuff in some basic OpenGL extensions? And how much less you can do without the significant amounts of overhead it causes--overhead you can't remove because it's in the spec and now it never goes away? Did you ever stop to think, for just one second amidst your "there is no reason" absolutism about something it certainly sounds like you don't know much about past laymanship...maybe they're not laymen and maybe they have a good reason for stripping away abstraction? Not even providing their own incompatible abstraction, but just getting rid of it? I mean, Snidely Whiplash wants to make his platform dev-friendly too, but instead of doing that he gives you this bleeding bare-metal API? Come on. Have you stopped to give these guys an ounce of credit? . And complaining about a "release schedule resulting in outdated hardware" fails to comprehend that "outdated hardware" is every nine months. That is a feature, so that normal people don't have to go buy nVidia GTX9581 Platinum Edition cards every two years. Your position frankly beggars belief. The PC gaming treadmill sucks. The mobile treadmill sucks. And you want to make people jump to it on consoles? Do you know a normal person?
- shmerl 12y ago> Never mind that Apple is doing Metal and AMD is doing Mantle because of defined, demonstrable issues with higher-level abstractions Bad comparison. While AMD proposed to Khronos their Mantle as a base for OpenGL-next and in general aim to make it open, Apple didn't do any such thing. Apple does Metal precisely out of lock-in mentality. Any API that will lock developers to one platform is a dead end. > "release schedule resulting in outdated hardware" fails to comprehend that that is a feature, so normal Yeah, a "feature" that degrades games' quality because developers are constantly held back by requirements of console ports. It's not a "feature" to stagnate hardware for such long periods of time. Consoles are closed platforms with manufacturers in full control. It has some pluses like more stable expectations, but minuses outweigh them. Open platforms are the future and the locked-in ones will be considering some changes when stronger competition will give them a kick.
- eropple 12y ago> Bad comparison. While AMD proposed to Khronos their Mantle as a base for OpenGL-next and in general aim to make it open, Apple didn't do any such thing. Apple does Metal precisely out of lock-in mentality. If you don't think Apple has invested a shit-ton of money into GLES to make it habitable I just don't think you're living in a world inhabited by the rest of us. Apple has spent tons of man-hours and money dealing with the OpenGL process. But no, Snidely fuckin' Whiplash is over here curling his moustache and hissing "yessss, yesss, everything we do by stripping out layers of abstraction and making things faster for obvious and comprehensible reasons is eeeeeeevil." They still support GLES. They still participate in the process. But they offer a frankly better solution too, one on top of which you can build an agnostic API that can better leverage each platform's better options than OpenGL. > It's not a "feature" to stagnate hardware for such long periods of time. Cool. Get normal people to shell out for a new console--you know, that thing that lives in a home theater center that you buy and stop thinking about--every two years. Don't worry, everybody else will definitely wait for the market to prove you right, they won't be over here cooking on what actually works.
- shmerl 12y ago
- pjmlp 12y agoSony asked major studios if they wanted OpenGL ES 2.0 and they didn't care. http://sandstormgames.ca/blog/tag/libgcm/ http://sandstormgames.ca/blog/tag/libgcm/ <quote> At one point, Sony was asking developers whether they would be interested in having PSGL conform to the OpenGL ES 2.0 specs (link here). This has unfortunately never happened however, as developers seem to have mostly preferred to go with libGCM as their main graphics API of choice on PS3. This has meant that the development environment has started becoming more libGCM-centric over the years with PSGL eventually becoming a second-class citizen – in fact, new features like 3D stereo mode is not even possible unless you are using libGCM directly. </quote> > There is no valid reason why OpenGL can't be made to perform well on consoles except the lock-in mentality which plagues consoles market. Game studios culture doesn't care about FOSS. What matters is making the best game on the platforms the publishers are paying in advance for.
- shmerl 12y agoThe "major studios" are mentioned here probably because most developers simply don't target PS. I.e. indie developers aren't interested in it that much. So I wouldn't take that as an indicator that developers at large don't care about cross platform APIs. If Sony would offer an open platform without barriers to enter, those answers would be very different.
- eropple 12y agoMost developers don't care about the platforms with the most reach and most invested gamers. Sure. Must be why every indie developer I know would sell their eyeteeth to get even a mid level promo package on PSN. You're taking your ideology and trying to retrofit the world to accomodate it. Doesn't work that way. In the world of what is, rather than the world of what one might like it to be, nobody really cares. Tough.
- shmerl 12y ago> You're taking your ideology You are talking about Apple's spin of Metal (which is lock-in ideology). In practice it's easier for developers to use one toolkit instead of using 20 locked-in incompatible APIs. If developers use ready engines it becomes easier for them, but that burden is shifted to engine developers then. Someone will have to deal with that major mess. There is clear pragmatic benefit in cross platform APIs for gaming, and claiming that it's just ideology is nonsense.
- pandaman 12y agoIt's actually a fault of OpenGL. The main issue is that the modern GPUs are executing draw calls concurrently. If you've done some programming you might know that you cannot really have global mutable state together with parallel execution, yet the global mutable state is the core of OpenGL. So you need to copy the state every time you launch a draw call, which is an expensive thing to do even with the hardware aids available. Definitely more expensive than just launching parallel draws each with its own state. Not just the OpenGL is suffering from this, DirectX has very similar problem up to DX11, the DX12 is out to address this. There are extensions that allow you to do the same in OpenGL but then what would be a point to bring the entire OpenGL if you are only going to use the extension that is nothing like the OpenGL and does the same the native API already does?
- shmerl 12y agoOpenGL 4.5 addresses some of concurrency bottlenecks. My point was not to say that OpenGL is perfect as is. But to say that any potential successor can't claim that OpenGL is bad because it aims to be cross platform, therefore better alternatives all need to be platform specific. That's a false logic. Cross platform API can be made better.
- pandaman 12y ago> OpenGL 4.5 addresses some of concurrency bottlenecks. How so? It adds DSA which is just a different way to access global state. The global state is still the cornerstone of the 4.5. The only way it addresses performance issues is through "bindless" extension, which pretty much tosses away the entire OpenGL pipeline and leaves just a draw_indirect_multi call call with everything pushed into shaders. It's too extreme for many developers even it's been available on non-NVidia hardware. > My point was not to say that OpenGL is perfect as is. Never mind me then. I only replied to your claim it's not the OpenGL fault it's slow on consoles.
- shmerl 12y ago> How so? I mean new flush control support.
- pjmlp 12y ago> The PS3 had OpenGL No. It had OpenGL ES 1.0 with Cg for shaders. > The PS4 has OpenGL Since when? Only if a third party company is offering it. http://develop.scee.net/files/presentations/gceurope2013/ParisGC2013Final.pdf http://develop.scee.net/files/presentations/gceurope2013/Par...
- eropple 12y agoPSGL and GLES are close enough for the discussion at hand; if Cg vs. GLSL is really going to grind your gears you've already lost. You're right about the latter, though--I misunderstood a prior discussion with a friend of mine (he was speaking in hypotheticals, I thought he was speaking in specifics). Mea culpa. It doesn't change the abject silliness of the sibling thread though.
- pjmlp 12y agoYeah, but by not being the same thing, in the end the result is the same. Multiple code paths, or backends to handle the differences. > It doesn't change the abject silliness of the sibling thread though. Agreed. I do boring IT stuff. But once upon a time I had some opportunities in gaming (long long time ago), which I blew up for being more focused on the OSS aspects of the tooling than what really mattered, having a game. I really learned the hard way, how the different the game development culture is from the FOSS one. Which I should have known given the similarities with the demoscene. Even though I am not in the industry, I do follow it regularly.
- eropple 12y agoIt depends on where you're coming from though, yeah? Like, PC->PS3, (good) OpenGL/Cg to GLES/Cg wasn't a big step (I use Cg with OpenGL today). Nobody really used it anyway, though, because libgcm was just so vastly superior.