Search options (Page 18 of 20)

www.ufe3d.com, then scroll down to Navigation and click Installation.
(direct link: http://www.ufe3d.com/doku.php/installation)

I'd bookmark this page.  I was coming here about 5 times a day in my first few weeks getting to know UFE .

For your animation question, as long as you don't trigger that animation, missing said animation should be fine.  You can see this by disabling Parry and removing all parry related animations.  Same should work if you remove bounce animation and ensure no attacks cause bounce.  There might be an issue with a couple standard animations that you never see, but using a default animation for that should work as a quick fix.

-----------

The way I see it, there's three things from Smash you'd want to look into.  Attack/combo system, health/percent system, and the platforming system.

Attack/Combo system
The attack/combo system should be fairly easy to copy, with minimal code changes.  It's mostly your attack data, and a low-ish movement friction.  If you want DI for falling characters, you'll need to alter code in ControlsScript for that (it is a bit of work, but shouldn't be too hard).  You'll probably want to add a new variable in CharacterInfo's PhysicsData for DI (controlling how much influence they have with DI), and use that in the ControlsScript DI code.

Additionally, check this post about editing the combo counter to be live updated instead of after the combo finishes.  If you want to be exactly like Smash, you can remove combo text display altogether.

Health/Percentage System
For the health system, you'll definitely need to alter code, and you'll also need to integrate it into the knock back physics of each character.  Essentially it's a new health system.  I'd create a new variable for hit percentage, don't use Life Points as that could create more issues.  Those variables should be added to CharacterInfo, but you'll need to change corresponding functions in ControlsScript (each hit adds percentage instead of damaging Life Points, and percentage also affects knock force).

Oh, and slightly related would be the rounds system tweaked with stock/time instead.  Unless you want unique stock values for each character, I'd put this into a global config class, probably Round Options.  While there, you can also change Spawn positions from float to Vector2 (for height) to prepare for platforms...

Platforming System
But to me, the hardest part is the platforming aspects (multiple platforms you can jump through from below, and the kill zones at far edges of the world space).  UFE is base on traditional 2D fighting game mechanics, which doesn't have multiple grounds.  You would need to completely alter how UFE handles jumps and registers ground states.

For the killzone, your best bet is to create a manager that tracks all on-screen character's positions and just triggers appropriate KO animations/functions when they reach stage limits (which you'd have predefined in the manager script - could also be specific to the stage).  You won't be able to use Unity's OnTrigger since there are no rigidbodies / colliders on UFE characters (hitboxes aren't colliders).

-----------

Looking at the video MisterMind posted on Unity forums, they managed to get everything except the multiple platforms bit.  However, they got the killzones (at least at the bottom), so that's a good start.

There's also this post from PsychoGames a while back.  He's made a small start by looking at IsGrounded() in PhysicsScript (where I'd start looking to), but not sure of his progress since.

Honestly, each of these systems is pretty much worthy of their own thread!  Normally, I try testing ideas myself and posting my findings.  But "make UFE like Smash" isn't a 10 mins coding task .  It's likely going to take a while to get everything working right.  If you can design your game to work without multiple platforms (like the video), then it's probably not as daunting a task since you're not not altering so much base code.

Good luck!  If you're desperate, or get really stuck, keep posting here and I'll try to pitch in where I can.

Yeah, I thought you might have already considered mobile friendly assets.  I was posting more to cover all bases and help others that might be having issues.

There's a story mode with a new loading screen, that's scheduled for released once Unity 4.6 is released.  So it might be worth holding out for that if your project isn't due anytime soon (we're all waiting on the Unity 4.6 GUI update, basically).

Oh, you're building to mobile.  That makes a big difference.

Let me try building to iOS.  It's been on my to do list for a few days now, so it's about time I tackled it .  I'm in +11 GMT, so hopefully you'll see something by the time you get up (I'm assuming you're in a US timezone).

This is a fairly hard one to answer without seeing the project for myself.  But let's try and see what we can find .

• Is this delay only on your custom project and not on vanilla UFE?

• Is the delay also present when using Start Game Immediately option in Global Config? If no, then this would mean it's not the characters/stage that's causing the issue, could be one of the select screens.

• Have you made any modifications to default scripts?  I see you've done something to ControlsScript, which is probably the most likely offender here as you've noticed.  Any other changes to it?

• Do your characters have large move sets?  This is probably the only thing I can think of, outside of modding, that could cause such a delay.

• Have you done any isolation tests?  i.e.: load with your stage, but use default UFE characters; load with default UFE stage and your characters; both with/without start immediately option…

Essentially, I'm trying to figure out what could be causing the delay.  I'm hoping it's not something specific to your machine (running out to hdd ), since I've never noticed any lag issues on my projects.

Oh, yeah.  I forgot to mention.  For this script to work, the weapon bone can't be animated.  So it must be just a static child of the hand bone.  The hand effectively does the weapon's animation.

This will be fine for swords.  But things like bo staffs or nun chucks, where they can move within the hand, it wouldn't work out of the box. 

Accommodating animations should be possible.  If you get stuck on implementing it, post back here and I'll see if I can figure it out.

We're still in debugging phase, so it's hard to tell exactly when.  But it should be soon now.  Sit tight!

That is correct, projectiles do not mirror. 

Test your projectile in Scene view by dragging it around:

• If trail follows behind it correctly, then you're fine.

• If the trail does not follow behind and stays in set orientation, either modify particle effect so it follows behind or you'll need to modify some code to get it working.

Looking at ProjectileMoveScript.cs, I think adding:

transform.localScale = new Vector3(transform.localScale.x * -mirror, transform.localScale.y, transform.localScale.z);

// below line is in case angled projectiles don't mirror correctly
transform.localEulerAngles = new Vector3(transform.localEulerAngles.x, transform.localEulerAngles.y, transform.localEulerAngles.z * -mirror);

in the Start() method just after the transform.Translate() line should work.  But depending on how your projectile is generating its effect, this might not be enough for it to look right.  Yours looks to be 2D, so this might work for you.  Just make sure the pivot of the projectile object is the middle of the ball part and not the flame part.

EDIT: added line for angled projectiles.

Ah, I think I figured this out.  Do you have your Right Hand assigned in your hitbox set up?  The projectile is trying to instantiate from the right hand, but if no right hand has been assigned then it will default to world 0 on instantiating.  I just tested my projectile by assigning to Custom 7 which isn't assigned to anything and got the same results in your video.

Since you have two heights of fireballs, my guess is the yellow one isn't a prefab at world 0?  Check all child objects of your prefab.

I picked up Prototype yesterday, so thought I'd give this a try.

Prototype (and I assume ProBuilder as well) uses their own system for generating the meshes.  This is good, in that it helps them create a nice fast and simple workflow; but bad for us because when we try to create prefabs out of it it just doesn't work like you'd expect.

From what I could figure out, it looks like Probuilder needs to export the mesh for you to be able to save as a prefab.  The only way I could get it to work in Prototype:

• Make your Prototype mesh, then goto Tools -> Prototype -> Actions ->Make Asset, to put the mesh into the heirarchy.

• Then Actions -> Strip all pro builder scripts in scene.  This will remove it from their system and make it a normal Unity game object.  Without this step, Prototype will take control of the mesh when the prefab is Instantiated into the scene and you won't be able to see it or add the mesh data into it.

• Rename Mesh and drag into Project folder to create prefab.

• Delete scene mesh.

• In Project folder, look at prefab and you'll see it's missing the mesh data in Mesh Filter component.  But you should have that mesh data in your Assets folder (mine was pb-Cube[Detail]-XXXXXX, so look for a similar name).  Just drag that into the prefab's missing spot.

After that, just making sure you've copied the ground Plane from the Training Stage, and it should come up as a level.  I was able to get this to work, but the workaround just felt really dumb to do.  Not to mention that having removed all Probuilder scripts means you can't edit the mesh again.  Which completely destroys one of the key features of Probuilder. 

I'm hoping this is just a Prototype limitation and not in Probuilder as well.  I can understand them wanting to keep major features out of the free version, but this makes it practically useless if we can't prefab their meshes.  I'm sure I'm missing something, but what ever the step is it's not entirely obvious...

When you say jump vertically, do you mean they can't jump forward/back, or something else?

It looks like a transform position issue in Max.  I haven't used Max in a while, but in Blender there's a common issue where if something is not at origin then it's offset during movement.  You just need to apply it's position to fix it.  Not sure what the Max equivalent would be though.  Hope this helps at any rate.