Search options (Page 1 of 10)

immortalfray wrote:

I’ve been away from UFE since 2.0 initially came out. So for some reason it’s removed from my asset list and it looks like I have to purchase it again?  I still have a working build of 2.0 that I wanted to try and implement cinemachine in for story mode cutscenes.

No, you don't have to purchase it again. If you still have your invoice number I recommend contacting Unity at support@unity3d.com.

immortalfray wrote:

So with the new 2.0 coming out, how will network play affect the personal changes I've made to the core of ufe?  I'm very novice when it comes to network code so I'm training up in prep for 2.0.  Will I be able to use the core changes I've made and have them come across the net?  Mainly I've added image effects to moves and powsr/speed multipliers as well as a dynamic power guage.

Good question. I'll try to answer the best I can.

Say you have a multiplier that changes the damage of attacks based on the remaining life points. Before, you had something like this:

public class ControlsScript : MonoBehaviour {
(...)
    public float afkTimer;
    public int airJuggleHits;
    public AirRecoveryType airRecoveryType;
    public bool applyRootMotion;
    public bool blockStunned;
    public float comboDamage;
    public float dmgMultiplier; // Your variable
(...)

    private bool DamageMe(float damage){
(...)
        dmgMultiplier = 1 + ((opInfo.lifePoints - opInfo.currentLifePoints)/100);
        myInfo.currentLifePoints -= damage * dmgMultiplier;
        if (myInfo.currentLifePoints < 0) myInfo.currentLifePoints = 0;
        UFE.SetLifePoints(myInfo.currentLifePoints, myInfo);
(...)
    }
}

It will now look like this:

public class ControlsScript : MonoBehaviour {
(...)
    public FP afkTimer;
    public int airJuggleHits;
    public AirRecoveryType airRecoveryType;
    public bool applyRootMotion;
    public bool blockStunned;
    public FP comboDamage;
    public FP dmgMultiplier; // Your variable
(...)

    private bool DamageMe(FP damage){
(...)
        dmgMultiplier = 1 + ((opInfo.lifePoints - opInfo.currentLifePoints)/100);
        myInfo.currentLifePoints -= damage * dmgMultiplier;
        if (myInfo.currentLifePoints < 0) myInfo.currentLifePoints = 0;
        UFE.SetLifePoints(myInfo.currentLifePoints, myInfo);
(...)
    }
}

In the example above, the only big difference is that you must recast the value from float to FP. Now let's say you need dmgMultiplier to be tracked in case of a rollback. In that case you can track by 2 different means: Auto Tracking and Manual Tracking.

Auto Tracking
Its the simplest way, but it consumes more CPU. To use it, under the Rollback Netcode options, toggle "Track UFE Variables" and add the RecordVar attribute to your custom variable:

[RecordVar] public FP dmgMultiplier;

Manual Tracking
More complicated but has 0 impact on the CPU.
To use it, first we need to open UFE\Scripts\Netcode\NetworkCore\FluxStateTracker.cs and find nearby variables to where you are casting dmgMultiplier. Following the example above, you would need to do the following:

(...)
protected static void LoadCharacterState(FluxStates.CharacterState state, int player) {
(...)
        controlsScript.blockStunned = state.blockStunned;
        controlsScript.comboDamage = state.comboDamage;
        controlsScript.dmgMultiplier = state.dmgMultiplier; // Your variable
(...)
}

(...)
protected static FluxStates.CharacterState SaveCharacterState(int player) {
(...)
        state.blockStunned = controlsScript.blockStunned;
        state.comboDamage = controlsScript.comboDamage;
        state.dmgMultiplier = controlsScript.dmgMultiplier; // Your variable
(...)
}

Now open UFE\Scripts\Netcode\GameState\FluxStates.cs and add the casting for the new state variable:

(...)
public struct CharacterState {
(...)
        public bool blockStunned;
        public FP comboDamage;
        public FP dmgMultiplier; // Your variable
(...)
}

Doing this will ensure your variable is tracked and deterministic on all machines.

Now, on a side note, if you have added a new option in one of the editors, remember that aside from casting it to FP, you also need to change how the editor reads it:

Before:

moveInfo.elementalDmg = EditorGUILayout.FloatField("Elemental Damage:", moveInfo.elementalDmg);

After:

moveInfo._elementalDmg = EditorGUILayout.FloatField("Elemental Damage:", (float)moveInfo._elementalDmg);

To carry the values from your previous project to UFE 2.0, instead of replacing the casting, create a new variable below your previous one and add the prefix "_". Now add the following to UFE\Editor\UFEUpgrade.cs and run the update:

(...)
private static void SpecialMoveUpdate(MoveInfo move) {
        if (move == null) return;
        move.version = 2f;
        move._elementalDmg = move.elementalDmg; // Your variable
(...)
}