Closed rolandoislas closed 7 years ago
I know im being a pain in the ass here, but I think this might relate to my new problem. I stupidly done a system reset to get rid of parental controls and any Mii's that were on the system (which I now know was a very stupid move) as now im getting a memory error and no touchpad control when the gamepad pairs back up at system restart. Im sorry for all the problems im having, im usually good with consoles but this one has jinxed me from the start lol.
Edit, the touchpad probably still works, but it just throws up a memory error about 5 seconds after the initial screen.
Where does the error appear? It sounds like it is from the Wii U (on screen). Is the error similar to #10?
Sorry for taking so long to reply. Anyway this is what happens.
Step 1 - Turn on the console img_20170329_214424
Step 2 - Press the sync button on the console img_20170329_214504
Step 3 - Get the key and start the server and it pairs ok img_20170329_214852
Step 4 - Run the client and get this screen on the tv img_20170329_214858 and this on the client img_20170329_215147
Step 5 - About 5 seconds later on the client screen after I hit the mouse button to touch img_20170329_215238
Then the console freezes and I have to power off. I could maybe try the new server version with the old euro firmware and see if that works. If thats possible?
Edit: Removed inline images
Version 1.1 sends the old firmware data, but the Wii U may attempt to update it and fail anyway.
If the newer server is started with the -f
parameter (e.g. drc-sim-backend -f
) the logging will increase in verbosity. With the ~/.drc-sim/log/backend.log
I might be able to get a better understanding of what the Wii U is requesting. Note that the log from the terminal (all output) and ~/.drc-sim/log/wpa.log
will contain SSID found when connecting and is not required.
Sorry m8, didnt see the last comment before I got a loan of a pad and used that to start and update.
Thankx for all you did to make this possible even without the sound, sorry if I was a pain in the ass lol.
Hi, I'm having the same problem too. This may be a problem because I am running the server and the client on the same slow computer. Basically what happens is I turn on the wiiU and connect the virtual gamepad but when I tap the screen, the client and WiiU freeze up and after about 5 seconds, it displays the message "A System Memory Error Has Occurred." I don't know if this was because of the know if this is because of the server or the client. It would be great if you could find a patch for this or identify the issue. Thanks so much!
If it only happens after touch input, try to navigate with button input. Also see this previous comment for enabling debug logging.
Sorry to bother you again but it actually requires you to touch the screen and I don't think theres button input for that. Do you know another way?
I need the logs to know more about the error.
Here are the outputs of the client and the server Output logs.txt
The Wii U now registers DRC Sim as an up to date gamepad.
The data is from an NA gamepad, so I expect it will not work in other regions.
The dev branch now has a region selector in the GUI. Could someone test the NA version data with a Wii U of a different region?
Swedish wii u. Tried the NA version data and it worked better until it crashed with the same system memory error in the system setup right after the screen resolution settings.
Now it worked although now it wants to update the gamepad and gets the error: Error Code 165-9901 The update cannot be completed using a Wii u GamePad designed for different region.
Did the setup complete? The error code is the same as in #10.
After the setup, reconnect with no specified region or "None". The Wii U will display a few messages about it being unable to communicate with the gamepad but it should still work.
The setup did complete. And now it 100% works after I changed the region to none like you sad. Thanks man, really appreciate your work and your quick answers.
Currently drc-sim sends null data to the Wii U when asked for the firmware version.
Make that not so.