Wheel of Time Quick Troubleshooting FAQ

Update 09/2008: I made a pass through the entire text to remove all deprecated links and provide alternatives where possible.

Update 07/2008: A lot of the links in this FAQ are now outdated. Proceed with caution!

Update 02/2004: Wow, this FAQ still gets ~400 unique hits per month. If you came here from the official WheelOfTime page, please note that this FAQ is in no way affiliated with Atari. It was a personal project back in 99 that I did after we had finished the game. Feel free to explore the rest of my page for more information. BTW, Legend Entertainment was shut down by Atari earlier this year.

Wheel of Time Troubleshooting FAQ

Maintained by Matthias Worch
Updated 02/11/01 (final update)

Contents

1. About this FAQ
2. Walkthrough/Tip and Tricks
3. Where can I still buy Wheel of Time?
4. Available Patches and other official Legend releases
5. Installation and Game Crashes
   • Windows 2000
     
   • Installation Problems
     
   • Problems loading the game
     
   • Problems with the copy protection
     
   • Reporting Bugs
     
6. Video Issues
   • D3D Performance
     
   • Glide Issues
     
7. Movie Issues
8. Multiplayer Issues
   • Server Problems
     
   • Client Problems
     
9. Editor Problems

1. About this FAQ
   This FAQ covers most problems asked in the Wheel of Time forum. It is NOT complete – for additional information please go to the release notes and the GT FAQ and see if your problem is covered there.
    
2. Walkthrough/Tip and Tricks
   There’s an extensive walkthrough of the SP campaign one the Clan FUBAR page. It includes screenshots. Another walkthrough is available on GameFAQs.com.
   If you are looking for multiplayer and Citadel hints please refer to my Citadel guide.
    
3. Where can I still buy Wheel of Time?
   CompuExpert is still selling the game as the game for only $9.99, just search their PC section for “Wheel of Time”. At this point, Amazon.com might be your best bet.
    
4. Available Patches and other official Legend releases
   The current version of Wheel of Time is 333.310. To update your 300.250 (retail) version to 333.310 please download the following patch:
   • If you own the US version of WoT please download the US 333b patch.
   • If you own the German version of WoT please download the German 333b patch.
   • If you own the French/Spanish/Italian/English (not US!) version of WoT please download the international 333b patch.

   Please note that the last two patches are considered beta – they have been throughoutly tested by us, but please use them at your own risk.

   We have also released a NEW D3D patch with the latest D3D enhancements that were inplemented after the release of the 333b patch. You can download it here. This patch should work with ALL versions of WoT.

   Additonally Legend has released two new Arena maps and THUMB, a tool to easily remap your Angreal keys. Please refer to the WoT.com download page for more information.

5. Installation and Game Crashes
   
   
   Windows 2000

   Windows 2000 is NOT officially supported, but most people have been able to get Wheel of Time running without problems on Win2k machines. If WoT crashes on startup the copyprotection is probably to blame and you might have success with a no-CD crack that removes the protection. Unfortunately we are not allowed to provide the location of such a crack, you’re on your own there :]

   Installation problems

   • Problem: The setup program stops installing when it reaches the file ‘Mission_10.wot’.
     Solution: You probably have a bad CD. Return your box to the store and get a new CD.
      
   • Problem: There are two identical CDs in the box.
     Solution: There have been some isolated cases where one box contained two CD1s or two CD2s. If you got a box like this take it back to the store and get a new copy that contains a CD1 and CD2.

   Game Crashes

   If your game crashes please open the file ‘wot.log’ in the ‘system’ directory and scroll to the bottom. You will find a batch of Critical messages which describe the nature of the problem.

   • Problem: The game crashes after the intro movies with an error that reads Critical: FString::Parse.
     Solution: This error indicates that something deep inside your Windows installation got corrupted. The only known solution to get WoT to work is to reinstall Windows (which would be a good idea, anyway). We’re working on a solution that doesn’t require a reinstallation of Windows.
      
   • Problem: The game freezes as soon as the movies start playing/while the the movies are playing
     Solution: Please refer to the Movies section of this FAQ.
     
     
     Problem: The game crashes in Mission_08 (The Ways) when I am trying to enter the Shadar Logoth pocket.
      
   • Solution: This is a rare bug that happens if you save and load the level very often. Right now only a workaround is available: Before entering the waygate to Shadar Logoth enter the console (‘Tab’) and type the following commands killall machinshin (enter), ghost (enter). Now fly through the waygate to the other side. Open the console again and type walk (enter). Save your game. Everything should work fine now.

   Problems with the copy protection

   • Problem: When I start the game I get the message that CD2 is not in the drive, although it is.
     Solution: A few CDROMs are having problems with the copy protection that WoT uses. If you’re using a TEAC CDROM you will need to download and install the latest firmware for the device at this adress.

   Reporting Bugs

   We feel like we have a good handle on which bugs exist in the game and what needs to be fixed. Please to not email us directly. If you want to report bugs in an official forum (the message board on www.wheeloftime.com for example) please do the following: If you’re reporting a crash take a look at the ‘wot.log’ file and post the Critical messages with your problem. If you’re having other problems make sure to post your system specs.

