February has been mostly spent sorting out all of the various odds and ends of the major release of last month. Bugs and customer problems have been getting sorted and triage-d, and a lot of kinks have been getting worked out on the new website.
I’m working to better surface the workflows for using World Machine with the various common game engines (Unity, etc), as this is a very common question that we can do a lot better at addressing. Also good news — the Unity splatmap import script is fixed for the latest version of Unity…
I want YOUR workflow
Very soon I’m going to pour some significant dev time into workflow related issues and features, and I’m all ears to hear from all of you.
- What would make World Machine work better in your production pipeline? Are there file formats, features, etc that you need to make things work, or that would make your life happier?
- What are the most painful steps when you’re working with terrain you’d really like to be able to avoid?
I can’t promise that I can get to everything that’s brought up… but I’d love to do what I can. Feel free to post in the comments or just email me at email@example.com.
The crash dump files that ya’ll have been submitting have been very helpful, so thanks for that!
I’m happy to say that I’ve identified and fixed some of the major crash and usability issues that folks have been running into. Build 3020 will address them. Software will never run out of innovative new ways to fail 😉 but hopefully we can keep things stable and productive the vast majority of the time.
What’s next on the Dev Channel?
The next major new feature release is still roughly on track for an April release. More to come on this later!