[Bug 41425] New: Everquest Titanium (Project 1999) crashes if you start in fullscreen
https://bugs.winehq.org/show_bug.cgi?id=41425 Bug ID: 41425 Summary: Everquest Titanium (Project 1999) crashes if you start in fullscreen Product: Wine Version: 1.9.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aaronbpaden(a)gmail.com Distribution: --- If you install EverQuest Titanium, it crashes by default because it starts in fullscreen mode. I'm using wine-staging, but I think I remember seeing this in stable as well.
From the logs, it looks like the game is trying to switch to 1280x720 and failing, though xrandr tells me my display does support this resolution.
The workaround is to either edit the config and switch to windowed mode, or use a virtual desktop at 1280x720. The game does support widescreen modes in fullscreen, and they do work, but using those modes don't prevent the crash at startup. As a result, if you want to play fullscreen you have to start in windowed mode and then switch to fullscreen in game, then switch back to windowed mode before you quit. I'm using WINEARCH=win32, winecfg is set to Windows XP, and a clean wine prefix. The last few lines repeated about a million times before I killed the process. I cut those out for convenience. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41425 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #1 from winetest(a)luukku.com --- "From the logs, it looks like the game is trying to switch to 1280x720 and failing, though xrandr tells me my display does support this resolution." Can you switch into that mode in your desktop? xrandr -s 1280x720 -r refresh rate. This bug sounds like invalid to me. I think your xrandr is missing the resolution. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41425 --- Comment #2 from Aaron Paden <aaronbpaden(a)gmail.com> --- You're right, my bad. I read it several times but saw only 1024x768, I guess because of the era the game was made in. No idea why EQ is trying to use this display mode, though. :/ -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41425 --- Comment #3 from winetest(a)luukku.com --- (In reply to Aaron Paden from comment #2)
You're right, my bad. I read it several times but saw only 1024x768, I guess because of the era the game was made in.
No idea why EQ is trying to use this display mode, though. :/
You can add resolution modes into xrandr. I dont remember how, but ARCH guides are quite good in general. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41425 Aaron Paden <aaronbpaden(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #4 from Aaron Paden <aaronbpaden(a)gmail.com> --- That did work, thanks! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41425 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTOURBUG |INVALID --- Comment #5 from Matteo Bruni <matteo.mystral(a)gmail.com> --- Let's claim that the application is the culprit here (although it's not obvious that's the case) and thus resolve this bug INVALID instead. Glad you made it work :) Are you using Nvidia binary drivers by any chance? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41425 --- Comment #6 from Aaron Paden <aaronbpaden(a)gmail.com> --- I'm on radeonsi, actually. I wonder if I should file a bug with mesa, as far as not supporting the resolution... Well, I know the supported resolutions are generated from the EDID, so my display is probably at fault, or the DVI to HDMI adapter in-between. Then again, I know I didn't have this issue when I was still maintaining a Windows partition on the same hardware. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41425 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Bruno Jesus <00cpxxx(a)gmail.com> --- Closing invalid bugs. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org