News for hackers. Stuff that matters.
Re:Why you should use OpenGL and not DirectX by pjmlp on Thursday December 05, 2013 @02:17AM (#6853090)
Yes, many that bash DirectX never experienced how the whole ecosystem works and the existing offers in terms of tooling for performance analysis.
Re:Why you should use OpenGL and not DirectX by exDM69 on Thursday December 05, 2013 @03:14AM (#6853205)
> Yes, many that bash DirectX never experienced how the whole ecosystem works and the existing offers in terms of tooling for performance analysis.

Usually people don't "bash" DirectX or D3D. Most OpenGL programmers acknowledge that it is a better API with more corporate backing (ie. budget). But at the same time it is still Windows only, and for a lot of people it simply isn't an option.

For OpenGL, the tooling is provided by individual vendors, and yes, it's not as good as d3d. But the situation has improved in the past few years and keeps on improving.

Re:Why you should use OpenGL and not DirectX by pjmlp on Thursday December 05, 2013 @07:20AM (#6854014)
Which vendors? Besides gDEBugger there isn't any tool that I am aware of, that can match the performance monitoring of DirectX and console specific APIs.

Even NVidia only started to invest in OpenGL performance measuring tools, after their Android support started.

Re:Why you should use OpenGL and not DirectX by exDM69 on Thursday December 05, 2013 @08:52AM (#6854339)
> Which vendors? Besides gDEBugger there isn't any tool that I am aware of, that can match the performance monitoring of DirectX and console specific APIs.

Yes, there probably aren't tools that are as good as the D3D tools. But Nvidia, AMD and Intel have all released OpenGL profiling and debugging tools. Yes, every vendor has their own tools. Not ideal.