playMaker

Author Topic: [SOLVED] HELP - I lost all my FSM when using Behaviour Designer's PM assets  (Read 1609 times)

MlleBun

  • Playmaker Newbie
  • *
  • Posts: 28
Very critical moment, and I'm not having a great help from Opsive's forum. All my FMS's components are empty after I downloaded a PlayMaker package from Opsive's Behaviour designer's download page. Every GO with an FMS component looks like the attachement  :-[ :-\

Is there a way to get back the local FSMs please (#feelingDesperate)?
« Last Edit: March 14, 2021, 05:25:30 AM by MlleBun »

MlleBun

  • Playmaker Newbie
  • *
  • Posts: 28
Moreover Playermaker itself has dissappeared from the menu. I'll try to reinstall the whole tool.

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 4141
  • Official Playmaker Support
    • LinkedIn
Re: HELP - I lost all my FSM when using Behaviour Designer's PM assets
« Reply #2 on: March 13, 2021, 02:44:07 PM »
It looks like the Unity Inspector is in Debug mode.

See Toggling Debug Mode:
https://docs.unity3d.com/Manual/InspectorOptions.html

EDIT: Playmaker not being in the main menu usually means there are errors in the project preventing editors from compiling. Check the Unity Console.

MlleBun

  • Playmaker Newbie
  • *
  • Posts: 28
Re: HELP - I lost all my FSM when using Behaviour Designer's PM assets
« Reply #3 on: March 13, 2021, 02:57:40 PM »
It looks like the Unity Inspector is in Debug mode.

See Toggling Debug Mode:
https://docs.unity3d.com/Manual/InspectorOptions.html

EDIT: Playmaker not being in the main menu usually means there are errors in the project preventing editors from compiling. Check the Unity Console.

Hi Alex, thanks for responding. The inspector is in Normal mode and yes, I had 35 errors in the inspector after installing that BD package. Errors coming from Cinemachine, ArrayMaker etc. All the GO that has a Playmaker FMS component. I deleted the corresponding folders from the disk and now I have the following errors  :
Code: [Select]
Assets\PlayMaker\FsmProcessor.cs(53,92): error CS0246: The type or namespace name 'PlayMakerUiEventBase' could not be found (are you missing a using directive or an assembly reference?)

Assets\PlayMaker\FsmProcessor.cs(61,78): error CS0246: The type or namespace name 'PlayMakerUiEventBase' could not be found (are you missing a using directive or an assembly reference?)

I'm really afraid to delete the PM's components on my GOs, uninstall and reinstall Playmaker. I've worked a month on those FSMs and gosh, it hurst feeling that I'll have to do it again. Is there a way to backup those FMSs? There are not templates and I don't know where to find them on my disk  :'(

MlleBun

  • Playmaker Newbie
  • *
  • Posts: 28
Re: HELP - I lost all my FSM when using Behaviour Designer's PM assets
« Reply #4 on: March 13, 2021, 03:57:10 PM »
Ok, backup plan setup. Even if I can't open an FSM, I can see that the Playmaker components still have the States and transitions references in the drop-down menu. I'll back up my projet, delete and install Playmaker again and redo all the FMS from scratch again. But if anyone has a better idea, je suis preneuse (I'll take it) !

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 4141
  • Official Playmaker Support
    • LinkedIn
Re: HELP - I lost all my FSM when using Behaviour Designer's PM assets
« Reply #5 on: March 13, 2021, 04:20:03 PM »
You shouldn't have to remake the FSMs.

First remove the Behaviour Designer add-on. If you can't figure out which files it added, import it into a new project and note the files in the package import dialog.

Then re-import and install PlayMaker.

Once there are no errors in the project, and the PlayMaker editor compiles, it should find all the data in the PlayMakerFSM components.

MlleBun

  • Playmaker Newbie
  • *
  • Posts: 28
Re: HELP - I lost all my FSM when using Behaviour Designer's PM assets
« Reply #6 on: March 14, 2021, 05:24:49 AM »
 :D :D :D It worked ! I'm so grateful !!

EDIT : I was still having errors after re-installing Cinemachine package (2018) from the Ecosystem, but at least it was a more targetted issue. The errors came from Actions that I'm not using but I solved it with a couple of install/uninstall/delete and re-import the package:
  • Assets\PlayMaker Cinemachine\Actions\VirtualCamera\VirtualCameraAimPovGetYaxisSettings.cs
  • Assets\PlayMaker Cinemachine\Actions\VirtualCamera\VirtualCameraAimPovSetXaxisSettings.cs
  • Assets\PlayMaker Cinemachine\Actions\VirtualCamera\VirtualCameraAimPovSetYaxisSettings.cs
  • Assets\PlayMaker Cinemachine\Actions\VirtualCamera\VirtualCameraAimPovGetXaxisSettings.cs
I'm only using the Virtual Camera Set Priority.

Ex of errors from VirtualCameraAimPovGetYaxisSettings.cs :
Code: [Select]
Assets\PlayMaker Cinemachine\Actions\VirtualCamera\VirtualCameraAimPovGetYaxisSettings.cs(11,56): error CS0305: Using the generic type 'CinemachineActionGetAxisSettingsBase<T>' requires 1 type arguments

Assets\PlayMaker Cinemachine\Actions\VirtualCamera\VirtualCameraAimPovGetYaxisSettings.cs(26,24): error CS0115: 'VirtualCameraAimPovGetYaxisSettings.Reset()': no suitable method found to override

Assets\PlayMaker Cinemachine\Actions\VirtualCamera\VirtualCameraAimPovGetYaxisSettings.cs(34,24): error CS0115: 'VirtualCameraAimPovGetYaxisSettings.OnEnter()': no suitable method found to override

Assets\PlayMaker Cinemachine\Actions\VirtualCamera\VirtualCameraAimPovGetYaxisSettings.cs(44,24): error CS0115: 'VirtualCameraAimPovGetYaxisSettings.OnUpdate()': no suitable method found to override
« Last Edit: March 14, 2021, 05:56:04 AM by MlleBun »