Just a few questions [SOLVED]

[ghosttales]

Hello inVector forums, first off I want to say this asset is fantastic and worth every penny. So thanks for making such a great add on. I just have a few questions and I figure this would be the best place to ask them considering I'm sure there's plenty of experienced inVector users here.





I have intermediate experience with C#, but less than three week's experience with Unity if that means anything. I'm catching on quite quickly but picking apart such a massive project like the Melee controller with a program I'm not quite warmed up too is a little difficult at times to say the least! So apologies if any of this seems very silly or for lack of better phrasing "A stupid question".





First off, I'm aware you can make global objects that you can pick up and drop with the Item List. However once you make these objects using this very handy menu, how does one go about placing them in their scene or world for pick up? I've created a basic weapon and consumable that I'd like to place somewhere in my world but can't for the life of me figure out how to just drop it in my world. There's no instantiated object appearing in my assets as I expected there would be. I'll link a picture for reference!

EDIT: Didn't see there was a video covering this! Got it figured out.






My next question is about the animator and state machines. I have developed move sets for a couple more weapons such as axes and daggers, I was just wondering how inVector handles its move sets. How does invector actually choose which move set to apply, which scripts handle this, and what other things influence this?




When importing new weapon models, I have a very difficult time getting the weapon to sit in my characters hand, I watched the video on creating a weapon but I wasn't entirely sure what it meant by "Correcting the pivot" I did as was in the video but subbing it under an empty object and resetting the position but it still looked off.

Edit: Noticed the custom equip point configuration, took a little while to see it but that definitely makes placing weapons on characters easy!





And lastly, which script handles the Inventory, I notice it pauses the game once pressed. I'd like to disable this if possible. Thanks in advance for any advice



Cheers!

[Invector]

Hi man.
In the vItemManager has a field in Inspector called InventoryPrefab. In this prefab contain the vInventory with a field called Timescale while is open. Try to change this.

[shadex]

Oct 26, 2018 9:32:52 GMT ghosttales said:

My next question is about the animator and state machines. I have developed move sets for a couple more weapons such as axes and daggers, I was just wondering how inVector handles its move sets. How does invector actually choose which move set to apply, which scripts handle this, and what other things influence this?

I think of movesets are stances/movement and AttackID are the weapon attack's and combo's. The animator is split into differn't layers. All your attacks are in "Full body" and all your locomotion is in the first layer. They do this because you can overwrite a change the priority of an animation.

The animator is setup using transitions (lines) and conditions for the transitions. So the logic for an attack is (If AttackID = 4 (or whatever your Melee Weapon's AttackID is set) enter the AttackID 4 state. Inside this state it has a default attack, then conditions for strong attack/weak attack triggers. The code triggers weak attack/strong attack parameters inside the animator. This triggers the attack animation. During the attack animation a state machine behavior (script that is attached to a state) enables the colliders on the weapon, and disables them for the hit.

[ghosttales]

Oct 26, 2018 19:42:22 GMT Invector said:

Hi man.
In the vItemManager has a field in Inspector called InventoryPrefab. In this prefab contain the vInventory with a field called Timescale while is open. Try to change this.

Thanks pal!

[ghosttales]

Oct 27, 2018 8:59:20 GMT shadex said:

I think of movesets are stances/movement and AttackID are the weapon attack's and combo's. The animator is split into differn't layers. All your attacks are in "Full body" and all your locomotion is in the first layer. They do this because you can overwrite a change the priority of an animation.







The animator is setup using transitions (lines) and conditions for the transitions. So the logic for an attack is (If AttackID = 4 (or whatever your Melee Weapon's AttackID is set) enter the AttackID 4 state. Inside this state it has a default attack, then conditions for strong attack/weak attack triggers. The code triggers weak attack/strong attack parameters inside the animator. This triggers the attack animation. During the attack animation a state machine behavior (script that is attached to a state) enables the colliders on the weapon, and disables them for the hit.

Excellent! Thank you. This makes things much more clear .