search

PhantomGamers / SteamFriendsPatcher

EnableNewSteamFriendsSkin, now with a GUI and auto scanning!
MIT License
199 stars 8 forks source link

Black window on minimized startup #12

Open NuclearMeltdown opened 3 years ago

NuclearMeltdown commented 3 years ago

Hi, I've had this issue for a while now. After updating the client from 0.1.29 to 0.1.35 (didn't prompt me to update since that version came out), it still persists. Whenever SteamFriendsPatcher starts, it opens up a tab in the task bar. When clicking on it, you only get a completely black window that can't be interacted with. It can be resized, minimized, but not closed. When closing it, it stays open, but you get that little notification that SFP is now scanning in the background. The only way to get rid of this is whenever the program starts, to click on the tray icon to 'open' the program and then the previously black window becomes interactable. This might have to do with the 'start minimized' option in the settings, because it doesn't happen when it is disabled. Before this broke, it only ever created its tray icon and stayed away, which is my preferred way of using this program. Have it be out of the way and do its thing in the background. I've attached a picture of this issue happening.

image

PhantomGamers commented 3 years ago

"After updating the client from 0.1.29 to 0.1.35 (didn't prompt me to update since that version came out), it still persists." This was my fault, I had accidentally broke the update checking functionality, but it's fixed now so you should be alerted of future updates.

As for the primary issue at hand, this is very strange behavior. The only thing that changed between 0.1.29 and 0.1.35 that I think could be responsible for this is the update to .net framework 4.8. I'd recommend installing (or even reinstalling, if you already have it installed) the .net framework 4.8 runtime and see if that fixes it https://dotnet.microsoft.com/download/dotnet-framework/net48

Also what version of windows are you running? What is your hardware setup like (are you only using a dedicated graphics card, or do you also have integrated graphics?) It could perhaps be related to hardware acceleration (I'm unsure if the framework used for the GUI of the program uses this)

FWIW though on my end I also use Start Minimized and I don't have this problem. These are the settings I'm using: image

NuclearMeltdown commented 3 years ago

I think I didn't clarify, I had this issue on 0.1.29 too. I was hoping it would've been fixed somewhere along the way to 0.1.35. I can't recall when exactly it started happening. But if the runtime was changed between 0.1.29 and 0.1.35 and the behaviour persists, I'd figure it can't be related to that. The program works perfectly fine, too, just not on startup if start minimized is enabled. I wouldn't even know how I would uninstall .NET Framework 4.8 because it doesn't show up in any program list. The repair tool only fixes issues installing newer versions and I can't install 4.8 because it's already installed.

I'm running Windows 10 Education aka. Enterprise with a different name 20H2 19042.630 and I have an RTX 2080ti, so no integrated graphics.

I would guess the program thinks it's minimized to tray but is somehow stuck between the two states of being minimized and showing the window, so it only renders the frame? No idea what could be causing this though. I also deleted everything in the config path to see if something in there would be causing issues but it stayed the same.

These are my settings minus start minimized because it's broken and stuff.

image

PhantomGamers commented 3 years ago

"I think I didn't clarify, I had this issue on 0.1.29 too." Sorry, this was my mistake not yours, I misread your initial message.

You said "Before this broke, it only ever created its tray icon and stayed away, which is my preferred way of using this program." Does this mean it worked as intended in some previous version? Do you remember which version? It would help me to be able to go and see what I changed between a functional version and a broken version.

NuclearMeltdown commented 3 years ago

Unfortunately, I can't remember what version it was where it still worked. I don't even remember if I even updated the app for it to not work anymore, which would indicate that it's a problem on my end. It might've been a Windows update or an update to something else OS related. I'm really not sure.. I could go back and install a few versions before 0.1.29 and see if it works then, if that would help.