FT3: My world altitude has been inverted
I have a FT3 file that I open from time to time to extract different map projections for my D&D campaign. Besides that I dont really touch the file.
Today as I opened it, what has been land since I generated the world shows as ocean, while ocean shows as land. The altitue number reflect this, so it is not a display issue.
I have not touched the file for a few months, and neither have I touched my FT3 installation.
I have tried reinstalling, but to no avail. I also tried using a method of inversing the altitudes from a tip I found in another post using global math [Roughness]=[Roughness]*-1 and while it is somewhat successful, the coastlines do not match what they looked like in earlier versions.
I am at a complete loss. There have been no changes on my end except that it has been a few months since last I opened the file.
What could have caused this flip of altitude data?
Today as I opened it, what has been land since I generated the world shows as ocean, while ocean shows as land. The altitue number reflect this, so it is not a display issue.
I have not touched the file for a few months, and neither have I touched my FT3 installation.
I have tried reinstalling, but to no avail. I also tried using a method of inversing the altitudes from a tip I found in another post using global math [Roughness]=[Roughness]*-1 and while it is somewhat successful, the coastlines do not match what they looked like in earlier versions.
I am at a complete loss. There have been no changes on my end except that it has been a few months since last I opened the file.
What could have caused this flip of altitude data?
Comments
I'm not the one to solve the problem, since I don't know enough about FT3 to really help here, but I am just incurably curious...
What happens if you click the next world button, and then the previous world button?
I know that's not a cure - I'm just curious, that's all.
If you're going to do the global math trick, then you also need to do it to the Offset (and possibly Prescale Offset) channel as well. Just applying it to the roughness channel will only invert the fractal function, not any editing that you might have made.
I have several versions of the FT3 file, and it seems that every saved version now shows inverted altitudes. I can reopen the MDR file and it shows the correct altitudes, but that would make me lose quite a bit of altitude remapping etc.. Thanks for the tip. Yeah, the offset was what inverted the altitudes (typo in original post), however applying roughness as well does not seem to do much. I tried prescale offset as well but that throws an error "Unable to select a valid destination"
The attached photo shows what has happened and attempted fix via global math
Yes, the world was started from a Wilbur-generated .mdr file, and I am positive I never ran a Burn In to Surface at any point.
Currently my work folder contains several versions of .ftw files with varying versions/names, as well as a bunch of .mdr files. I did this work about 2 years ago and I cannot remember exactly why I saved the mdrs. I think I was just playing around.
I assume I now have two options: 1) start from the original .mdr and do a burn in and then try to re-create my edits or 2) somehow re-attach an existing .mdr to the newest but wonky .ftw.
So how do binary files and ftw files play along? I tried just renaming a .mdr file to the same name as the .ftw but that did nothing. Is there any way I can take my current wonky .ftw and inject some .mdr love, eh, altitude into it or is the easier course of action to just roll back a few steps and burn in from the start?
I tried it, and I'm pretty sure it has reverted all climate data for example.
Thanks for your help so far, even if I am not able to recover my edits, I now know to burn in the mdr data before proceeding further.
Thank you so much for your kind help and patience