-= Gametoast.com =-

lucasfart wrote:So this problem ONLY happens after you load your map, not when you start ZE?

Ding. Give him a prize.

Hey, i was just checking

So just to get this straight, it starts acting wierd AFTER you load your map into the editor, this has never happened before in the past, and it only happens on this map? Hmmmmmmmm. What did you add to your map or change in an LUA before this started happening?

The lua would have nothing to do with that. Whatever the problem is, it stems from the hardware having trouble rendering the scene and the editor. The tearing/spiking is a clear indication of a problem, along with the fact that the treetops and foliage are also not being rendered.

Come to think of it, it may be the editor's view distance, coupled with the thick vegetation. From what I see, there is a lot of foliage everywhere, along with trees, and other objects. Try clicking the minimum view distance preset button the next time you load the map, and see what happens. There's a chance making the editor render less could clear up the problem.

linksith wrote:What did you add to your map before this started happening?

Rocks.

MercuryNoodles wrote:Come to think of it, it may be the editor's view distance, coupled with the thick vegetation. From what I see, there is a lot of foliage everywhere, along with trees, and other objects. Try clicking the minimum view distance preset button the next time you load the map, and see what happens. There's a chance making the editor render less could clear up the problem.

Huh?

The small buttons (mouse cursor size) on the lower right portion of the main toolbar, it's the one farthest to the left. The group of buttons is normally labelled "Visibility".

Here is a picture to help you know what he is talking about.

Well that doesn't help.

Just a thought that could have little or no effect. Try removing the rocks. If this doesn't work then try the following: create a new world, open your world, hit ctrl+s, go to the new world and save your world there, copy your odf and msh files to the new world and anything else that is necessary.

EDIT: another thought, try doing a clean (that may and may not have any effect).

linksith wrote:Just a thought that could have little or no effect. Try removing the rocks. If this doesn't work then try the following: create a new world, open your world, hit ctrl+s, go to the new world and save your world there, copy your odf and msh files to the new world and anything else that is necessary.

Tried it. Didn't work.

linksith wrote:EDIT: another thought, try doing a clean (that may and may not have any effect).

I'll try that. But should I do a manual clean, or the Munge clean?

I would do the munge clean first and then the manual clean.

DIdn't work.

Well, the last thing I can probably say is make a new world like I said before.

Fine. Goodbye, WIP.

What is WIP anyway?

EDIT: Just to make sure, you may want to keep the original world folder just in case the ultimate fix to your problem gets found.

Too late.

And WIP stands for Work-In-Progress.

Are you saying you've totally deleted your map?!?

This could probably be fixed, you know, if you kept trying new things to fix it...

A clean won't change what's in the editor. That had nothing to do with the problem.

My other suggestion, which I should've posted first, would've been to remove the foliage. Even the richest stock maps don't have more than a patch here and a patch there. It's even mentioned in the docs that they used placeholders for at least one type to reduce the problems with it while in the editor. Unfortunately, removing foliage would've meant blindly navigating the menus to remove all foliage (since it'd be easier to erase everything), because apparently foliage placement data is part of the terrain file. Otherwise, you would have needed to redo the terrain.

I knew this.

If the problem is Only after you load a map then (maybe) the memory resorses are low. Try closing all un-needed programs before loading the map.