Time X Extension Bug

[drnebula]

I have been trying to use the Time X extension that was ported from MMF 1.5 to MMF 2.0. I'm using build 243 of MMF 2 dev. It seems that timer 0 works, but not the other timers (1,2,etc.). Anybody else notice this problem? I'm resetting the timers and then checking to see when they are greater than a certain number. The number is in 1/1000 of a second.
Steve

[neat_Kliker2]

havent used it in ages (never for 2.0) but all timers worked fine for the 1.5 version

[aidmm]

I've also noticed this. Only timer 0 seems to work.

[neat_Kliker2]

i take it BrandonC reports the same bug with his snake problem ?

[Brandon]

I don't think that this is the same problem for a two reasons.

1. All of my timers seem to work.
2. I didn't even change my program and it started working again.

And just to clarify I am Brandon. BrandonC is a different person.

[drnebula]

Then I tried to use the Timer Object. I'm not sure if this comes with MMF2 or is an add-on extension. It seems to also allow a number of timers, but they did not work as I had hoped. I reset timer 0, and then added a condition to start timer 1 when timer 0 was greater than a certain value. No matter what I did, it seems that timer 2 started at the same time as timer 1. I tried using seperate groups which were deactivated, but the same thing happens.
Steve

[drnebula]

There are some really nice functions of the Timer X extention. I do a lot of simulations of repeating motions, like a pedulum swinging back and forth. The Timer X extension was the only way I have found to set a conditions such as: Every so many seconds (loaded from a counter) do something.
STeve

[Novabrain]

Steve: Are you setting the number of timers you need in the dialog you get when you insert the extension?

TimeX does not work for more than one timer unless you have allocated timers. I have always set it for 10 when I insert the extension, just in case. However, I do have to remember to increase that number by double-clicking on the object if I need more.

Also, you can set a counter to get the total number of timers if you want to keep track of what you set TimeX to.

It works fine for me, (build 244) in that case.

[drnebula]

Thanks Novabrain,
I did not remember doing that in MMF 1.5. I'll try it out. I found a workaround by resetting the one timer and using it over and over.
Steve

[aidmm]

aaahhhhh... good point. I'll have to go back and test this.