How to Export your height map from Wilbur

[Runninghead]

Hi, Anyone know how to delete a Post?

I actually still need to know what is considered a decent size (pixels) for creating a good map, considering I'll be running it through Wilbur.

Cheers.

[johnvanvliet]

depends on your computer
a almost antique Pentium 4 or antique pentium3 or 2 with 32 meg to 1 gig ram will need a very small image as input ( 256x256 to 1024x1024 )

a dual I7 and 64 gig ram well easily handle a 8192x8192 px image


i have a older I5 and 8 gig ram and working on a 4096x2048 px image is no problem


as to delete post
ask one of the moderators to do it

as to exporting i use BT almost all the time
it is a 32bit floatingpoint image that GDAL has no problems with

[Runninghead]

Thanks John- I've a MacBook Pro and it's maxed out on RAM.

Problem I've been having though is that I'm using 16Bit greyscale 300dpi A4 jpg image and it's taking too long in Wilbur, plus the Erosion settings seem really feeble.

The Incise Flow makes ugly diagonal lines too (maybe I need a Noise pass for the ocena depths?)Screen Shot 2016-10-19 at 21.07.44.png

[johnvanvliet]

16Bit greyscale 300dpi A4 jpg image

jpeg is a 8 bit format and 300 dpi ONLY refers to printing on paper
and NOT the size of the image

but a 12x16 inch image at 300 is 3600 x 4800 px
-- medium to small for current hardware

now png can use 16 bit gray or 8 bit
tiff can be 8 ,16,16s 32f

normally i stretch out the 32 bit values to 1 to 65535 or close to that
import into wilbur
run a incise with a 0.1 variable blur
then 3 or 4 erosion passes with a 1% to 2% per pixel noise ( not over all ) and 0.33 strength
original , then incise , then erode


this 1600x1100 took only about 8 seconds for each of the 3 erode cycles

[Runninghead]

Thank you so much John.

I have now also found Waldronates "Fun With Wilbur" tutorials at the Fracterra site so that's a relief too.

Still struggling to get a vaild link to the latest version of Wilbur though.
I just realised I've got a 1.62 version (the one at the top of the Downloads page).

I should be using 1.85, which I'm hoping will run as well as 1.64 under Wineskin.

I get the difference between print and digi but couldn't recall the pixel dims of A4 at 300dpi when I was typing the post, sorry.
Glad to hear that's considered Small to Medium for current hardware.
I'm going with 2480px square, while testing and learning.
I must say I find Wilbur amazing. Must chuck those folks a fiver sometime.

Thanks for sharing your process, looks great- I'll try it.

[Runninghead]

Well, I know I'm being really dense here because I can see a heading for Wilbur 1.85 over at http://www.fracterra.com/wilbur.html but no link to that version.
It says the latest to run on windows 98 is 1.62, but I'm running 1.62 under Wine on Mac El Capitan, so maybe 1.85 would work for me, if I ever find it!

Also- what "bit" flavour is 1.85? 32, 64 or raspberry ripple?

I'm having a great time playing with the version I currently have, looking forward to sharing my results next week.

[waldronate]

Try looking at the part just below the "Older Version Descriptions / Changes" paragraph, where the page says

"
Download
Download the Wilbur 32-bit Setup Program
Download the Wilbur 64-bit Setup Program
"

See also https://cartographersguild.com/showthread.php?t=29412

[johnvanvliet]

use the 32 bit with WINE
the 64 bit was seg faulting on me and i have NOT looked into it

but seeing as 99.9% of windows software is 32 bit source code ( even if built using a x86_64 compiller )

[Runninghead]

Thanks Waldronate and John, sorry for slow response- for some eason Tapatalk did not alert me to your replies.

I have read some more, as you advise and decided to Download the 32 version from http://www.fracterra.com/wilbur.html (did not realise that this is the latest 1.85 version).

If all's well I may try the 64Bit version later.

Bit rushed at the mo but will feedback on how it goes!

[su_liam]

Yeah, 64 bit doesn't work on Wine. At least not on a Mac. There's apparently a conflict between how 64 bit Windows wants to use a register and how MacOS wants to use it. Apparently there's no such conflict with Linux. Waah.