my blueprint is running out of memory i think

Development Programming & Scripting Blueprint
, ,
1

ok so I’m not 100% sure not what the actual problem is but I think it has something to do with the number of execution calls being made in my blueprint.
what I’m making is a procedural dungeon generator, it allows for the end user to set some variables about the number of rooms, the maximum size of the rooms, the number of rooms per branch and the min and max ranges for when a loop can be made as well as some other user generated information like tile size and such. any way for all of this to work the second stage of the generator has to run through a testing loop to find suitable places to make the room and a probability matrix to understand what to do with that information. its a pretty complicated system with loads of custom function and sub graphs. the issue that I’m having right now it I seem to be hitting a cap on the number of rooms I can make because the blueprint just finishes that stage of the generation before it fulfills the number of rooms to make. at the moment I’m able to generate a dungeon with around 350 rooms before it stops making any more. I’ve divided up the blueprint into separate graphs with separate events triggering them from the construction script but that is the height of efficiency I can manage. have I reached a stage where I now have to start creating custom nodes with C++ to be able to handle more rooms in the generation?
my intention with this project is to sell the final result on Fab so that other developers can get their hands on a good dungeon generator for a good price. the thing is I wanted it to be all handled in blueprints so that anyone can just jump in and make edits to it or expand on it to suit their needs if they find that necessary. do I have to give up on that ideal to get it to be capable of generating more rooms?
I did want the end user to be able to make multi thousand room generations if that is what they want for their games but I think that may be out of reach for blueprints and I might have to do this with C++. is their something I’m overlooking or should I start learning C++ now?

Thanks in advance for the advise/help.

2

System Memory is a huge factor when working with arrays and loops. Frame time hitches are also major hurdles. New frame cannot start until the previous frames loops are finished.

Large execution chains should make use of sequenced steps.

  1. Start
  2. Do X, store result, call next step
  3. Delay Until next Tick, Do X, store result, call next step
  4. Delay Until next Tick, Do…
  5. Delay Until next Tick, Do…
  6. Delay Until next Tick, Finish up

Free up memory as you go. If you no longer need array data you clear it. For other stored vars simply set them null.

Heavy math and loops should be in C++.

3

thanks for the tip, hopefully this will do the trick. ill let you know how this turns out.