Table of Contents
News for June 2006June 30L3DT 2.4 is available!Hurrah! It's been nearly three months since the first beta-release of L3DT 2.4, and I'm proud to announce that it is finally ready for public consumption. Many thanks go to the cast of beta-testers for their assistance and patience with debugging, and also for their numerous suggestions for improvements. ChangesMost of the changes since the last 'stable' release (v2.3d) are recorded in the release announcements for v2.4 beta1, beta2, beta3 and RC1. Here is a quick round-up:
In addition to these changes, there have been innumerable bug-fixes and other tweaks to the algorithms or user-interface. How to get itThe L3DT Standard Edition is available for free on the downloads page. Licenses for L3DT Professional Edition will go on sale on Monday the 3rd of July at a cost of $25 USD per-person or $60 USD for a multi-user license (up to five users). Evaluation licenses will still be available on request after this date, but the lifetime of new keys has been reduced from six to three months. Users who have previously registered for 365-day or 180-day trial licenses may download the new version (from the pro downloads page, consult your registration e-mail), and freely use it until the expiry of those keys. What is next?The next big thing on the cards is a better map-editor interface (long overdue!), and support for editing the heightfield, attributes map and texture map. The map-display may also be re-done too. In any case, I'll be talking a break from development for the next little while to rest my weary brain and focus on some other 'real-world' commitments (eg. work). In this time I will, of course, continue to provide bug-fixes if they are required. Feedback or questions?Please leave feedback on the community forums. June 27Vale Tony SandersonWe will miss your good humour Tony, your helpfulness without limit, your honesty, your friendship and company. You made the world that much more interesting a place to live, not by trying, but by simply being. Friday lunchtimes, flat batteries, strong, hot lattes, wrong extensions, lost packets, funny e-mails, ugg boots at work, commie rants from a fellow traveller, and let's not forget perl. These things, and so many more than I dare think of now, will forever remind me of a dear colleague, and a dear friend, dearly missed. Farewell Tony, may you rest in peace. June 22L3DT 2.4 Release Candidate 1I've uploaded what will hopefully be the last pre-release of L3DT v2.4. This version has a few more bug-fixes compared to beta3, re-re-jigged erosion, and better default settings for the design/inflate terrain generator. I've also changed the texture size limits for the Standard Edition (max is 4x texture res, or 2048×2048 pixels). If you find any bugs in v2.4 RC1, please let me know as soon as possible. Cheers, Aaron. PS: The RSS feed for this news weblog system now works properly, and can be found at: June 2011 days to go!Back in February I nominated the 1st of July to be the release-date for L3DT 2.4, which is eleven days from now. It looks like the release version is ready to go now, but I'm going to keep to that date anyway, just so that I can say I was exactly on-schedule (it doesn't happen often). Sooo…not much to do now, except maybe indulge in some navel-gazing1). Selling software. Selling my hobby. It's a bit of an eerie feeling. When I started this project, way back when, L3DT was just a little program to make a map for an RTS game I was developing (or rather, thinking about developing). At that point I didn't consider the possibility that L3DT would ever be released to the public2), much less sold to the public. It did what I wanted, and nothing more. It was really ugly, and damn-near impossible to use if you were not, in fact, the programmer himself. Now it's a product. It has to do what other people want it to do, in the way they expect it be done. It has to have an intelligible, no, intuitive, user-interface. It has to check entered data, it has to work on other computers, it has to have sensible documentation, and it cannot ever crash. In fact, it shouldn't even throw errors. A warning might be acceptable, but not an error. Lord no. You don't pay money for errors. It can be quite a responsibility to meet those expectations, particularly so when it's your hobby, not your job. Wow, that makes the whole thing sound miserable and unrewarding. The reality is quite the opposite. Delivering a program that people use, that people like to use, is just an awesome feeling. I honestly get a vicarious kick out of seeing what other people do with L3DT. Making their own games, making their own worlds, making art, having fun, being creative, pursuing whatever their hobby happens to be. Compared to that warm-and-fuzzy feeling, the annoyance of having to 'fix' a bug that's not a bug, or write some bizarre file-exporter, or even re-do a dialog that's a bit hard to use, is utterly trivial. It's a good deal for me, and I shan't complain. Cheerio, Aaron. PS: I nearly forgot - The very first of the 6-month trial keys for L3DT Pro will expire on the 9th, so this release won't be a moment too soon. June 1L3DT 2.4 beta3 is availableThe third and final beta-release of L3DT v2.4 is available for download. As usual, a summary of the changes is provided on the release history page, and a description follows: Bug-fixesThe main focus of this release was to fix bugs in preparation for the final L3DT 2.4, and indeed there were many bugs to fix:
Further patches may be issued over the coming fortnight to address any bugs that may be identified by users. Textures and bump-mapsAs previewed last month, the bump-mapping and texturing algorithms have been improved to give greater realism at high texture resolutions. Pretty screenshots of this may be found in the gallery, and more are on the way. I will, at some point, update the algorithms pages to explain how the new system works (but not right now). ClimatesI've added a new 'desert' climate and revised the 'artic' and 'temperate' climates. These aren't the finalised production-versions, but they're pretty close to what you can expect from L3DT release 2.4. You may also notice that I've removed the 'arid', 'temperate (deluxe)' and 'temperate (basic)' climates. The reasons for this were:
I will try to re-build 'temperate (basic)' for v2.4, but I make no promises as to the other climates. Climate file changesIn previous releases, climate files were located in [Resources\Climates] and textures were in [Resources\Textures]. This arrangement made it difficult for users to copy and re-distribute climates, so it's been changed for beta3. Now textures may be in the same directory as the climate file, so you can easily zip-up and e-mail a climate, textures and all. The down-side of these changes is that the file-paths in old climates are broken. If you have any custom-made climates, you will need to manually re-set the correct file paths. While you're at it, it might be a good idea to create a new directory for each climate (see the examples provided) and copy the relevant textures into those directories, thereby making your climates readily 'portable'. In addition to these changes, the weighting of the texture-blending and bump-mapping system have been re-defined, so things might not look exactly as they did previously. Similarly, the perlin-noise frequency of each land type is now relative to the size of a heightfield pixel, rather than 1/16th of it (as in beta2). Over the next week or so I will revise the user-guide to reflect these changes and explain exactly what all the numbers mean. Next releaseThe next release will be the 'final' L3DT 2.4 in about two weeks time. It is highly unlikely that any new features will be added at this stage, so the only changes between beta3 and final should be fixes for any bugs still in beta3, plus a few more climates. As foreshadowed in January, the Professional Edition will no-longer be free for L3DT v2.4. Licenses will be available at cost of $25 (US dollars), with free upgrades provided up to 18 months after purchase. The accepted payment method will be PayPal. Evaluation licenses will still be available on request, as before, but the lifetime of such keys has been reduced to 60 days (from 180 days). These changes do not apply retrospectively, so older 180- or 365-day keys are still valid. FeedbackPlease leave your comments and suggestions in the community forum. Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Share Alike 3.0 Unported
|