View Issue Details

IDProjectCategoryView StatusLast Update
0002150DarkRadiantMap Editingpublic29.09.2010 06:59
Reporterdowner Assigned Togreebo  
Status closedResolutionfixed 
Product Version1.1.0 
Target Version1.2.0Fixed in Version1.2.0 
Summary0002150: Negative zero changes between maps
DescriptionI've been messing around with a way to find brushes that are not snapped grid. If I diff between an autosaved map that has vertexes snapped to grid, and a regular saved map that has the brushes snapped to grid, the diff will show which brushes have moved, and so which ones cause errors.

I guess the trivial issue is, before I can diff between an autosave map and a normally saved map, I have to find and replace all "-0 " with "0 " every time. It seems like a small thing, but maybe this is one step closer to someone writing a plug-in for finding corrupted brushes in the editor --like Half-Life's Hammer has. Maybe it would be easier to just make "-0 " consistent, than just remove it, but it seems weird to even have that.
Additional InformationYes, this sounds like a strange request, but my map is pretty big, and its next to impossible to always inspect every brush for when *Radiant might silently "help" and move unselected vertexes.

Thanks, that great speed-up of exiting after vertex snapping definitely helps!
TagsNo tags attached.


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
22.02.2010 17:03 downer New Issue
05.03.2010 16:14 greebo Status new => acknowledged
05.03.2010 17:02 greebo Status acknowledged => assigned
05.03.2010 17:02 greebo Assigned To => greebo
05.03.2010 17:02 greebo Status assigned => resolved
05.03.2010 17:02 greebo Fixed in Version => 1.2.0
05.03.2010 17:02 greebo Resolution open => fixed
05.03.2010 17:02 greebo Target Version => 1.2.0
29.09.2010 06:59 greebo Status resolved => closed