[Bug 55233] New: A-Train PC Classic - UI is incorrectly sized and cannot switch between selected windows.
https://bugs.winehq.org/show_bug.cgi?id=55233 Bug ID: 55233 Summary: A-Train PC Classic - UI is incorrectly sized and cannot switch between selected windows. Product: Wine Version: 8.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- The UI windows in A-Train PC Classic are unusable. Note: This game was ported from the Nintendo 3DS, and most / all of it's UI is intact. "UI windows" are essentially the game's menu / dialog box interface. (Called "windows" here as that's what the game's configuration INI file calls them.) Attempting to start a new game the first time causes each window to fill the entire application window and draw on top of each other. With only the top most window receiving user input. For the second attempt to start a new game, the windows are correctly sized / placed but only the most recently drawn window accepts user input with no way to switch to an inactive window. This breaks the game as the first requirement of the player is to use an inactive window's "Enter Company Name" button. The game's configuration INI file contains options for setting each window's origin X/Y coordinates, width and height. However editing these values manually seems to result in a deadlock. With the game continuing to update the application window (minimize / partial hide / etc.) but otherwise refusing user input after showing the company logos. Attempting to use a known good configuration file from Windows also doesn't work. As the game seemingly ignores it with no visible window behavior change from when starting a new game. As described above. -- 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=55233 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- This bug report is missing vital information. Please see https://wiki.winehq.org/Bugs#Do.27s_and_Don.27ts -- 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=55233 --- Comment #2 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- Created attachment 74847 --> https://bugs.winehq.org/attachment.cgi?id=74847 Console log Sorry, forgot the console log. FYI: The crash at the end of the attached log occurs when the user quits out of the game. The bad file descriptor client errors and "Failed to read display config." errors have started occurring in *all* of my prefixes (pre-existing and new) after having updated to wine 8.12, and I have yet to see them cause any new bugs with anything. -- 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=55233 --- Comment #3 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- Created attachment 74848 --> https://bugs.winehq.org/attachment.cgi?id=74848 Image of first time selecting new game with bugged window / cursor. This image shows how the game draws it's UI the first time the user selects the new game option. (Note: The window behind is the "3DS menu screens" which should be visible to the user by default.) The black transparency on the cursor is only visible for that specific frame of it's animation. -- 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=55233 --- Comment #4 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- Created attachment 74849 --> https://bugs.winehq.org/attachment.cgi?id=74849 Image of first time selecting new game and attempting to click the window This image shows an obvious window movement bug occurring when the user attempts to click on the oversized window. This bug only occurs the first time the user tries to start a new game. Subsequent attempts draw the windows with their correct size, and this visual bug doesn't occur. -- 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=55233 --- Comment #5 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- Created attachment 74850 --> https://bugs.winehq.org/attachment.cgi?id=74850 Image of the second time the user starts a new game. This image is of the subsequent times the user tries to start a new game. In this case the UI is mostly drawn correctly, but some visual bugs (like the black cursor transparency on that one animation frame) are still present. -- 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=55233 --- Comment #6 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- Created attachment 74851 --> https://bugs.winehq.org/attachment.cgi?id=74851 Image of second new game attempt. (As far as the user can get.) This image is as far into a new game that the user can get. Attempting to click on the "Enter company name" button on the inactive window doesn't work. Nor does the game recognize that the mouse cursor is over it. (The game should highlight the button by making it brighter in that case, but it doesn't.) The inactive window also cannot be selected. As the game should cause that window to draw over the dialog box below it in that case. (Due to it overlapping.) The windows are also locked in their current positions and cannot be moved by the player. (They should be movable by clicking and dragging them with the mouse.) -- 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=55233 --- Comment #7 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- Created attachment 74852 --> https://bugs.winehq.org/attachment.cgi?id=74852 Image of bugged opening FMV. For completion's sake, this is an image of the opening FMV. Which is clearly cut off during playback. Note: This specific visual bug can be worked around by installing dxvk into the prefix. Doing so however will not fix anything else in this bug report, and was not performed when creating the attached images and logs. -- 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=55233 --- Comment #8 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- Still present in wine-8.16. Is there still additional info needed? If so, what? -- 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=55233 --- Comment #9 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- Still present in wine 9.0-rc5. No changes to the bug's behavior since wine 8.16. Why is this still marked as NEEDINFO? -- 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=55233 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |UNCONFIRMED Ever confirmed|1 |0 CC| |o.dierick(a)piezo-forte.be --- Comment #10 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Patrick Hibbs from comment #9)
Why is this still marked as NEEDINFO?
Hello, Changed back to unconfirmed. Regards. -- 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=55233 --- Comment #11 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- Still present in wine 9.5. A small improvement, it is now possible to run the game in a clean wine prefix. -- 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=55233 --- Comment #12 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- (In reply to Patrick Hibbs from comment #11)
Still present in wine 9.5.
A small improvement, it is now possible to run the game in a clean wine prefix.
Misspoke, the game still requires mfc120 from winetricks. Sorry for the noise. -- 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=55233 Vijay Kamuju <infyquest(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |infyquest(a)gmail.com --- Comment #13 from Vijay Kamuju <infyquest(a)gmail.com> --- Can we close the bug as it's working fine in a clean prefix albeit with mfc120 from winetricks. Wine development considers MFC* component out of scope and will not be implemented within the project. -- 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=55233 --- Comment #14 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- (In reply to Vijay Kamuju from comment #13)
Can we close the bug as it's working fine in a clean prefix albeit with mfc120 from winetricks.
Wine development considers MFC* component out of scope and will not be implemented within the project.
No, the game fails to recognize inputs to the UI properly. (As described previously.) The game is unplayable under wine, and is rightfully classified as Garbage in wine's AppDB. The last comment I made above was the result of me fat-fingering the up arrow key on my keyboard one too many times during testing. Which caused me to use the wrong prefix for the game. Using a clean prefix will result in the game crashing due to the prefix lacking mfc support. Installing mfc120 via winetricks allows the game to start, but it's still unplayable. (Due to the issues described in this bug report.) -- 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=55233 --- Comment #15 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- Clarification: In no circumstance does wine play this game correctly. The game's UI is broken, and as of this posting no prefix I have tried has ever gotten the game's UI to work correctly. Regardless of prefix modifications or winetricks use. -- 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=55233 --- Comment #16 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- Created attachment 76586 --> https://bugs.winehq.org/attachment.cgi?id=76586 wine-9.10 console log Still present in wine-9.10. A small change of note, wine is now outputting unixlib errors when playing the intro video. (No changes to the video output however.) -- 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.
http://bugs.winehq.org/show_bug.cgi?id=55233 --- Comment #17 from Patrick Hibbs <hibbsncc1701(a)gmail.com> --- Created attachment 79038 --> http://bugs.winehq.org/attachment.cgi?id=79038 Hidden window borders made visible by game exit prompt. Still present in wine-10.12. Attempting to close the game from the main menu, after attempting to start a new one, now causes it to show a black screen with the normally hidden borders of the game's (previously closed?) windows visible to the user. The good news is the borders are (mostly) in the correct places. The extra borders seem to be the result of the initial windows being incorrectly sized as previously reported. Screenshot attached. -- 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)
-
WineHQ Bugzilla