GreatLucifer

To clarify a possible misunderstanding, I can't actually help at the moment (don't even have Oblivion or the CS installed at the moment), just here for advice. As for the mannequin spell, I can't say. Don't have the mod. It is however probable that that script relies on the TAI command, which in turn would make it probable that no hits at all are registered. And don't get me wrong, I'm not saying it's not possible or anything, just... there's no easy-fix. But perhaps the mannequin spell'll work, or obse (not my area), or something else. Or ofcourse, settle for some form of compromise.

If the vases/pots are activators, it should be possible (but with a drawback). There are already vanilla examples of how a static can release havok, like traps. Thing is, the OnHit blocks on activators only activate from spells and arrows, not meleeweapons. They could also be made creatures, in which case they'd react to all forms of attack. Skeletons are a good example of how a death-animation can release havoks. Script to keep them inactive is simple enough too, but here the problem is that they will be detected by detect life. Just sayin'...

Why not make the compass and needle different meshes, so you can manipulate only the needle via script (which is easy enough; put a script on the (needle-less) compass to move the needle to his exact position, and freeze it's rotation)? Just in idea from the top of my head, but I'm quite sure it'd work with vanilla scripting...

Actually, his name is Behemecoatyl :ninja: http://www.youtube.com/watch?v=I7Y_Zm2bXmY And yes, this would be completely awesome. But I don't think it can be done. As a matter of fact, I think that's the reason it hasn't been done before too.

Hello Lord Frostcraig, long time no see. Glad to see you're still with oblivion, it's getting quieter and quieter around here. Just curious, but I see Alonso isn't mentioned in the credits. Does this mean you're not using his resources? Or did they get lost or something...? The piece of heart especially would make a great addition...

Apologies, you seem to have misunderstood. Perhaps I should rephrase: We have new meshes, we're trying to create a new nif. We have the new meshes, one for the desk, one for the drawer, and one for the little door. We have collision meshes for them all too. They're just all in OBJ. NifSkope appears to have an import-obj option, which appears to work. And I already somewhat work with NifSkope, indeed with copying and adjusting branches and such. But I have no idea how to create a new nif / switch out (and add) collisionmeshes. This is the first big hurdle. How to give a certain mesh (branch) a collisionmesh and adjust its properties... Second, how to constrain that little door (for clarity, the desk has three drawers on the left and one little door (cabinet) on the right). I have looked at many other constrained meshes, anything from shopsigns to tapestries to the scales, but I still have no idea how to adjust / copy / whatever this.... :( As in amnesia, we want to make the drawers havoked, so you can actually pull them out. Same (but constrained) for the little door. No animgroups. I have looked for tutorials and such on the subject, but all I seem to find is either not about this or technical to the point of me not understanding. Please understand, I (we) have no idea what all this jargon means. I'm not even sure what they keep meaning with things as ninodes and nitristrips.... :psyduck: Any help, link, or especially steps on the subject would be veeery appreciated. Thank you, and happy new year, Lucifer

Hello peoples, I'm here with a friend, and we have some questions about NifSkope. He's rather good at making meshes, and made an amnesia style desk, which we want to behave similarly in oblivion. Problem is, we have no idea how to create a new mesh in NifSkope... We want the drawers to be havoked, and the little door constrained. We figure this ment that the desk itself would need a red (static) collisionmesh, the drawers blue (havoked) collisionmeshes, and the little door a purple (like traps and signs and such, a constrained havoked) collisionmesh. Furthermore, the door would ofcourse have to be restrained (like a hinge). So... How do we... -constrain one mesh (branch) to another? -give certain branches certain collisionboxes (and 'choose' their property (colour))? -actually put it all together (like the import of obj, etc)? Or more basically, do all this...? Any advice, links, or anything will help. Much Obliged :ninja: Happy holidays, Lucifer

Well, besides the max of 1 companion, I'm already quite content with the Skyrim companion-system. Rather well-made, if you ask me. I don't actually know neverwinter night (let alone 2), so am unsure of what is actually being asked. But due to this; I was under the impression it might be a number-problem. As for actual commands and such, it can ofcourse be done, but would indeed not be as simple... Ah well :psyduck:

@ Balakirev "...manually set a series of wander-to-x markers for each one of these actions..." This method simply mimics the follow package without the max-set of (iirc)7. Actual commands would ofcourse require additional effort. And indeed, the small-corridor-I-want-to-go-back-but-my-companion-is-blocking-me-problem would occur with this method. Makes sense really, as a normal follow package would have that problem too and all this does is mimic it :P @David Brasher What...? First-off, how many people you can have around without lag is computer-dependant, so I will not discuss such things (as I did not do in the first place, nor has it anything to do with this). Secondly, there is an actual maximum defined that governs the maximum amount of AIs following a single target (7 iirc). This is to get around that. Never said it would. Does circumvent a restriction, though. Indeed I do. As I said; "I just use one called 'gamemechanics' containing all these little sort of codesnippets, to keep the amount of processing scripts down", translated; I only have one running questscript, set to 0.5, containing all these forms of gamemechanics, and therefore (overhere atleast) never noticable. About as 'eco-friendly' as it gets.

Well, though those mods may not use it, there actually is a method to circumvent that. And rather simple at that.... Trick is, the package you'd normally give npc's / creatures you wish to have follow you, would be a follow-player-package. Instead of this, make it a wander-to-x-marker package. Than have a quest script (I just use one called 'gamemechanics' containing all these little sort of codesnippets, to keep the amount of processing scripts down) which moves the x-marker to the playerposition. This way, they're technically not following the player. Appears that way, but they're not :psyduck:

I will, thank you :thumbsup:

Wow... again, thank you. That is a lot to digest.... I will get started tonight, with a bit of luck it'll actually work :D I will, thanks. Cause if I understand correctly, this'd allow me to make something like (for example) a doorcollision (wall with hole, basically...), which'd allow me to make even more :) I'll start the 'digesting' tonight, when I have a decent computer and no people around.

Wow... well thank you, that is indeed what I ment. I'll try it out, sure it'll work. Did you just say you adjusted the shape of the collision in NifSkope....? And adjusted vertices... in NifSkope? If that is possible, could you please show me in the right direction on how to do that? Might allow me to make far more.... As far as the exterior-tileset goes (if anyone cares), it's going rather well. I'm actually suprised I haven't seen this done before... And ofcourse, have a kudo :ninja:

If I'm not mistaken (and I could be wrong here..), simply renaming the file should do the trick. Original filenames (which have to be used) can be found using the BSA extractor.

You're welcome ;) Indeed, very true. One of the few things that keeps bothering me... I can't reliably intercept 'death'. It seems to work on occassion, but always bugs out sooner or later. Quite a shame... :facepalm: For reliable 'death'-interception, I can therefore say very little. I'm one of those people who doesn't (and can't) use OBSE. Yes, we still exist :ninja: