Universal Fighting Engine

User Tools

Site Tools

You are here: UFE » Global Editor » UFE 2.0 Netcode
global:netcode

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
global:netcode [2024/01/07 06:17]
Mistermind 		global:netcode [2024/12/10 16:17] (current)
Mistermind
Line 23: Line 23:
 ---- ----
 ===== Converting to 2.0 ===== ===== Converting to 2.0 =====
 +//This tutorial is meant for conversion between UFE 1 and 2. If you are starting from UFE 2 you can skip this step.//
 +
 UFE 2.0 was developed with backwards compatibility in mind. Several processes were created specifically to deal with converting large amounts of data at once. A prototype of your project with the new netcode can be created in less then an hour if you know what you are doing. The whole process can be divided in 4 easy steps: UFE 2.0 was developed with backwards compatibility in mind. Several processes were created specifically to deal with converting large amounts of data at once. A prototype of your project with the new netcode can be created in less then an hour if you know what you are doing. The whole process can be divided in 4 easy steps:
  
Line 32: Line 34:
 \\ \\
  
-  * **Step 2: Record Character Maps (PRO/Source)** +  * **Step 2: Update Character File**
-Now that we have our asset files converted to //Fix64// we can move to the next step to ensure synchronization: Map the character animations. This is a fairly simple process, but can be a bit time consuming depending on how many characters you have or how often you change your animation files.\\ +
-First, open the scene ''Scenes\MapRecorder.unity'' and under the hierarchy click on the Main Camera. Notice the script attached to it: Animation Recorder.  +
-{{ :global:netcode_animationrecorder.png?nolink |}} +
- +
-Drag one of your characters into the //Character Info// field and hit **Play**. If you have your hitbox setup correctly you should see something like this: +
-{{ :global:netcode_maprecorder.png?nolink |}} +
-Select the Move Set and click //Record Basic Moves// to start recording all animations listed under your basic moves into //Fix64// position maps. Once completed, do the same for //Special Moves// then hit **Stop**. Replace the character info file with the next character and repeat the process.\\ +
-\\ +
- +
-  * **Step 3: Update Character File**+
 Next up is the HitBoxes' radius, rectangles and offsets. Because these values are recorded under the prefab itself we need to do this from the Character Editor. Open the Character under Hit Box Setup and hit "Restore Legacy Values": Next up is the HitBoxes' radius, rectangles and offsets. Because these values are recorded under the prefab itself we need to do this from the Character Editor. Open the Character under Hit Box Setup and hit "Restore Legacy Values":
 {{ :global:netcode_legacyvalues.png?nolink |}} {{ :global:netcode_legacyvalues.png?nolink |}}
Line 50: Line 42:
 \\ \\
  
-  * **Step 4: Photon Setup (Standard/PRO/Source)**+---- 
 +===== Photon Setup ===== 
 In order to have the client-server accessibility you need to download [[https://assetstore.unity.com/packages/tools/network/photon-unity-networking-free-1786|Photon Unity Networking]] and create your own Photon Account. Sign up for free: [[https://www.photonengine.com/en/PUN]]\\ In order to have the client-server accessibility you need to download [[https://assetstore.unity.com/packages/tools/network/photon-unity-networking-free-1786|Photon Unity Networking]] and create your own Photon Account. Sign up for free: [[https://www.photonengine.com/en/PUN]]\\
 Once you have an account go your Public Cloud -> Applications and copy your App ID as displayed here: Once you have an account go your Public Cloud -> Applications and copy your App ID as displayed here:
Line 71: Line 65:
 ===== Map Recorder ===== ===== Map Recorder =====
  
-One of the key elements that makes UFE easy to prototype is the guided transform hitbox system, meaning you only need to tell it where the joints are and UFE will take care of the rest. Unfortunately this means that we are tracking position information directly from the animation itself, and that value can only be read in //float// format (non-deterministic).\\ +One of the key elements that makes UFE easy to prototype is the guided transform hitbox system, meaning you only need to tell it where the joints are and UFE will take care of the rest. This means that we are tracking position information directly from the animation itself, and that value can only be read in //float// format (non-deterministic). 
-To solve this, Map Recorder runs and stores the //position maps// (and delta displacements) of all identified hitbox on every frame of animation throughout the character's moveset, saving them in //Fix64// format (deterministic). UFE Engine will then play these maps synchronously to the animation during gameplay.\\+ 
 +{{ :global:netcode_maprecorder.png?nolink |}} 
 + 
 +To solve this, Map Recorder runs and stores the //position maps// (and delta displacements) of all identified hitbox on every frame of animation throughout the character's moveset, saving them in //Fix64// format (deterministic). The Engine will then play these maps synchronously to the animation during gameplay.\\
 \\ \\
 Map Recorder is located at ''UFE\Engine\MapRecorder.unity''. Run it whenever you have to add new moves or change one of the character's animation files. Map Recorder is located at ''UFE\Engine\MapRecorder.unity''. Run it whenever you have to add new moves or change one of the character's animation files.
 +
 +{{ :global:netcode_animationrecorder.png?nolink |}}
 +
  
  
global/netcode.1704626235.txt.gz · Last modified: 2024/01/07 06:17 by Mistermind

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki