[color=#ff0000][color=#006600]i5 3570K @ 4.5GHz/GTX 660 Ti/RAM 4GB/Win7 x64[/color][/color]
[Wii] 428: Fuusa Sareta Shibuya de
|
02-28-2022, 12:43 AM
Not sure it is my own problem or no one reporting since there is no testing entry.
This game need to set Texture Cache = Safe to run properly, otherwise the text is unreadable. Appreciate someone look into this. 02-28-2022, 01:11 AM
(02-28-2022, 12:43 AM)wongheiming Wrote: Not sure it is my own problem or no one reporting since there is no testing entry. This is a very common problem with games, so you a probably correct. 03-16-2022, 01:06 AM
I encountered another glitch after hours of playing, obviously I'm too focus on the story
First at all, attachment Default should be the correct rendering (too lazy to test on a real Wii..), which Texture Cache = Safe is set in user profile, otherwise globe settings leave as default. To take advantage from the program, I changed the graphic settings globally for normal playing session. Internal Resolution = 2x Native Anti-Aliasing = 2x MASS Here comes the glitch, there are "square graphical artifacts" just like resident evil 2 & 3 with above mentioned settings. (attachment Normal) Then I add ForceFiltering = False in user config, the artifacts still exists. (attachment Enhance) Further, I add InternalResolution = 0 and MSAA = 0 in the profile, and expect it works just like the Default. Apparently it is not. (attachment Enhance Full) However, I found the square spacing is a bit different between Enhance and Enhance Full, probably due to the resolution different. Here comes the details of the profile. [Video_Settings] SafeTextureCacheColorSamples = 0 [Video_Enhancements] ForceFiltering = False << (used in Enhance and Full) [Video_Settings] InternalResolution = 0 << (used in Full) MSAA = 0 << (used in Full) After adding [Video_Settings] parts, the game run much slower then without it. I assume the emulator use the globe setting at the beginning, and then apply user profile settings in the second step? So in this case the emulator scale up the resolution to x2, and then scale down to native, thus a degraded performance as a result I expect it runs as smooth as the default setting though 03-16-2022, 03:31 AM
InternalResolution = 0 corresponds to "Auto (Multiple of 640x528)". If you want "Native (640x528)", you should use InternalResolution = 1.
For MSAA, I'm not actually sure what 0 means. But you should use MSAA = 1 if you don't want MSAA. 03-16-2022, 01:54 PM
(03-16-2022, 03:31 AM)JosJuice Wrote: InternalResolution = 0 corresponds to "Auto (Multiple of 640x528)". If you want "Native (640x528)", you should use InternalResolution = 1. Thanks! InternalResolution = 1 fixed the slow down problem (my fault). However I do curious how does auto resolution work? From a post "What does auto resolution actually do?" on reddit, mbc07 says: Auto will select an internal resolution multiplier closest to the window size or closest to your native screen resolution if you're playing in fullscreen (e.g. if you're playing in full screen and your native screen resolution is 1366x768, Dolphin will pick 2x IR if you left it on Auto). By chance, my native screen resolution is 1366x768. When I mistakenly set InternalResolution = 0, it should have the same effect as Auto, Dolphin will pick 2x as mbc07 describe, which is what I selected in globe setting. Then why I experience a slowdown when added in user config? For MSAA, from the wiki page GameINI it says MASS = 0 will set it to the top of the list value which is "None", and adding SSAA = Ture / False will toggle between SSAA and MSAA. Therefor I believe MASS = 0 will turn off Anti-Aliasing, and it works as expected. |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)