News:

Huge spam cleanup. I hope, everything important is still in place. :-)

Main Menu

Elevate tiles (F4) rendering

Started by TechnoTroll, December 20, 2009, 08:27:47 AM

Previous topic - Next topic

TechnoTroll

First off I'd like to thank the CentrED team for this wonderful tool they're working on, for it has made map developing for our shard so much easier and allowing us to work on projects way more complex than before.

Recently we updated to the 0.5 version (hooray for undo!), but it seems the F4 function isn't working properly any more. While elevating tiles in flat mode the program doesn't render the change instantly (the actual z changes and it shows if you have the new "show height" function turned on, but the actual tiles are not rendered until you move the screen or enter the menu of any of the functions and change any of the settings). This shouldn't be a problem per se, but when landscaping I often use the boundaries function so that the tiles I elevate are removed from the screen, allowing for easier work on those that remain.

Anyone else experienced this, or is it a local thing?

Hitman

I just tried the following: switch to flat mode, change some altitudes (using the elevate tool and also using the mouse wheel), the displayed Z value was adjusted correctly. I switched out of flat mode and the tiles were rendered correctly.
What isn't done, that filters are applied (in case of elevation that would be the boundaries only). I haven't decided yet if I declare that as bug or feature. The downside is clearly as you described: if you want tiles you elevate to flip out of the boundaries to not see them anymore, it's fine. The upside however is also nice: if you edit statics within a house for example, you usually blend out the upper parts of the building with the boundaries. If you now play around if tile placement, they can easily leave these boundaries and would be invisible then. As it is currently, you still see them and can correct the issue.
On the other hand ... as you also said, it works as expected when moving the view, so if I don't fix it it's probably too inconsistent. Ok ok, it's a bug, and will be fixed :D

Thanks for the report!