• Welcome to World Machine Community. Please login or sign up.
 
September 18, 2019, 09:10:23 pm

News:

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 - froesccn

1
General Discussion / Re: What is a modder to do.
July 17, 2007, 02:27:36 am
Well,you've got a point there. The 512x512 limit is a sound business plan,
as it requires to buy the standard version if you actually intend to use a
generated heightfield for any purpose, and the pricing is reasonably low
that people like me who are just toying around might actually buy it
anyway (as I did).

As it is, it might be more fitting to rename "Basic" to "Demo".  On the other
hand, if the intent was to provide a free community edition for non-commercial
purposes, the better way would be just blocking advanced devices and
productivity features such as the explorer view and preview locking,
possibly also reducing output to 12-bit for high resolution worlds or
watermarking a corner of the output with a world machine logo :)
2
Bug Reports and Help / Re: query about build length
June 01, 2007, 03:23:36 pm
Quote from: curt_sundberg on June 01, 2007, 04:05:14 am
is this normal though? does going from 2048 to 4096 really bump up the build time this much?
or has something stalled maybe? just wondering because i have other work that needs doing


The problem is most likely that the memory requirements for 4096 exceed your
available physical RAM, which leads to swapping and really slows things down.
Unless you already did so, select "Keep only output build results" in your
world machine preferences dialog to conserve some memory.
3
Bug Reports and Help / PNG Export
May 01, 2007, 04:43:15 am
I'd really appreciate if the grayed out PNG write option would be filled with life  :D
It's a wide-spread format, suitable for height fields, patent-free, good compression,
very easy to implement (especially if you don't need the fancy bits, basically you
never need to write anything except raw 16-bit gray values). Also, there is a free
implementation available for commercial use: http://www.libpng.org/

Some other points (played around with it a bit after purchasing the Standard Edition):

I think it would make more sense to use the same executable for all editions and
just unlock features after entering the purchase key. Not much point in downloading
and reinstalling basically the same app (most purchasers will have tried Basic). This also
avoid the hassle when someones download fails during purchase. And when your
program becomes popular enough to attract the attention of hackers, they will
find a way to get their hands on a non-Basic executable anyway.

As you already keep track of the "modified" state of the terrain, it would be customary
to indicate that state by appending an asterix (*) to the file name in the title bar.

Considering that this forum explicitely offers to "Hide E-Mail from Public",
I did wonder why I see an icon "Send E-Mail to" next to my posts :roll:
4
An option to do the internal processing with 16-bit or 24-bit heightfields would also help a lot.
The rounding errors should be quite acceptable for most terrains, as even a 16-bit height field
has a much higher spatial resolution vertically than horizontally.
5
Bug Reports and Help / Minor GUI issues
April 10, 2007, 02:25:40 pm
Just downloaded the basic version and it looks quite nice (but I didn't actually do much terraining yet).

There is a very old thread called "GUI bug" describing a tooltip problem (tooltip text displayed is always one step too old, size is correct). Just wanted to say that the problem still exists in the current version. The suggestion to disable hardware acceleration on the graphics adapter worked, but is not really the best thing to do. Using XP with a GeForce FX 5200.

May I ask what kind of odd-ball GUI library you are using for this app :D

Hmm, disabled sliders seem to look more or less like active sliders. Sounds like QT. But not quite?

Also, I think it is unnecessary to disable the toolbar buttons just because the sidebar gets focus,
as long as the device workview is visible. BTW, the disabled toolbar buttons look rather strange.
Furthermore, when you click on a device, the button should remain pressed or otherwise marked
as selected (after all, it determines the effect of the next "+" actions in the workview)

Aestethically, it would be more pleasing if the two frames below the preview window in the sidebar
were of the same width as the lower frames. Functionally, resizing the sidebar is currently not very
useful. It would be nice if the size of the preview window would scale to use the maximum unused
space in the sidebar.

Well, you did lately blog that it is satisfying "to make rapid and daily progress" on user interface issues  8)
6
I also get this when hitting F1 just about anywhere. Especially when a device is selected,
I would expect to get the device reference instead  :)