if texture cache rework slowed down the game, why didn't anyone report this so we could fix it? its the first time i've heard of any game slowing down. Can you show before and after for where its slower?Etrian Odyssey V got the slow down
if texture cache rework slowed down the game, why didn't anyone report this so we could fix it? its the first time i've heard of any game slowing down. Can you show before and after for where its slower?Etrian Odyssey V got the slow down
Sorry but I haven't touch canary in ages....I was just checking canary only for Radiant Historia.if texture cache rework slowed down the game, why didn't anyone report this so we could fix it? its the first time i've heard of any game slowing down. Can you show before and after for where its slower?
yesss the game has a demo. i'm getting sick of buying random games i'll never play just to fix bugs in themSorry but I haven't touch canary in ages....I was just checking canary only for Radiant Historia.
The slowdown is during whole game period (from title),
The frame time simply jumped from single digit to double digit.
The console log on both versions are 100% identical...
(Edit: CPU JIT on, hardware renderer on, shader JIT on, VSync off, Limit framerate 100% (no effect when turn off), internal resolution auto window size)
Below are rough numbers:
nightly-571(auto window size)
in-town - frame time: 4.50ms
dungeon - frame time: 5.50ms
nightly-572 (auto window size)
in-town - frame time: 19.70ms
dungeon - frame time: 24.40ms
Edit: Just found out what affects the most - internal resolution increase becomes much more costly after texture cache rework
nightly-572 (native)
in-town - frame time: 7-12ms
dungeon - frame time: 14.30ms
And it took nightly-572 slightly longer (a full second?) to stop the emulation in both cases.
blog post is live! https://citra-emu.org/entry/improvements-to-hardware-renderer/ citra speed up hype!
I don't have an AMD GPU but I'll drop you the answer that I got in Citra's Subreddit because I think that it applies to your situation too:AMD HD5870, catalyst 15.6 (OGL 4.4)
Fire Emblem Awakening - citra closes itself with 3d models appearing
Metroid SR - driver crash at start or 2-3 sec after
So far so good!
Are there any optimisations in plans or it's just hopeless for me?
Canary is the place where we try to fix the bugs, but still let people test the latest features. No guarantee that we can fix your specific setup, but this is just the first release. Make sure you update your graphics drivers as well.
I don't like AMD for bad OGL drivers and abandoning non-CGN videocards (mine HD5870 was almost on par with HD7850 when it first came out) But a crash tendency? They do their job well if all you do is playing regular Steam games. You need to look into each separate case to determine where the problem lies. We don't have internet cafes where I live but I bet they use the cheepest components (such as MB, memory) in their PCs. I'd start digging here.Why do AMD GPU tend to crash PCs?
Didn't AMD help develop the OGL standard?...I don't like AMD for bad OGL drivers and abandoning non-CGN videocards (mine HD5870 was almost on par with HD7850 when it first came out) But a crash tendency? They do their job well if all you do is playing regular Steam games. You need to look into each separate case to determine where the problem lies. We don't have internet cafes where I live but I bet they use the cheepest components (such as MB, memory) in their PCs. I'd start digging here.
i guess your gpu is bad?With Native Resolution, it's 60FPS.