6. Video Issues

   Direct3D Problems

   • Problem: The D3D rendering is slow.
     Solution: There are several things that you can do to improve your D3D performance: 
     1. Install the 333b patch.
     2. Download the latest D3D(2) patch.
     3. Install the latest drivers for your video card. Here are the links to the latest drivers for popular cards:
        • NVidia Detonator drivers (TNT/TNT2/GeForce)
        • Matrox G400 drivers
        • ATI Rage 128 drivers
        • S3 Savage 4 drivers
     4. Play the game in 16bit mode. To do this you have to set the Windows desktop to 16bit (“high color”) mode.
     5. Disable Detail Textures in the Hardware menu.
     6. Disable Volumetric Lighting in the Hardware menu.
     7. Defrag your harddrive. This will help especially when you got a system with 96 or less MB of RAM.
     8. Don’t run any applications like virus scanners, ICQ etc. in the background while you’re playing. These programs can take up large amounts of RAM that WoT needs.

   • The following tips might or might not work for you, depending on your system configuration. Use them at your own risk.
     Open the Advanced Options to change the following settings:

     1. If you are using a Creative TNT2 Ultra try this: Start the ‘Creative Launcher’, select Blaster Control Properties/Tweak/Advanced. Set the Texture Cache Size to 0.
     2. Go to Advanced/Game Engine Settings and increase the value for CacheSizeMegs.
     3. If you’re using an ATI Rage 128, go to Rendering/Direct3D Support and set UseTrippleBuffering to “False”.
         
   • Problem: I can’t switch to 16/32bit in-game.
     Solution: WoT uses the bit depth that your desktop is set to as in-game color depth. To affect the game you have to change the Windows desktop to 16 or 32bit.
      
   • Problem: The 3D view looks grainy and washed out.
     Solution: You’re probably playing the game in 16bit mode. 16bit D3D mode is faster, but looks worse than 32bit.

   Glide Problems

   • Problem: The game gives me an error that reads Mutual exclusion prohibits this when I try to start the game.
     Solution: This is usually a sign that another application is already using the Voodoo card. Only one Glide program can be run at a time. If you don’t have any other programs open that could be using your Voodoo board your drivers might have gotten corrupted. Try reinstalling the Glide drivers.
      
7. Movie Issues

   Almost all problems encountered that have to do with movies freezing or playing incorrectly are caused by an outdated install of Quicktime 4.0. If you’re having problems with movies your first action should be to completly uninstall QT, reboot the computer and reinstall QT4.0 from the WoT CD1. This will probably help fixing the problem.

   • Problem: The game freezes when the Movies are playing.
     Solution:     
     1. You might have accidently hit the Space bar. Space pauses the videos, press it again to continue.
     2. If you’re connected to the internet your version of Quicktime might try to automatically update QT. Use Alt-Tab to switch out of the game and see if an “Update” dialog has popped up in the background. Do not try to update QT like this. Uninstall it and reinstall from the WoT CD.
         
   • Problem: Movies run slow, have stuttering or no sound.
     Solution: Try setting your desktop to 16bit. If you have a 64MB system make sure that no applications in the background are using any extra RAM. If this doesn’t help try installing the movies to your HD. Run the setup program on CD2 to do this.
      
   • Problem: I installed the 333b patch, and now the cutscenes aren’t playing anymore!
     Solution:Your MoviePath might have be overwritten. Insert the second WoT CD, right click on the icon and ‘Explore’ the CD. Run Setup.exe and install the movies to your HD. You can also manually change the .ini setting: open the file wot.ini in the ../WheelOfTime/System directory and find the line that starts with ‘Moviepath’:     

     1. If you installed the movies on your HD change it to ‘MoviePath=../Movies’
     2. If you did not install the movies change the line to ‘MoviePath=X:/Movies’ (where X is the letter of your CDROM drive.
         
   • Problem: The system crashes when playing a movie AND I’m using a Matrox G400.
     Solution: The latest G400 drivers have a known problem with Quicktime and desktops running in 16bit. Please read the release notes on the Matrox page and follow the directions provided.
      
8. Multiplayer Issues

   Servers Problems

   • Problem: I can’t create a server using the in-game menus!
     Solution: You will not be able to start an MP server this way without applying the server patch first!
   • Problem: I can’t run a server without CD2 in the drive.
     Solution: You can start dedicated servers from the command line:

     ucc server Arena_01.wot?game=WoT.giMPArena (ini=Arena.ini log=Arena.log)
     ucc server Battle2_01.wot?game=WoT.giMPBattle (ini=Battle.ini log=Battle.log)

     If you don’t specify an .ini file the server will use whatever settings were set in the game’s Multiplayer menu. If you want to use a different .ini file make a copy of the file wot.ini, open it with a text editor and make the changes manually.

   • Problem: I can’t set up a “listen” server / I want to run a server and client on the same machine.
     Solution: WoT does not support listen servers, but you can run a server and a client on the same machine (although it is not recommended). When setting up the server use the Max Client Framerate setting to specify how much of the CPU power the server is allowed to use. If you leave it at 0 the client will claim all the processing power, making the server very slow.
      
   • Problem: My server is very slow.
     Solution: WoT generates a lot more network traffic than conventional DM games due to all the seeking missiles etc. A server should have enough processing power to handle bigger games. A P2-266 will host up to 4 players comfortably, for more players you’ll want a bigger system.

   Client Problems

   • Problem: Ping times are very high.
     Solution: As already mentioned WoT needs to create more network traffic than conventional DM games to be able to handle all the seeking projectiles, counterspells etc. This results in higher ping times, especially if the server can’t handle the amount of players that have joined. If a game becomes unplayably slow try joining another server and see if your ping gets better. Also check the next tip to see if you should change your netspeed.
      
   • Problem: The menus are missing an option to set my netspeed.
     Solution: You’ll have to do this through the console: “netspeed xxxx“. 2600 is the default and recommended for modem users, 5000 for ISDN and 10000 for DSL/T1.
      
   • Problem: The server browser gives me the messages “”Unable to resolve Master.Gamespy.Net” (or something similar) and no servers show up in the browser..
     Solution: Try hitting F5 to refresh the list.

      

9. Editor Problems

   As stated in the setup program, the Wheel of Time editor (“WotEd”) is neither supported by GT nor Legend. But there are a lot of helpful pages on the net that can help you to get the program running and to give you help understanding the editor. Please note that none of these pages are affiliated with Legend or GT.

   • Problem: The editor won’t load because of missing files.
     Solution: Go to the this help page on ShadarLogoth.com and download the fix.
      
   • Problem: I need help understanding the editor.
     Solution: ShadarLogoth.com has this tutorial page for WotEd.