Curious to who is sticking with OpenGL now...

[Mars_999]

I am curious to see who here is planning on sticking with OpenGL or moving onto DX or some other means. Would like to see who is planning on leaving the community and who is staying around. Trying to get a feel for what support is left for OpenGL as a hobbyist game coder.

[Simon Arbon]

I will certainly be staying, i have always used OpenGL in preference to the continuously changing DX.
With the rapidly growing support for Linux in Australia i want all of my applications to be cross-platform.
Wine wont help as it just translates DX into OpenGL anyway.

I dont agree that this is the disaster that many people are claiming, vendors will still be able to write a separate high-performance driver for the Forward_Compatible context, and all of the missing DX10/DX11 features can easily be added as extensions.

I do agree that the longs-peak object model should have been the FIRST thing they did though, the planned incremental conversion can be nothing but a compatability disaster.
The claims that it was to allow for people with existing code to make a gradual conversion just doesn't make sense as they just introduced two separate mechanisms (2.1 upgrades and the profiles) that allows this to happen in parallel with a new API.

Even more worrying is the stuff that seems to have been included for the purpose of preventing anyone from writting a more efficient renderer for slightly older cards.
This was either plain DAFT or a ploy by the hardware vendors to get more people to buy new cards.

Anyway, i have my new 2.1 renderer half finished so at least i dont need to write a separate one for 3.0 as nothing has really changed.

The most important thing for me at the moment is what new extensions ATI and NVIDIA are going to add in the near future,
i could really do with a GPU tesselator at the moment.

[bootstrap]

I am. I have no choice, because I cannot allow my application to become dependent upon the evil empire. Either people forget how many times they have been shafted by macroshaft, or they haven't been developing software long enough yet to *repeatedly* find out and get angry enough to abandon them on principle AND out of self-preservation. I must admit, it took several time to sink into my lame brain.

In other words, I am one of those people who choose OpenGL because it runs efficiently on Linux, at least with nvidia drivers (the only ones I have tried the past several years).

A question. Is now the time to create a new 3D graphics/rendering API for realtime applications [and leave OpenGL for CAD, if recent threads are on-point]? Is this kind of project impossible (unless you are nvidia) because no access to the low-level hardware or drivers is provided by the GPU makers?

BTW, I have seen many people complain that "games" are being sacrificed for the "CAD companies". I believe that is a very dangerous way to characterize the situation, because the concept "games" tends to trivialize the importance of realtime graphics/rendering applications - which have virtually identical requirements to "games". I refer to presentation of simulations of physical [and fictional] processes (mechanical, chemical, atomic, optical, you-name-it), vision systems, robotic systems, and everything non-trivial that must be realtime or interactive. ALL of these applications will be thrown out with the bathwater if people can deem them "games" (unimportant).

[Korval]

I cannot allow my application to become dependent upon the evil empire.

You realize that characterizing Microsoft as "the evil empire" and calling them "macroshaft" only makes you sound like a GNUdiot, right?

vendors will still be able to write a separate high-performance driver for the Forward_Compatible context

Except that they will still have to write and maintain the "low performance" context. Do you really expect IHVs like ATi to write two GL implementations?

And it does nothing about the whole "bind-and-set" model, nor does "direct_state_access" (because the bind-and-set model will still exist and implementations will have to conform to it).

Is this kind of project impossible (unless you are nvidia) because no access to the low-level hardware or drivers is provided by the GPU makers?

Believe me, if we could have just done an end-run around IHVs, we'd have done so long ago. Probably after the FBO fiasco.

[NeARAZ]

We (at Unity) are obviously sticking with OpenGL on OS X. Well, we have no other choice here, right?

D3D9 and OpenGL on Windows (keeping OpenGL path in there just because it happens to still work, but D3D9 is the default). Switching to D3D9 by default on Windows was one of the best decisions we ever made (at a cost of about 3-4 man months of porting the renderer to it).

And other APIs on other platforms (iPhone, Wii).

[dor00]

Thats a problem for me.

I try to clear my mind and see whats the best way to continue.

Switching to DX10 cost a bit more. Is probable Vista+VS.net plus losing cross platform feature, which i dont like it.

On the other hand, i have to many things to worry about the new OpenGL3 and his future.

Decisions, decisions, bloody decisions...

[Jan]

I'll switch to D3D10 for personal stuff, but stay with OpenGL for other stuff. I'll definitely visit these forums as often as before, it is the best and most interesting community that i have found so far.

Jan.

[Ffelagund]

I'll continue using OpenGL. I really dont like DX (syntax), and it doesnt give me more features than OpenGL. I know that now, with GL3.0, we have more burden in the API than we expected (we expected exactly the opposite) but that doesnt worry me at all. Long time ago I choose for many GL operations only one way of coding things and ignored the rest, so that burden doesn't disturb me at all. And one more important thing: I cant loose portability. I need code for linux (in my job)

P.D: I have the hope that after reading the GL community reactions, Khronos will make GL3.1 better, at least removing totally the deprecated stuff and promoting geom shaders to core... Thats the only things I really care about 3.0

[Seth Hoffert]

I've decided to learn D3D10 and use it for future personal applications. It's never a bad idea to know both. So far, I have had a pleasant experience with the API. I will continue using OpenGL for a couple of projects, and I will continue to check these great forums.

[Timothy Farrar]

I'm sticking to GL for personal commercial projects, while at work I use DX on PC (not my choice) and the console specific APIs.

With GL3 I see no reason to use DX unless ATI drivers don't show up. I also prefer GL3 as well, especially with MapBufferRange()...