ok, next step :)
It seems that rendering a doom3 map is a little more complicated as a rendering Q3 map...
With the editor I can verify that the brushes are a set of planes. And I agree with LogicalError that the next thing is a 2x3 matrix. I think it is for translating the worldspace coordinates in texture coordinates.
The planes in the brush define a volume, so our vertices are the intersections of three planes.
Bye,
Oesi
Edit: typo
Doom 3 .map question
The .map file holds the brush and patch descriptions and the entities. This file is compiled during the dmap process into a .proc and a .cm file. The .proc file contains informations to render the map and the .cm file contains information for collision detection.
Brushes are described by a plane (the first 4 numbers) and two points. This representation of a brush saves a lot of disk space for big maps.
Brushes are described by a plane (the first 4 numbers) and two points. This representation of a brush saves a lot of disk space for big maps.
The brush consists of 6 planes which are described by each line in the brushDef. Just to to clarify my last post... :)
hmm...I'm quite shure that it's a 2x3 Matrix and not just "2 points".
I made a simple cube with a texture on it and for every plane it was the same matrix. So if it were points they wouldn't even lay in the plane...
Bye,
Oesi
I made a simple cube with a texture on it and for every plane it was the same matrix. So if it were points they wouldn't even lay in the plane...
Bye,
Oesi
Right, they are the S and T texture vectors. I've read that with the two points on some other forum or so and didn't take a deeper look into it. It's obvious, because where else should the texture alignment be saved, doh!
>>It seems that rendering a doom3 map is a little more complicated as a rendering Q3 map...
With the editor I can verify that the brushes are a set of planes. And I agree with LogicalError that the next thing is a 2x3 matrix. I think it is for translating the worldspace coordinates i<<
does doom3 come with a world editor with it?
+ is it any good?
With the editor I can verify that the brushes are a set of planes. And I agree with LogicalError that the next thing is a 2x3 matrix. I think it is for translating the worldspace coordinates i<<
does doom3 come with a world editor with it?
+ is it any good?
Quote:Original post by RickmeisterQuote:Original post by zedzeek
havent tryed doom3 yet (somehow i doubt my celeron433/128mb with gf2mx wont quite do it justice :) )
but anyways that looks very similar to quake3's *.map files.
Does it have a 'Turbo' button?? Try pressing it [smile]
Totally offtopic but...
HAHAHAHAHAHAHAHAHAHAHAHAHAHA ... that made me squirt Dr. Pepper from my nose.
well there is a map editor in doom3, but I can't say if it's useful or not, because I don't have any mapping experience, skills or knowledge ;)
But I guess ID created the game with it, so it should be quite good :)
Simply start D3 with "Doom3 +editor" or start the Game, press CTRL-ALT-~ to open the console and type editor <enter>. In both cases Doom3 will be started and then it switches back to the desktop with the editor.
Bye,
Oesi
But I guess ID created the game with it, so it should be quite good :)
Simply start D3 with "Doom3 +editor" or start the Game, press CTRL-ALT-~ to open the console and type editor <enter>. In both cases Doom3 will be started and then it switches back to the desktop with the editor.
Bye,
Oesi
hmm...as the anonymous poster said the map file isn't the file to look at but the proc file is.
I haven't found a file spec yet and I don't understand it completly on my own.
Obviously Doom3 uses portals (should be convex) created by a solid leaf-based bsp-tree.
The proc file contains a lot of models. Some of the models are the leafs (called areas) of the bsp-tree, but I'm not sure about the others.
A model consists of some surfaces, similar to the faces in Q3 I think.
There are also some other structures like the connection between the areas (called interAreaPortals) and shadowvolumes (?).
To render the map we also need the map file, because the proc doesn't contain any information about entities.
The cm file is just the collision model so not directly of interest. I heard somewhere that the aas files are for collision detection of different monster sizes, it seems correct if you look into the files.
I'm not sure how visibility is handled in Doom3. Maybe they use only frustum culling (BBs of the areas or maybe testing the visibility of the interAreaPortals). But the proc Files doesn't contain any BBs.
Bye,
Oesi
PS: sorry for my english ;)
I haven't found a file spec yet and I don't understand it completly on my own.
Obviously Doom3 uses portals (should be convex) created by a solid leaf-based bsp-tree.
The proc file contains a lot of models. Some of the models are the leafs (called areas) of the bsp-tree, but I'm not sure about the others.
A model consists of some surfaces, similar to the faces in Q3 I think.
There are also some other structures like the connection between the areas (called interAreaPortals) and shadowvolumes (?).
To render the map we also need the map file, because the proc doesn't contain any information about entities.
The cm file is just the collision model so not directly of interest. I heard somewhere that the aas files are for collision detection of different monster sizes, it seems correct if you look into the files.
I'm not sure how visibility is handled in Doom3. Maybe they use only frustum culling (BBs of the areas or maybe testing the visibility of the interAreaPortals). But the proc Files doesn't contain any BBs.
Bye,
Oesi
PS: sorry for my english ;)
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement