Reply To: Extreme Memory Usage

[adoby]

@Gavalakis
It’s a nice tool, for small projects. but we are not looking at small projects here.
We can’t just use a tool and find out mid-development that we get memory problems.

Thats why we made the tests and try to get support. If it’s not foreseeable to fix the high memory usage, then thats a nogo in the long run.
It’s totally nice for smaller projects and I’m not saying that you coded something bad.
FlowCanvas is powerful and works better than most of the other tools I used in terms of compile time and integration.
We probably just hoped that there would be a playmaker replacement/blueprint equivalent that wouldn’t have a major drawback.

@rixter
Talking about RAM, its increasing linearly.
Small test with 2000 flowscript doubled the RAM usage as well.
And our test uses a very small flowScript, you would need way more states to create a working app.
We can’t make a real world experiment, that would take too much time.

Have a nice day/night
We may take another look at it.
Maybe you find something that lowers the memory usage.
E.g. Editor properties like Descriptions, Names of states etc. in the build.