Emulator Issues #8787
closedLilt Line (wiiware) Error
0%
Description
Game Name?
Lilt Line
Game ID?
WLZEXY
What's the problem? Describe what went wrong in few words.
Multiple errors appear on game opening screen and game hangs. After skipping errors in the game text appears "press any button" but game doesn't react to controller
What did you expect to happen instead?
Game should proceed into the main game menu
What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]
1.Run the game
2.Skip developer logos
3.errors appear
4.after skipping all errors game logo is shown and "press any button" text
5.game doesn't react to any buttons
Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
3.5
4.0
4.0-6997
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
game worked perfectly in 3.5 with "real external frame buffer"
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Windows 8.1 x64, 8Gb Ram, Intel Core i5-3470, Nvidia Geforce GTX 760
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
List of errors
08:43:983 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b50, PC = 0x8007d8f0
08:44:593 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b54, PC = 0x8007d8f8
08:45:088 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b58, PC = 0x8007d8fc
08:45:121 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b5c, PC = 0x8007d900
08:45:154 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b52, PC = 0x8007d904
08:45:188 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b52, PC = 0x8007d910
08:45:219 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b58, PC = 0x8007d918
08:45:253 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b5c, PC = 0x8007d93c
08:45:286 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b60, PC = 0x80004530
08:45:319 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b61, PC = 0x80004530
08:45:353 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b62, PC = 0x80004530
08:45:391 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b63, PC = 0x80004530
08:45:417 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b64, PC = 0x80004530
08:45:448 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b65, PC = 0x80004530
08:45:481 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b66, PC = 0x80004530
08:45:515 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b67, PC = 0x80004530
08:45:547 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b68, PC = 0x80004530
08:45:580 MsgHandler.cpp:80 E[]: Warning: Invalid Write to to 0x10176b69, PC = 0x8006d0c0
Updated by JMC4789 over 9 years ago
Can you try this in 3.5 with the game properties option of Enable MMU checked? It should crash then, I believe, which would mean this is not a regression as much as a 3.5 inaccuracy allowed it to boot.
Updated by 30zaozabot over 9 years ago
It didn't crashed with "Enable MMU checked" checked.
Updated by JMC4789 about 9 years ago
Sorry for the long delay, issue tracker change over. Please bisect the issue for me. Find the build that broke this game's compatibility.
Updated by JosJuice about 9 years ago
- Status changed from New to Fix pending
Updated by JosJuice almost 9 years ago
- Status changed from Fix pending to Fixed