sorry, i got you mixed up with Danv . you had the opengl driver goofy shit, he had concerns about vram. when i was pinging you regarding image compression stuff, i meant to ping them instead.
Win10, i7-7700, gtx1070 8gb, 16gb RAM
i see, then id say its safe to assume those stutters are because your gpu doesnt support astc so it has to fallback convert to rgba, meaning the load times wont be improved by astc. well cant win them all i guess, but good to have as an option because if the hardware supports it its heaps better. glad that atleast unloading offscreen images is useful, even without astc )
Just a question.What version of the checker you use? 11.0.1 or a beta one ? or maybe even 10.2 or what it was.
my version is 11.0.1 and I am getting that error for a different thread
Not sure if it would be possible now with the new check rate implemented on the site (a couple of weeks ago i think it was), and it might cause more issues and errors instead of helping. And I am on 11.0.2 1437 beta version now so my guess is it might be an api issue or a database issue.
I'll have to check the cache api logs. My guess is the thread was made private for a small amount of time, it was refreshed during that time, so it was cached that it was unavailable, then it was reopened, and threads that don't exist get cached for up to 14 days. Also I'm away for next week or so, can't really do much about it for now.
You're right, that's not really feasible. What I could do is try to make it forget that it doesn't exist if it is found in the 12-hour periodic version check (currently it doesn't touch entries that don't have a version cached, so threads that don't exist are skipped), and in the latest updates check (same here)
No worries, have fun and Happy New Year, in case I won't be able to tell you later.
Actually, thinking about it some more.
This actually sounds like something it could be relatively easy implemented, something like "Ignore X for 24 hours or 1 week" or whatever time it was set.
Something like that, yes. It could have multiple options, like a timer as i said, or a checkmark for permanent, ofc with option to remove it later on.
It's not always a matter of time. Some games just get removed from f95zone indefinitely for breaking the rules or whatever else. Possible solutions I see is either yeah with a timer or indefinitely, where it ignores until it is available again (which is possibly never). Would also need to find a way to indicate somewhere that it is ignored.
Might be a bad suggestion or idea... but this makes me wonder if it can be implemented in the error message the reason in more details why the thread is gone? For example if it is banned for rules breaking, when you get the error to have it stated there. I know we have a general idea of why.
