@Rickv123: for what i can see in the log, first and less important you already have the files in the destination folder, the app will no overwrite existing files always usea clean folder as destination, and second
the mip_4 file has a wrong size, it should be 256x512 but it is 128x256, the glitch part is an erro and i will try to solve it.
(04-01-2017, 05:49 AM)Tino Wrote: [ -> ]@Rickv123: for what i can see in the log, first and less important you already have the files in the destination folder, the app will no overwrite existing files always usea clean folder as destination, and second
the mip_4 file has a wrong size, it should be 256x512 but it is 128x256, the glitch part is an erro and i will try to solve it.
It also happens when I remove all files inside the ouput folder.
As for the texture resolution.
"mip0" = 2048x4096
mip1Â Â = 1024x2048
mip2 Â Â = 512x1024
mip3 Â Â = 256x512
mip4 Â Â =128x256
so mip 4 is the correct size right!?
Also when I create a mip5 or mip6 or anything smaller than the original texture resolution, it still says "expected resolution of 256x512" which oddly enough is the exact same size as the orignal resolution of the texutre.
(04-01-2017, 05:57 AM)Rickv123 Wrote: [ -> ]It also happens when I remove all files inside the ouput folder.
As for the texture resolution.
"mip0" = 2048x4096
mip1Â Â = 1024x2048
mip2 Â Â = 512x1024
mip3 Â Â = 256x512
mip4 Â Â =128x256
so mip 4 is the correct size right!?
Also when I create a mip5 or mip6 or anything smaller than the original texture resolution, it still says "expected resolution of 256x512" which oddly enough is the exact same size as the orignal resolution of the texutre.
yes that is the bug, thanks
will try to fix it asap
Ishiiruka is just being plain slow, 52-58 FPS usually, but 59-63 on normal dolphin. Crashes on random, hard to navigate, and  honestly I just prefer normal dolphin. So just try to make it more like that.
(04-01-2017, 11:24 PM)diegochiha Wrote: [ -> ]So no way to fix it yet?
Tested on my system and no hang, can you sare your configuration?
(04-01-2017, 12:46 PM)Shuik Wrote: [ -> ]Ishiiruka is just being plain slow, 52-58 FPS usually, but 59-63 on normal dolphin. Crashes on random, hard to navigate, and  honestly I just prefer normal dolphin. So just try to make it more like that.
I will be really happy to fix issues, but for that I need more detail, what configuration are you using? Backend? Hardware? What game are you testing? What do you refere to when you say "hard to navigate"?
updated latest folder with a new version, merge latest master changes to fix some hangs issues reported here.
Hello Tino,
I just tried version 918 and I experienced severe screen tearing playing Xenoblade Chronicles.
I went back to 914 (the previous one I found in the MEGA folders) and it was gone. (I've never had V-Sync enabled in either version.) This is on the Direct3D 12 backend.
In general though, the last few versions have made Xenoblade finally playable for me at a stable 30 FPS. I would have given up on the game a long time ago had I been forced to play it using the official version (very choppy), so thank you.
(04-02-2017, 01:36 PM)Consolarificus Wrote: [ -> ]Hello Tino,
I just tried version 918 and I experienced severe screen tearing playing Xenoblade Chronicles.
I went back to 914 (the previous one I found in the MEGA folders) and it was gone. (I've never had V-Sync enabled in either version.) This is on the Direct3D 12 backend.
In general though, the last few versions have made Xenoblade finally playable for me at a stable 30 FPS. I would have given up on the game a long time ago had I been forced to play it using the official version (very choppy), so thank you.
The last version fixed vsync disabled in dx12, in prev version it was allways enabled, so now if you need to remove tearing you will have to enabe vsync