q3map2 error (First I've ever gotten like this. Ydnar!)

(Matt) #1

In the light process, it gives a little crash window, (You know, q3map2.exe has encountered a problem and needs to close. We are sorry for the invonvenience.)

When I clicked for more info, it says these things…

AppName: q3map2.exe
AppVer: 0.0.0.0
ModName: ntdll.dll
ModVer: 5.1.2600.0
Offset: 000036f7

I am using WindowsXP Pro on an AthlonXP cpu, with v2.3.38.

This only occurs when I use -samples instead of -super.

I’m assuming (from my limited knowledge of programming errors) that the actual thing that had a problem was ntdll.dll, and the ‘000036f7’ number is something to do with either ram, or a location in the ntdll.dll.

(Matt) #2

Here are my .bat settings.


-light -fast -fastgrid -filter -patchshadows -area 1.5 -bounce 3 -point 1.5 -samples 3 "path	o\map"

p.s. Ignoring the -area, -bounce, and -point variables, are those the highest quality settings I could use for a final -light? What would you recommend for the highest level of detail and quality?

(Matt) #3

WAIT

SCRATCH THAT, it happens with -super 2 as well. I guess it’s going to happen all the time.

What the hell.

(Matt) #4

It happens at this point:

--- Radiosity (bounce 1 of 3) ---
--- StoreSurfaceLightmaps ---
   806981 luxels used
   835584 luxels stored (96.58% efficiency)
     1156 identical surface lightmaps, using 39413 luxels
        0 vertex forced surfaces
        0 vertex approximated surfaces
       51 BSP lightmaps
       51 total lightmaps
      316 unique lightmap/shader combinations
Writing C:\Program Files\Quake\Quake 3\baseq3\maps	heend.bsp
0...

And then it crashes.

(Matt) #5

Still no answer…

It only happens with 2.3.38. I’ve been trying to download 2.3.37, but shaderlab is really slow right now.

It happens with all maps, and only with 2.3.38. I tried with 2.3.33, and everything went smoothly, however before I send it out to it’s fate, I’d like to compile the map with the latest stuff.

(ydnar) #6

Odd, sounds like you have a crash in the radiosity code.

A new build should be along soon.

y

(Matt) #7

I really… REALLY love q3map2, but when push comes to shove, I hope it is q3map2 that is screwed up and not ntdll.dll, because it’s near impossible for me to format and install Windows.NET, with the .4TB of data I have sitting on these disks.

I’ll tell you one thing odd. It worked since you released 2.3.38 (I make it a point to get it the second the new ones come out) and I probably built the map 20 times, checking things, all with the same settings, and just now it started this. :???:

(neotic) #8

my q3map2 is crashing just today when i run lighting (12/2/03) just after cleaning out a simple virus last night from my computer… not sure if its related. i can run bsp, and im not using any special extentsion to the command other than light -faster. it occurs right here after a hang

— LoadMapFile —
Loading C:/Games/Quake3/baseq3/maps/sad.map
entering C:/Games/Quake3/baseq3/maps/sad.map
Connection closed.

Athalon AMD w/ Win XP Pro. I’d had been using q3map2 fine for months… dont know what changed.

(ydnar) #9

What version?

(Matt) #10

lol, something from February being bumped. :stuck_out_tongue:

I read the post and wondered when the hell it was, because I said I was still using XP before SP1, and wasn’t on AMD64 yet. :slight_smile: