Iteration Limit Setting Broken

Development Audio
, , , ,
1

Thank you for adding the Maximum Loop Iteration Count setting to the Project Settings. Unfortunately it seems to be broken or still quite limited:

LogScript:Warning: Runaway loop detected (over 10000000 iterations)

Seems to be capping out at 10 Million, even though I set it to 1 Billion.

I then tried 10 Billion, but the display in the Editor capped out at 2147483647. I still get the 10 Million limit warning.

I am guessing that I am going to need at least 10 Billion, though perhaps 1 Trillion would be a better upper limit? :stuck_out_tongue:

1 Like
2

Hi Zeustiak.

The number 2147483647 is the maximum of a 32bit signed int. I’ve internally reported your request for a higher cap.

Regards,

Jonathan

3

Thanks, but that doesn’t solve the first issue. I can set it to 2 billion, but it still limits me at 10 million.

1 Like
4

I’m not seeing that problem in 4.5.

LogScript:Warning: Runaway loop detected (over 2000000000 iterations)

Any idea why you’re seeing this limitation and I’m not?

5

Looks like it may have been stuck, because now it works.

Thanks for the higher cap request! :slight_smile:

6

Hey Zeustiak,

Just letting you know that we’ve been investigating the prospect of raising the iteration count, and it turns out that changing that would cause other problems. We’re still trying to see if it’s feasible, but for the meantime, you’ll need to work around the 2147483647 limit.

7

I understand, thanks for the inquiries.

I can use Rama’s plugin in the meantime if necessary. As soon as I get back to working on my river system I will work on carving it out as a standalone BP which should give me a little more room, assuming the iteration limit resets between blueprints… :slight_smile:

8

Bump here, is there any update on this? I also require the same feature.

9

Bump, or maybe unrelated. When I exceed the 33 bit limits it assigns a negative symbol and then every gate node causes a crash. Version 4.22.3

10

Still not working.