Is it okay to copy the Coloring folder over ? I don't have ft3+ and ft3 in the same location. And there are some planet colors I use that aren't in the newer version.
That value is a Not-A-Number (Indeterminate) according to the IEE-754 specification, the results of certain types of math errors. In the case of FT3+, these errors are most likely to occur while during painting or some of the more obscure channel operations. NaNs have some annoying properties (mainly that the result of any math operation with a NaN is also a NaN), and FT3+ should be automatically eliminating those results when they occur, for the most part.
Tools>>Actions>>Normalize Data should manually eliminate any of them in your world file.
Here's one that I don't think has been mentioned in detail on this thread (something like it was, in passing, but that was, I think, before the latest update): Find rivers finds too many rivers in FT3+.
If I try to perform a find rivers operation at anything above a coarse level, I get my entire map (including the oceans!) covered in a very non-river-like network of "rivers". If I use a coarse or very coarse level, I get a crazy crosshatch of rivers scattered around the edges of the continents, but again, not a very river-like network at all.
(At first I thought it might be because I'm building a rather rainy world and the wetness was overwhelming the system, but this happens whether I check the box to include rainfall in the calculations or not.)
I used an earlier version of FT a while back and rivers worked fine, but now coming back to it the rivers function seems to be broken, or at least changed in some way that makes the settings to use pretty opaque to me.
Comments
I just noticed that I still have to type ffix to get the symbol and bitmap fill path to be correct.
Will this be fixed eventually ?
My apologies. I forgot my other question.
Is it okay to copy the Coloring folder over ? I don't have ft3+ and ft3 in the same location. And there are some planet colors I use that aren't in the newer version.
Thanks.
I've already copied the individual files from one folder to the other to keep all the user files I created.
Thanks. I'll do that tomorrow.
I would be careful not to overwrite any updated schemes, though ;)
What does -nan(ind) mean on height? Attached picture shows several voids on the continent up towards the north pole.
That value is a Not-A-Number (Indeterminate) according to the IEE-754 specification, the results of certain types of math errors. In the case of FT3+, these errors are most likely to occur while during painting or some of the more obscure channel operations. NaNs have some annoying properties (mainly that the result of any math operation with a NaN is also a NaN), and FT3+ should be automatically eliminating those results when they occur, for the most part.
Tools>>Actions>>Normalize Data should manually eliminate any of them in your world file.
That worked splendidly, thanks.
Here's one that I don't think has been mentioned in detail on this thread (something like it was, in passing, but that was, I think, before the latest update): Find rivers finds too many rivers in FT3+.
If I try to perform a find rivers operation at anything above a coarse level, I get my entire map (including the oceans!) covered in a very non-river-like network of "rivers". If I use a coarse or very coarse level, I get a crazy crosshatch of rivers scattered around the edges of the continents, but again, not a very river-like network at all.
(At first I thought it might be because I'm building a rather rainy world and the wetness was overwhelming the system, but this happens whether I check the box to include rainfall in the calculations or not.)
I used an earlier version of FT a while back and rivers worked fine, but now coming back to it the rivers function seems to be broken, or at least changed in some way that makes the settings to use pretty opaque to me.
Yeah, Find Rivers seems to have a bug in FT3+, but still works in FT3. Can see a little more from this thread.
https://forum.profantasy.com/discussion/12000/one-day-worldbuilder-ft3-find-river-issue