Messages

I can compile a non-steam version and see if that will work!

From what I've been told, the testers tried running other games and had no problem. So it's something specific to this version of AGS.

And I didn't see your post about it being from the setup file. Will ask him to send another one!

COnfirmed. The tester turned off compatibility and was running fullscreen in openGL.

I told him to run it without, but I asked him to confirm.

OK here's the log file. It looks very strange to me. I'm not sure if the tester did it right.

Code: ags

Adventure Game Studio v3.4 Interpreter
Copyright (c) 1999-2011 Chris Jones and 2011-2018 others
ACI version 3.4.1.13

Installing exception handler
Initializing allegro
Initializing game data
Looking for the game data file
Located game data file: c:/PROGRA~2/Steam/STEAMA~1/common/Unavowed/Unavowed.exe
Opened game data file: game28.dta
Game data version: 49
Compiled with: 3.4.1.13
Setting up game configuration
Running Setup
Built library path: d3d9.dll

The problem only occurs with OpenGL in fullscreen mode only. Direct3D mode works fine.

The tester sent me the log file, so I can only assume that it was generated fine.

Sorry the the double post. This has happened to two more testers. Hopefully one of these two will help me out and generate that log file for me!

One of my testers is reporting that that her desktop's normal mouse overlays the in-game mouse and causes the game to not take her input.

I asked her to generate a log file. Any light-shedding appreciated!

Code: ags

Adventure Game Studio v3.4 Interpreter
Copyright (c) 1999-2011 Chris Jones and 2011-2018 others
ACI version 3.4.1.13

Installing exception handler
Initializing allegro
Initializing game data
Looking for the game data file
Located game data file: c:/PROGRA~2/Steam/STEAMA~1/common/Unavowed/Unavowed.exe
Opened game data file: game28.dta
Game data version: 49
Compiled with: 3.4.1.13
Setting up game configuration
Setting up window
Initializing TTF renderer
Initializing mouse: number of buttons reported is 5
Checking memory
Data directory: c:/PROGRA~2/Steam/STEAMA~1/common/Unavowed
Initializing speech vox
Voice pack found and initialized.
Initializing audio vox
Audio vox found and initialized.
Initializing keyboard
Install timer
Initialize sound drivers
Sound settings: digital driver ID: 'AXA ' (0x41584120), MIDI driver ID: 'Auto' (0xffffffff)
Installed digital driver ID: 'AXA ' (0x41584120), MIDI driver ID: 'W32M' (0x5733324d)
Install exit handler
Initialize path finder library
Load game data
Game GUI version: 118
Requested script API: v3.4.1 (5), compat level: v3.2.1 (0)
Built library path: agsteam-unified.dll
Plugin 'agsteam-unified' loading succeeded, resolving imports...
Game title: 'Unavowed'
Checking for disk space
Initializing MOD/XM player
Initializing resolution settings
Game native resolution: 640 x 360 (32 bit)
Device display resolution: 1280 x 720
Game settings: windowed = no, screen def: explicit, screen size: 1280 x 720, match device ratio: ignore, game scale: stretch
Using graphics factory: OGL
Created graphics driver: OpenGL
Supported gfx modes (32-bit): 
	320x200;320x240;400x300;512x384;640x400;640x480;800x600;1024x768;
	1280x720;1280x768;1280x800;1280x1024;1360x768;1366x768;1400x1050;1440x900;
	1600x900;1680x1050;1920x1080;
Attempting to find nearest supported resolution for screen size 1280 x 720 (32-bit) fullscreen
Attempt to switch gfx mode to 1280 x 720 (32-bit) fullscreen
Running OpenGL: 4.4.0 - Build 20.19.15.4364
Succeeded. Using gfx mode 1280 x 720 (32-bit) fullscreen
Render frame set, render dest (0, 0, 1279, 719 : 1280 x 720)
Requested gfx filter: StdScale
Graphics filter set: 'StdScale', filter dest (0, 0, 1279, 719 : 1280 x 720)
Using gfx filter: StdScale
Mouse control: on, base: 1.000000, speed: 1.500000
Mouse confined: (0,0)-(1279,719) (1280x720)
Check for preload image
Initialize sprites
Initialize game settings
Prepare to start game
Audio is processed on the main thread
Checking replay status
Engine initialization complete
Starting game
Game GUI version: 118
Unable to write log to ''.
***** ENGINE HAS SHUTDOWN
[/quote]

