mmf 2 is silt! - calculations per second

I created a program that calculates and displays certain number of all possible combinations. Unfortunately, with 6 variables and 14 figures MMF are calculated tragically slow.

For example, I created the same program in C + +
and here is the result:

MMF2Dev - 1000 fps (max) - 1000 calculations per second - about 2.5 hours (with luck)

C + + app - fps X (possibly computer) - X calculations - about one/two seconds

And now my question:

Does the mmf is impossible to calculate faster than a 1 calculation / millisecond?

What are your events?

It sounds like you would benefit from using fastloops to perform these calculations, so you're not waiting for the event list to roll around again once the frame is updated.

Also, it is bound to be slower as it is interpreted not compiled.

What problem exactly are you trying to solve?

Quote:

---

Originally Posted by Jax

Also, it is bound to be slower as it is interpreted not compiled.

---

But the overhead of this won't be enough to turn 2 seconds into 2.5 hours. His events must be very poorly structured.

No true, I just mean that overall you probably shouldn't be doing brute force things in MMF.

He is only doing 1 calculation per MMF frame, my bet in an always event.
OP what you need to do is a fastloop, see below.

+ Start of frame
- start loop "calculate" -1 times

+ OnLoop("calculate")
- do calculations here

+ OnLoop("calculate")
+ result has been found
- Stop Loop "calculate"

I tried also with fastloop. Unfortunately, mmf hangs (no response). When using fastloops mmf overlooks some calculations: for example, would need to calculate 5 234 761 and the calculation is calculated, eg 4 835 332 (for here is talking about large numbers and not 1000 or 2000) if not completely mmf crashes.

during each loop, the program must calculate some figures and classify them in the list of results by using the "string parser obiect". at this point sort takes place only in 20%

If you are using anything like List object then that is Windows' fault because it tries to redraw objects like List and Edit every time they have a change.

I've made a program that can calculate expressions up to 16 decimal places, do any Sqrt() etc command, x, /, +, -, etc, and it barely takes a second.
Although admittedly it's around 4 layers of loops and located in an AI program.