Pretty cool!
I was wondering if it would be possible to use (as in change states) placeables like this without necessarily flagging them as "usable" in the toolset. I've been looking for a way to make levers and buttons move via script instead of forcing them to be highlighted whenever someone hits "Z".
I also downloaded PJ156's placeables.2da file from his cornucopia, but I see that it's full of spaces instead of tabs (which would explain why it's so huge). Isn't there another version with tabs instead of spaces?
I probably did something wrong, or don't have the credentials, because the range 12880-12999 is again shown as "available".
& thanks for looking into reserving Ranges; it really is on the priority list for a project like this, i believe
Good news, the 12880-12999 range is now reserved for this package. 
By the way, due to SoZ containing a duplicate line 2534, I'll start at 12879 (that one off numbering explains why Lance didn't get the right appearance during the tests).
I also reserved the range 801-825 for the trapdoors (in doortypes.2da); so the override version should be easy to install (just copy/paste in your existing 2da).
I'll need a few days to reset the blueprints and update the placeables.2da, but I'll start right now.
Good news, the 12880-12999 range is now reserved for this package.
I also reserved the range 801-825 for the trapdoors (in doortypes.2da); so the override version should be easy to install (just copy/paste in your existing 2da).
I'll need a few days to reset the blueprints and update the placeables.2da, but I'll start right now.
Hi Thierry,
UPDATE: The line *is* duplicated (as you say), but it did not show unless I used a basic text editor, like notepad. HOWEVER: I have removed it from my own placeables.2da by the looks of it ... after checking my own file with notepad!I wonder if I removed the duplicate line some time ago, as I do have SoZ, but I don't have that duplicated line. So, just to be clear, when you start your pack at 12879, will that be 12789 for me too? (Remember, I don't have the duplicated line. I must have removed it some time ago.)
Just as I got it all working from 6000 as well .... 
EDIT: I just double checked my OC SoZ placeables.2da (zipped in data folder), and it does not have the double entry. Do you have some other package (MoW perhaps? - I don't have that) that doubles the entry. Or, maybe some SoZ packages don't have the double entry? (I have diamond and non-diamond versions, but cannot recall which version is installed.)
Any ideas?
Cheers,
Lance.
suggestion: create the pack as if everything it relies on is correct
that is, don't go second guessing things, 'cause that's just putting a kludge on top of an error ...
right?
EDIT: I just double checked my OC SoZ placeables.2da (zipped in data folder), and it does not have the double entry. Do you have some other package (MoW perhaps? - I don't have that) that doubles the entry. Or, maybe some SoZ packages don't have the double entry? (I have diamond and non-diamond versions, but cannot recall which version is installed.)
nwn2daEditor appears to correct mask it on load
check it with a text editor, Lance.
nwn2daEditor appears to correct mask it on load
check it with a text editor, Lance.
suggestion: create the pack as if everything it relies on is correct
that is, don't go second guessing things, 'cause that's just putting a kludge on top of an error ...
right?
Hi KevL,
So, how does this work then, bearing in mind some people may or may not have the extra line? Wouldn't it also be dependant upon the editor they are using to edit the file?
E.g. I have SoZ (whose official 2da has the extra line, but my own does not). And if I used editors other than notepad, I would be none the wiser about the extra line anyway ... and so where would the editor put the new lines?
Do you see my confusion?
Lance.
i don't know, Lance. idk!
i've gotten used to having an attitude: build it however you want, & I'll fix it however I want.
so,
[edit] look at it this way, there's a row number that's duplicated in the .2da
So, how does this work then, bearing in mind some people may or may not have the extra line? Wouldn't it also be dependant upon the editor they are using to edit the file?
The line number itself is not used by NWN2, it's just here for us human readers. However, its *position* in the file is important. So, if you removed/renumbered the second line #2534, your line #6000 will actually be in position #6001 (remember the first line starts at 0).
However, most (if not all) packages created based on SoZ placeables.2da will have line #6000 in position #6002.
This explains why there was this one off issue during the tests, and as KevL said:
that is, don't go second guessing things, 'cause that's just putting a kludge on top of an error ...
I'll just start at line #12880, which will in fact be shown as #12881 in the toolset, but actually be located at position #12882 since the first line is numbered 0.
The line number itself is not used by NWN2, it's just here for us human readers. However, its *position* in the file is important. So, if you removed/renumbered the second line #2534, your line #6000 will actually be in position #6001 (remember the first line starts at 0).
However, most (if not all) packages created based on SoZ placeables.2da will have line #6000 in position #6002.
This explains why there was this one off issue during the tests, and as KevL said:
I'll just start at line #12880, which will in fact be shown as #12881 in the toolset, but actually be located at position #12882 since the first line is numbered 0.
i don't know, Lance. idk!
i've gotten used to having an attitude: build it however you want, & I'll fix it however I want.
so,
[edit] look at it this way, there's a row number that's duplicated in the .2da
Yes, thank you for the additions. Its good to have new capabilities.
Good stuff! Very nice to have more animated placeables.
OK, I just reserved the range "12880-12999".I also downloaded PJ156's placeables.2da file from his cornucopia, but I see that it's full of spaces instead of tabs (which would explain why it's so huge). Isn't there another version with tabs instead of spaces?
I fixed that if you want to use the 2da.
When I get to the next update I will include this is that is okay?
PJ
Absolutely!
By the way, as I added the 6880 lines I needed with Excel (quicker, and saving as tab separated file), I'm afraid I used the range 12880 to 12940 (and even more, as I've already added two more placeables today - still work in progress though:
12941 is a stone bridge (yes, RWS and others have made some already, but I found this model quite nice...
and it can be used several times for a longer bridge!
But the bridge I had in mind (#12942) is this one!
Now that I got the walkmesh right (curve, not plane )
I'll start working on making it move (wind, weight of the creature)
Hi Thierry,
Any updates you make to this ... or as new haks ... I welcome if you are able to make them available.
Like you, I need to get back to the module proper now, but keep me updated of anything you do new.
Again ... Many Thanks !
Lance.
He he he, I got side-tracked again and my campaign hasn't progressed at all.
But I've got tintable chests, tintable coffins, new chests, new coffins and more importantly slower animations for some levers and other placeables!
Gimme a few days to clean the folders, make some more testing and upload the new packages.
He he he, I got side-tracked again and my campaign hasn't progressed at all.
But I've got tintable chests, tintable coffins, new chests, new coffins and more importantly slower animations for some levers and other placeables!
Gimme a few days to clean the folders, make some more testing and upload the new packages.
Here's some feedback for 4760:
And for PJ:
Maybe I didn't know how to add mipmaps at the time... Does it look better with these textures?
About the close sound out of sync, do you mean the animation is longer than the sound?
Maybe I didn't know how to add mipmaps at the time... Does it look better with these textures?
That's much better.
About the close sound out of sync, do you mean the animation is longer than the sound?
Yes; enough to be quite noticeable.
OK, then I've got two options: either quicken the animations (doubling the speed) or find a slower sound.
Retour en haut