A friend of mine is getting an unexpected shutdown of the AGS engine. Any thoughts what this could be? There is no error message, and the log is as follows,
Adventure Game Studio v3.3 Interpreter
Copyright (c) 1999-2011 Chris Jones and 2011-2014 others
ACI version 3.3.0.1156
*** ENGINE STARTUP ***
Installing exception handler
Reading config file
Initializing allegro
Setting up window
Initializing game data
Game data file: e:/Data/Games/ERRAND/ERRAND~1.3-2/Errand.exe
Initializing TTF renderer
Initializing mouse
Checking memory
Initializing audio vox
Initializing keyboard
Install timer
Initialize sound drivers
Install exit handler
Initialize path finder library
Load game data
Errand
Checking for disk space
Initializing MOD/XM player
Init gfx driver
Built library path: d3d9.dll
Created graphics driver: Direct3D 9
Initializing screen settings
Init gfx filters
Detecting maximal supported scaling
Applying scaling filter: StdScale5
Switching to graphics mode
Widescreen side borders: disabled (windowed mode)
Attempt to switch gfx mode to 320 x 200 (32-bit)
Succeeded. Using gfx mode 320 x 200 (32-bit)
Preparing graphics mode screen
Initializing colour conversion
Check for preload image
Initialize sprites
Set up screen
Initialize game settings
Prepare to start game
Audio thread started
Checking replay status
Engine initialization complete
Starting game
Loading room 0
***** ENGINE HAS SHUTDOWN
Well, if it would just crash, it won't write "ENGINE HAS SHUTDOWN". It looks rather a normal shutdown, but it could be caused both by game script or engine itself (if it detected some problem).
Does this occur anytime your friend is launching this game? And other people run it without problem?
EDIT: This brings my attention:
Quote
Loading room 0
Do you actually have a room 0 in your game (AGS suggests room 1 by default, although room 0 is technically supported too)?
The odd thing is that this sometimes happens and sometimes it doesn't, and I have been unable to reproduce it on my computer. Yes, there is a room 0 (older versions of AGS do default to room 0, which used to be called title.crm or start.crm or something like that).
Hmmm... maybe it's an odd setting of game.abortkey or something? But that should pop up a message box "the game was aborder", shouldn't it?
This issue keeps confusing me. No, it's not game.abortkey. However, it appears that removing the .TRA files from the game folder (even when no translation was selected!) avoids the crash. Isn't that weird?
Quote from: Radiant on Wed 14/01/2015 20:34:23
This issue keeps confusing me. No, it's not game.abortkey. However, it appears that removing the .TRA files from the game folder (even when no translation was selected!) avoids the crash. Isn't that weird?
Can I check the game?
Certainly. I'll PM you.
Issue solved, it's not an AGS engine problem. Thread can be locked.
Can you hint the issue at least?
Quote from: Dualnames on Thu 22/01/2015 06:36:04
Can you hint the issue at least?
Right mouse button was scripted to close the game when in main menu.
User was clicking mouse buttons randomly to skip the logo screens, and occasionally clicked RMB in main menu.