Difference between revisions of "Hardware specifics: NVidia"

From OpenGL.org
Jump to: navigation, search
m
(Current issues: Removing info about the validator, as it has not been updated.)
Line 7: Line 7:
 
The classic problem case is using vec3(1,1,1) instead of vec3(1.0, 1.0, 1.0) as GLSL (as of version 1.1) does not do automatic type promotion.
 
The classic problem case is using vec3(1,1,1) instead of vec3(1.0, 1.0, 1.0) as GLSL (as of version 1.1) does not do automatic type promotion.
  
Newer drivers from Nvidia (80+ series) seem to emit warnings when features are used that are non-conformant. However, developers are recommended to run their shaders through the [http://developer.3dlabs.com/downloads/glslvalidate/ 3DLabs shader validator] or make the validator part of their development toolchain.
+
Newer drivers from Nvidia (80+ series) seem to emit warnings when features are used that are non-conformant.
 
+
  
 
== Legacy issues ==
 
== Legacy issues ==

Revision as of 14:45, 9 September 2009

Current issues

These are known issues for current Nvidia hardware/drivers.

GLSL shader conformance

Early Nvidia GLSL implementations are known to be quite accepting of features of other shading languages like Cg. This has lead to problems when developers using Nvidia cards unknowingly use these features which cause shader compile errors on other hardware.

The classic problem case is using vec3(1,1,1) instead of vec3(1.0, 1.0, 1.0) as GLSL (as of version 1.1) does not do automatic type promotion.

Newer drivers from Nvidia (80+ series) seem to emit warnings when features are used that are non-conformant.

Legacy issues

These issues may affect older drivers/hardware

Multicore CPU and Driver Issue

This is one thread about the issue and you can find more with a search on the forums
http://www.opengl.org/discussion_boards/ubb/ultimatebb.php?ubb=get_topic;f=3;t=015274