FSM not preprocessed warnings : game completely broken [SOLVED]

[RoiSinge]

Hi,

I recently updated our project from unity 5.3.5 to 2017.3 and plamaker from 1.8.1 to 1.8.6.

Our game works fine in editor but everything gets messed up (collisions not working as expected, character jittering...) in build (windows standalone).

I noticed that the output log is literally flooded with "FSM not preprocessed" warnings.

This issue is highly critical and is a real problem regarding our deadlines.
Help will be greatly appreciated, you'll find the output log attached.

[djaydino]

Hi,
Do you have some custom actions from the Ecosystem?

if so, try redownloading them.

Mainly the actions that have different update types.

[frogwise]

I also have "preprocess" warning preventing my builds from going through as well.

With your suggestion above, about downloading custom actions again, how can you filter by actions that you have downloaded in the ecosystem? I have so many that I have no idea how to re-find them.

[djaydino]

Hi.
What playmaker and unity version you have?

Can you check the action "Trigger Event" (Right Click the action and select 'edit script')
These lines should be there :



If not you should try to update playmaker.
Before you update Make a backup from your project !

If there is, there is a different issue.

As it gives a null reference it means it does not find a reference object.

[frogwise]

Latest - Playmaker 1.8.9.  I had just updated from 1.6.

I seem to have those lines.

[frogwise]

I only get this error when I try to make a WebGL build. Playing the game in the editor does not produce this error.

[djaydino]

Hi.
i am not sure whats going on.
Can you send a bug report from inside unity?

You can find it under playmaker/tools

[jeanfabre]

Hi,

 you likely need to clean up your project:

1: back up your project
2: extract the templates and global resource you have possibly in the PlayMaker folder
3: delete the PlayMaker folder
4: delete all the playmaker dll inside the PLugins/folder
5: import PlayMaker again from the ecosystem
6: welcome screen will not appear ( because of Unity errors)
7: manually import PlayMaker package located in Assets/PlayMaker/Editor/Install
8: if you still have an error after that, let me know which one and also install again step 7) it's likely that Unity still prevented PlayMAker from proceeding fully to setting up your project.

 Let me know know if this doesn't work.

 Bye,

 Jean

[RoiSinge]

Hi,

Thanks for your answer djaydino.
 
The issue seems indeed related to actions with different update types handling.
After upgrading Unity and playmaker I made an update of this script : FsmStateActionAdvanced.cs (found on github) in order to fix actions using late update which were not working anymore.

If I revert this change the game runs fine again, except for actions using late update.

So I tried to update some custom actions from the ecosystem : Get and Set position advanced.
The result is the same as updating FsmStateActionAdvanced.cs : game behaves fine in editor, including late update handling, but everything fall aparts in windows build.

Jean, is your answer intended for me or frogwise ? I have no errors in editor console.

[djaydino]

Hi.
@RoiSinge :
I think Jean's answer is for frogwise.
Do you have "Get/Set property" actions in your project/scene?
if so you might need the Linker wizard

[RoiSinge]

Ok, i had to go through all my custom actions, some of them not from the ecosystem, and modify the code in order to handle properly fixed and late update.
 
I finally got rid of "fsm not preprocessed" warnings, and windows build seems to run fine again.

One thing though, in the output log i see that there are some messages like this "fsm updated please re-save the scen/project". Seems to happen after a scene was loaded. Is it normal ?

Indeed i have many get/set property actions in my project. Do you recommend using the linker wizard even if my problem seems to be solved ?

[Alex Chouls]

You get "FSM updated please re-save the scene/project" if any actions have changed since the FSM was last saved (or if the data needs to be resaved for some other reason, e.g., the data layout changed in an update).

It's a good idea to re-save when you see this message since old data has to go through slower loading paths to recover parameters and update the data. You should definitely re-save before shipping anything.

It's a good idea to use the Linker Wizard on any platform that strips "unused" classes/methods/properties from the build. It may look like everything is working, then you hit that one Set Property action that rarely gets called and it breaks your game because the property was stripped. Better safe than sorry!

[RoiSinge]

I'm not sure to understand.

The "FSM updated please re-save the scene/project" messages come from the output log of windows build, not from unity's editor console.

All my scenes and project are properly saved before building.
Am i missing something here ?

[Alex Chouls]

So you don't get the "FSM updated..." message when loading the scene in the editor? Whenever you see "FSM updated...", at runtime or in the editor, it means the loading code had to do more work to update the FSM data. Try running: Tools\Update All FSMs in Build.

[RoiSinge]

No i don't get the messages when i open the scene in unity, neither do i when i play the game in unity.

I tried "update all fsm in build" and the problem is still there :
1. I make a pc build
2. Push it to steam
3. Launch it
4. Quit the game
5. Go to appdata/locallow folder and open output_log.txt : i see the messages, always pointing out the same fsms