RandomGitUser321

That seems pretty normal and would likely do that even on the console itself. Sometimes, devs manually set LODs on singular assets.

> I doubt the console has these squares Well you were talking about buggy LODs, as in the models shifting between higher and lower levels of detail. The texture/shadow artifacts...

Example of the VRAM usage during my workflow:  **EDIT**: I've managed to reliably trigger this three times in a row. It happens on exactly the 30th call to Ollama....

How safe is something like this? Sounds like a good way for bad actors to potentially inject malicious exploits into workflows.

I can also confirm this. It took a lot longer than five zooms, on an 8gb GPU, but it eventually ran out of vram and crashed. To clarify, it was...

> It happens everywhere, so a save wouldn't really be that useful. If I have time later, I might try recording a video of it with some RTSS graphs of...

Here's like 7 minutes of VRAM usage. The graph range is from 0-8GB. The sloped ramp-ups are from me playing with the map to fill it up. The first dip...

No the vram usage stays even after the map is closed. It takes warping away to clear the stored up pool or rapidly loading in a bunch of new draw...

It's a Windows scheduler issue. This same stuff happens with python.exe based apps. You have to run them as admin to get it to use the p-cores, otherwise, they'll only...

> > It's a Windows scheduler issue. This same stuff happens with python.exe based apps. You have to run them as admin to get it to use the p-cores, otherwise,...