Log In  

I've just got Voxatron from my friend through gift from Humble Bundle, and downloaded game as standalone. When I've ran it, after 10-15 seconds screen goes black, and nothing works, including Ctrl+Alt+Del or anything on keyboard or mouse. I'm using Windows 7 SP1 with ATI Radeon HD 4600 Graphic card and AMD Athlon64 X2 on 2.2 GHz.

How to fix this problem? Version is still 0.1.4.

P#3722 2011-11-09 15:44 ( Edited 2012-01-31 23:13)

Can't remove this one, just read upper post and ignore this one.

P#3723 2011-11-09 15:45 ( Edited 2011-11-09 20:46)

weird Im playing on win 7 with integrated HD card (lol) and it runs fine. Try running it as admin?

P#3724 2011-11-09 16:01 ( Edited 2011-11-09 21:01)

As an experiment, could you try switching to windowed mode as soon as it starts up? (alt+enter).

You could also switch off DirectX support: Go into the folder Voxatron was installed in and edit config.txt. Look for the line "windib 0" and change it to "windib 1" then run the program again.

In the same folder, Voxatron also generates a log file called log.txt which you could paste here or email to me at [email protected]

So I take it you can see the first 10-15 seconds ok before it crashes? (the lexaloffle intro screen) Were you doing anything when it crashed (starting a new game / skipping the intro screen etc.) or does it seem random?

P#3726 2011-11-09 16:13 ( Edited 2011-11-09 21:15)

First, I can't do anything when it begins to fullscreen. That includes even alt+enter.

Second, there is no config.txt.

Third, this is only what says in log before I reset my PC as I can't take any other action:

codo_init
codo_system_init
SDL version 1.2.14
codo_reset_timer
codo_gui_init
codo_keys_init
codo_text_init
codo_gfx_init
opengl_blit not supported
retrieving video information
stored desktop resolution: 1280 1024 32
ok
codo_set_screen 0 0 32 11
retrieving desktop resolution: 1280 1024

Don't ask about updating drivers as they are already updated a lot of times.

Fourth, The first 10-15 seconds after running Voxatron executable, that's just where game seems to load in background, or how else to say, it's not showing up yet. When it shows up, all what I see is black screen and hangs. There's no intro screen, or any kind of game graphic during whole time of load of game.

I hope I didn't confused you about fourth reply.

EDIT: It seems that when I've installed through setup, game works, while standalone zipped file doesn't work. I'm not sure what was missing in it. Try to at least check how to make it work in portable.

P#3799 2011-11-10 03:03 ( Edited 2011-11-10 08:18)

Bump, it seems that there's other problem... I've just left my PC idle for 3 hours, and tried to play. Again same problem, even on 0.1.5. I don't know anymore what's problem.

P#3948 2011-11-11 04:40 ( Edited 2011-11-11 09:40)

Thanks for the information -- this is indeed strange behaviour. I'm not sure why using setup.exe vs unzipping somewhere should make a difference, as the installer basically does the same thing.

It might be something to do with the permissions of the installed folder, but Voxatron should be able to run fine from a read-only disk in the worst case (just, not settings can be saved).

The reason there is no config.txt file is that the game seems to be crashing before it gets a chance to write one out.

If you have time, please try this:
In the same folder as log.txt, create config.txt containing the following single line:
windib 1

It looks like it's crashing during initialising the video mode. Normally what happens is if this fail it drops down from DirectX to a simpler blitter (Windows DIB). It's possible it's crashing instead of just reporting a failed attempt.

P#4171 2011-11-12 20:45 ( Edited 2011-11-13 01:46)

As far it goes now... It seems stable on windib 1.

About setup.exe vs unzipping, it doesn't make any effect, though setup version caused black screen few runs later, while unzipped one caused it at first run.

Suggestion: Make troubleshooting about config.txt in readme file so that people can try to run game properly if they can't.

P#4456 2011-11-15 14:07 ( Edited 2011-11-15 19:07)

Woo -- yeah, thanks I'll add this to vox.txt (and config.txt itself)

It sounds like the unzipped vs. setup thing is a red herring, and it fails reasonably randomly.

P#4495 2011-11-16 08:32 ( Edited 2011-11-16 13:32)

Hey! I just signed up specifically to add to this...

I, too, have had the same problem. I'm reading this at work, so I can't try this fix... but running a very similar system and Windows 7/64-bit, I've had the same screen-blackening occur.

Thanks!

P#4887 2011-11-23 21:18 ( Edited 2011-11-24 02:18)

Same problem here...ASUS RampageIII, Intel i7-970, 24gb ram, ATI 6870, Win7 x64 ULT.

It acts like it crashes the graphics drivers, locks up the PC for 30+ minutes...usually requires reset, unless I can open task manager and close vox.

Log.txt:
codo_init
codo_system_init
SDL version 1.2.14
codo_reset_timer
codo_gui_init
codo_keys_init
codo_text_init
codo_gfx_init
opengl_blit not supported
retrieving video information
stored desktop resolution: 1920 1200 32
ok
codo_set_screen 0 0 32 11
retrieving desktop resolution: 1920 1200
SDL_SetVideoMode failed .. retrying in windowed mode.
succeeded at 1920 1200 32 0
codo_joystick_init
found 2 joystick(s)
0 Razer Nostromo
Number of Axes: 6
Number of Buttons: 24
Number of Balls: 0
1 Controller (XBOX 360 For Windows)
Number of Axes: 5
Number of Buttons: 10
Number of Balls: 0
ok
codo_sound_init
SDL_INIT_AUDIO ok
SDL_OpenAudio ok
codo_load_pod_set: C:/Program Files (x86)/Voxatron/vox.dat ok
generated sounds: 2866ms
Initialised vox scores.
instruments: 13

P#5446 2011-12-22 09:41 ( Edited 2011-12-22 14:41)

Do you see any change if you set "windib 1" in config.txt?

P#5450 2011-12-22 15:30 ( Edited 2011-12-22 20:30)

hmm wish this board had notification emails :)

windib 1 fixes the crash problem

P#5824 2012-01-31 18:13 ( Edited 2012-01-31 23:13)

[Please log in to post a comment]

Follow Lexaloffle:          
Generated 2024-03-28 08:54:01 | 0.013s | Q:26