Questions about the limits for landscape

Feedback on past, current, and future development.
Post Reply
User avatar
psi29a
Posts: 5361
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:
Contact psi29a

Re: Questions about the limits for landscape

Post by psi29a »

All the packages necessary to run are available, you shouldn't have to compile anything yourself with worldsynth.

The packages are listed here: http://www.mindwerks.net/2013/03/worlds ... -released/

I should probably post those on the main project page.

Python sadly isn't batteries included on windows... :/
Top
User avatar
sjek
Posts: 442
Joined: 22 Nov 2014, 10:51

Re: Questions about the limits for landscape

Post by sjek »

Image
https://www.flickr.com/photos/50822638@ ... 202803552/

would say that here is no height limit at least in common sense. rendering may still be dependant on viewing angle if the prop is some kilometer high .p

tesanwyn or the data creator would be good to have some smoothing option as the hills multiply in those heights.

hme gave flatter map and the result with scaling was better and that paint included is nice extra althought cannot generate textures itself.

with configurations in worldsynth the module depencies needs a bit honing. the pytables pro version is nowadays merged into free release and with 3.1.1 worldsynth doesn't start. the zigzag in smesh might be solved using the newer tesannwyn. tried to built with cygwin but gave "ld terminated with signal 11 segfault" in gnu libs the linker needs some update and "warning array supscript has type char" which is a compiler issue or the libraries was compiled on windows ?
may still work for flatter terrain yet.

here's the error report in first run. may be missing libraries
Spoiler: Show
got it working with both taking the bmp image and converting it to esm with tes dependency toolkit and then placing morrowind.esm as master. otherwise it gave this error ------

