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

Glitching in editor and game #83713

Open
therabug opened this issue Oct 21, 2023 · 8 comments
Open

Glitching in editor and game #83713

therabug opened this issue Oct 21, 2023 · 8 comments

Comments

@therabug
Copy link

Godot version

4.2.beta2

System information

Windows 11 - Godot 4.2.beta2 - Vulkan (Forward+) - Nvidia GT 1030 - Amd Ryzen 3 1300x

Issue description

In settings (sdfgi or any graphical setting) if you go quick and crazy this glitch happenes and only way to fix this is restart the editor.
image

Steps to reproduce

-Created a project
-Created a 3D Scene
-Added a WorldEnviroment
-Quickly maximize SDFGI settings

Minimal reproduction project

testttt.zip

@Calinou
Copy link
Member

Calinou commented Oct 21, 2023

The linked project uses the multi-threaded rendering model, which has known issues as the warning message on startup says. Please revert that setting to its default value and try again.

-Quickly maximize SDFGI settings

Which SDFGI property did you maximize specifically?

@therabug
Copy link
Author

The linked project uses the multi-threaded rendering model, which has known issues as the warning message on startup says. Please revert that setting to its default value and try again.

-Quickly maximize SDFGI settings

Which SDFGI property did you maximize specifically?

i saw now sorry. um i maximize min cell size it made it. But i think this bug happens because godot has no gpu vram limit? because when i open big scenes this bug appears cause my of gpu struggling to procces.

@Calinou
Copy link
Member

Calinou commented Oct 21, 2023

But i think this bug happens because godot has no gpu vram limit?

This is probably not related directly to VRAM exhaustion, but indirectly related to Vulkan synchronization errors occurring because of the GPU becomes much slower when VRAM is exhausted.

There's a fair chance #80566 resolves this issue.

@therabug
Copy link
Author

But i think this bug happens because godot has no gpu vram limit?

This is probably not related directly to VRAM exhaustion, but indirectly related to Vulkan synchronization errors occurring because of the GPU becomes much slower when VRAM is exhausted.

There's a fair chance #80566 resolves this issue.

okay thx i hope it'll fixed soon

@AllianceDarkSylinc
Copy link

Hi!

I cannot reproduce.

Tried on:

  1. Windows 10, GeForce 1060 3GB, i7 7700 32GB
  2. Windows 10, AMD Radeon RX 560 2GB , i7 7700 32GB (though I have the Polaris bug when MSAA is enabled)
  3. Windows 10, Intel HD Graphics 630, i7 7700 32GB
  4. Xubuntu 20.04, Radeon RX 6800 16GB, Ryzen 5900X 32GB

I didn't try Windows 11. Another common factor is that except for the Intel iGPU, my GPUs are faster than yours (it could be either a race condition, or the driver gives up if too much work has been queued up).

Questions:

  1. Have you tried disabling multi-threaded rendering model as you were asked to?
  2. Could you try by disabling MSAA? (Project -> Project Settings -> Rendering -> Anti Aliasing -> MSAA 3D set to "Disabled (Fastest).

Cheers

@therabug
Copy link
Author

therabug commented Oct 22, 2023

Hi!

I cannot reproduce.

Tried on:

  1. Windows 10, GeForce 1060 3GB, i7 7700 32GB
  2. Windows 10, AMD Radeon RX 560 2GB , i7 7700 32GB (though I have the Polaris bug when MSAA is enabled)
  3. Windows 10, Intel HD Graphics 630, i7 7700 32GB
  4. Xubuntu 20.04, Radeon RX 6800 16GB, Ryzen 5900X 32GB

I didn't try Windows 11. Another common factor is that except for the Intel iGPU, my GPUs are faster than yours (it could be either a race condition, or the driver gives up if too much work has been queued up).

Questions:

  1. Have you tried disabling multi-threaded rendering model as you were asked to?
  2. Could you try by disabling MSAA? (Project -> Project Settings -> Rendering -> Anti Aliasing -> MSAA 3D set to "Disabled (Fastest).

Cheers

idk i just use default settings thing that i just changed is sdfgi options

i think you need to do fastest and highest possible settings

@jss2a98aj
Copy link

jss2a98aj commented Oct 25, 2024

Since #80566 was superseded by #87340 and it got merged, was this issue resolved? I am not seeing it happen on my system with stock 4.3, but my GPU has a lot more VRAM than a GT 1030 does.

@clayjohn
Copy link
Member

It's possible that this was fixed, but it's tough to say as only the OP was able to reproduce the issue in the first place. We will have to wait for them to confirm

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

No branches or pull requests

5 participants