Infinite loop detected too soon

Development Platform & Builds
, , ,
1

When i am running this script I get an infinite loop detected if I place map size X AND Y at 500+.

I have checked and my infinite loop detection under project settings is set to 1 million this should only be producing 250,000.

So:

  1. Why is it detecting 4 times the number of loops?
  2. How safe is it for me to crank that infinite loop detection to say 10 mil or 100 mil? I mean if its an actual infinite loop wouldn’t it just cause a bit of lag before detecting?

Appreciate the help.

NextGenerator macro just prints a string, has a .5 second delay then moves to the TerrainGen(TG)
“SetCentre” just centres the terrain to the world

298238-untitled-1.jpg
298238-untitled-1.jpg777×706 150 KB

2

What are X and Y set to?

Only other thing I can see is you might have your TG calls referring to each other, are you sure that’s not the case?

3

The blueprint works fine with x and y set to 475 but when set to 500 or more an infinite loop is detected

Im working on increments of 25 and X and Y are currently being set to the same value.

Definitely not an issue with the NextGenerator macro

4

Strange, no idea, sorry…