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

Replace threaded renderer particle function fail conditions with warnings #54965

Closed

Conversation

briansemrau
Copy link
Contributor

@briansemrau briansemrau commented Nov 14, 2021

Fixes #54964

These checks make no sense to me, as these functions don't do anything to stall anything.

Nevermind, I forgot they get pushed through the command queue.

@briansemrau briansemrau requested a review from a team as a code owner November 14, 2021 04:45
@briansemrau briansemrau marked this pull request as draft November 14, 2021 06:01
@briansemrau briansemrau changed the title Remove incorrect(?) error checks for particles Replace threaded renderer particle function fail conditions with warnings Nov 14, 2021
@Chaosus Chaosus added this to the 4.0 milestone Nov 14, 2021
@akien-mga akien-mga modified the milestones: 4.0, 4.x Feb 12, 2023
@akien-mga
Copy link
Member

Is this still relevant as of 4.0 RC 1?

@brianwinterpixel
Copy link
Contributor

The linked issue is still reproducible, and this approach should still fix it.

This isn't a critical issue, however.

E 0:00:01:0602   particles_is_inactive: This function should never be used with threaded rendering, as it stalls the renderer.
  <C++ Error>    Condition "RenderingServerGlobals::threaded" is true. Returning: false
  <C++ Source>   servers/rendering/renderer_rd/storage_rd/particles_storage.cpp:1541 @ particles_is_inactive()

Perhaps the GPUParticles design needs to be altered to not call these functions if possible, but I think demoting these errors to warnings is appropriate.

@brianwinterpixel
Copy link
Contributor

Someone on the rendering team should check in on this issue some time.

@YuriSizov
Copy link
Contributor

The linked issue has been closed by #76859. So I guess we can say this is superseded now. Thanks for your contribution nonetheless!

@YuriSizov YuriSizov closed this Jul 14, 2023
@YuriSizov YuriSizov removed this from the 4.x milestone Jul 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Vulkan GPUParticles3D related error spam with multithreaded renderer
5 participants