Lego Dimensions crash to desktop #1102
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Current Behavior
The last version of CEMU that worked correctly with Lego Dimensions and the ToyPad emulator was version 2.0-49, every version after this will crash to desktop after it asks you to put Batman on the ToyPad. I don't know if the real thing still works correctly as mine broke.
Expected Behavior
Game to keep working and not crash to desktop.
Steps to Reproduce
System Info (Optional)
OS: Windows 11 Pro
GPU: Nvidia GeForce GTX1650 4GB GDDR5
CPU: Intel Core i9 9900k
RAM: 2x16GB G.Skill Trident Z Royal 4400MHz DDR4 CL19
Mainboard: Asrock Z390 Extreme4
Emulation Settings (Optional)
No response
Logs (Optional)
log 20-66.txt > Log with crash in 2.0-66
log 20-49.txt > Log without crash in 2.0-49
You're using a pirated copy of the game
I'm not going to lie, I did download this copy of the game from a website, that is correct. If it really matters, I can dump the disk and try again. It just takes a lot of "effort" to do so as my Wii U is currently in storage and getting Haxchii installed again. But if it is really needed I will.
This is also a duplicate report, as the crashing is already mentioned in a PR working on the issue.
https://github.com/cemu-project/Cemu/pull/971
Nope this is something completely different and has nothing to do with having the ToyPad emulator integrated into CEMU itself. This emulator for the ToyPad should behave and be detected as a real physical USB-ToyPad even though it is an application running on a VMWARE Linux/Debian, and it works correctly with the "old" version. If my Physical pad would still be in working order (4 year old kid with scissors while playing Lego Dimensions with her, is not a great combo) I would test it with that as well, and I'd be 99% sure that would not work either.
[Wrong.
Read (https://github.com/cemu-project/Cemu/pull/971#issuecomment-1813261040) (and https://github.com/cemu-project/Cemu/pull/977 where a mitigation was first proposed)
First of all, that issue is not really working on this specific error, but mentions it in a fleeting way, on to which you have made a small patch or hack that still isn't added into the current version, but again it isn't clear that this patch/hack actually fixes THIS issue.
Secondly, I had indeed found that specific issue before making this one
Finally, if I wasn't sure regarding that specific issue being known as I've did an extensive search on it before making it, then I cannot be the only one. Therefore, having it as a visible issue for everyone to see is betterer...