I've been a Tekken guy since PS1 - funny how quickly things can change :) My wallet is already getting nervous :O

View this comment - View article - View full comments

Can confirm. If you start developing with cross-vendor and -driver OpenGL, you will stumble upon this rather quickly.

View this comment - View article - View full comments

Quoting: DrMcCoy

Quoting: NyamiouYou don't need to answer that.

I can, however, sell you a very reasonably priced tin foil hat.

If your post only consisted of that line, it would have been twice as good ;-D

View this comment - View article - View full comments

This isn't about slamming anyone - neither the dev nor Nvidia.

View this comment - View article - View full comments

And how does this example show, that compilers don't do any optimizations elsewhere?

(Yes, it's a trap)

View this comment - View article - View full comments

But that wasn't the example "you have", was it? And why does it show, how limited optimization is? We're talking about things from like simple type conversions to replacing whole shaders. You just provided a for-loop which doesn't tell us anything.

In general, you're not doing much more then keep telling us, how stupid we all are. Other than insults, you didn't contribute much so far.

Quoting: alexSee this talk, you will se that in order to fix bad behavior you simply dont use Nvidia - you rewrite the code! (Which ofc, would be blatantly clear if you knew anything about the limitations a compiler faces)

In how far is this different from what I suggested in the first place?

View this comment - View article - View full comments

Quoting: tuubi

Quoting: alexThe mirv example was well documented and if this is true then yes thats a good and specific example. But when you explain in terms of " magic" and such it's just completely obvious you dont know anything about software development.

Damn. Busted. I wonder how our software design business lasted for ten years before anyone found out I have no idea what I'm doing. Please don't tell our clients. :'(

So you're working for Microsoft? ( ͡° ͜ʖ ͡°)

View this comment - View article - View full comments

What "real" examples (you have) are you referring to?

View this comment - View article - View full comments

I wonder. Is there something specific you want to tell us?

View this comment - View article - View full comments

Quoting: liamdaweA game being "ported" isn't some magical milestone, it means it compiles and runs on Linux, that IS when the proper testing begins, and they can only test one GPU at a time unless they can do both at the same time there is always going to be one that is first.

If they only have one machine available for development (and testing). Otherwise you just run the same build on different machines and see if it works or where errors occur.

Quoting: ImantsAm I understanding things correct. NVidia is making bad opengl code preform better on they're cards buy violating opengl specification? So if programmers would know better opengl and programmed as it should be done code would work as fast as it needs on any drivers? So in the end it is people knowledge witch is lacking and NVidia is just patching it up.

Yes.

Quoting: alex[...]and when given the choice this vendor's driver devs choose sanity (to make things work) vs. absolute GL spec purity.

But what's the point then in having standards (especially open ones)?

Besides, if you're writing GLSL Shaders and do mistakes (according to the Khronos specification), but Nvidia's compiler accepts your code (because it's sort of guessing what you meant), this may lead to unpredictable behaviour. Nvidia's driver try to adress suboptimal code - sometimes successfully, sometimes breaking the program/game.

It's a difference, if you try to fix some bad practice or code that isn't supposed to work.

View this comment - View article - View full comments