-
Totally off topic... But the lead animator from runic is here, in our humble forum
I'm sooo exited. You honour us @Matthew Lefferts, from all of the Torchmodders a big welcome.
-
-
o m g
I am stunned. I am giddy. "Welcome @Matthew Lefferts " is all I can think of atm. You really do honor us with your signing-up and posting here!
@Lord Nyriox if we need to reduce the polygons on the models there's a simple way to do that in Blender. I'll give it a shot this weekend and share the models with you. -
-
It's also highly likely that characters like Ordrak exceed the bone count for hardware skinning, so if you have any flags in there for that it would cause it to crash.
@Matthew Lefferts, @Phanjam:
Well I'll be danged. Disabling "hardware skinning" DID solve the problem. Just goes to show you that hardware acceleration doesn't always work…I'll post a screenshot shortly.
EDIT: How do I take a screenshot in-game? I removed the built-in Windows tools for it… -
-
EDIT: How do I take a screenshot in-game? I removed the built-in Windows tools for it…
Shift + F9 then search for them in the appdata folder for Torchlight files. -
-
-
Haha! There u go
hope he doesnt get stuck in some of the narrower passes! 
-
-
@Phanjam:
Ha! As if.
During my early testing for the Dragonkin Overlord, I increased his scaling value to 10 (no joke). He had a beautiful Godzilla effect (with a lot of clipping through buildings in town), but he walked the narrow spaces just fine.
Also, pets that get stuck eventually skip across the map to where you are.
Now, does anyone have any advice for backporting his skills?
EDIT: For now I'm going to experiment with mapping Ordrak / Zealot skills to the Vyrax animations. Likely I'll also start experimenting with AI support soon.
Thanks again,
– Nyriox
-
-
...does anyone have any advice for backporting his skills?
Normally just copying over all the contents of his skill folders will do. But you'll want to look into any .LAYOUT files his skills use, to see what they point to (the sounds and particles mainly) and that those are present / copied over as well for the skill to use. Within the particles, do check that all their components are present/copied over as well.
-
-
But you'll want to look into any .LAYOUT files his skills use, to see what they point to (the sounds and particles mainly) and that those are present / copied over as well for the skill to use.
Ah. So all those "Resource" references I found (and didn't recognize) in the .LAYOUT files pointed to particles. That certainly answers my question.Within the particles, do check that all their components are present/copied over as well.
Well, then. I'd best get on it. ;}
– Nyriox
-
-
So all those "Resource" references I found (and didn't recognize) in the .LAYOUT files pointed to particles. That certainly answers my question.
What will alert you to look into further are all those lines that have <STRING>DESCRIPTOR:. These are things the .LAYOUT will need to execute properly. Descriptors can be...
<STRING>DESCRIPTOR:Camera Shake
<STRING>DESCRIPTOR:Damage Shape
<STRING>DESCRIPTOR:Layout Link Particle
<STRING>DESCRIPTOR:Timeline
<STRING>DESCRIPTOR:Sound
<STRING>DESCRIPTOR:Unit Spawner
(I think that's it, but there may be others)
The Particles should be easy to find since they are referenced explicitly by their .layout filename with a full path to boot.
Sounds are a little tricky because they are referenced by their GUID. You will have to find that GUID in one of the several .DAT files in the MEDIA\SOUNDS folder (player.dat, skills.dat, etc.) to find out which actual sound files are being used.
I forgot to mention in addition to the Particles and Sounds, the Unit Spawner is important too because it spawns any units (duh) that the skill wants to call.
Within a <STRING>DESCRIPTOR:Unit Spawner "block", the unit referenced is the one in the line <STRING>Resource:. -
-
Hellooooo! Looks like the issue was with the hardware skinning bone count! I remember dealing with that too. Glad we could figure it out together. Reach out to us like that when you get really stuck. Brian Ward on our community relations team saw the issue sent to us and reached out to me for help. Messages usually do reach us.
I always wanted to be able to talk to people directly before I worked in games, and it's awesome to follow through on that, on the other side. -
-
@Matthew Lefferts:
Hellooooo! Looks like the issue was with the hardware skinning bone count! I remember dealing with that too. Glad we could figure it out together.
Yeah, I had no idea such a limit even existed. I would have thought the vertices would affect skinning more than the bones.Reach out to us like that when you get really stuck. Brian Ward on our community relations team saw the issue sent to us and reached out to me for help. Messages usually do reach us.
That was pretty much what I was thinking when I sent the support ticket. We might have figured the issue out eventually, but it would probably take months before any of us tried fiddling with the game options.
Since we were all stuck running around in circles (and I'm not afraid to ask for help), I felt that someone who helped develop the game might have a better understanding of the issue we were facing.I always wanted to be able to talk to people directly before I worked in games, and it's awesome to follow through on that, on the other side.
It's awesome for us all too! Thanks again for helping out!
If you're interested, I should have a new version of the pet mod I am working on released in the next couple of weeks (backporting Skills is a new challenge). ;}
See you around,
~ Lord Nyriox,
Necromancer of Torchlight
-