http://bugs.winehq.org/show_bug.cgi?id=16403
Summary: No text visible in Ever17 Product: Wine Version: 1.1.10 Platform: PC URL: http://www.download.com/Ever17-Out-of-Infinity/3000- 7494_4-10573528.html OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: tyle7@hotmail.com
Created an attachment (id=17728) --> (http://bugs.winehq.org/attachment.cgi?id=17728) Terminal output when running the game.
The text in ever17 is not visible, this applies to all text in the game except the start and the options screens. This occurs both in the Japanese DVD version, and the US trial version of the game.
The only difference between the two is that the Japanese version gives a message that "since MS Gothic couldn't be found, character display is likely to become strange."
I have tried adding MS Gothic and other fonts to wine's Fonts folder, but to no effect.
This has been tried with a clean ~/wine folder on wine from latest git with the patch http://bugs.winehq.org/attachment.cgi?id=17707 applied to avoid the crash in bug 10005.
System used is Ubuntu 8.10.
http://bugs.winehq.org/show_bug.cgi?id=16403
tyle7@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
http://bugs.winehq.org/show_bug.cgi?id=16403
tyle7@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #1 from tyle7@hotmail.com 2009-01-05 13:07:40 --- This seems to have been fixed in wine 1.1.12. When trying with a clean wine prefix, text is displayed as it is supposed to.
Resolving as FIXED.
http://bugs.winehq.org/show_bug.cgi?id=16403
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Alexandre Julliard julliard@winehq.org 2009-01-16 10:39:09 --- Closing bugs fixed in 1.1.13.
http://bugs.winehq.org/show_bug.cgi?id=16403
Svein Ove Aas sveina@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sveina@gmail.com
--- Comment #3 from Svein Ove Aas sveina@gmail.com 2010-09-12 09:24:42 CDT --- As of Wine 1.2, this bug is back in action.
The no-render hack at http://wiki.winehq.org/FAQ#head-3b18ce54edb7ea108c8f08945bc52812c4e3ef71 "fixes" it, apparently at a dramatic cost in performance.
http://bugs.winehq.org/show_bug.cgi?id=16403
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #4 from Dan Kegel dank@kegel.com 2010-09-12 11:01:36 CDT --- Please attach a log of console output.
http://bugs.winehq.org/show_bug.cgi?id=16403
--- Comment #5 from Svein Ove Aas sveina@gmail.com 2010-09-12 12:04:06 CDT --- Created an attachment (id=30719) --> (http://bugs.winehq.org/attachment.cgi?id=30719) Terminal output
I actually tested wine 1.1.44 as well - bug there too - and now wine 1.3.2, which is where this log output is from.
http://bugs.winehq.org/show_bug.cgi?id=16403
--- Comment #6 from Jeff Zaroyko jeffz@jeffz.name 2010-09-12 16:23:31 CDT --- (In reply to comment #5)
Created an attachment (id=30719)
--> (http://bugs.winehq.org/attachment.cgi?id=30719) [details]
Terminal output
I actually tested wine 1.1.44 as well - bug there too - and now wine 1.3.2, which is where this log output is from.
If it was originally fixed then please file a new bug report.
http://bugs.winehq.org/show_bug.cgi?id=16403
--- Comment #7 from Svein Ove Aas sveina@gmail.com 2010-09-12 16:24:54 CDT --- I have no reason to believe it was in fact ever fixed.
http://bugs.winehq.org/show_bug.cgi?id=16403
--- Comment #8 from Jeff Zaroyko jeffz@jeffz.name 2010-09-15 01:49:12 CDT --- (In reply to comment #7)
I have no reason to believe it was in fact ever fixed.
You said it was back in action... for something to be back, it had to have first been.
If you have tested 1.1.12 and it does not work for you then it may well be a different bug, since the original reporter said it was fixed for them in that release.
If you do test 1.1.12 and find that it is working correctly in that version, then it is a new bug also.
If the original reporter can confirm they were mistaken, this should be reopened.
http://bugs.winehq.org/show_bug.cgi?id=16403
--- Comment #9 from Svein Ove Aas sveina@gmail.com 2010-09-15 02:48:32 CDT --- I cannot test 1.1.12, as it does not compile on a modern Linux system due to (at least) libpng API changes. I said the bug was back under the assumption that it had at one point been fixed, but since I have no real evidence of this I no longer feel it's safe to assume that.
If you insist, I can open a new bug instead.