Please post any bugs you encounter here. Updates about current patches will appear here as well (unless Valisarius moves this thread, of course ; I'm kinda overstepping the line here while he's away).

Please provide cell coordinates and the nature of the bug. Short descriptions are fine: eg. '255,224 land tear' or '133,-17 floating trees' is fine unless the problem is more complicated than that, in which case, simply describe the problem as best as you can.

I am currently working on a patch to correct landscape errors, specifically landscape mesh tears and missing meshes, which occur mostly around the edge of the map.

Not overstepping the mark in the least. Give me a day or two and I will upload the new master file and LOD. There are plenty of bits to fix, sadly.

Two points: wondering if you knew what this warning was related to:

I get it every time I start up the CS with hiboriamain.esm loaded.

Second: I've been fixing a tear along the extreme right edge of the heightmap (in cells 256,160 up to 256,226, a span of 66 cells) where the 16 quad overview window cuts off, but it's outside the draw area and I'm wondering if fixing it will have any adverse effects (or if it's even worthwhile). It won't be visible in-game (at least, I don't think it will have any visible effects) but I'm adverse to leaving such a large error in the map.

Also, it's interesting to note that you can draw outside the limits of the overview window with the landscape editor and even (apparently) generate regions outside of it. The landscape size limitations seem to be a heightmap restriction only.

Bad forms error.

I have experienced that now for months. I have absolutely no idea what on earth it is. I tried asking on the main forums and have played intensively to get it to throw up an error in game, even a crash, but nothing. It seems to have come up during a very early merge and I can only assume it is something that is only of issue in the CS. I simply accept it and ignore it.

As for fixing things outside the current cells, try not to as it adds cells onto the landmass and can cause bloat to the master file. When you do it the computer probably hangs for a few seconds, thats because it is creating new land outside that already made. It wont cause problems, but will add size to the files.

Yes, it is definately a heightmap editor issue alone, however its also a size of the file issue too. I gave up at a certain point adding new land as it can become so huge as to be simply beyond download. Maybe in the future we could add to it, though it would need merging into the master file as distant land is only produced from the master file owing to the CS not being able to cope. I have to use external software to produce the distant land.

Yes, I was kind of leery of adding to the file size so I thought I might pull the land back a couple of cells along that edge to keep it within the present area as opposed to expanding it. It's probably pointless, since it doesn't seem to affect anything, but I like to avoid potential bugs if at all possible. Most of that land is blank anyways and still needs to be region generated so it's not like it's going to hurt anything. I'm sure it's outside the border anyways. Meh. I'm going to go work on my modeling.

I left an edge to the map so that we could put impassible borders there. You can see it in the distance but not walk in it, to save the file size. Good that you are fixing these things when you see them. Let me know where you have fixed so that I can make a note to prevent others overlapping it.