(edit: anyhow worked as same landmass with hme when did only dependency update to esp, something in the data structure.... worldsynth average evelation and landmass enabled also makes spikes. 52000 game units evelation.

yeah. something like that. with old tesannwyn gives (in 512, 1024, 4000) 16x16 cell land by 1024x1024 resolution. some algorithm settings causes the next error as didn't get it this time)

------

Code: Select all

getUint(mCtx.leftRec);
getUint(flags);// This header entry is always zero
getUint(flags);
mCtx.leftFile -= 12;

// Check that sizes add up
if (mCtx.leftFile < mCtx.leftRec)
fail("Record size is larger than rest of file");
https://github.com/OpenMW/openmw/blob/a ... reader.cpp

as for the what teaser likes the lightwave has been playing around a bit ,p
http://www.oceanlightwave.com/morrowind ... hot438.jpg

or these ones
http://www.oceanlightwave.com/morrowind/2x2/shot487.jpg
http://www.oceanlightwave.com/morrowind ... hot291.jpg
http://www.oceanlightwave.com/morrowind ... hot397.jpg
cannot really deside
Top
User avatar
sjek
Posts: 442
Joined: 22 Nov 2014, 10:51

Re: Questions about the limits for landscape

Post by sjek »

Image

Image

heh :D it works when keeping in moderate heights with hme. under 25 000 units that one.

just when these all get out in some years
http://www.shotn.com/forums/
http://forums.bethsoft.com/topic/145486 ... s-edition/
http://provincecyrodiil.project-tamriel ... .php?f=272
+ couple more
all bundling maybe to http://www.project-tamriel.com/

that's gonna be big map........... and game... all handcrafted........ o.O
Top
Cramal
Posts: 186
Joined: 19 Sep 2014, 13:37

Re: Questions about the limits for landscape

Post by Cramal »

Its looks very good!!
Have you tested maw height between 25000 and 52000? Where is the limit?
For information, what is the max heights in morrowind?
Top
User avatar
sjek
Posts: 442
Joined: 22 Nov 2014, 10:51

Re: Questions about the limits for landscape

Post by sjek »

testing underway .p

for the limit it's depending how good your picture is if thoses spikes aren't coming from tesannwyn itself. which is probaply not wholly as it's has been tried and used and in certain ways it works slendidly. maybe with manual edit without so much color radiant ..
lightwave has bunch of applications http://www.oceanlightwave.com/morrowind/ for moving landskapes and admits this isn't the best piece of software what has wroten in readme.

as of static rendering over 3 cells and such not much tech savy but probaply need to wait still nearer with bug tracking and optimisation to 1.0 as http://www.ogre3d.org/2015/01/04/review ... -into-2015 changing to ogre 2.0 needs to be desided. there's most notably for this material system overhaul coming and changes to loaders. + bullet physics 3.0 nears it's completion althought gonna be majorly backward compatible. aaaaaaaaand jiggle bone for woman chests :D

in vanilla it's ca 32000 GU what makes in tesannwyn 456 m or from mountainous red mountain : )

Image

https://www.flickr.com/photos/50822638@ ... 238165945/ yeah. would say it's bug and the high color radiant in hme. trying with flat pancake gives no problems

Image
Image
Image

bigger height variance with h helps to tich those seams but it in high s height the program cut the landskape to pieces. around 40 worked what makes 1,15 km or 81900 GU

inside 54 000 it works good. would suggest that take the heighmap and modify it with some other program as the drawing tools are very small in hme. it goes for details better. worldsynt might also work this way

8-bit bmp can be modified in almost anything. gimp could do 16 bit and with few tricks 32 bit but if right from the oven it needs photoshop or some specialty program

edit:... gimp won't save the heigh map along as least traight from hme... code looks like could even understand in matter of weeks to pinpoint problems at least and relatively small one. http://bulletphysics.org/mediawiki-1.5. ... om_scratch this helped a lot for msvc what the heck situation.
Last edited by sjek on 14 Jan 2015, 18:46, edited 1 time in total.
Top
User avatar
silentthief
Posts: 456
Joined: 18 Apr 2013, 01:20
Location: Currently traversing the Ascadian Isles

Re: Questions about the limits for landscape

Post by silentthief »

sjek wrote:testing underway .p

for the limit it's depending how good your picture is if thoses spikes aren't coming from tesannwyn itself. which is probaply not wholly as it's has been tried and used and in certain ways it works slendidly. maybe with manual edit without so much color radiant ..
lightwave has bunch of applications http://www.oceanlightwave.com/morrowind/ for moving landskapes and admits this isn't the best piece of software what has wroten in readme.
There are many things to consider when trying to not get "spikes" or torn landscape from an image. One image may show them at 1.0 scale and won't at say 0.5 or 0.25 scale. Spikes and torn landscape or other artifacts also show up if the BMP image is not the correct formatting (I think it was 8bit or 24bit)

If you create a landscape in Gimp, then open it in HME and save it, this alone should save it as the properly formatted image file. I won't guarantee that this will always work, but I seem to remember that gimp won't use proper format no matter what way you save as.

As for moving landscape, you can set what cells the land goes to in TESAnnwyn, but I found that in trying to generate land this means you have to test is by running/flying/swimming your character to that location. I always made the land right at 0,0 to see it then moved it using tesfaith. Wish that this was much simpler.
sjek wrote: Image
That image shows a good example of the "torn landscape" where the morrowind engine either won't stretch the texture over too large of a distance or the data for the points is too far apart and it causes this artifact. I am not fully sure why this happens, but I know it is related to the distance between points - as lowering the scale in TESSAnnwyn will close these gaps.

Just noticed that the "wilbur" page does not reolve... hmmm. I grabbed the wilbur executables as well as any documentation I could find on it a while ago. Not sure when the page went down.

I will see if I can give any more insight on the landscape stuff soon.

ST
Top
User avatar
psi29a
Posts: 5361
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:
Contact psi29a

Re: Questions about the limits for landscape

Post by psi29a »

The hight distance between two pixels are too extreme. I think that HME algo need to be fine-tuned a bit to give a more realistic landscape. You can always throw the BMP into gimp/photoshop and do smoothing/bluring of the heightmap. That should give more of a rolling effect instead of spikes.

Or just follow my instructions to install the libs and run worldsynth. I repeat, you shouldn't have to build anything.
Top
User avatar
sjek
Posts: 442
Joined: 22 Nov 2014, 10:51

Re: Questions about the limits for landscape

Post by sjek »

thing is that i have it :)

