RTSS generated shaders with Direct3D11 do not tolerate missing NORMAL/COLOR in vertex declarations #2070
Labels
wontfix
the fix would make the software much more complex and much less maintainable
Comments
|
See swebb2066@dbcddd3 for a possible approach |
|
actually, my plan was to do the reverse: adding that exception to GL3Plus: #1458 This exception is a good hint that you are actually doing something wrong, like lighting a mesh that has no normals. |
|
Is there a way for the shader generated to consider the vertex declaration? It seems that it needs a to exclude in parameters that do not exist in the buffer.
My usecase is robotics (not gazebo), where many objects are dynamically generated. For example the target tracks on a surface (for visualization ) do not need normal/color to be sent to the gpu.
On Jun 7, 2021 9:01 PM, Pavel Rojtberg ***@***.***> wrote:
actually, my plan was to do the reverse: adding that exception to GL3Plus: #1458<#1458>
This exception is a good hint that you are actually doing something wrong, like lighting a mesh that has no normals.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#2070 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADJDRCYAAR5TUUUSU5UPGXTTRSRITANCNFSM46G4NZNA>.
|
|
you do this when assigning the material to a entity/ renderable.
you must be consistent with what you want. You cannot enable VertexColourTracking and not provide any vertex colours. |
paroj
added
the
wontfix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See also https://forums.ogre3d.org/viewtopic.php?p=547896
System Information
Detailled description
Direct3D11 throws an exception while OpenGL3Plus does not. For example:
It would make render systems more interchangable if Direct3D11 would instead use some arbitrary normal/color value instead of throwing an exception. I successfully tested a change in which a missing semantic was handled as:
Ogre.log
The text was updated successfully, but these errors were encountered: