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

Add warning for the incompatibility of stereo type #8031

Merged
merged 2 commits into from
Aug 13, 2024

Conversation

z3moon
Copy link
Contributor

@z3moon z3moon commented Aug 9, 2024

Print a warning in case the stereoscopic type in a compiled package is different than what's in the engine's setting. The application may proceed, but it could end up visual glitches when enabling stereoscopic rendering.

This requires the stereoscopic type to be written into the package, which needs a material version bump.

Print a warning in case the sterescopic type in a compiled package is
different than what's in the engine's setting. The application may
proceed, but it could end up visual glitches when enabling stereoscopic
rendering.

This requires the stereoscopic type to be written into the package,
which needs a material version bump.
@z3moon z3moon added the internal Issue/PR does not affect clients label Aug 9, 2024
if (materialDomain == MaterialDomain::SURFACE) {
StereoscopicType const engineStereoscopicType = engine.getConfig().stereoscopicType;
StereoscopicType materialStereoscopicType = StereoscopicType::NONE;
materialParser->getStereoscopicType(&materialStereoscopicType);
Copy link
Contributor

Choose a reason for hiding this comment

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

Does the bool returned here indicate whether getting the chunk was successful or not? Should we only do the following conditional only if the chunk was successfully parsed?

I think this'll happen if the material is of an older version than filament.

Copy link
Contributor Author

@z3moon z3moon Aug 13, 2024

Choose a reason for hiding this comment

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

Yeah I also realized it returns a boolean but found other usages don't check that either. Maybe it'd be nice to handle them together later.

@z3moon z3moon enabled auto-merge (squash) August 13, 2024 01:14
@z3moon z3moon merged commit 9de29a4 into main Aug 13, 2024
11 checks passed
@z3moon z3moon deleted the zm/material-stereo-type branch August 13, 2024 01:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Issue/PR does not affect clients
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants