Open Caraamon opened 1 year ago
I'm using version 1.32.1 beta 24.
The screenshots are definitely not from v1.32.1 (which should be about 20 years old by now). You can check the version number in the About dialog (menu Help > About Near Infinity).
I can't reproduce this issue on my end with the current NI version. Can you open the debug console (menu Tools > Show Debug Console) and see if there are any error messages?
It would also be helpful to know the installed Java version and architecture. It should be displayed in the "System Information" block shown on the main panel when you start up Near Infinity. If it's not shown then enable it in the Preferences dialog (menu Game > Preferences...): General section > Display System Information at Startup.
Whoops, was looking at the wrong number.
Near Infinity: v2.4-20230729 Java Runtime: OpenJDK Runtime Environment Java Version: 17.0.7 (2023-04-18) Java VM: OpenJDK 64-Bit Server VM (17.9.7+7, mixed mode) Java VM Architecture: amd64 Available Memory: 16336 MB
Debug console is empty.
Side note: it does still have the issue in fullscreen mode, but it seemed to take longer to happen.
System specs look fine to me. It could be video driver issue, but that's just a guess.
Could you clarify what exactly "fullscreen mode" means? Did you mean at maximized window?
Sorry, yeah, maximizing the window seems to delay the corruption, but it's not like I tested extensively, just SEEMS that way.
So I'm getting some GUI corruption and I'm not sure if it's an issue on my end or a problem with NI. I'm using version 1.32.1 beta 24.
Here's what it looks like, and I don't have the skills to know where to even begin to look for the problem. It doesn't seem to be limited to any specific menu and it doesn't always happen (but it happens pretty often). I can get it to reset by resizing, dragging it to my other monitor, or minimizing and bringing it back, but once it starts doing it, it keeps doing it, even after closing the program and restarting.
Any suggestions?
Edit: I just noticed this while getting more screenshots, it does NOT seem to do this while fullscreen, only when windowed. Which I guess solves my problem, but I'll still submit in case this somehow helps someone else.