It tells time to time that this version of pytables does not support indexing and in noise land option and the other one upper that modules is missing. Does it look for envirom variables .?

Then i try to use it in tesannwyn the height values go even without mountains to 2 or 3 km or so +/- and the adjacent cells are other on up and the other at nearer the bottom. Have to try to scale it down under 200m thought.

Problem is also inside cells that adjacent vertixes do the zigzag to x and/or y direction depending on picture formatting.

https://github.com/psi29a/TESAnnwyn/blo ... r/common.c might get this to build in msvc. Basically just need c edition of 2010 or any of newer ones and create empty win32 console application and load the codefiles. That should do it that there's no external dependencies. Then starting to comment some some calculations out.

Code: Select all

if (opt_lod) {
lod_height[(ppc+1)*(i) + (j)] = (float) height * 8.0f - 8.0f; /
Line 379 just looks suspicious... c book from library maybe

If that vex function calls for vertex colors that's on the trying list. Besides of raw or bmp checking on filename at least and getting the data out + error checks there seem to be no differentiating functions for data itself so it needs to be just right kind of file. As what comments go that takes the cells as one big array of numbers and then seems to bake it to esp format.

As of testing its kinda easy this time. The 10000000000 distand land setting isn't taking much on comp and it can be saved levitating near the spot without crashing the game. doing those maps with -x 60 setting currently

gimp + hme save works with minor seams and inverted heighmap ... making better one later
Image

---------
edit: right link this time althought wizard island is kinda good reckon xP

and bumped into gimp image lua coding tutorials / handbook. http://pippin.gimp.org/image_processing/chap_dir.html ... something also in the image file it is as run-length encoding compression in gimp makes the ground all spiky

viewtopic.php?f=7&t=2301&start=10 --> previous page + 3d editing + github land search.. that's gonna be later case after esp record structure

this might take it's time anyhow. msvc tells outdated code and need to go those point by point with stackoverflow or some other or find older compiler. any idea with what version of C that was written .? ^^

ps. Microsoft Visual Studio 10.0\VC\include <-- this to include directories needed.
Spoiler: Show
_CRT_SECURE_NO_WARNINGS goes to properties --> c/c++ --> preprocessor --> preprocessor definitions. that's makes 1/4 off about .p in undeclared indentifier there's might be linker problem. 4-6 different errors : )

Simplest things first. needs to find equations what are used for those images and tweaking and comparing can be done with scilab 3d graphs. Then it's tweaking those to match and let's hope that terrain gonna be one piece or that c code has something to handle vertixes. There's external matrix libraries but dunno about those or better to look directly at openmw code and how the land coding is done. Would think that exporting command easy to keep but let's see how the code goes


Hme:
Spoiler: Show
worldsynth: something like this route
https://github.com/psi29a/worldsynth/bl ... acement.py
https://github.com/psi29a/worldsynth/bl ... ightmap.py
https://github.com/psi29a/worldsynth/bl ... th.py#L665

seems to generate kinda clean function. would say that export part needs possible tweaking

tesannwyn: ..... little bit harder
https://github.com/psi29a/TESAnnwyn/sea ... %93&q=Vhgt z coordinates are good place to start.

Edit: limit in vanilla comes from esp file 16 bit nature which only allows values up to that 32 657 or so.

viewtopic.php?f=3&t=1607&start=40#p25846
The tearing related to height changes may actually not be based on textures but rather on models; the traditional way the terrain works is by having an immense number of points and interpolating between them-the tearing occurs because the UV mapping, which applies the texture, doesn't necessarily scale up as the distance between points does. Divinity: Original Sin is a modern game that suffers from this a ton if you're not careful when designing levels. I'm not sure if OpenMW has a solution to this.
viewtopic.php?f=2&t=1055&p=9937 of desing
Top
Post Reply

Return to “Feature Requests and Suggestions”