Execute Functions cause Inspector Tab FPS drop

[souldomaintmParticipant]

I noticed that when adding that execute function action task from script control, it slows down the frame rate of the inspector tab. But only when viewing the game object that has the particular FSM.cs script attached to itself that also got all those execute functions in its nodes. This is only when not being in editor play mode. The more execute functions are in the graph, the lower the FPS of the inspector.

So normally its about 30-40 FPS in the inspector tab of the Unity editor. But by adding only one execute function action task, the FPS goes down to 20 already. Two more and I’m on 5 FPS.

I’m on Windows 8.1 with the latest NodeCanvas.

[GavalakisKeymaster]

Hey,

The issue is resolved in NC version 2 where the Script Control task’s inspector was slow 🙂
By the way if you are to start a project, I would strongly suggest that you please wait for version 2 to be released, basicaly because of the reason that graphs prior to version 2 are not updatable to version 2 (although I really tried to, but there are just so many core changes).
There are many improvements to version 2 and and its a free update as well 🙂

Cheers and thanks for the reports!

[souldomaintmParticipant]

Yeah, I just wait for NC version 2. And thanks for fixing and improving stuff!

[Author]

Posts