LuckyBoy wrote:
Hi, this look like a bug specific with 10X0 NVidia card reported before on previous game versions.
NVidia was not able to reproduce the issue.
You're saying the reproduction is easy, right ?
Yes. It's easy. It happens every time I open the game and go to the map editor.
And it's happened across 2 driver versions. The driver in my signature is the current one I'm using.
LuckyBoy wrote:Could you give us more details:
On the repro. steps and on your config:
I see you've a 1080 but do you have multi-display setup ?
No. I'm using a single monitor. BenQ BL3201-B. No other monitors or TVs are connected to the PC. Just this monitor, connected via DisplayPort.
As to the reproduction steps:
Launch ManiaPlanet from a desktop shortcut. I use the standalone version.
Connect normally.
Go to a title.
Go to map editor.
Choose Advanced editor or Simple editor (both have it)
Choose any mood (they all have the same issue)
LuckyBoy wrote:Are you displays using same resolution ?
Are you asking the game the same resolution as windows' display one ?
Thanks
Windows and ManiaPlanet are set to the same resolution, the monitor's native resolution, 3840x2160.
I'm using Windows 10 Home (10.0.16299 Build 16299)
Windows resolution:
ManiaPlanet launcher settings:
Storm Water:
Storm Land:
Lagoon:
Stadium:
Stadium64:
Even some of the overlay messes up if I enter a title and then exit back to the main menu.
And legacy titles, like the TM2 one have messed up buttons, which disappear until I hover over them:
And this affects all titlepacks, not just the new maker ones. I opened the editor in TM2 multi-env and in TMOne Alpine. Both had the same issue.
In all these cases, if I tab out and back in, it fixes it.
If I go windowed, it fixes it. Going fullscreen again and the problem doesn't return. It's only there when loading the game fullscreen.
Okay, I just performed a little test. I actually have a second install of ManiaPlanet on another partition. It doesn't have the issue.
But if I copy over my
Default.SystemConfig.Gbx from the install that has the issue, the second install also has the issue.
Deleting
Default.SystemConfig.Gbx and letting ManiaPlanet generate a new one allows the second install to work again.
Here's a copy of the configuration with the issue:
Default.SystemConfig.Gbx
And a copy of the new config that ManiaPlanet generated (this one works):
Default.SystemConfig.Gbx
It's not the most pressing issue for me personally (since there's a workaround), but it's one I'd never experienced before, and I've had this card for over a year.
Thanks for taking an interest in the issue. I imagine more people will be picking up 10X0 series cards as time goes on and prices drop.