 |
I've confirmed that moveable_base_brick is fine in TDM (big ugly black boxes appear in both editors, and serve no useful purpose, but that's beside the point and possibly due to defs, I don't know). I guess this confirms that the problem is in fact within DR. Edit: Furthermore, if I change (in notepad) all of the moveable_base_bricks in the map to func_statics, then DR loads it fine, and shows all of the brush information properly. DR definitely does not like whatever is different about that class type or its path or folder or... As soon as I change (in DR) the func_static back into moveable_base_brick, the brush disappears. I hope/assume this makes determination easier. Another edit! Further discovery: If I change one of the func_statics back to moveable_base_brick, using the classname browser to search for "doom 3 junk/moveable_base_brick", the entity breaks in DR (as seen in this entry). If, however, I change it to a moveable_base_brick by *typing that name into the classname field*, it works! So it seems for the second part of this at least (the renaming from within the editor), the classname browser is at fault. One more edit: the above is true, UNTIL I reload the map in DR again. Now, my properly working moveable_base_brick is in fact broken again. ?! I'm trying to determine what's going on with diffs. |
|
|
Okay let me summarize what I've just done, to get away from the confusing garble above. 1. took the working brick map (fromDE) and made three copies of it. 2. for copy 1, I changed the bricks to func_static, and confirmed that it worked. 3. for copy 2, I changed the bricks back to moveable_base_brick via the classname browser. This broke them in DR immediately, and in TDM, they don't work. 4. for copy 3, I changed (func_statics) back to moveable_base_brick by typing the name into the classname field, NOT browsing. This did not break them in DR (yet), and upon saving this out, it worked in TDM! 5. however, when I reload copy 3 in DR, the bricks are back at square one, broken in DR. If I save this out, they don't work in TDM. SO. It appears from the outside that the following things are happening: 1. DR doesn't like that entity's (and all others like it in whatever way) path or definition or something else. As a result it doesn't display/handle the brush properly on load. 2. DR also does not save this entity properly (obviously it cannot if it's broken on load or change). 3. The classname browser applies changes immediately, while typing in new classnames does not. They act differently, at least, that's for sure. Furthermore, as seen in 3 and 4 above, the classname browser is doing something (destroying/modifying, "primitive" -> "dummy") to the brush info for an entity it doesn't handle. I think that's it? It appears that definition changes to moveable_base_brick during reorg merely exposed this problem. It is highly recommended that whatever is wrong with moveable_base_brick definition NOT be fixed until after this problem is addressed in DR, otherwise there will be no means to verify the fix is successful and thus safe to use. |
 |
Ok, thanks for putting so much effort in narrowing this down. I'll look into it sometime, but I can't make any promises at this point. |
- Anonymous
