Framerate Issues Between between UFE Life and UFE Source

Also, are you using a sprite sheet or separate files per sprite?

It depends on the size of your sprite files honestly. The first time they play in the scene and get put into RAM might potentially be causing a hitch. I've never tested it on phones. It shouldn't be due to the source version though.

To use a sprite sheet you'd create it like any other sprite, except you'll just have to do all your pivot points and sprite cut outs all in one file instead of individually. I had some performance success when doing setting up a local Third Strike variant/redux by doing that. Also will come in handy if you need to look into doing palette swaps down the road. I haven't gotten that fully functioning yet so I haven't made a tutorial on doing such atm.

There is no relation to framerate and the version of UFE you are using. There are a lot more variables at play, so I wouldn't jump into that assumption. I believe the problem is somewhere else.

Under Unity, go to Edit -> Project Settings -> Time. See if the values match these:
Fixed Timestep: 0.01666667
Maximum Allowed Timestep: 0.3333333
Time Scale: 1
Maximum Particle Timestep: 0.03

@Mistermind

The only difference I saw was Fixed Timestep: 0.02

I made the change but didn't really see any improvement.

Thanks for the help nonetheless

That alone should be the cause of the problem. When the Timestep is incorrect that is the exact result you'd see. To run at 60 FPS you need Fixed Timestep at 0.01666667.

About the FixedUpdate, that is not the problem. The profiler is just pointing out the function that uses the most resources, which is UFE's main tick function (since it calls out to everything else in the game). Notice you will see the exact same result with your previous copy of UFE lite.

The problem is most likely because you copied the files onto an existing project instead of extracting UFE Source package directly. As a result, some of the project settings were not properly overridden. This process can be done manually, here is how:

- Close Unity.
- Using the explorer and navigate to (Project Folder)\Assets\UFE\ProjectSettings
- Open ProjectSettings.zip
- Extract its content to (Project Folder)\ProjectSettings
- Reopen your project in Unity

No it wouldn't change anything. Setting it to 30 fps means changing your entire game architecture to understand data at 30 fps, not 60. That means moves that were designed with 15 frames would run in half a second instead of a quarter of a second.

About your craches, it sounds like an unrelated problem to this topic. Take a look at this post, see if your settings match these instructions:
https://forum.unity.com/threads/univers … st-3815395

Good news! Everything seems to work after I compressed the individual 2D sprites into High Quality and compressed images in other places around Unity.

UFE has its own FPS counter and it operates tightly with Unity time manager and the options under Global Editor -> Advanced -> FPS and the FPS architecture of each move:
http://www.ufe3d.com/doku.php/move:general?s[]=fps
http://www.ufe3d.com/doku.php/global:advanced?s[]=fps

Make sure you know what you're doing when changing your FPS settings.

It could be that your game is loading necessary assets during gameplay and that is overloading the CPU.
Try checking the "character preview" under each of your move assets. If you have linked character prefabs on those moves that are not the characters that are currently active, that will load unnecessary assets to your game.

Also, are you using Resource loading methods for loading your character assets (instead of prefabs)?
http://www.ufe3d.com/doku.php/character:prefabs
Under Character Prefab, select "Resource Folder" as your loading method to make sure the game only loads the necessary assets. You can read more about it here:
https://docs.unity3d.com/Manual/BestPra … nity6.html

Also, make sure you are doing the same for the Move Sets. Use Stances (Resource) instead of Stances (Preloaded).