This article was converted from a previous version of TWHL and may need to be reviewed
- The formatting may be incorrect due to differences in the WikiCode processing engine, it needs to be revised and reformatted
- Some information may be out of date
- After the article is re-formatted and updated, remove this notice and the Review Required category.
- Some older articles are no longer useful, or they duplicate information from other pages. In this case, delete the page after merging any relevant information into other pages. Contact an admin to delete a page.
The new Hammer Editor 3.4 is a bit buggy and glitchy. It especially seems to have problems with Geoforce Video cards, Windows XP and Voodoo Video cards.
Possible solutions: Right now, there are three known solutions that may or may not work for you:
- Using SGI's OpenGL driver (438,888 bytes) instead of your video card's native OpenGL drivers. Extract the file named opengl32.dll to your WorldCraft/Hammer directory.
- Upgrading your video drivers to the latest version. Check out: nVidia's driver page.
- Downgrading your video drivers to a prior version, the most recent driver may not be as stable as older versions.
There may also be problems converting your old WorldCraft 3.3 maps to Hammer 3.4, the best solution for this is to open your old level in WorldCraft 3.3, copy EVERYTHING, then open Hammer, start a new map and paste it all in.
There have also been problems with longer map names in Hammer, especially with compiling. Like WorldCraft, you should compile outside of Hammer with a batch file or front end. And there are more minor problems.
If you have problems with Hammer forgetting your settings so you have to set it up every time, this happens to some CPUs. Your operating system may be causing it, or something else. The fixes I have heard of are:
- Using an older version or different of Windows.
- Try to always use a User Profile.
- Make changes to the WAD files installed, then save.
- Change the save maps folder to a sub folder deeper down.
- Try to configure Hammer and then create and save any map, even a single wall will do, you can exit the program and load again and your configuration files will load. If they don't however you
can do the process again and it normally works the second time - sometimes.
- Search your HDDs for files named *.wc. If you find them outside of your Hammer folder move them into your Hammer folder. (Do this while Hammer is not running.) Things should work properly after doing this.
- Installing Hammer into a path with no spaces (ie: X:\Hammer)
- Moving everything to the default path in C:\Programs\Valve Hammer Editor... conflicts with the one above.
- In one case where hammer would not
reinstall right, it was found you had to hand remove from the
registry (
HKEY_CURRENT_USER\Software\Valve\Hammer) before reinstalling.