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

Merge with trunk #3

Merged
merged 370 commits into from
Jul 26, 2024
Merged

Merge with trunk #3

merged 370 commits into from
Jul 26, 2024

Conversation

Vecvec
Copy link

@Vecvec Vecvec commented Jun 16, 2024

Connections

Description
merges with trunk again, there were some ray-tracing bugs in wgpu-hal that were fixed

Testing
CI is fine, and the only error when I run the examples on my machine is about the blas format (see gfx-rs#3631 (comment))

Checklist

  • Run cargo fmt.
  • Run cargo clippy. If applicable, add:
    • --target wasm32-unknown-unknown ray-tracing is not on the web
    • --target wasm32-unknown-emscripten
  • Run cargo xtask test to run tests. - done by CI
  • Add change to CHANGELOG.md. See simple instructions inside file. part of ray-tracing

teoxoy and others added 30 commits June 19, 2024 14:05
Otherwise, the emojis aren't parsed on Crates.io, leaving the table without much utility unless a user navigates to GitHub.

Fixes like these are very simple, but super helpful for some users! :)
- Improve logging in `StatelessTracker::remove_abandoned` to show the
  outcome of the call.

- Add similar logging to `BufferTracker` and `TextureTracker`.

- Let `device_create_buffer`'s log only the new buffer's label, id,
  and whether it's mapped at creation. It used to show the whole
  descriptor, which is too much detail.

- Have `queue_submit` log the submission id, and have `device_poll`
  log what it was waiting for, and what actually got done.

- Have `Device::drop` log the destruction of the raw device when it
  actually happens, so it's properly ordered with respect to logging
  from other parts of the device, like `Device::command_allocator`.
* Ensure webgl example build only contains webgl and webgpu example build only contains webgpu
* fix ip printed on run-wasm
* Update examples on running examples on the web
dependabot bot and others added 28 commits July 8, 2024 09:42
…4.6.3 (gfx-rs#5921)

Bumps [JamesIves/github-pages-deploy-action](https://github.com/jamesives/github-pages-deploy-action) from 4.6.1 to 4.6.3.
- [Release notes](https://github.com/jamesives/github-pages-deploy-action/releases)
- [Commits](JamesIves/github-pages-deploy-action@v4.6.1...v4.6.3)

---
updated-dependencies:
- dependency-name: JamesIves/github-pages-deploy-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Expose gpu allocation configuration options

This commit adds hints to control memory allocations strategies to the configuration options. These hints allow for automatic profiles such as optimizing for performance (the default, makes sense for a game), optimizing for memory usage (typically more useful for a web browser or UI library) and specifying settings manually.

The details of gpu allocation are still in flux. The goal is to switch vulkan and metal to gpu_allocator which is currently used with d3d12. gpu_allocator will also likely receive more configuration options, in particular the ability to start with smaller memory block sizes and progressively grow the block size. So the manual settings already provision for this upcoming option. Another approach could be to wait and add the manual option after the dust settles.

The reason for providing presets and defining values in the backends is that I am convinced that optimal fonigurations should take hardware capabilities into consideration. It's a deep rabbithole, though, so that will be an exercise for later.

* changelog

* Update CHANGELOG.md

Co-authored-by: Andreas Reich <[email protected]>

* Add a comment about not entirely knowing what we are doing

---------

Co-authored-by: Andreas Reich <[email protected]>
…ources.

It's worth noting that `suspected_resources` never contained those resources.
The Vec only ever contained 0 or 1 command buffers.
We now acquire an encoder on every submit for pending writes but that's not a problem since those are coming from a pool anyway.
…ive in `LifetimeTracker.handle_mapping`

This change doesn't change behavior as `Global.buffer_drop` already unmaps the buffer.
…cing-updated

# Conflicts:
#	wgpu-core/src/device/life.rs
#	wgpu-core/src/device/queue.rs
#	wgpu-core/src/device/resource.rs
@atlv24 atlv24 merged commit d659a41 into atlv24:ray-tracing Jul 26, 2024
27 checks passed
@atlv24
Copy link
Owner

atlv24 commented Jul 26, 2024

Thanks for this

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.