Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

move the adjacency flag to render operation where it belongs ogre-next-3-0 #455

Conversation

bishopnator
Copy link

move the adjacency flag to render operation where it belongs instead of the geometry shader - for e.g. rendering adjacency buffers without an geometry shader attached.

Lubomir Kovac added 3 commits July 26, 2024 12:44
…of the geometry shader - for e.g. rendering adjacency buffers without an geometry shader attached.
…ationType. The D3D11RenderSystem::_hlmsPipelineStateObjectCreated didn't properly initialized the D3D11HlmsPso::topology and in GL3PlusRenderSystem::_setPipelineStateObject the mUseAdjacency member was not correctly intialized.
…imply overwritten, but it should be set to true only if geometry shader explicitly set it, otherwise the value must be preserved from the initialization where it could be already set to true.
/** Sets whether this geometry program requires adjacency information
from the input primitives.
*/
/// @deprecated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regarding deprecation we introduced the OGRE_DEPRECATED_VER( n ) macro where n is the major version in which it was deprecated.

Thus the code should look like this:

OGRE_DEPRECATED_VER( 4 ) virtual bool isAdjacencyInfoRequired()

(master branch is currently 4)

@darksylinc
Copy link
Member

I've pushed two changes to your PR (one to fix Clang Format, another to port your enum changes to Vulkan).

Once CI is done checking I'll merge your PR.

@darksylinc darksylinc merged commit dca8d56 into OGRECave:master Aug 4, 2024
2 checks passed
@darksylinc
Copy link
Member

Thank you for the PR!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants