5/28/2023 0 Comments Retroarch windows 10 flickeringI did a "sudo raspi-config" to adjust a few settings (locale, keyboard, timezone, memory split 256/256, etc) Here's my full history since first boot of this fresh card image: This was on a fresh Raspbian Wheezy image that I just download from the official site. It is now solved, I'll commit it next hour.This first "make" failed for me (for Retroarch). "Hide when Running Game" : Thanks, I do crash too, it is a bug, due to the CPU use hack I added for WIN32. I usually use around 250 Mb and it work pretty fine with all themes. For now : Either use a low VRAM theme, either increase VRAM preference. It would need a complete rewrite, but it is a very big work. Then, it needs to display the image and reload it, it needs room, it unload the image again, and so on. It flickers because it loads the image, it needs room, it unload the image. The VRAM manager doesn't care about what's on the current screen. Better not change anything, and let the user do. Different methods are needed according to the kind of video card. Furthermore, Windows has no unique way to do that. "Detect how much vRam is available" -> Can't find a portable way to determine that. But it must be beautiful compared to where I live. Never went so far -) Don't know if I ever will. Good run on bug fixes, that's 3 for 3 Tasmania. I thought the 200MB Vram would have been fine, thanks again for simple fix, but maybe we can force a dual reload when returning from a ROM, like i said every 2nd time you returned from a game it would work perfect again, so it is possible to get it to draw correct every time even with low vram? not important now it's fixed tho. Since you made it drop usage I had no need to enable it, like you said then, you can disable it for Windows machines ) I use Power saving mode disabled since mentioning the issues with scraping with it set to anything else making it abort scraping. If I enable "Hide when Running Game" it will crash ES entirely when I exit back to ES, I have to close with TaskMGR, I use a dual screen setup, this might cause a issue). Increasing VRAM fixed it, Do you have the ability to detect how much vRam is available, because my system has 1023 MB Physical Memory and seeing as the default ram size is 100mb it might be worth checking this in a Windows OS quickly each boot so it can change the default 100mb (if detected as 100mb to be more by default (not Pi's default)). I guess that is why I switched to Emulation, it's always gonna be appreciated. Maybe it is related too -> Try disable powersave I have lived in Tasmania all my life, most I done was make LastOS (Windows mods) since early 2000's until today, it's a lot slower since Windows 10 came and killed off modding. I have flickerings issues too when I set VRAM too low and it occurs in the 1.9 release too -> Try increase VRAM limit - On Windows with an NVIDIA card, you can set it to 500 without any problem.Īre you using a powersave mode ? When using powersave, Mouse/Keyb events are the only way to redraw the screen. ![]() There is a mecanism to unload/reload resources (which, honestly, should be rewritten too, but I didn't touch it yet). ![]() Using your theme & preloading, it would require > 3Gb VRAM (yes 3Gb !!!) you can see it enabling the option "show framerate"- to keep everything in memory. Maybe your scapped images are very big too. Your theme is HD and needs a lot of VRAM. Image loosing/reloading is caused by not enough VRAM. To be in 1.9 release condition, you should try setting the option "HIDE WHEN LAUNCH." to ON ? This option is not available in 1.9 releases, and loading/unloading is a bit different when disabled. I have tried this with 1 rom on a clean release and it still Hi Glenn, from Austalia -) (dawn it is far from France.), I don't reproduce the problem, but you don't provide a lot of informations. I have NVidia GTX 550Ti, but this bug also affected my nVidia 610m on my laptop. I have tried transitions set to fade, slide and none, always does this glitch. ![]() and the next exit is broken - so I am thinking a flag/toggle is set wrong or checked to be a value >1 instead of =1 or something. I just noticed if I run a 2nd rom once it's messed up, once it returns from that it is fine again. ĭoesn't matter if I use windowed mode or full screen. I have always had this bug since your first 2.10 release, it has changed a bit (improved) as it used to lose some collection icons and the main wallpapers on the carousel. The only reason it comes back at 21 seconds is due to me manually moving the window using the mouse, once I do this it fades the collection wallpaper and icon back in.īTW I can actually exit from one Collection and enter another and the wallpaper/icon is still missing until the 3rd or 3th time I enter a collection then it also redraws properly after fading back in. This shows the re-draw bug when I exit any game, using any theme.
0 Comments
Leave a Reply. |