Posted December 17, 2011
In Daventry, when I got the axe in the windmill I go outside, a cut scene occurs and then the game just stop's, I doesn't hang or anything just stops, can anybody help?
Water1111
New User
Registered: Oct 2009
From Namibia
Entropy.971
New User
Registered: Sep 2008
From United States
Posted January 02, 2012
First Person mode also helps a lot in the underworld levels, as you can then see the skeletons before they see you. Use the bow. If you are having difficulty with the game, check a walkthrough.
PS. If you use a glide emulator, you can run the game in hi-res.
iondrive
New User
Registered: Mar 2011
From United States
Posted February 06, 2012
Hi Water,
This bug bugged me (no pun intended) and I wanted to tackle it since I saw that I could get a logfile and open .cs files with a text editor. Here's the fix:
Edit AX.CS:
The file you want to edit is AX.CS and it should be in KQ8\Daventry\kq. Open it with a text editor and go to the bottom. Look for the numbers "1000 3 0 6 4" and change that last number from a 4 to a 1. That's it. Save and run the game. I've been testing with winXP on a geforce 7800GTX with drivers 162.50 so I can only vouch for that setup but I feel confident it will work for others but I still have to say "try at own risk". I was using direct3d mode and it works with all shadows on/off and doesn't matter if you enter the cutscene in 1st or 3rd person view but I recommend 1st person view since the cutscene ends better that way. It shouldn't matter if your axe is in hand or not. If not then he draws it automatically in the cutscene.
For a deeper understanding:
Study that AX.CS file along with the logfile (Mask.log) from a run when the game crashes comparing it to another logfile from when the game doesn't crash. My fix makes that last part of the script run sooner and that seems to fix things. It hands control back to the user even before the cutscene is done. I don't have supreme knowledge here so it's possible this fix might cause a new bug but I don't think so. Looks like the key is the "handsOff 0" line that probably returns keyboard control to the player. Maybe someone smarter than me can come up with a better fix but anyway, you can enable logfile generation by editing Console.CS and commenting out the last "if" and "endif" statements.
Water, if you can change the name of this thread, please do. Try editing your top post and changing the topic to "axe cutscene control freeze fix" or something like that so that others can recognize it easier as what they are looking for. Thanks.
To all future users of this fix, you're welcome. Maybe something similar can be done with other parts of the game but I don't plan on working on it anytime soon. Maybe someone else will work on it now that they know about the logfile and editing .CS files.
Later all and happy adventuring
--- iondrive ---
This bug bugged me (no pun intended) and I wanted to tackle it since I saw that I could get a logfile and open .cs files with a text editor. Here's the fix:
Edit AX.CS:
The file you want to edit is AX.CS and it should be in KQ8\Daventry\kq. Open it with a text editor and go to the bottom. Look for the numbers "1000 3 0 6 4" and change that last number from a 4 to a 1. That's it. Save and run the game. I've been testing with winXP on a geforce 7800GTX with drivers 162.50 so I can only vouch for that setup but I feel confident it will work for others but I still have to say "try at own risk". I was using direct3d mode and it works with all shadows on/off and doesn't matter if you enter the cutscene in 1st or 3rd person view but I recommend 1st person view since the cutscene ends better that way. It shouldn't matter if your axe is in hand or not. If not then he draws it automatically in the cutscene.
For a deeper understanding:
Study that AX.CS file along with the logfile (Mask.log) from a run when the game crashes comparing it to another logfile from when the game doesn't crash. My fix makes that last part of the script run sooner and that seems to fix things. It hands control back to the user even before the cutscene is done. I don't have supreme knowledge here so it's possible this fix might cause a new bug but I don't think so. Looks like the key is the "handsOff 0" line that probably returns keyboard control to the player. Maybe someone smarter than me can come up with a better fix but anyway, you can enable logfile generation by editing Console.CS and commenting out the last "if" and "endif" statements.
Water, if you can change the name of this thread, please do. Try editing your top post and changing the topic to "axe cutscene control freeze fix" or something like that so that others can recognize it easier as what they are looking for. Thanks.
To all future users of this fix, you're welcome. Maybe something similar can be done with other parts of the game but I don't plan on working on it anytime soon. Maybe someone else will work on it now that they know about the logfile and editing .CS files.
Later all and happy adventuring
--- iondrive ---
Post edited February 29, 2012 by iondrive
kazmajik
New User
Registered: Sep 2011
From United States
Posted November 10, 2012
This bug bugged me (no pun intended) and I wanted to tackle it since I saw that I could get a logfile and open .cs files with a text editor. Here's the fix:
Edit AX.CS:
The file you want to edit is AX.CS and it should be in KQ8\Daventry\kq. Open it with a text editor and go to the bottom. Look for the numbers "1000 3 0 6 4" and change that last number from a 4 to a 1. That's it. Save and run the game. I've been testing with winXP on a geforce 7800GTX with drivers 162.50 so I can only vouch for that setup but I feel confident it will work for others but I still have to say "try at own risk". I was using direct3d mode and it works with all shadows on/off and doesn't matter if you enter the cutscene in 1st or 3rd person view but I recommend 1st person view since the cutscene ends better that way. It shouldn't matter if your axe is in hand or not. If not then he draws it automatically in the cutscene.
For a deeper understanding:
Study that AX.CS file along with the logfile (Mask.log) from a run when the game crashes comparing it to another logfile from when the game doesn't crash. My fix makes that last part of the script run sooner and that seems to fix things. It hands control back to the user even before the cutscene is done. I don't have supreme knowledge here so it's possible this fix might cause a new bug but I don't think so. Looks like the key is the "handsOff 0" line that probably returns keyboard control to the player. Maybe someone smarter than me can come up with a better fix but anyway, you can enable logfile generation by editing Console.CS and commenting out the last "if" and "endif" statements.
Water, if you can change the name of this thread, please do. Try editing your top post and changing the topic to "axe cutscene control freeze fix" or something like that so that others can recognize it easier as what they are looking for. Thanks.
To all future users of this fix, you're welcome. Maybe something similar can be done with other parts of the game but I don't plan on working on it anytime soon. Maybe someone else will work on it now that they know about the logfile and editing .CS files.
Later all and happy adventuring
--- iondrive ---