Problems with a new build of map2dif
by Stefan Brink · in Artist Corner · 08/24/2004 (11:56 am) · 6 replies
Hi
I have Problems using the latest build of map2dif. I am using Hammer and i am compiling a quite large map. During the compile process map2dif only gives me the standard errors : orphaned polygons and 1 ambigous brushes. when i try to load my map into torque it doesnt load the interior. trying to add the interior by adding it with the editor creator doesnt work aswell. console.log only says couldnt load X.dif . However an old version of map2dif (i dont know the date but its 1.020kb big) compiles everything aswell and the dif also loads into torque without a problem. But only using the old map2dif isnt very good aswell as it sometimes moves vertexes. So When 2 Vertexes of 2 Brushes are at the same position in Hammer, they sometimes arent in Torque...
Any ideas why the new version doesnt seem to work for me?
thx for your help Stefan
I have Problems using the latest build of map2dif. I am using Hammer and i am compiling a quite large map. During the compile process map2dif only gives me the standard errors : orphaned polygons and 1 ambigous brushes. when i try to load my map into torque it doesnt load the interior. trying to add the interior by adding it with the editor creator doesnt work aswell. console.log only says couldnt load X.dif . However an old version of map2dif (i dont know the date but its 1.020kb big) compiles everything aswell and the dif also loads into torque without a problem. But only using the old map2dif isnt very good aswell as it sometimes moves vertexes. So When 2 Vertexes of 2 Brushes are at the same position in Hammer, they sometimes arent in Torque...
Any ideas why the new version doesnt seem to work for me?
thx for your help Stefan
#2
www.modernwarfare.net/vertexerror.jpg
map2dif really doesnt seem to like these sloped walls :(
08/24/2004 (12:14 pm)
Mmh that version produces the same vertex errors as the version i usedwww.modernwarfare.net/vertexerror.jpg
map2dif really doesnt seem to like these sloped walls :(
#3
08/24/2004 (12:41 pm)
Make sure you have floating point output enabled
#4
08/24/2004 (4:31 pm)
Where can i activate that?
#6
UNcheck "don't write floating-point coords"
09/01/2004 (2:15 pm)
Quark configuration window -> Maps -> OptionsUNcheck "don't write floating-point coords"
Associate Matt Fairfax
PopCap