-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"nil is not a string" error message while starting a game #551
Comments
I cannot reproduce this here. Can you open up the installed game and check the file "ABUSE.LSP"? You should be able to find it inside a file called something like "Abuse.pure.zip" inside the "Saves" directory of your RetroArch installation. ABUSE.LSP should be next to ABUSE.EXE and should be around 1416 bytes of size. Alternatively you could get the game data and source from this page http://abuse.zoy.org/wiki/download and extract the "data" directory out of abuse-0.8.tar.gz. Then add the ABUSE.EXE from your DOS version to create a full package for DOS. Though I haven't tested more than just launching the first level with this. There is also https://github.com/Xenoveritas/abuse/releases/tag/v0.9.1 which has maybe even more fixes but misses the sound effect files so you'll need to start off from that 0.8 download anyway. |
Hi, here's the content of the abuse.lsp:
I've used DosBox Pure 0.9.9 and DosBox 0.7.4 via Launchbox and the file did load without any issues. I've checked some forums regarding "nil is not a string" and it seems to be a much high complex issue, not only related to this game. |
some related info if you find it useful. The 10MB "Abuse (USA) (En,Fr,De).zip" version has weird bugs... The "Abuse (Europe) (En,Fr,De) (Rerelease).zip" version does work fine. |
Installing the Abuse CD version and running it will show me the following error message while the game is loading the required files.
However, loading the game in the legacy DosBox will not show the error message refering to 'nil' and loads the abuse.lsp properly.
The text was updated successfully, but these errors were encountered: