LTW - Evolution v1.68

[Selaya]

Alright, could you add a hint that tells everyone to reset their game after playing to stop them from crashing?

And could you do anything about the glitch that occurs when typing -rdy at initialisation?

EDIT: Another glitch that I`ve noticed: The 'cooldown' for the spawns begin to tick with initialisation instead of the game begin, ie when the host spends the full 30 (or whatever) seconds
to choose the game mode you`ll be able to send wolves and skeletons much sooner (in 30 seconds, actually) than when he doesn`t. (Sorry for this shitty explanation xd)

<3, Sela

 

[Selaya]

Hm, I just made a map (blank, but I changed the decay bone time in the gameplay constants to 1.00 seconds) and looped this trigger below for like, half an hour (more than 300 spawns per second made my game lag, so I decided against doing more xd), and my Warcraft hit like 700.000 KiB of memory allocated without crashing, and when I exited the map my Warcraft went blank for like a minute of time until resuming (cleanup), and went soundly to < 200.000 KiB of memory allocated.

• Events
  • Time - Every 0.01 seconds of game time
• Conditions
• Actions
  • Unit - Create 1 Sorceress for Player 1 (Red) at (Random point in (Playable map area)) facing (Random real number between 0.00 and 360.00) degrees
  • Unit - Kill (Last created unit)
  • Unit - Create 1 Archer for Player 1 (Red) at (Random point in (Playable map area)) facing (Random real number between 0.00 and 360.00) degrees
  • Unit - Kill (Last created unit)
  • Unit - Create 1 Sorceress for Player 1 (Red) at (Random point in (Playable map area)) facing (Random real number between 0.00 and 360.00) degrees
  • Unit - Kill (Last created unit)

Your LTW however crashes with, like some 400.000ish KiB of memory allocated, throwing some fatal exception about Memory.cpp.

<3, Sela

 

[Ubahnub]

The problem with the permanent crashing is related to the old warcraft 3 engine. There are no map scritp dependent memory leaks (not that I knew) and I was really aware of them while coding the entire map. The problem lies in the general behaviour of LTW games as they spawn tons of units on the map during a game which results in many minor memory leaks in the warcraft 3 engine. These leaks can not be fixed by a mapper! So it would be blizzards task to fix them, however, I do not think that this will ever happen. This crash occurs since one of the more recent versions of warcraft 3 and has not existed before.

tl;dr: As a mapper, I can't fix this crash issue.

Robbepop

The weird thing is, I only have this issue with your map. As Selaya shows with the test, it is not engine related, otherwise it should happen during the test as well.

On other maps with a lot of spawning units, such as X-Hero Siege (admittedly less than LTW) or Hero Line Wars, I don't have similar crashes.

 

[Robbepop]

Hiho,

it has been a long time since I respond here but if you want you can have a look into the map's scripts to prove me wrong about my assumption that nothing is wrong with the code since I have even recoded it from scrath and regained the completely same error before as after.

Just PM me about the map's scripts and you will receive them.

Regards,
Robbepop

 

[Robbepop]

I have updated the map with version 1.68.
Have fun and good luck with it!

Regards,
Robbepop

 

[Selaya]

So I just decided to give the 1.68 version a shot (yes, after two whole years!) and I tried to build a maze to see how rusty I am just to realise that the tower limit's hard capped at 150.
Not amused.

You literally cannot complete a maze at 150 (even the idiot linemaze clocks at 175) so I'm really curious what made you hardcap the tower limit at 150?

 

[Robbepop]

The tower cap might be lifted by some modes (e.g. -nolimit (-nl) or simply increasing the soft tower limit before game start.
However, I am not sure about that since I haven't touched the game (and especially the 1.x versions) since ages.
LTW-Evolution was designed to be very flexible to provide amusement for all kinds of players and their preferred configurations.
Besides that LTW-Evolution was also designed to be well balanced which directly leads to some limits that exist purely for balancing the game.

Also one cannot lift the limits (also for units) to infinity due to massive game lags that are a result of the old wc3 game engine that was never meant to be used the way it is in LTW style games.

 

[Selaya]

I understand why limits exist.

I've already tried the modes too, you simply cannot lift the 150 cap (thats why I said hardcap). Oh well. Can always go back to 1.67 so there's that :^]

In any case, on an unrelated note, you might want to fix the grid hotkeys (0,2 is Z and not Y, fuckin' Germans!), and I could have a look at the source code for the crash issue (3 years later!), I think I have a suspicion what's causing it.

 

[Robbepop]

Yeah sorry, for being german!

What is your suspicion? At least as far as I remember I can only remember trying to fix this nasty crash error all the time when working on LTW. I even invented numerous new systems to prevent allocations, scanned the entire source code base (with friends and tools) multiple times - nothing. Tried so hard, got so far but failed in the end.

 

[Selaya]

How the spawns are handled (they dont have a decay bone state from what i've seen; and possibly get cleaned up by a trigger, not sure without looking at the source)

 

[Robbepop]

All units have a very low decay rate (I think about 5 seconds whereas normal is about 180 seconds). It acutally is so low, that their animations do not even end. It was important in order to reduce lags.

 

[Selaya]

Yes, obviously. However, it seems (to me at the very least anyways) that it'd cause the crash. May I ask for the complete decay settings, or better yet just a look on the entire source myself :^]