Page 1 of 1
Running the Game
Posted:
29. September 2008, 06:23
by c_byran
Hi. I've finally downloaded the game today after 2 hrs lol. I install it on my old Dell Computer. 600mhz about 378mb ram and the game runs then exits to windows. I wonder why? I also have a GFORCE 2 Graphics card. Is my computer missing something? Thanks.
Re: Running the Game
Posted:
29. September 2008, 06:34
by vbtricks
I think you coult help the team tracking the error by posting the file
C:\Users\<YourUserName>\AppData\Roaming\Broken Sword 2.5
on Vista or
C:\Document and Settings\<YourUserName>\AppData\Roaming\Broken Sword 2.5
(not completely sure)
under XP.
Re: Running the Game
Posted:
29. September 2008, 07:19
by Master of Desaster
vbtricks wrote:I think you coult help the team tracking the error by posting the file
C:\Users\<YourUserName>\AppData\Roaming\Broken Sword 2.5
on Vista or
C:\Document and Settings\<YourUserName>\AppData\Roaming\Broken Sword 2.5
(not completely sure)
under XP.
You forgot to say which file it is, vbtricks!
It's the file log.txt.
Under XP:
This path:
C:\Document and Settings\<YourUserName>\Application Data\Baphomets Fluch 2.5\
or
C:\Document and Settings\<YourUserName>\Local Settings\Application Data\Baphomets Fluch 2.5\
Re: Running the Game
Posted:
29. September 2008, 07:19
by c_byran
Well, all it does it boots out. and gives me the error send report or don't send. i don't know what else to do???? I am in Windows XP and it won't allow me to copy and paste the error?
Re: Running the Game
Posted:
29. September 2008, 07:26
by Master of Desaster
Post the log file, then can the team help you!
Re: Running the Game
Posted:
29. September 2008, 08:53
by Neo
Hey
Try the newest driver for your Graphiccard !
Re: Running the Game
Posted:
29. September 2008, 12:34
by TobiasE22
same probs ... mit den aktuellsten treibern !
hier mein log:
Broken Sword 2.5 Engine - Build: Aug 30 2008 - 00:43:30 - VersionID: cd8a3ce31688fb99f90eea857689185
-----------------------------------------------------------------------------------------------------
KERNEL: created.
KERNEL: CPU detected (vendor name: "GenuineIntel", CPU name: "Intel(R) Pentium(R) 4 CPU 2.60GHz").
KERNEL: CPU features: MMX SSE SSE2.
KERNEL: Window created.
KERNEL: Service 'lua' created from superclass 'script'.
LUA: Lua initialized.
KERNEL: Script bindings registered.
PACKAGEMANAGER: Script bindings registered.
KERNEL: Service 'physfs' created from superclass 'package'.
PHYSFSPACKAGEMANAGER: Package 'data.b25c' mounted as '/'.
INPUTENGINE: Script bindings registered.
KERNEL: Service 'winapi' created from superclass 'input'.
GRAPHICENGINE: Script bindings registered.
KERNEL: Service 'opengl' created from superclass 'gfx'.
SOUNDENGINE: Script bindings registered.
KERNEL: Service 'fmodex' created from superclass 'sfx'.
GEOMETRY: Script bindings registered.
KERNEL: Service 'std' created from superclass 'geometry'.
MOVIEPLAYER: Script bindings registered.
KERNEL: Service 'oggtheora' created from superclass 'fmv'.
FMODEXSOUND: FMOD Ex initialized. Sample rate: 44100 / Channels: 32
PHYSFSPACKAGEMANAGER: Directory 'C:\Dokumente und Einstellungen\Terraner\Anwendungsdaten\Broken Sword 2.5\saves' mounted as 'saves'.
LUA: Error in coroutine
LUA: ------------------
LUA: thread: 0E17EF18
LUA: /rooms/chh/scripts/default.lua:264: The renderobject with the handle 52756 does no longer exist.
LUA: stack traceback:
[C]: in function 'SetVisible'
/rooms/chh/scripts/default.lua:264: in function 'DoPortal'
/rooms/chh/scripts/default.lua:198: in function </rooms/chh/scripts/default.lua:198>
LUA:
KERNEL: Active service 'oggtheora' disconnected from superclass 'fmv'.
KERNEL: Active service 'std' disconnected from superclass 'geometry'.
KERNEL: Active service 'fmodex' disconnected from superclass 'sfx'.
KERNEL: Active service 'opengl' disconnected from superclass 'gfx'.
KERNEL: Active service 'winapi' disconnected from superclass 'input'.
KERNEL: Active service 'physfs' disconnected from superclass 'package'.
KERNEL: Active service 'lua' disconnected from superclass 'script'.
KERNEL: Window destroyed.
KERNEL: destroyed.
Re: Running the Game
Posted:
29. September 2008, 13:53
by Ania
I have exactly the same problem as you c_byran and I still don't understand what to do next. I don't think that it's the graphics problem because I have GeForce 4, isn't it good enough?
Re: Running the Game
Posted:
29. September 2008, 20:27
by zerolink
I have the same problem. I'm posting the log file.
- Code: Select all
Broken Sword 2.5 Engine - Build: Aug 30 2008 - 00:43:30 - VersionID: cd8a3ce31688fb99f90eea857689185
-----------------------------------------------------------------------------------------------------
KERNEL: created.
KERNEL: CPU detected (vendor name: "AuthenticAMD", CPU name: "AMD Sempron(tm) Processor 2600+").
KERNEL: CPU features: MMX SSE SSE2 3DNow! 3DNow!Ext.
KERNEL: Window created.
KERNEL: Service 'lua' created from superclass 'script'.
LUA: Lua initialized.
KERNEL: Script bindings registered.
PACKAGEMANAGER: Script bindings registered.
KERNEL: Service 'physfs' created from superclass 'package'.
PHYSFSPACKAGEMANAGER: Package 'data.b25c' mounted as '/'.
INPUTENGINE: Script bindings registered.
KERNEL: Service 'winapi' created from superclass 'input'.
GRAPHICENGINE: Script bindings registered.
KERNEL: Service 'opengl' created from superclass 'gfx'.
SOUNDENGINE: Script bindings registered.
KERNEL: Service 'fmodex' created from superclass 'sfx'.
GEOMETRY: Script bindings registered.
KERNEL: Service 'std' created from superclass 'geometry'.
MOVIEPLAYER: Script bindings registered.
KERNEL: Service 'oggtheora' created from superclass 'fmv'.
FMODEXSOUND: FMOD Ex initialized. Sample rate: 44100 / Channels: 32
OPENGLGFX: WARNING - Could not set vsync status. Reason: NO_DRIVER_SUPPORT_FOR_VSYNC
OPENGLGFX: WARNING - Could not set vsync status. Reason: NO_DRIVER_SUPPORT_FOR_VSYNC
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - GLS_Blit() failed. Reason: INVALID_SUB_IMAGE
GLIMAGE: ERROR - Could not create GLS_Sprite. Reason: TEXTURE_CREATION_FAILED
MAIN: ERROR - Exception "EXCEPTION_ACCESS_VIOLATION" occured at 0x0044792F.
MAIN: Memory dump written to "C:\Documents and Settings\Facu y Agus\Datos de programa\Broken Sword 2.5\dumps\2008-09-29 16-24-cd8a3ce31688fb99f90eea857689185.dmp".
KERNEL: Active service 'oggtheora' disconnected from superclass 'fmv'.
KERNEL: Active service 'std' disconnected from superclass 'geometry'.
KERNEL: Active service 'fmodex' disconnected from superclass 'sfx'.
Good bye
And good luck :)
Re: Running the Game
Posted:
30. September 2008, 04:49
by c_byran
Well, I decided to give up on my old dell and go to my grandmas where I have a top of the line computer. NVIDIA 680iLT Style motherboard. With an NVIDIA 7900 XTreme graphics card. lol. Anyway, I redownloaded the game to my new machine loaded and behold. The game is awesome. It feels as if the story continues from Broken Sword II perfectly. I noticed a difference in humor but ah well :)
Now when will the ENGLISH/Voices be released? Next year? Im so excited. I can't wait. BTW: What are the best printers to get to make CD/DVD Labels, DVD Templates etc. I wanna make a perfect Broken Sword 2.5 :)
Re: Running the Game
Posted:
2. October 2008, 12:31
by thepr
edit: SORRY ABOUT THAT, IT WORKS PERFECTLY! ALL YOU NEED IS TO UPGRADE YOUR DISPLAY DRIVERS!
Very nice of these Mindfactory guys... they said the requirements for the game were supposed to be close to those of the original Broken Sword 1 and 2 games, and still there's an error when starting the game. I experienced it and got really pissed. And it seems like the BS 2.5 team will not answer this topic. I thought if there's a bug in your game you ought to fix it, right? I really hope the team won't let us down and try to fix this error. I mean, we WERE expecting this game for seven years, right?
Re: Running the Game
Posted:
2. October 2008, 12:33
by thepr
c_byran wrote:Well, I decided to give up on my old dell and go to my grandmas where I have a top of the line computer. NVIDIA 680iLT Style motherboard. With an NVIDIA 7900 XTreme graphics card. lol. Anyway, I redownloaded the game to my new machine loaded and behold. The game is awesome. It feels as if the story continues from Broken Sword II perfectly. I noticed a difference in humor but ah well :)
edit: DON'T MIND THAT! ALL YOU NEED TO DO IS UPGRADE YOUR DISPLAY DRIVERS IF THE ERROR PERSISTS!
Re: Running the Game
Posted:
2. October 2008, 14:52
by MassaSnygga
thepr wrote:Very nice of these Mindfactory guys... they said the requirements for the game were supposed to be close to those of the original Broken Sword 1 and 2 games, and still there's an error when starting the game. I experienced it and got really pissed. And it seems like the BS 2.5 team will not answer this topic. I thought if there's a bug in your game you ought to fix it, right? I really hope the team won't let us down and try to fix this error. I mean, we WERE expecting this game for seven years, right?
The statement about the requirements is no longer true. This is mainly due to the videos that use a rather slow video codec. This was not our choice but licensing problems forced us to do this. Apart from that almost every graphics card with 32-bit support should suffice. This rules out the 3Dfx Voodoo cards but everything newer than that is enough. The problem you are reporting is not uncommon but it turned out to be a driver issue. Try updating to the latest drivers for your graphics card.
thepr wrote:This is what I mean! You need a very good graphics card to play this! It really sucks, though, because people with lower PC's would like to play the game too!
As I said above: this is not true. There are people who play this game with a Riva TNT2. The problem you are having is most likely caused by your driver. I am looking for a way to work around this driver defect but so far I could not reproduce it on any system I have access to.
Re: Running the Game
Posted:
4. October 2008, 18:12
by zerolink
As MassaSnygga and others said, this problem was solved (in my case) by updating the drivers for my nvidia graphic card.
It IS a driver issue.
Thanks to all for the support.
Good luck, and as Neo said: Try the newest driver for your Graphiccard !
Bye.
Re: Running the Game
Posted:
5. October 2008, 08:35
by thepr
Problem solved. I upgraded my graphics card and the game works perfectly! Congratulations to the creator for a remarkable job!