[Bug 23616] New: Fallout 3: childbirth scene halts after every (second) line of dialogue, preventing new game

wine-bugs at winehq.org wine-bugs at winehq.org
Sun Jul 11 15:29:35 CDT 2010


http://bugs.winehq.org/show_bug.cgi?id=23616

           Summary: Fallout 3: childbirth scene halts after every (second)
                    line of dialogue, preventing new game
           Product: Wine
           Version: 1.2-rc6
          Platform: x86
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: -unknown
        AssignedTo: wine-bugs at winehq.org
        ReportedBy: aka.motub at gmail.com


Created an attachment (id=29538)
 --> (http://bugs.winehq.org/attachment.cgi?id=29538)
terminal output during childbirth scene

I have been experiencing this since 1.1.44 all the way through to 1.2-rc7, but
my investigation revolves around rc6, so that's the version I'm reporting.

My specs:

Linux Mint 9 Isadora 32-bit
wine 1.2-rc6
nvidia 7900GS (AGP) 512MB driver 195.36.24

new wine prefix
only vcrun2005 installed via winetricks (only because the Launcher won't run
without it)
new install of Fallout 3, patched to 1.7

The issue presents itself immediately upon entering the childbirth scene. With
some versions of Wine, my father would not even "say" his initial line (I don't
have sound in the childbirth scene, like everyone else, but I do turn general
subtitles on before running the game for the first time). In this case, the
baby-cam continues to move, and the visible characters continue to animate, but
there is no further progress (or so I thought), forcing me to ESC and quit.

With RC6, Dad does say "Let's see... are you a boy or a girl?" as expected, but
this does not trigger the expected gender choice dialog. Again, the visible
characters continue to move (the game is not crashed or hung), but the dialog
doesn't appear so one can't progress through character creation.

This time, instead of quitting, I ESCaped to bring up the main menu, then chose
'Continue' rather than Exit to re-enter the running game, and hit 'E'. Lo and
behold, the gender choice appeared. I chose my sex, and Dad said his next line
("It's a girl? A girl!... etc"), and then the game "halted" before Catherine
(Mom) could say her line. ESC=>ESC=>E got her to say her bit.

In this way (ESCaping out to the menu, choosing Continue, and hitting E when
back in the Play screen-- sometimes twice, as the scene is running a bit slow,
but that's just me, I think) I was able to get to the penultimate moment of the
scene, where the baby (me) is moved out of the room, which should trigger a
whiteout to the next stage, before you even reach the door. In this case, I was
pushed all the way through the door and into the hall-- which I had never seen
(thank heavens they made a hall on the other side of the door), and this time
it required 3 ESC==>ESC combos to trigger the whiteout (because Dad has like
two separate speech sets and maybe the whiteout is also similar in terms of how
it's triggered).

At no time did the game crash, hang or stop; at times Dad would look right and
then seem to stop, but the blinking lights on the monitors in the back of the
scene always continued, even if the actors seemed to be frozen. The system
seems to be that if there's a player dialog triggered (gender choice, name
choice, appearance), then getting that dialog to appear and making your
choice(s) will cause the following response line from whatever actor (Dad,
usually) to be said automatically, but any further speech (response from
another actor, triggering of another dialog) has to be done manually.

There's nothing much significant-seeming in the terminal log, but it's attached
anyway.

In any case, if this can be confirmed, the only reason it avoids being a
blocker (to people starting a new game) is that there appears to be a
workaround, slow and tedious though it is. But I certainly for several versions
didn't even play FO3 because this appeared as a blocker to me before I happened
upon the workaround.

Please confirm or advise as to possible other causes native to my system or
Wine installation.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.



More information about the wine-bugs mailing list