Every time I make a new worldspace and build LODs with Oscape, cell 0,0's normals and colors are black and the whole cell mesh is like a sinkhole.

The actual mesh, colors and normals are good, when you move closer or directly stand over the cell.

I've noticed the extracted heightmap that Oscape shows in the Preview tab has a black dot where cell 0,0 is going to be. I've tried to force Oscape to read from the original heightmap I built the .esp from, but the defective LOD cell is still there when I test it ingame.

It looks like Oscape is bugged and totally ignores cell 0,0 when reading and building data for LODs.

Anybody else experienced this same problem and/or found a solution? Thank you. =|

0 views!?

Reviving.... -.-

Barely 10 views and 0 replies.....reviving. =p

Your 'revive' posts are barely hours apart.

Normally people wait a week before bumping their own thread.

Wait at least until your thread is off the front page, to bump, and the views are lagged. It only updates like every hour or so.

Just looking at your post, I's say you have a faulty heightmap
For what you're suggesting, Oscape isn't bugged. Granted, there may be a few small bugs, but it doesn't ignore cell 0,0.
As mentioned above, something is bugged on your heighmap and that's why Oscape cant read the data properly

Twenty minutes and my post is in the 2nd page. Few hours and is 4th page. At this speed, if after 30 minutes I still have only 10 views, better I revive it.

I've double checked the heightmap that TESAnnwyn uses to make up the .esp file and it's perfect. I've replaced the heightmap generated by Oscape with that one and I still get a blank 0,0 cell LOD.

Honestly, now, I cant remember if replacing the heightmap fixes or not the meshes, but I'm sure that the color/normals are still broken.

Nice!

If you can build a 16x16 quads world as good as that one, I want a guide to fix issues!!! =D

[UPDATE]
This is a series of screenshots from a test terrain I've generated yesterday.

This one is a screenshot of the terrain as it is generated in World Machine 2:
http://i903.photobucket.com/albums/ac235/Spiegel365/Cattura.jpg

These two are screenshots of the cell 0,0 LOD seen from two different distances, colors/normals only and meshes/colors/normals:
http://i903.photobucket.com/albums/ac235/Spiegel365/ScreenShot3.jpg
http://i903.photobucket.com/albums/ac235/Spiegel365/ScreenShot5.jpg

These are some screenshots of the whole volcano (sorry for the foggy weather):
http://i903.photobucket.com/albums/ac235/Spiegel365/ScreenShot6.jpg
http://i903.photobucket.com/albums/ac235/Spiegel365/ScreenShot7.jpg
http://i903.photobucket.com/albums/ac235/Spiegel365/ScreenShot8.jpg
http://i903.photobucket.com/albums/ac235/Spiegel365/ScreenShot9.jpg
http://i903.photobucket.com/albums/ac235/Spiegel365/ScreenShot10.jpg
http://i903.photobucket.com/albums/ac235/Spiegel365/ScreenShot11.jpg

3rd page and no new views/replies....time to revive. =p

No new replies or views.....reviving in the hope for a help. =|

As a matter of interest, how deep is the hole. Place a static at the bottom and get its Z coordinate.

I've heard something about this problem occurring on ESP files, but not on ESMs.

Maybe you'll have more luck asking your question in the Oscape thread...

Gonna try by turning my esp to esm....might be a solution....although I cant really imagine what difference this can make, since all Oscape does is reading the vertex coordinates (or at least this is what it does).

Thank you for the hint, I'll let you know