Game Development Community

Strange errors from map2dif...

by David Massey · in Torque Game Engine · 08/09/2001 (9:12 pm) · 11 replies

Heya... While trying to get several worldcraft maps into .dif format for v12, I've run into a lil problem. Every map I try to compile with map2dif gives me the same errors. I've tried basic cubes and some more advanced maps, even the examples included in the sdk. And they all give me these types of errors:

(this is all I can see from dos prompt...)

+portal: 0
-zones: 1
-number of surfaces:372

warnig warning warning
Errors in this interior. Please use the debug rendering modes to find and correct the following problems:
Ambiguous brushes: 0
Orphaned Polygons: 24

exporting to runtime...done.
writing resource: persist..(fkeep.map/fkeep.dif)

Then this error bos pops up:
Unable to write detail level to stream

There is no .dif created...

I've configured worldcraft (v3.3) with the fgd from the v12 sdk, and tried several ways to adjust its settings (include the detail index number..) Im baffled... Any help you can offer would be greatly appreciated...

#1
08/09/2001 (10:33 pm)
Very wierd... I think orphaned polys are ones that map2dif thinks are not visible to anything in the world. Can't think of much off hand that would cause this problem with a simple cube... in fact one of the examples with the test app is a cube. Maybe your textures scale factor is really high? You might try comparing your .map cube with the example cube .map file to see what's different.

You also might try processing one of the existing maps and make sure everything is running :)
#2
08/09/2001 (10:47 pm)
Are all of you polys textured?
#3
08/10/2001 (12:52 am)
I opened up the cube example and pyramid1 and also got the warnings. It does however write out the dif files. Now if I only knew what to do with those now that I have them.

-Mark
#4
08/10/2001 (1:46 am)
I just verified. They can safely be ignored for now. I was able to get it to work (check a post coming soon in the discussions forum). Still would like an explanation about the warnings and what they mean though.

-Mark
#5
08/10/2001 (8:27 am)
So would I :) If I get time, I'll look through the source a little, but since a number of other people have the source now as well, maybe someone will beat me too it...
#6
08/10/2001 (12:00 pm)
Hmmm...I have been trying to remember when I first got those warnings and what I did to fix it...

If I remember corretly, I was getting those erros when I had more than one wad file spcified in Worldcraft. Is this the case with you?
#7
08/10/2001 (2:05 pm)
What is the difference between Worldcraft v3.3 and 2.1. Could that be producing some problems? What version of WC was map2dif developed against?
#8
08/10/2001 (2:37 pm)
You should be using WorldCraft 3.3, I have no idea if it works with earlier versions.
#9
08/10/2001 (4:08 pm)
Hmm... Originaly, I was using multiple wad files, but saw a warning agaisnt that so I switched to one wad file. All the brushes have valid textures. The only thing mentioned that I have no idea on is the texture scale. The v12 fgd doesnt have anyplace to set the texture scale (that I've seen anyway). I've used worldcraft quite a bit (for quake2, tribes1, and my own engine) I know the quake2 fgd has a texture scale property under map/properties... where do you set it for v12? Also, I get the exact same warnings/results (ie: no dif file created) when I try to compile any of the .map files in the example dir of the sdk. I'm running map2dif from the dos prompt in a directory outside of the v12 sdk, passing the directory that my textures are located in with the -t parameter. The textures are all in .jpg format, and I've tried just using the textures from the evil1 directory as well. Welp, thanks for checking into this... Im going to go set worldcraft up to compile the map files inside worldcraft and see what results that gives... 'till next time...
#10
08/10/2001 (4:32 pm)
Doh! Allrighty, I found out why it wasnt making the .dif file... since I'm running map2dif from the dos prompt (old timer that I am...) I needed to specify the output directory with the -o parameter... I figured it would default to the current directory, but nope. Anyway, I'm still getting the same warning messages, but it is making the .dif file... Now to see how it turned out... peace out...
#11
08/10/2001 (4:43 pm)
Woohoo! It's a-working perfecto... Thanks for the input fellas...