yo, quakewiki.org -> random mapping tips or something? 

going to point out that this is exactly why I wanted to make a compendium of knowledge that covered things like this over a year ago. The Quake Wiki was a compromise.

There needs to be a more firm collection of not only the basics but the nuances of the process or everything will be lost. 

That's cool. Many things need to be but they won't if people just keep pointing out that they need. 

Thank you very much, Lunaran, for those two extensive posts. Most of what you wrote in #14359 were things I did not know, or certainly did not understand as clearly as you explained here.

And thank you, ijed, for that additional tip. 

i wonder if it would be better to just have a way to grab a post in it's entirety, put some tags on it and then throw it in a pile to be searched... 

 

I've made the wiki my homepage to guilt myself into writing something on it.

We'll see what wins - stubbornness or frustration. 

Dunno if its useful, but i stumbled upon this skybox generator. Its online and ... check for yourself.

http://www.nutty.ca/webgl/skygen/ 

 

Using Trenchbroom to create rocky paths and walls ... these verts were all perfect sitting on top of each other. Is this just something I have to accept or should I be snapping all vertices to INTs or what?

https://dl.dropboxusercontent.com/u/161473/Misc/VertexDrift.jpg

(in before FifthElephant tells me he has snap to grid bound to space bar) 

in before FifthElephant tells me he has snap to grid bound to space bar 

I'd like to check that out. Maybe send just the part in the picture. 

I'll work on a solid repro and send that to you. I already fixed that area. I've got drift everywhere now and I'm wondering if I need to burn the boats and start over.

Is it recommended to turn "Force integer plane points" on for maps full of organic shapes? It seemed to do bad things to the brushes when I reloaded the map ... cuts moved into nearby planes and made extra verts on a bunch of brushes.

It's hard to describe.

Maybe I'll just make an interior map with axis aligned walls. :P 

Sorry to read about the headaches with the vertices etc., but it's awesome that one of my favourite mappers is making something for Quake again. Yay! 

Is it recommended to turn "Force integer plane points" on for maps full of organic shapes?

It's recommended to turn it on before you do anything else with the map. :P TB2 does not even have an option to disable int plane points.

Willem Is Making A New Map! Yay!

Yup! This will be cool. 

Oh, so it's the recommended way? I didn't realize. The warning it throws up and the description text in the dialog box made it sound like "Only as a last resort!" kind of thing.

Turning it on now! 

 

You'll be missed 192.99.166.15 ... I always considered you a friend. 

Forcing integer plane points will result in more vertex drift as the editor needs to move vertices around so that the planes are all represented with integers. You'll get vertices off grid and such. 

But isn't that better than the verts drifting slowly over time as I close and re-open the map? At least I can see it happen and fix it on the spot. 

You're wrong. TB2 doesn't have this option at all and always allows you to use float points for planes. It will give you warnings in an issue browser though, with a quick way to fix them.

int plane points may or may not safe you from drifting vertices. I can't quite remember how TB1 handles it, but I think the problem is in writing and reloading floating points through text files - it's always lossy.

But as necros said, integer vertices will cause vertices to wander. There really isn't a way to deal with this problem that completely avoids any headaches. Integer plane points will give you off grid vertices, and float plane points may give you drifting vertices. Both might result in microleaks. 

integer vertices will not cause vertices to wander, but it will often result in vertices which are off the grid. 

I have the thingy majingy bound to the doodly do 

How does one become a beta tester for TB2? :P I have a project I'm working on, so I can provide real world feedback... 

I was thinking ... Of course you've considered this, but I'm wondering why you would have rejected the idea. What about a custom .TB file format or something? Why use the MAP file format for all I/O? It seems like that's where the loss is happening. If you stored the map in your own format and just spit out a fresh MAP file for each compilation you would eliminate this problem.

Like what Worldcraft did...