#Dragon age origins emulator mac code
#Dragon age origins emulator mac Pc
#Dragon age origins emulator mac windows

Seeing all these opposites between DirectX and OpenGL, I wonder if Microsoft deliberately made it this way to be difficult. I think the specific ones had to do with bringing over Direct3D's BGRA vertex color ordering whereas OpenGL was traditionally RGBA, allowing the fragment co-ordinate origin to be in the upper-left as in Direct3D compared to OpenGL's traditional lower-left, and something about the provoking vertex being the first vertex in a primitive as in Direct3D compared to the last vertex in OpenGL. OpenGL 3.2 also added several more extensions with the explicit focus of being more compatible with Direct3D, which I believe some OpenGL purists were objecting to. I believe Brad Oliver mentioned new half float formats for vertex array and pixel formats and new texture format extensions which were added in Snow Leopard and are part of OpenGL 3.0 and are used in Direct3D and common in console games, which seeing how things are going, being console friendly is important. Well to help balance things out, OpenGL has been moving toward being more Direct3D friendly.

#Dragon age origins emulator mac code

Note, however, that the console versions are slightly different (no toolset, and you have a more restrictive camera with regards to zoom levels, and the combat mechanics are slightly different to cope with the limited resources available on consoles).ДЄs much as I want to see it, developers these days rely more on making the code more DirectX friendly then OpenGL friendly, crysis, and LFD anyone?

#Dragon age origins emulator mac windows

Of course, BioWare also switched to DirectX for Dragon Age, but there's no guarantee that they're all that similar to what was done for NWN2.ДЄs suggested, pick it up for Windows or your console of choice. NWN2 started with the Aurora engine, sure, but the graphics layer was entirely new (NWN was an OpenGL game Obsidian threw out most of the graphics code and wrote their own, switching to DirectX in the process, from what I understand). EA would almost certainly have to self-publish a port due to the post-release downloadable content and social community support (the game is pre-allotted a two-year lifeline for active development and enhancement) I don't think Aspyr would even try to touch it (look how well NWN2 post-release support and user content worked out for them). So if they were planning a Cider 'port,' it probably definitely would have already been announced long before shipping.

#Dragon age origins emulator mac Pc

NWN2 used a Bioware engine (albeit an old one souped up to try and handle it) and was very very buggy and sluggish on PC which translated across to the Mac port.Just to clarify, BioWare now *is* EA (bought-and-paid-for division). The real question is then what performance drop we're going to see. Of course, since that's the case, Aspyr, who previously worked with EA quite a bit, could feasibly approach EA and to a traditional port with, hopefully, better performance. The main problem here is that Bioware is now published by EA, who have this thing for Cider, which isn't exactly ideal when you're working with newer engines. It's almost pointless to speculate since we might get a game soon, or it might take years to get picked up. So who knows? Its a possibility, but until something's announced we won't know for sure. NWN2 used a Bioware engine (albeit an old one souped up to try and handle it) and was very very buggy and sluggish on PC which translated across to the Mac port. NWN2 wasn't Bioware, it was Obsidian, Bioware's little offshoot developer (by which I mean, a bunch of guys left and formed Obsidian who then did a few sequels to Bioware games).Д«ut the last Bioware game we got was actually Jade Empire, which we got through Cider.