One thing that could be of some help, is adding a line number of the GEMUS script where the error occurred. That would make it a bit easier to find what caused the error message.
However, it's quite simple to find the location in the GEMUS script manually.
The only thing you have to do is put a few Show_Message commands in the script.
These messages will be displayed in a popup window. You have to press the OK button to let GEMUS continue parsing the script.
Example:
Code: Select all
Add_CLP( -option1)
Show_Message(Step 1)
Add_CLP( -setting2)
ShowMessage(Step 2)
Set_CFG_Value(1||Setting3||true)
Show_Message(Step 3)
Run_Emulator()
If nothing is filled in under Script Files in the GEMUS menu, running a game with this emulator will display a popup
"Step 1", then a popup
"Step 2" and then an error message
"Invalid file referenced in script file".
So the error must be between Step 2 and Step 3.
And indeed, the line
Set_CFG_Value(1||Setting3||true) is the cause of the error message.
Also inserting this line:
just before the line
Run_Emulator() could help you debugging the GEMUS script.
It will display a window with the Command Line Parameters before the game starts.
In GB 1.3 Beta, you can also add a line
Show_KV().
This line will display a window with the applied Key=Value pairs before the emulator starts.