Just use Property.PossessedSimple() to check for non-inherited properties.That won't work because some rapiers can be the default blue ones and I need to know if they are blue because they rolled blue or because they haven't been updated yet.
Isn't the color already "stored" in the object model and icon properties? Why store it again?
Isn't the color already "stored" in the object model and icon properties? Why store it again?Currently, in the Coloured Laser Rapiers mod, I have to store the colour variable in the DoorCloseSound property
Do mention any dbmod issues, if there's any I want to make sure we fix them, including better ways to add or change scripts and args.
Does it have the ability to block vanilla event handlers?
So for instance, if casting a PSI power sends a message to the player to, say, increase their armour, would we be able to intercept this and say "ACKCHAULLY, don't do that at all"
Defining new archetypes in Squirrel could be interesting, but DML should still be good enough for most purposes (except for creating objects with physics - so I hope that's fixed)
Does Night Dive have an official stance yet on fans taking upgraded SS2EE assets and making them available for use in vanilla SS2?
Can absolutely be done, but not sure if I'll have enough time for that.eldrone
Are you going to make a Blender plugin for making animations? Like exporting .nut file with animation coordinates? Also would it be possible to edit interpolations between frames?
I am somewhat concerned about the performance impact of invoking a scripting language to perform real-time animation effects, especially things like reloading that are likely to happen in the middle of combat. Yes SCP uses scripting for animation too, but since it's an optional mod we can get away with just warning people that it has higher system requirements than the base game.
// Add the 'Shotgun' category
g_weaponAnimations["Shotgun"] <- {};
//============================================================================================================
// shoot
//============================================================================================================
g_weaponAnimations["Shotgun"]["shoot"] <- NDPointRigAnimation("shoot", 30, 100, {
// Weapon
"weaponModel" : [
{ "frame":0, "pos":[0.0, 0.0, 0.0], "rot":[0.0, 0.0, 0.0] },
{ "frame":2, "pos":[-1.5, 0.0, 0.0], "rot":[0.0, -4.0, 0.0] },
{ "frame":16, "pos":[0.0, 0.0, 0.0], "rot":[0.0, 0.0, 0.0] },
{ "frame":22, "pos":[-0.3, 0.3, 0.0], "rot":[20.0, -15.0, -30.0] },
{ "frame":28, "pos":[-0.3, 0.3, 0.0], "rot":[18.0, -15.0, -30.0] },
{ "frame":48, "pos":[0.0, 0.0, 0.0], "rot":[0.0, 0.0, 0.0] },
],
// shotgun pump
"joint1" : [
{ "frame":0, "pos":[0.0, 0.0, 0.0], "rot":[0.0, 0.0, 0.0] },
{ "frame":20, "pos":[0.0, 0.0, 0.0], "rot":[0.0, 0.0, 0.0] },
{ "frame":23, "pos":[-0.6, 0.0, 0.0], "rot":[0.0, 0.0, 0.0] },
{ "frame":26, "pos":[-0.6, 0.0, 0.0], "rot":[0.0, 0.0, 0.0] },
{ "frame":29, "pos":[0.0, 0.0, 0.0], "rot":[0.0, 0.0, 0.0] },
{ "frame":99, "pos":[0.0, 0.0, 0.0], "rot":[0.0, 0.0, 0.0] },
],
});Such a feature would technically be very easy. The reason games don't do this is because games are supposed to present a balanced out-of-the-box experience. That's why the sort of OCD tweakery you seem to be unironically requesting is usually hidden in debug menus or left to mods.And there is no reason why, if this hasn't been done before, that it can't be done in this new version.
Still fighting that save scumming addiction I see.
Are there ANY games with such absurdly granular difficulty customization?
System Shock 2 already has an extensive system for modifying all of the difficulty settings you mention. It just requires a text editor and knowledge of dml.
It's probably better for them to focus their efforts on things that aren't currently fixable by the community (like the multiplayer, etc) than to implement things the community can already do.
Yeah, I feel like being able to add new sound schemas, strings, and motions dynamically in mods would be sweet.
Impressive. And yeah, Looking Glass/Irrational did like to use Gouraud shading on large flat surfaces to crudely simulate per-pixel lighting.
Hypothetically, does this also mean you can decouple arm models from weapon models, so a mod can now reflect a player career choices/level actions? So you could have a Navy arm-sleeve for players choosing Navy, a different Psi arm-sleeve for Psi players etc? If so, that'd be fantastic news. I know there's newer SDKs for Half Life 1 that allow this e.g. mappers can now more easily have the player use scientist arms, then change them to HEV arms, when the player gets a HEV suit later on.
Absolutely, please release those tools if you can: there'll be a whole new audience checking out Enhanced Edition & thus potentially a new generation of modders, so easier to use tools, would be a godsend. Even if we have to pester Nightdive on your behalf, hopefully it won't come to that!
On another note, I know I'm the dumb, incredibly naive ideas guy, there's a ridiculous amount of complexity involved and so on. You've said here previously, that the Half Life 1 method of "put a skeletal animation joint on the mouth, with the audio file volume controlling its movement" won't work on the vanilla models, as there's not enough space on the vanilla models for such a method, which is 100% fair and valid. No point in having a solution that doesn't work both with vanilla and enhanced models!
However...for very obsessive/determined modders who don't mind deliberately breaking vanilla model compatibility, would it possible to add in a mouth joint, that's not working in the game only due to an deliberate "typo" in the code? So for FM authors or campaign modders, they can easily fix the "typo" to enable it, albeit it'll obviously only work with Enhanced Models? HL1's method allowed for both plain maps & vastly more expansive mods, to implement custom dialogue very easily. Just make the custom sound file in the required format and voila: no need to muck around with face posing, syncing up mouth movements etc like in later games. Plus it's from 1998, so it'd be era appropriate for the level of graphic fidelity Enhanced Edition is going for.
They always used object face normals. I'm guessing you mean they now use the Gouraud normals.
Seems like it would be preferable to extend the MTL syntax to allow selecting whether face or Gouraud normals are used for a material.
Well that isn't true. Its utility may be limited, but it's perfectly functional in NewDark. For example you can use it to make screens fade out when viewed off-center, simulating the display characteristics of LCD panels. I've used it to simulate snow sparkle, by making bright pixels appear and disappear on the surface as the player moves around.
Since EE is essentially using an all-new renderer, would it be safe to assume that the glitches when Gouraud-shaded and non-rectilinear textured polygons are partially offscreen no longer exist?
Looking into .dml's and having them be applied in mod order to avoid having to worry about patch-dml's of vanilla patching mod gamesys...
Personally I've been looking as much into the viewmodel (arm and guns) as I can, and concluded it should be possible to bypass weapon stuff and make custom weapons that don't have to follow the limitations of the hard coded system.
The new weapon stuff currently parses all the information from weapon properties, as well as a few additional NVscript args to build up the new viewmodel, and it's entirely in squirrel, this allows for post fire ejection of shotgun shells and can be extended to anything imaginable.
I'm doing some research into making melee weapons more easy and flexible, including an idea to have the melee weapon viewmodel pick the world model and attach it to an empty handed viewmodel, so that new melee weapons could be implemented without having to touch rigged meshes.
There'll be a toolset (collection of scripts and batch files) I hope I can release in the future to make asset-exportation way more seamless than it is now, I have it down to one .bat file to export models from blends, textures from .psd's, animations, scripts, dml's, compile a motiondb and copy them all into a modfolder, in just two clicks, and the setup is just a single config file.
They always used object face normals. I'm guessing you mean they now use the Gouraud normals.envmaps/cubemaps/incidence now uses normals of objects ... no more faceted objects
Seems like it would be preferable to extend the MTL syntax to allow selecting whether face or Gouraud normals are used for a material.you can still split up edges to get proper normals here
Well that isn't true. Its utility may be limited, but it's perfectly functional in NewDark. For example you can use it to make screens fade out when viewed off-center, simulating the display characteristics of LCD panels. I've used it to simulate snow sparkle, by making bright pixels appear and disappear on the surface as the player moves around.incidence is absolutely amazing and was completely unusable in newdark previously
Loading...