Tweet
As stated in this thread referred to by this page, if you install Quake and Worldcraft 3.3 with QuakeAdapter1 on different drives under Windows, building/running maps doesn't work.
I installed Quake via Steam which places my games on D: whether I want it or not, and I really like to keep applications on C:, but after a bit of digging I came up with a different solution that works fine for me, at least. All I really needed to do was the following:
- In Worldcraft, select File => Run (or press F9)
- If you're not already in expert mode, click the Expert button
- In the list on the left, click the line at the top saying "Change Directory $exedir" (don't uncheck it, just select it)
- Click "Move Down" until it goes between the "Copy File" command and the "$game_exe" command (i.e. second last in the list).
- Click "Go!".
Now, this essentially leaves the working directory unset at the beginning of the script and delays setting it until just before the game is run. I'm assuming that this works because the default working directory is the Worldcraft directory. But if you still get texture-less maps even after the above fix you might try adding another "Change Directory" command at the top that forces the working directory to the same drive as Worldcraft.
The actual cause of this problem appears to be that the worldspawn entity in the generated .map file contains a "wad" entry where the drive letter is stripped off. If a drive letter is manually added at the beginning of the wad path, then the rest of the build process works fine.
I installed Quake via Steam which places my games on D: whether I want it or not, and I really like to keep applications on C:, but after a bit of digging I came up with a different solution that works fine for me, at least. All I really needed to do was the following:
- In Worldcraft, select File => Run (or press F9)
- If you're not already in expert mode, click the Expert button
- In the list on the left, click the line at the top saying "Change Directory $exedir" (don't uncheck it, just select it)
- Click "Move Down" until it goes between the "Copy File" command and the "$game_exe" command (i.e. second last in the list).
- Click "Go!".
Now, this essentially leaves the working directory unset at the beginning of the script and delays setting it until just before the game is run. I'm assuming that this works because the default working directory is the Worldcraft directory. But if you still get texture-less maps even after the above fix you might try adding another "Change Directory" command at the top that forces the working directory to the same drive as Worldcraft.
The actual cause of this problem appears to be that the worldspawn entity in the generated .map file contains a "wad" entry where the drive letter is stripped off. If a drive letter is manually added at the beginning of the wad path, then the rest of the build process works fine.