![]() ![]() Possibly related to audio as turning sound off makes the video play smoothly.īugs that occur simply because there's no code in place to make something happen or prevent it from happening. SMK playback stutters and goes in slow motion under DOSBox. The same problem may exist in Witchaven II but the maps there did not use any sprite doors. Witchaven I used some sprite-based rotating doors which could over-rotate into a wall due to clock speed issues. Known cause: animateobjs in WHANI.C handles missile's vertical movement, but fails to adjust it to the game speed.Ĭrashes when throwing pike axes in Witchaven I might be related? Player's deceleration after moving was clock speed dependant. Known cause: dophysics in WHINP.C handles player's vertical movement, but fails to adjust it to the game speed. Jumping/falling speed is dependent on machine speed For workarounds, see the troubleshooting section above. ![]() The faster the system that the game is run on is, the worse these errors become. These are bugs that occur because the game is not correctly adjusting to varying system speeds. It is possible that more functions than are currently documented were broken during the transition of the code to Witchaven II's form. There is currently a significant bias towards information based on the Witchaven II code base, as I have not (yet) dug too deeply into the internal differences between the first game and the sequel. This is a project to seek out the bugs in Witchaven and Witchaven II, and find out whether they are bugs that manifested at the time of release or if they are latent bugs resulting from machine or emulator incompatibility. Witchaven II can be run completely from hard drive by copying the SMK files from the CD to the game folder and running the game with the LOCAL parameter. If this is not the case, it may be that you have patched the game incorrectly, either with a poorly-made "no CD" patch or with two official patches that are not meant to be applied simultaneously. This message normally appears if you have set up the game to use a joystick and you are being asked to calibrate it. If you get an erroneous "center stick press button" message on screen: As with DOSBox cycles, you may have to experiment a bit to find the right balance of smoothness and good behavior.Įither way you run the game, you might also get some beneficial slowdown from switching the game to 640x480 resolution, though it may become a bit choppy as well.īear in mind that the setup program isn't clever enough to unbind a key from one action when you assign it to another, so if it appears that remapping the keys isn't working, make sure the key is assigned to only one function. Bear in mind that you do not want to slow the computer down anywhere near as much as you would for the 1980s DOS games that such utilities are usually used for. Slowdown utilities could help if actions like jumping are still too fast I find that on a 333mhz machine, they're mostly ok. I had more quirks under 64-bit GNU/Linux DOSBox than under 32-bit Windows DOSBox (however, this is based on old tests and may be due to a faulty DOSBox build of some sort). You may experience other issues under DOSBox that are not fixable with the cycles parameter. Although I previously recommended using the Witchaven II intro cinematic as a gauge, a good cycles value for it may make the rest of the game too choppy. You will have to experiment with values to get it right. Playing on a native machine rather than emulation will usually net you better results for the vanilla EXEs the closer to the system the game was developed for, the better.Īdjust cycles lower with a "cycles = #" command on the DOSBox prompt or in your configuration file. EGwhaven attempts to patch these out, although the fix is not quite perfect yet and I do not guarantee exact correctness for time-sensitive functions. The biggest problems you are likely to run into are clock speed issues. I have tried my best to document the game's behavior accurately, but be aware that in some cases I may have misinterpreted the game's source code, or strange bugs in the behavior may manifest that I haven't caught. Here you can find some troubleshooting tips and a catalog of observed bugs, with their causes if known. The Witchaven games are notoriously buggy. ![]() Witchaven and Witchaven II - Bugs and idiosyncracies
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |