SC2Mapster

On my computer periodic events cause a framerate decrease that goes from 45fps to 4fps after something like 30 seconds.
The problem is solved when I replace the periodic timer event with a while loop or a recursive function call.

Can you please test if you have my same problem? I can record a video if you don't believe me :D
I attached the map I used for tests, download it and try to activate one trigger at once and see if you get framerate decrease (ctrl + alt + F to show FPS)

Edit:
Another thing you can notice is that when you open the menu the FPS returns back to normal, when you hide it they lower again instantly.

Edit2:
If you have a real good pc probably you should wait more then 1 minute to see the fps decrease, try to leave the map loaded in background and check it back after 5-10 minutes.

Edit (figured out):
The bug seems related to the amount of text that the debug window contains and periodic loop events spam a lot of text. It doesn't matter if you close it after it started because it's only hidden, you MUST disable it from starting while testing maps.

@Bibendus: Go

I loaded the map into the editor and played it(with all three triggers enabled), sorry man no frame drop whatever, stayed at max the whole time. I'm using an E8500(dual core Intel) @4.2ghz with 2x8800GTX video cards, what are you using?

Quote from Forge_User_20974461: Go

@Bibendus: Go

I loaded the map into the editor and played it(with all three triggers enabled), sorry man no frame drop whatever, stayed at max the whole time. I'm using an E8500(dual core Intel) @4.2ghz with 2x800GTX video cards, what are you using?

GeForce 275GTX 860MB
Phenom II X4 Quad Core 955
4 GB Ram

I suppose it's a processor problem, that started happening from 2-3 patch before the beta end.

@Bibendus: Go

Well that's just bizzare because such a CPU smokes my own for its ability to handle threads and workload, your GPU is roughly on par with my pair as well.

Quote from Forge_User_20974461: Go

@Bibendus: Go

I loaded the map into the editor and played it(with all three triggers enabled), sorry man no frame drop whatever, stayed at max the whole time. I'm using an E8500(dual core Intel) @4.2ghz with 2x800GTX video cards, what are you using?

GeForce 275GTX 860MB
Phenom II Quad Core 955
4 GB Ram

I suppose it's a processor problem, that started happening from 2-3 patch before the beta end.

Quote from Forge_User_20974461: Go

@Bibendus: Go

Well that's just bizzare because such a CPU smokes my own for its ability to handle threads and workload, your GPU is roughly on par with my pair as well.

I mean that probably blizzard messed up with this model of CPU, I'm searching for other testers :|

That's a pretty common CPU though and I'd have expected more backlash if such a CPU's existence created problems like that, ever run a program like CPUz to see if its actually running at what it should be? I really recommend just as a 'try it to rule it out' kind of thing to see if its reporting your CPU's current settings as matching what it should be capable of.

CPUz is freeware and available at:
http://www.cpuid.com/softwares/cpu-z.html

If you're in doubt post a screen shot of that first page it shows.

Consider that many players are experiencing fps low rate on third person shooters and THAT could be their problem. And that's only a custom map problem related to maps that contain heavy keyboard control checks and that kind of map are not popular on bnet cause of lag. That could be a common problem, just people don't know the cause of that.

P.S.
I use Everest instead of CPUz and my cpu seems ok, we just need more guys testing it :|

No slowdowns over time, even after 20 minutes. No Trigger Debug window.

Phenom 9950 Quad Core

4 GB Ram

ATI Radeon HD 4870

hmm.. this is interesting.

• The timer gave me a little fps drop every 10 sec. so every 10 sec my fps would go down by 1 till hit hit around 10 or something
  
• The while loop did nothing to my FPS
  
• Neither did the Recursive trigger.

but I must say it took a while till I noticed it, like 5 mins before the FPS drop started.

@BumpInTheNight: I suggest you test it again. but than let your pc run the map for like 10 mins and than see the FPS

Specs:
2X GeForce 285GTX 1024MB
Phenom II X4 Quad Core 965
8 GB Ram

Quote from Jackolas: Go

hmm.. this is interesting.

The timer gave me a little fps drop every 10 sec. so every 10 sec my fps would go down by 1 till hit hit around 10 or something

The while loop did nothing to my FPS

Neither did the Recursive trigger.

but I must say it took a while till I noticed it, like 5 mins before the FPS drop started.

@BumpInTheNight: I suggest you test it again. but than let your pc run the map for like 10 mins and than see the FPS

Specs:
2X GeForce 285GTX 1024MB
Phenom II X4 Quad Core 965
8 GB Ram

Maybe u needed more time cause your computer is better then mine :D
On my comp that happens after just 1 minute or less lolz.

Oh the strange thing is that when you open the menu the fps come back to normal, then when you hide the menu again fps return low instantly

I'm slowing down too. Starts at about 25fps and is at that in the menus, but game slowly slows down and stays at about 8fps and now I'm down to about 2 fps.

<Bibendus> 2.0GHz Intel Dual-Core T4200

<Shawn|rawr> Si Senor

<Bibendus> Processor 2.0GHz Intel Dual-Core T4200

<Bibendus> Memory 3GB, 667MHz DDR2

<Bibendus> Hard drive 320GB 5,400rpm

<Bibendus> Chipset Mobile Intel GM45 Express Chipset

<Bibendus> Graphics Intel GMA 4500MHD (integrated)

<Bibendus> Operating system Windows Vista Premium

<Bibendus> Dimensions 14.9 inches wide by 9.9 inches deep

<Bibendus> Height 1.4 to 1.7 inches

<Bibendus> Screen size (diagonal) 15.6 inches

<Bibendus> System weight / Weight with AC adapter 6.3/7.2 pounds

<Bibendus> is that correct?

<Bibendus> can u reply with that?

That's because of the Trigger Debug Window. Everytime a new line is added, the whole log is being refreshed. When there are thousands of lines it takes some time, and therefore freezes the game.

When you click the Menu the game is paused, so the log doesn't get updated anymore, and you gain back your normal fps :)

A while loop and recursive trigger does not print any line everytime they get executed

Quote from vjeux:
That's because of the Trigger Debug Window. Everytime a new line is added, the whole log is being refreshed. When there are thousands of lines it takes some time, and therefore freezes the game.

When you click the Menu the game is paused, so the log doesn't get updated anymore, and you gain back your normal fps :)
--------

If you use the third trigger (the recursive one) the events printed on the window should be the same, however this doesn't slow down the computer.
However it seems to be a bug related to debug windows, looping timer events and some cpus/computers.

Edit:
Ok I've missed the the third trigger doesn't spam in the debug window so the bug seems just related to the amount of text contained in it.
It's stil strange that some guys don't feel that problem even with the debug window opened but the problem is not serious as I tought.
However it's good to know for mappers that looping event timers cause performance issues while trying to debug maps.

Quote from Forge_User_20974461: Go

Edit (figured out):
The bug seems related to the amount of text that the debug window contains and periodic loop events spam a lot of text. It doesn't matter if you close it after it started because it's only hidden, you MUST disable it from starting while testing maps.

AHHHH, okay I was just running the map full screen, yes indeed the debugger window can heavily lag out a system if its constantly feeding text...huge piles of slow down too. if you right-click on the window you can toggle what it shows, I often do that if I'm searching for say an event and don't want all the trigger spam, or turn off all but errors if I'm just looking for those.