1.2 is killing the FPS when a unit attacks another unit (with 1 unit fighting, the fps decrease to 48; multiple units attacking = lag lag lag)...

Seems like my CPU is getting hotter. I don't have that at map start.

edit:
I'm guessing it is a memory leak. I can bring the FPS down to 2 when idling in the middle of a bunch of weak monsters. If I die and shop at the town, my dialogs start FPS lags...

If I restart the map and let me hit again from multiple monsters, the FPS behave normal again. Even the first few hits don't really mess with the FPS.

edit:
to clarify this, I'm talking about my D1 map...

edit:
testing stuff in editor for "lagability" or RAM usage increase:
-text markers: no, only eat FPS when many many are displayed on screen.
-get & set custom values: no FPS decrease

After testing my map again, the used RAM by sc2 stabilizes, but the fps decreases are still happening.
CPU and graphics card temperatures are ok. Ok means not super high. With the big stress tests before it became hotter.

min (stress test with other map), max (stress test with other map), what I have:
CPU temp: 39, 50, 45 (middle, not high, normal heat)
graphics: 36, 55, 36 (has nothing to render because the game freezes, not the card denying it)


It is getting worse as longer the game lasts. After 20 ingame minutes, the fps drop to around 0 every few seconds. Currently there are maybe 400 running units on the map and many units that act as dungeon walls. But that ate 2-3 fps before patch. 3 monsters are attacking (-> starting unit is beeing attacked event) and 4 are trying to reach my monster, but are blocked by other units.

The activity stays between 1 and rarely 6, the arithmetical value is between 2 and 3. The average execution time of the unit is beeing attacked event is 0.112 ms. Total execution time of that trigger: 0.3 seconds during the whole time atm... Other triggers are rarely running.

The game is so slow that I can see the fps drops (the graphical output freezes, sound works without lags) with every time a unit is being attacked...

NEW TEST:
Now I'm disabling the damage calculation + dealing in my trigger (I was calling an action function).
Result: execution time was cutted to ~ 0.05. FPS keep decreasing.

So NEW TEST:
New map with 2 Zerglings with modified damage ( 0 damage ) and 1 trigger that runs when a any unit of any player is being attacked.

RESULT:
The event "Unit is being attacked" doesn't work properly and causes insane lag for a single event.

I have the same issue whenever I play ANY SC2 map, it lags to all hell until Ive killed about 5 or 6 units.

Ive noticed when the graphics are lower it hangs for less, but it still does the same thing.

Your lag may be caused by the effect models stuff. SC2 isn't loading that at the map start. That's why you don't see the first Firebat's flames or the first marauder's hit explosion. I guess it's loaded after a few seconds minutes after map start because I think everything plays fine in melee games.

And my graphics are mostly low. Only models and textures are ultra/high. I've rarely bigger fps drops (60 is my base which I like to be constant).

edit:
Devourer says he has no FPS drops.

1. Create a new map
2. create 1 zergling fpr player 1 & 1 zergling for player 15
3. modify the Zergling's claw attack's damage value to 0
4. delete default trigger and create a new one with the event "any unit is being attacked". Actions doesn't care.
5. Test the map and get your FPS display with pressing ctrl + alt + F at the same time. Don't do anything to the 2 lings poking each other.
6. Let the map run a few minutes. Check your FPS.

I've a decrease from my constant 60 fps to 52 fps within 1 game time minute. It is decreasing over time...

Post has been edited 1 time(s), last time on Jan 12 2011, 5:52 pm by Ahli.

I'm going to be like a black shadow and say this again...

What, you actually thought they were gonna fix it?
I promise you, they won't. Not until the next installment of the trilogy arrives.
And even then, I doubt they would.

Um, a memory leak that is very very easily repeatable, multiple times in a game, that very quickly reduces game performance would be of quite high severity and priority to be fixed. If they know about it, and the bug you're talking about actually is a general memory leak that affects everyone and not just those with specific computer setups, then I'm sure they'll fix it once they're aware of it. Honestly given the nature of what you've described, I think it's probably just affecting you two guys and is not really a general problem in the game, simply because if Blizzard saw this they'd fix it quick-smart.

I've already posted that on Blizzard's German forum.
I'll see if I get a bluepost in one of the 3 threads or if they will update their known-bugs list.

They only click on things on the first page every few days and my thread is on the second one.

Post has been edited 1 time(s), last time on Jan 15 2011, 8:54 pm by Ahli.

I've contacted them over their web contact form because it seems I'm getting ignored on the forums. :S

I'll post on the general EU/English forums also. Hopefully this will be solved in 1.2.1

I've got a mail.
translation by google :X

I've answered them that I know that they couldn't do anything about that problem except that they could throw the report into the direction of the programming department because the bug appeared with patch 1.2 and most of the users would never find the "detailed" source of the problem.
So I've suggested them to report that problem and let me know that they did that.

Let's see what will happen...

You could try getting the name of a programmer from Blizzard and emailing likely addresses. firtname.surname@blizzard.com for example.

nah, that's not the way it should be done. Should be the last option, thought ;D
If everyone would do that the programmers wouldn't program, they would have to clear their e-mail folders all day.

Anyway, another staff replied me and said me that they've reported that bug.

So at least they have the knowledge about that problem physically in their system.
That's the first step of fixing it.

Good job ahli. That's all I can say.