The following will outline the known issues that have been reported thus far from users running Wiisis. You will also find any workarounds that have been reported as we become aware of them. If you are suffering from any of these issues, we ask that you follow the instructions below to help us determine a solution.
1. Runaway Thread error
Workaround: None found yet, but we are working on a solution.
If you are experiencing this error:
1. Please create a file called "autoexec.cfg" (you will have to rename it) in your Crysis root folder and put the following in it:
con_restricted 0
log_verbosity 8
log_fileverbosity 3
2. Run Wiisis until you experience the error.
3. In your Crysis root folder, you will find a file "Game.log" (if ran in Crysis) or "Editor.log" (if ran in the Editor). Please paste the content of this log along with a generated DXDiag.txt file in the following thread: Wiisis "RunAway Thread" Error Reports.
4. To create a DXDiag.txt file, in the Start menu, use the run command. Type "dxdiag" and click the OK button. In the new window, select save the system information and note the location of where the file is saved.
2. Wii Nunchuk controller not detected
Workaround: None found yet, but we are working on a solution.
If you are experiencing this error:
1. First, ensure the Wii Nunchuk is fastly connected to your Wii Remote controller.
2. If the Wii Nunchuk is connected, try another Wii Nunchuk controller, to ensure the connection plug is not damaged. If you do not have another Wii Nunchuk controller, skip this step.
3. If you have another Wii Remote controller, try using it with Wiisis. Connect your Wii Nunchuk to it and see if it detects it.
4. If all else fails, please download and run the Wiisis Extension Check application. This program will return debug information to us to help determine the problem. Please follow the instructions provided in the Readme.txt file. Once done, please paste the contents of the log file in the following thread: Wiisis Extension Check results.