Slight brag mode.

Look what just hit #1 on the Adventure Gamers Hype-O-Meter!

I'll ask them to create a log!

EDIT: There is another thing, winsetup actually initializes graphic drivers to be able to get list of supported resolutions. If this crash is related to one of them, that could explain why winsetup also does not run.

What about changing driver in acsetup.cfg by hand and trying if any of them works?
List of possible options is here: https://github.com/adventuregamestudio/ags/blob/master/OPTIONS.md

Since running it in compatibility mode works, would running winsetup in compatibility mode and changing the settings that way work just as well?

Well, another tester had the exact same problem so it's not an isolated incident. Couldn't get the game or winsetup to launch, but running in XP compatibility mode fixed it.

I found a very hacky way to fix this problem.

I ran the debug window (activated by pressing "`") while alt-tabbing in and out of the game until the problem manifested itself. When it did, I noticed that the debug window reported that an "on_key_press 399" command was being activated over and over again. So the reason why the dialog keeps skipping is because the game thinks a key is being pressed continuously. Pressing ANY key on the keyboard fixes the problem.

So I did a very hacky solution.

1 - I created a GUi that contained a single text message: "Game Paused. Press any key to continue." I named it "gUnpause".
2 - I added this bit of code under "function on_key_press" in the global script:

Code: ags

  if (keycode == 399) 
  {
    if (gUnPause.Visible==false)
    {
      gUnPause.Centre();
      gUnPause.Visible=true;
    }
  }
  else if (gUnPause.Visible==true) 
  {
      gUnPause.Visible=false;
  }

This "pauses" the game if the bug gets activated (which only happens about 1/5 of the time), and then forces the user to press a key to continue the game. SUPER hacky, but in lieu of an alternate solution this does the trick. Hopefully this bug will get fixed one day!

edit: Another solution is to use the command:

Code: ags

Speech.SkipStyle=eSkipMouseTime;

This prevents keyboard input from moving dialog forward. Although having a key constantly being pressed in the background could produce other bugs.

Why does it bring up Unforeseen Incidents in that text file guys? Doesn't that suggest this was running at the same time??

Not necessarily at the same time, these errors are stored in system log.
You may notice Unawoved.exe is mentioned 3 or 4 times, probably run in different time. There is also chrome.exe mentioned.

Dave, do older versions of Unawoved cause same issue for him? What was the version of AGS Shardlight made with? Maybe do few experiments and see if other games made with AGS 3.4.1 cause this also?

I tried turning on DEP on my system (Windows 7 64bit) and Unawoved runs fine, but I have last year version.
Have anything significant happened to the game, like you started using some plugin?

Haven't used any new plugins. Shardlight was made with one of the 3.3s. This is the only user this has happened to so maybe it's an isolated incident? Hoping so.

Does that mean there's a problem specific to his machine? Or with how the game is interacting with his machine?

I admit this is worrying. One user having this problem at testing time usually translates to several hundred once the game comes out.

So the user says he does use anti-virus (AVG free version), but the games folder is ring-fenced to avoid such issues. And he only has a single monitor.

He actually was mistaken and it turns out that our old games DO run just fine, so it's something specific to Unavowed.

The non-latin thing probably isn't the case since he is a native English speaker. I'll ask him about the rest.

Yep. That's what I'm talking about. Sweet. Thanks!

I'm too close to launch to update to this WIP version. But hypothetically speaking, if I later decide to upgrade, saves created in 3.4.1 should be compatible (assuming I don't do anything that breaks saves)? That's amazing.

So one of our Unavowed testers has had a very strange problem. He launches the game and nothing happens. The task manager lists the game as active, but the game isn't displaying. I asked the user to open winsetup to change the display driver, but the same thing happens when running winsetup. On a whim, I asked him to try running Shardlight (made in the non-openGL version of AGS) and he had the same problem. What's weird is that he used to be able to play Shardlight just fine.

He found a weird workaround -- he went through the Windows compatibility troubleshooter and set it to "Windows XP Service Pack 3" -- and now it's working.
We asked him to try launching Shardlight and see if the same thing happens. So it seems like either something has changed in Windows or something changed on his computer that's causing a problem. But no one else has reported this, so I'm confused!

Any light shedding would be appreciated! Thanks.

-Dave

edit: Here's his DxDiag.txt, just in case that's helpful.

He returns! Good to have you back.