 |
If you rename it back to its original name afterwards it works again. |
|
|
This problem applies to trigger_entityname, trigger_once_entityname, trigger_once and trigger_multiple. |
 |
This isn't a problem. Dmap sometimes doesn't overwrite an existing *.cm file. This is not likely to get fixed, since the workaround is simply to delete the old *.cm file and let dmap make a new one. The *.cm file created by dmap includes collision model info. The first time you dmapped, it saved the initial entity name in the *.cm file. When you changed the entity name and then re-dmapped, and dmap didn't overwrite *.cm, TDM tried to find the renamed collision model in *.cm, couldn't find it, and ended up doing nothing. It basically stopped recognizing the trigger. When odd things like this happen, you can try deleting the *.proc, *.cm, and *.aas* files before dmapping to see if that fixes the problem. -------------------- This same problem can cause another odd effect: if you change the material on a brush, then re-dmap, the brush might behave like it has the old material on it. (I.e. try firing arrows at a wood wall, change the texture to metal, and try arrows again. Sometimes they'll stick. Fixed by deleting dmap's product files and re-dmapping.) |
|
|
I tested it and you are right. So "not a problem". But I would suggest that sometimes the dmapping method is changed in a way that it deletes the cm, proc and aas files at the beginning to avoid such things. |
- Anonymous
