TresCom Forums

Tatu, yes... "Allos_m_A01", I'm sure this is an actual model name for some dino we don't have. We'll use skynet to search for occurances of this string on people's harddrives.

Don't forget that Albertosaur's color scheme is based on Steve Kirk's illustration of Allosaurus. The in-game model even has prolonged arms and three fingers.
https://1.bp.blogspot.com/-F4gZQphJnL8/ ... saurus.jpg

Incidentally, the same functions from Build 32 and Build 55 are still there in Beta 96... which means that executable can be used to test old PVAs.

EDIT: build 97 also has them, though at a different set of addresses, which means there are some code differences between builds 96 and 97, after all...

Now I'm going to look at builds 99 and 103...

EDIT2: well, build 99 still has them, too, but by build 103 they have already been removed and the main functions look like the ones in the source code for build 116...

tatu wrote:I find it interesting to see that the TRex PVA is using the same names as the meshes in the levels. And I also see that the Allo also is using the same name theme as the TRex.

I have send a message to see if he remembers anything if these dinosaurs were ever implemented into a level.

Well, just to point out that the code for those functions was created using MAXscripts in 3DS MAX that would generate a set of C++ instructions from the actual mesh rigging inside MAX, which would then be copied and pasted into the source code at the proper place. Only at a later time, they replaced it so that the game would use t-scripts instead, which allows far more flexibility.
So, no wonder the function names mirror the mesh names in those cases...

If anything exists, I would expect it to be either MAX files, snippets of C++ code or some early test level...

I'm guessing the Stegosaur would be this one:





...which would point at some version of IJ, apparently. Some time after the E3 (at which time, its PVA function's code wasn't yet implemented), not sure whether after build 55 (if it hadn't been included yet) or before build 32 (if it had already been removed by then).

Not quite sure if this is the same mesh or not:










And are these the early Brachis?

IMO only the first steg image and raptor-attack one show the baby model.

Tatu, be sure that text project of yours includes a reference to the Tres dino texture illustration source

Uh, I didn't mean a baby Steg... there's not even a mention of one, BTW. I meant the old mesh for the Steg, before the one we currently have.

Eh okay. I recall the first image above was originally discovered with the name "baby".

I got a reply and he can't remember if they were working or not at some point. He does believe they had models for them all tho

Well, since I just remembered that I had forgotten that the trike in the build 55 version of JR had another skeleton arrangement, here it is now:
And here's the updated listing in Excel format for all the hardcoded PVAs in build 32 with their function names:
Don't forget to use this listing for reference:
If we ever find the corresponding meshes, I can rig the missing ones too...

I just realized that this one is the one which actually corresponded to PVA = 3001:

machf wrote:And here's one I forgot to finish last night(because I got sidetracked trying to export the long-clawed raptor to TPM):

TRex_f_A-PH.zip

I used the other Green Rex (the first one was from IJ, this is the one from PH) to provide the existing alternate hardcoded PVAs, corresponding to PVA = 3002; the other one is from PVA = 3001, which is the one both Green Rexes actually use, but I haven't found another Rex using the 3002 value in any level so far... so I said, what the heck, let's use the second one, since the vertex count is the same.

And the first one corresponded to PVA = 3000:

machf wrote:Forget what I said eralier, here's the Green Rex in all its 256*256-pixellated glory:

TRex_m_A.zip

Turns out that the software I had used for decompiling the exe had skipped that section, no wonder I couldn't find anything matching the Green Rex...

Now, let's go after the Brown Raptors...

So, it wasn't 3001 and 3002 as I first thought, but rather, 3000 and 3001... the main difference being that 3000 doesn't have a working lower jaw (all of the vertices are assigned to the head bone).

3002 OTOH has fewer vertices (198 instead of 226). Retail T-Rexes all have 248 vertices, and Albertasaur has 188, so, it isn't a match for them, either...

And now, here's the "Dancing Raptor" from PVA_4, which apparently used the same mesh as the PVA_Raptor0 from the E3 TestScene but with different assignments:
Can't think of any further meshes for now... unless I take another look at Anne from Beta 96, maybe.

Too bad the dancing PVAs don't make it dance

Some questions. Does the use of difference bones make the dinosaur act different (and less buggy?).

Will using these make the dinosaur act like they do in their original build? And which bone would be the best one to "use"? The retail?

The alpha animations come from the alpha engine; the PredefinedVertexAssignments only establish how the parts of the mesh are connected to the skeleton.

tatu wrote:Some questions. Does the use of difference bones make the dinosaur act different (and less buggy?).

Will using these make the dinosaur act like they do in their original build? And which bone would be the best one to "use"? The retail?

Draconisaurus wrote:The alpha animations come from the alpha engine; the PredefinedVertexAssignments only establish how the parts of the mesh are connected to the skeleton.

Yep. The behavior would be determined by whatever activities you enable in the t-scripts, in any case...