Uhm, map error message.

[Diego Cueva]

Yeah, I get this error message when I try to run my map in Quake (through WC, and without VIS):<br><br>************ ERROR ************<br>CanonicalVector: degenerate<br><br>First thing I tried was to delete some things I added to the map before I got the error message, but it didnt work. Now I´m thinking about  trying to run it again with VIS to see what happens, but since it takes 63 minutes to compile the map, I would like to know if theres any clue on what this message means and how can I fix it.

[Moose or Chuck]

Maybe you have too many things in your map, too many vectors.

[Diego Cueva]

Uh? Is there a "things" limit in Quake? Are you sure? Because that would ruin my project and days of hard work...

[Moose or Chuck]

I have no idea. I'm just throwing ideas out into the open.

[randall]

There is a limit, and 63 minutes to compile with PIII 800 is a serious red flag.<br><br>I would honestly work on the map in small chunks, and then add them all together when the project is finished. That way, when an area is done, you freeze it and move on to the next section.<br><br>It would be kind of like making 8 normal-sized maps and gluing them all together.

[Diego Cueva]

What I dont understand is that I got the error when adding a simple building. Not a big change, not making the map bigger, just a building. weird..<br><br>Randall, the idea about making it in chunks is possible but very hard because of several design reasons. I can make some buildings and small stuff and add them latter, but the main landscape, cityes and other complex stuff need to be created in a single file. <br>BTW, just a thought: if I use your idea, when I "glue" all parts together, wont I get the same "big map" error?<br><br>Last modification: Diego Cueva - 07/12/01 at 18:53:46

[randall]

There isn't a mysterious "big map error" phenomenon. The error could have happened for a number of reasons, none of which I can point out at this moment.<br><br>Here is the way I would do it:<br><br>Create an area, fine tune it, optimise and then freeze it. (meaning you don't work on it anymore because it is PERFECT).<br><br>Create a NEW area, fine tune it, optimise it, then freeze it. Glue it to the first part and ensure it compiles without any errors. Test it, and FREEZE those two sections.<br><br>Move on to the next area, fine tune it, optimise it, then freeze it. Glue it to the first and second parts... I think I get the idea now.<br><br>This will ensure your map will be as large as possible, with all bugs worked out along the way. Also, the individual compile times of the small maps will be much more managable. If you do it right, the r_speeds will be much more managable too.<br><br>By using your method, a single large area, you may get halfway into the map and then discover the compilers can't handle any more. Then you'll have a single large map, with huge areas that are incomplete. And the compile time keeps increasing, which makes it difficult to make changes to decrease the r_speeds.

[Diego Cueva]

[randall]

[Diego Cueva]

[randall]

[Diego Cueva]

[randall]

[Diego Cueva]

[randall]