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

Disable RAY_QUERY and RAY_TRACING_ACCELERATION_STRUCTURE by default #12862

Merged
merged 1 commit into from
Apr 4, 2024

Conversation

cart
Copy link
Member

@cart cart commented Apr 3, 2024

Objective

See gfx-rs/wgpu#5488 for context and rationale.

Solution

  • Disables wgpu::Features::RAY_QUERY and wgpu::Features::RAY_TRACING_ACCELERATION_STRUCTURE by default. They must be explicitly opted into now.

Changelog

  • Disables wgpu::Features::RAY_QUERY and wgpu::Features::RAY_TRACING_ACCELERATION_STRUCTURE by default. They must be explicitly opted into now.

Migration Guide

  • If you need wgpu::Features::RAY_QUERY or wgpu::Features::RAY_TRACING_ACCELERATION_STRUCTURE, enable them explicitly using WgpuSettings::features

@cart cart added C-Bug An unexpected or incorrect behavior A-Rendering Drawing game state to the screen labels Apr 3, 2024
@cart cart added this to the 0.13.2 milestone Apr 3, 2024
@cart
Copy link
Member Author

cart commented Apr 3, 2024

I'm recommending we include this in 0.13.2 (despite it being a breaking change) because this breaks 0.13.0.

@james7132 james7132 added the P-Crash A sudden unexpected crash label Apr 3, 2024
// them until they are safe to enable.
features -= wgpu::Features::RAY_QUERY;
features -= wgpu::Features::RAY_TRACING_ACCELERATION_STRUCTURE;

Copy link
Contributor

Choose a reason for hiding this comment

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

This is ok, but maybe the approach for overrides like this should be to add them to the WgpuSettings disabled_features default so that people can still override it if they know better?

Copy link
Member Author

@cart cart Apr 4, 2024

Choose a reason for hiding this comment

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

This would mean that setting disabled_features could inadvertently overwrite the default disabled features. I think its best to default that to none.

Users can still set these if they set WgpuSettings::features, which feels like the better pattern.

@cart cart added this pull request to the merge queue Apr 4, 2024
Merged via the queue into bevyengine:main with commit b27896f Apr 4, 2024
31 checks passed
mockersf pushed a commit that referenced this pull request Apr 4, 2024
…12862)

# Objective

See gfx-rs/wgpu#5488 for context and
rationale.

## Solution

- Disables `wgpu::Features::RAY_QUERY` and
`wgpu::Features::RAY_TRACING_ACCELERATION_STRUCTURE` by default. They
must be explicitly opted into now.

---

## Changelog

- Disables `wgpu::Features::RAY_QUERY` and
`wgpu::Features::RAY_TRACING_ACCELERATION_STRUCTURE` by default. They
must be explicitly opted into now.

## Migration Guide

- If you need `wgpu::Features::RAY_QUERY` or
`wgpu::Features::RAY_TRACING_ACCELERATION_STRUCTURE`, enable them
explicitly using `WgpuSettings::features`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior P-Crash A sudden unexpected crash
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants