ResolveThatChord

Nice contribution! A lot of modders recommend simply learning Blender 2.49 because it has the .nif scripts. It's a shame because keeping up with more current tech can open up all kinds of opportunities for new kinds of projects.

Nice work!

If you've never made a model and imported it into the game, the best and simplest thing to start with is a sword. A sword requires you to model the object, UV unwrap it, texture it, do nifskope sorcery to it, and put it in the CK. With armour/creature meshes, you need to do all that PLUS vertex weighting which requires a lot more effort and is trickier to import. Buildings don't need vertex weights but they do need collision which I'm not sure has been solved yet, and they require you to be very clever with your UV maps. As for tips? -Before you start UV mapping, make sure your topography is as clear and clean as possible. Good topography can save hours of work and frustration when UV unwrapping and texturing, and a good UV map helps make better looking textures. -Export vanilla buildings and other meshes to get an idea of how Bethesda do it. You can learn a lot this way. -Information/tutorials on mod-specific skills like importing and exporting tend to be incomplete, eclectic and spread thin. when you want to learn something put your project aside and make a simple model that will definitely work with the tutorial you find. -Also check out the Enclave modding school at TESA. -Good luck!

Funny thing is that scanning directly from real life is actually less realistic than doing it by hand. Even if you had the computer power to render something like Gollum in real time, with all his attendant physical simulation and sub-surface scattering, and a scanner/camera that picked up a real, moving object with equal detail, it wouldn't end up looking as good as say, Skyrim. This is the same kind of problem we have with rotoscoped or motion capture animation: tracing from real life gives you movements that read poorly and look weak. It takes and artist who understands the principles of animation to edit them into something decent. As for textures, there's all kind of information you need to make a realistically textured model that photographs can't really give you. The reflectiveness, the glossiness; all the optical properties of an object that work together to make that image aren't retained.

I think I'd enjoy some discussion on how it would work mechanically. Traditionally videogame bosses have some kind of pattern of attacks that you have to evade or outmanoeuvre, and a window of vulnerability in which they can be safely harmed. Some very satisfying boss fights exist in games where evading attacks is an essential part of the combat,and I think designing such bosses would be a good approach. However, you can't dodge in Skyrim, and you often can't block. I find though that the most fun and best designed bosses are the kind that aren't all about pattern recognition and skill, but rather puzzle solving. My favourites would be the bosses from Shadow of the Colossus, but again these are not at all suited to Skyrim's engine or gameplay mechanics. I'm very curious to know how you are going to attempt to create entertaining boss fights using Skyrim's mechanics. Could you explain it? It's a very interesting problem to me. Also, I have heard that Darkrider's "Reclaiming Sancre Tor" for Oblivion had some well designed bosses for Bethesda's engine, although I haven't personally tried that one yet. You might want to give it a look.

Check out the releases for the CK Basics final exams at TESA, there's some really impressive stuff: http://tesablog.tesalliance.org/?p=1668 I'm personally a big fan of Riverside Retreat by Maddox.

It is indeed possible. Brokefoot made a tutorial: http://forums.nexusmods.com/index.php?/topic/635550-showracemenu-data-export-to-npc/

Well, do you have a kitchen already? They're heaps of fun to make; plenty of resources to choose from. You may also try an indoor garden; my house mod had a little mushroom garden which worked quite well I think, especially if you get creative with custom lights. And insects.

Collision has been very tricky. You can create convex collision (statics only afaik) quite easily in nifskope following part 4 of this tutorial. However, I've also come across a promising tute for creating arbitrary custom collision meshes, which is fantastic, but I have yet to try it. Check it out here if you're feeling adventurous. Good luck!

Check out the CK basics course at TESA, that's a great place to start.

Nice work!

Okay, if you want to put it from blender 2.5x into blender 2.49 for .nif import, that's super easy; all you need to do is use the "append" feature. If you want to get it from 2.63+ into 2.49, then it's a little more complex. 2.63 has Bmesh, which has completely rewritten a lot of stuff, and the bottom line is that appending it to a non Bmesh version will not communicate the UVs, or the faces. You'll end up with a mesh entirely made of edges, and no UV data. Luckily there's a workaround: export to another format (like .obj) and import it in the non-Bmesh version. (just remember that .obj doesn't retain vertex weight data). Have fun! :teehee: By the way, your mesh looks great. Nice topology.

Unfortunately, as far as I'm aware we are currently unable to make collision of any kind, except for convex collision for statics (NOT havoked things like items). This is handled entirely in nifskope; you'll find details here, in part 4. Luckily there's a very simple workaround for havoked items: Copy the collision from a similar-shaped vanilla .nif.

Okay, the method you described works for weighted meshes (armour, creatures, characters), but not non-weighted meshes (weapons, statics, clutter). If you want to import a weapon/unweighted mesh, open nifskope and simply cllick flie, export, Export .obj, and choose the directory you want to save it to. Then in Blender (or max, I suppose. may work differently) click file, import, wavefront(.obj), select the file you just exported from nifskope, and bob's yourr uncle. This will also work for weighted meshes, BUT the vertex weight data will be lost, meaning it will no lpnger animate.

Nice work! What programs did you use? What's the polycount? Also: Red tie! Red tie!