• Welcome to World Machine Community. Please login or sign up.
June 17, 2019, 01:57:05 am


Read the Development Diary for an inside look at World Machine's progress!

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Erwin0265

Macros and Plugins / Re: Geoglyph macros 'invalid'
March 02, 2018, 12:30:44 am
I realise that this is quite belated, but what is the actual build number of your WM?
GG2 only works with WM 2.3.7 and up.
Earlier version crash.............
Macros and Plugins / Colorize & Colorizer devices
November 27, 2015, 03:21:33 am
Hi all,
I'm confused..............
Oh, I suppose I'd better give you some more information.............
Serious cap on:
I'm relatively new to WM and know the Colorizer device; the one with that uses gradients to colour areas of the terrain - found within the Converter devices.
But when looking inside some macros (Extended overlay, for example), there is also the Colorize device which has two colour inputs.
I have not been able to find any discussion/information regarding the Colorize device other than it is a Converter device; well, not, it's not - as it's not found there (or anywhere else, for that fact)..........
To further compound my confusion; when you open the Colorizer device, the title for the device is "Colorize".............. The Colorize device has the title, "Colorize properties"..............
The online device reference lists the Colorize in amongst the Converters (but it's not present in the actual program); there is no mention of the Colorizer device which is in the actual program converters section.....
My main reason for asking this question is I want to find the two-colour Colorize device so I can use it in my texturing workflow (when I manage to develop one.......).
Can anyone clarify this for me?
Necro all you like, TorQueMoD...  :D
My issue hadn't be resolved or responded to, so thanks for your help.
It may be a stupid workaround; but if it solves the problem, who cares?
I've had the same issue; in fact, it was with the file you posted at my request; "Hero Mountain Snow Line.tmd", posted on a thread entitled "Snow" started by Troedel.

My WM version is
I can't update for reasons I won't go into in an open forum; do you have a PM where I can explain my updating issues with you?
So, anyway, this appears to be a problem also found in WM 2, not just WM 3...............
Bug Reports and Help / Re: Snow
November 14, 2014, 09:08:22 pm
Remnant; unfortunately, I can't open the file (yeah, I took a while - been crook in hospital  again!); apparently, it was made in a newer version of WM than mine []..............
Bug Reports and Help / Re: Snow
November 02, 2014, 02:42:36 am
Thanks for that.
I keep on getting mountains that are far to eroded when I try to create a heavily-snowed (Grammar?) mountain.
I have been using the height output from the erosion device instead of the snow device to work around this but this totally looses much of the snow device's creation of snow with depth, rather than just a colour map (which I suppose is OK when the mountain is viewed from a distance, but when such a feature is there for the taking/using; I think I should be taking advantage of it................

I think I should reinstall WM temporarily elsewhere as I have accidentally saved over a few of the example files (D'oh!!)..........
Thanks again.
Hi all,
This post is essentially addressed to Remnant as it relates to an earlier post in which he offers to share a fantastic example world for using the Snow Device:
QuoteI actually have a fantastic example world  for using the snow device for a snowy peak; it uses a currently unreleased device but I will see if I can modify it and post it to this thread soon.

Post entitled "Snow" by Troedel back on Sept 19, 2012

@Remnant; whatever happened to the snow world illustrating the snow device's usage that you were planning on posting here?
I know it's been a couple of years since this post, but the need is still here............................
The post that I am referring to is entitled "Snow" by Troedel and was posted back on Sept 19, 2012................
I also replied to the OP but as it's over 2 years old, thought it prudent to make a fresh post............
Bug Reports and Help / Re: Snow
November 01, 2014, 01:03:39 am
@Remnant; whatever happened to the snow world illustrating the snow device's usage that you were planning on posting here?
I know it's been a couple of years since this post, but the need is still here............................
I  think you're missing the point of this thread.
I want to know how to obtain the Snow distribution map, as explained in my OP.
I know all about the Gamma Correction feature in Vue - I don't use it - I prefer to obtain an unadulterated output that I can post process to my heart's content.
Besides, the only reason for posting that image was to show you that I already knew how to use the maps (which is what you were going to explain to me).

So, can you tell me: How to generate the output of the Snow device as shown in my screencap, "Snow Mountain v3 - 2D output of Snow device", attached to my OP?
I use both Vue and Terragen.
However, I know how to use the maps in those programs; I want to know WHY the preview shown in WM2 is not what is being written to disk.
The 3D output is fine for creating the mountain/whatever in Vue/Terragen but I would like to try the actual map shown in the preview to see what I can create with that.
Further; looking at the 3D preview (especially when rendered at high res.) - as shown in the "Preview of the terrain viewed within WM2" attachment from my last post; I really like the snow distribution with that map and want to try it out in Terragen/Vue.
Attached is a preview quality render from Vue using the Snow Device Heightfield Output that is written to disk.
It's OK, but not as good as the 3D preview shown within WM2................
Hey all,
I am still relatively new to WM2 and have been trying to output a certain map that I can preview (both 3D and 2D) using the preview output parameter within WM2, but when I write the output to disk I get a totally different map.
I have added 4 attachments:-
Snow Mountain v3 - Device view is, well, the device view of my project (don't worry about all of the outputs; I'm exploring what each does...).
Snow Mountain v3 - 2D output of Snow device is the map I am trying to generate - remember, this is just a screencap at 1000x or so pixels...
Snow Mountain v3 - 3D output of Snow device is just the preview of the terrain viewed within WM2.
Snow Mountain v3 - Snow Device Heightfield Output is the output I am obtaining when I write the output to disk.

Why is the preview shown within WM2 so totally different to the actual saved to disk output?
What am I doing wrong/is there another device/macro that I need to add to the Device graph (terminology?) to obtain what I am after?
I await the wisdom to come flooding in...........;)
The main ones that appear to have this issue are Erosion and Advanced Perlin -other generators may be the same but being a newbie means not having used many generators as yet...........
Not sure what you mean by "devices going forward".....
As for boxes being grey; all the ones in Erosion and Advanced Perlin are quite black and highlight blue - so they are available parameters....
Regardless; if this is a problem due to the program's framework, it's something we'll just have to put up with.
I'm sure you don't want to start from scratch, using another framework (even if there is such a thing available); you're just up to WM3; I imagine the thought of WM1 v2 would be a very bitter pill to have to swallow................ :)
Yeah, I think "Viewer" could be a good name ("Imager" again implies there's an image to be had......).
Either way, it shouldn't be listed in the output manager dialogue box.

"End Result {not available for export}" (or something similar) may also be an option........
Just throwing ideas out there; worst thing that can happen is that they are rejected; I cope pretty well with rejection... :)
Hey all,
I'm relatively new to WM; this is my first topic initiation.
I was wondering whether I am missing something regarding changing parameter setting in property dialogue boxes.
To use an example to make myself clear:-
The Advanced Fractal Perlin Generrator dialogue box has many available settings; most come with ether a drop-down menu or a slider.
However, many (all?) with a slider also have a numerical readout that can be highlighted.
Usually (comparing with other softwares), one can type in a numerical value rather than using the slider - to make changes more precise and/or to set a value higher than the slider can go (Vue, for example).
I discovered today (when I tried to return the Random Seed back to a previous value which I had copied to the clipboard) that this does not appear to be possible in WM ( Pro).
Am I missing something or is this how WM is set?
Thanks for any help..............
Nice image.
I'm pretty much a newbie to both WM and Terragen.
Check out the Geekatplay website (geekatplay.com).
Most of their tutorials can be viewed on (and downloaded from) You Tube.
Check out the Exploring Terragen series; it's their that they explore terrain creation in WM and exporting to Terragen.
I'm currently viewing the Terragen tutorial, "Lake View" (there are 8 parts), which is part of the Exploring Terragen 3 - series 1; in the second video, he goes through importing a WM terrain that was created in some of the World Machine tutorials (Exploring World Machine series 2 - Snow Mountain, part one/Creating Mountains with snow packs in World Machine, part two).
Good luck.
As a fellow newbie to WM, may I suggest that this information regarding the overlay view be added to the Devices Reference as this was the same issue I was having [wanting to export the Overlay view as well as other outputs].
Exporting other parameters was fine; I just thought, being one of the export devices that it would, well, export..............
Thanks to JDwilley I don't need to create another post asking the same question.............

Also; another question (related); if Overlay view doesn't produce a savable output, why is it included in the Output manager dialogue box (with, "Not exporting" noted next to it)?
Its inclusion implies that there is a file there to be saved.................