apollyonica Posted May 24 Share Posted May 24 Under the following conditions: The Nexus Mod App is maximised The Nexus Mod App is on the primary monitor (of 2) The PC has just been woken from sleep User experiences a visual bug where random segments of the the Nexus Mod App flicker and show the programs/desktop "underneath" it. This flickering does not show up on screen recording, so no visual example is available. Issue can be corrected by exiting and re-entering the program. OS is Windows 10 Home running on a Core i5-12600KF and a 3060 Ti, with 32GB of RAM. More details available if necessary. --- Not a terribly pressing bug, but since it's still quite early days, I thought you guys might want to know. Link to comment Share on other sites More sharing options...
Staff Solution Sewer56 Posted May 24 Staff Solution Share Posted May 24 Pretty weird to hear. Not even sure if this is in our jurisdiction either, we rely on Avalonia for rendering. It's either an Avalonia issue, or a Graphics Driver (Nvidia) issue. Which of the two? I do not unfortunately know. Driver version might be helpful but not sure if we'd be able to reproduce, or do anything about it as is. Link to comment Share on other sites More sharing options...
apollyonica Posted May 24 Author Share Posted May 24 So, I was going to grab the driver version for you just in case, and then mark as done, since, as you said, this is only dubiously your jurisdiction, but abruptly ran into other issues. For about, eh, half an hour? The app straight up would not launch at all, and no logs were generated. This included attempts made after shutdown, after restart, as administrator, directly from NexusMods.App.exe, and from shortcut. I could hear my fans spin up for a few seconds, and then nothing. Then I made one last try with the log folder open to see if anything at all was happening there, and it launched just fine. At this point I'm concerned all of this is a hardware issue on my end, so I'm going to mark that reply as a solution and make sure my PC isn't imminently dying before I supply any more feedback . Link to comment Share on other sites More sharing options...
Staff Sewer56 Posted May 24 Staff Share Posted May 24 You can always pull a log file https://nexus-mods.github.io/NexusMods.App/users/faq/LogFiles/ In case there's anything interesting in there. Link to comment Share on other sites More sharing options...
apollyonica Posted May 24 Author Share Posted May 24 Failed and successful launch log files. They diverge on line 62. nexusmods.app.main.17.logFetching info... nexusmods.app.main.current.logFetching info... Link to comment Share on other sites More sharing options...
Staff Sewer56 Posted May 24 Staff Share Posted May 24 I'm guessing in the failed case, there was something unusual going on where the 'slim' server process had issues communicating with 'main' process. I'll tag @halgari out of curiosity, they'd probably figure it out a bit faster than I, since they're responsible for that part of the codebase. Link to comment Share on other sites More sharing options...
apollyonica Posted May 24 Author Share Posted May 24 If I can fetch anything else, let me know! Link to comment Share on other sites More sharing options...
Community Manager Pickysaurus Posted May 27 Community Manager Share Posted May 27 Not sure if this is the case. But whenever we saw these kinds of issue in Vortex it was always a GPU driver issue. We don't have an option in the app to turn off GPU acceleration but sometimes the GPU will attempt to apply effect like Anti Aliasing to desktop apps for whatever reason and it corrupts the visuals. Might not be that as you say it only happens when waking your PC but just thought I'd mention it Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now