There's no way Bethesda generated their LOD with the CK... Anyway, if they used the exact same thing, why would it take them so long to release it? I don't really think it took 3 months just for the steam workshop thing, and they could have just released an update for that anyway. Edit, about the topic: 3 seconds to load program 24 seconds to load Skyrim.esm including "Yes to all" dialogue 13 seconds for the *All list to open CPU: Q9550 3.7 Ghz Ram: 4GB SSD: Mushkin Chronos 120GB I've also never selected *All by accident. What's most interesting to me is... Loading Skyrim.esm with TESSnip takes only 16 seconds, and saving files with TESSnip is at least 5 times faster than the Creation kit, but files saved with TESSnip are about 3 times larger.
.
Let me warn you about something before we start discussing LOD. My experiences generating LOD haven't exactly been encouraging. In
Oblivion, it worked randomly and tended to clash with LOD work in other plug-ins (e.g. Just run Elswyr and Valenwood together and see what happens at the border). In
Fallout: New Vegas, it could take up to a fortnight or more of continuous running to generate full-scale world LOD and, I'm sorry, but where I come from the power quality isn't sufficient to keep your computer running continuously for that long. So, now I tuck things away below ridge-lines and try to avoid doing anything that will definitely require altering the existing LOD. As you might have guessed, I am not familiar with the current problems of LOD generation. I simply assumed that
Bethesda haven't had time to make it run properly on regular PCs.
.
When you run a sizable company servicing a profitable niche (and the directors aren't robbing you blind), you can afford to have a couple of big diesel generators, with an electrician to keep them running and give you seven days notice of any minor power fluctuations. Assemble a faraday cage directly into the building structure and, provided you cut yourself off from the power grid, you won't even have to stop for electrical storms (although it may be advisable to cut internet connections at such times). I haven't even gotten to the part where you can get someone to trick up a fast system by making some hardware alterations and trashing a few warranties in the process. The beauty of SSD technology is it need not be bottle-necked at three disk-writers servicing three platters. With the right architecture it can be so much faster.
.
And so, Bethesda could conceivably make the
Creation Kit components based on the kind of high performance systems that cannot be bought off the shelf. And, when the time comes to release an SDK, it gets bundled up into a unified IDE
et voila! Some of it works as expected, some of it won't work at all because it makes assumptions based on that special high speed architecture, and some of it requires specific procedures to be followed - only no-one's going to expect the general public to have any interest in reviewing a procedural library that would dwarf the
Encyclopaedia Britannica and is more than likely written for the non-integrated development environment that preceded the development of the IDE we see now.
.
However, I can well imagine particularly persistent bugs being dealt with by having the programmers working around the clock manually cleaning up the buggy output instead. I suppose it would be true to say that those programmers don't come bundled with the
Creation Kit. Lucky them. If some companies had their way...
.
http://www.gamesas.com/user/776788-turn-on-a-dime/ also mentioned third party software which lacked redistribution licensing Tsk, tsk! If you sell to developers, you have to expect and license for:
redistribution - anything else is naive, although stronger words may apply. In fact, a lack of redistribution licensing in products sold for profit in the developer market could be argued as cause for lack of merchantability in those products due to the requirements and default expectations of the developer market. Irrespective of any potential trade practice abuses which Bethesda may have fallen victim to, I have to concede that some things, perhaps even the LOD, may well have been generated with the third party software (perhaps because the in-house software isn't quite there yet).
.
And now for the bit I haven't got the patience for:
.
4 seconds to load the program
10 seconds while I stuff around setting the active file because the
Creation Kit can't read my mind. Actually, it is probably closer to 10 minutes because I often leave the office to make myself an espresso as soon as the program starts loading.
37 seconds, thence, to the first warning.
46 seconds from "Yes to all" to plug-in loaded.
2 seconds to load the Tamriel world-space.
28 seconds is how long
SkyCk takes to do it's thing if I inadvertently select the
All node without a filter - another excuse to go get myself yet another espresso!
5 seconds to close and no synchronization this time.
.
Last I checked, I run this on a 64 bit dual core AMD 3.0 GHz Athlon 6000 CPU with 4Gb 800MHz DDRAM, with a video card sporting 1 Gb G-DDR3-256bit vRAM on a Dual Link DVI-I/D-Sub/HDMI channel by Gigabyte 9800GT (nVidia GeForce) model GV-N98TSL-1GI. But the secret ingredient not mentioned in the hardware specs is the little 80Gb dedicated caching disk on its own SATA II channel (and Windows is currently set up to cache only to this disk). That leaves file handling on a separate channel because the operating system and programs have their own 1 tB disk on its own SATA II channel.
.
Of course, this can vary drastically, depending on system load. Let's do that again. This time, with the system just a little quieter:
.
3 seconds to load the program.
6 seconds of "mouse be nimble, mouse be quick" setting the active file.
27 seconds, thence, to the first warning.
46 seconds from "Yes to all" to plug-in loaded.
2 seconds to load the Tamriel world-space.
29 seconds if I inadvertently-on-purpose click the
All node without a filter
4 seconds to close
.
Sometimes,
Steam can take a few minutes to synchronize. I'm not sure how fast this would go under ideal conditions as I haven't been dedicating as much time to breaking in this instance of Windows. But after all that, I really do need another espresso!