GAE 0.3.1

[ChupaReaper]

Yes, I heard Silnarm is preparing for a release...

Cool, I should get my descriptions finished off and get back to work the second faction.

[silnarm]

Yes, 0.3.2 shouldn't be much longer, most everything is done now, but I'd like to leave it a for a while to see if anything else I've missed pops up.

I might actually put up a snapshot release so non-compiling people can help test.

Watch this space.

Edit:

Windows exe (dev edition) and data upgrade pack @ rev 952,
http://sourceforge.net/projects/glestae/files/snapshots/gae_win32_rev952.7z/download

[Omega]

Yes, 0.3.2 shouldn't be much longer, most everything is done now, but I'd like to leave it a for a while to see if anything else I've missed pops up.

I might actually put up a snapshot release so non-compiling people can help test.

Watch this space.

Edit:

Windows exe (dev edition) and data upgrade pack @ rev 952,
http://sourceforge.net/projects/glestae/files/snapshots/gae_win32_rev952.7z/download

Awesome Silnarm! I applaud you making a snapshot release, because my MSVS is totally shot up (can't seem to create projects) and have yet to learn any other compilers... I'll download at home (SF is blocked at school... )

[ChupaReaper]

The snapshot is working great only the lag is still there in 256 and 512 maps but the new descriptions and faction symbols are great, so are the minimap colours.

[John.d.h]

Crashes on Wine.   When clicking "new game", I get this:
Exception: SocketError in : getIP() [Error code: 110]
Connection timed out

Will try on *shudder* Windows.

[-Archmage-]

The snapshot is working great only the lag is still there in 256 and 512 maps but the new descriptions and faction symbols are great, so are the minimap colours.

Oh this reminded me, when playing on my main computer, I lagg up until I freeze. Can't be graphics because we have a relatively powerful ATI Radeon HD 4670(ftw!!!), processor is dual-core plenty to handle Glest. MG works fine with massive battles, or 256 maps.

My conclusion: Problem with GAE, and/or libs it uses.

Crashes on Wine.   When clicking "new game", I get this:
Exception: SocketError in : getIP() [Error code: 110]
Connection timed out

Will try on *shudder* Windows.

Win7 isn't bad. Better than Linux in many ways, but not all.

[wciow]

Great stuff Silnarm   works good on Win7.

The new faction logos and tool tips are a really nice addition which fit seamlessly with Glest and make it feel more polished.

EDIT: show map option still appears to be broken on windows  :'(

[silnarm]

Thanks for the feedback guys 

'showmap' is working, but I didn't have the default data directory set right on that build, which will break it, and the program shortcuts ... 

Re. performance issues on big maps.
I just did a 'longish' profile on a 256x256 map, accelerating the action by giving everyone a bunch of units from the Lua console. It spent an inordinate amount of time in the functions related to the hierarchical search... Something is indeed very wrong, but I wouldn't have a clue what at this stage, and it may take a while to track down the problem.

[ChupaReaper]

Re. performance issues on big maps.
I just did a 'longish' profile on a 256x256 map, accelerating the action by giving everyone a bunch of units from the Lua console. It spent an inordinate amount of time in the functions related to the hierarchical search... Something is indeed very wrong, but I wouldn't have a clue what at this stage, and it may take a while to track down the problem.

Well having more players and different faction increases how fast the lag comes and 512 maps lag faster.

[silnarm]

Here's another snapshot exe and data patch for windows, (attack notice sounds were added for tech and magic, and guard and patrol commands were tweaked a bit)

http://sourceforge.net/projects/glestae/files/snapshots/gae-win32-r970.zip/download

Performance on big maps should be much better, 256x256 maps should be ok, but you may still get lag if a whole bunch of units wanting to go to the other side of the map hit the pathfinder all at once. 512x512 maps are probably not ok, additional 'hierarchies' for the path-finder will solve this, I've added that to the list for 0.4.

Enjoy.

[ChupaReaper]

Started a 256 map with 8 players, sent some workers to go and build, a second after them moving it crashed:

(click to show/hide)

Crash
Version: Advanced Engine 0.3.x @ rev.970
Time: Tue Nov 30 02:48:17 2010
Description: Access violation (Reading address: 0x8C001A3E)

Call Stack:
  Frame       Code address
  0x010FF344  0x003DCA53
  0x010FF35C  0x003DCB60
  0x00000000  0x004F46CD PHYSFS_writeSBE64+0x1749d

=======================

Edit: Tried a 128 map and got the same crash, nothing to do with build because the units managed to place the be_built state of the building where as on the 256 map they just started moving to the build site. I think I've got some 'missing' textures, they weren't missing before, maybe my tgas aren't right or there's some odd bug... I'll reformat the tgas and test again later.

[ultifd]

Oh yeah, I forgot to report that I always get that problem...weird. And yeah, it doesn't matter on the map, it'll crash on any...

[silnarm]

Oops.

I can't reproduce on a debug build, nor a release-with-debug-info, but easily enough on a straight 'release'. Looks like the missing pdb was causing the problem, new build (windoze),
http://sourceforge.net/projects/glestae/files/snapshots/gae-win32-r979.zip/download

@ultifd: I think because we use exceptions to pass control around in a few non-exceptional circumstances ( ) the new windows exception handler tries to load the pdb, if it can't find it, it chokes... until I figure it out for sure and fix it, switch your build configuration to 'RelWithDebInfo' and it should all work fine.

[ChupaReaper]

Thanks for the quick responce, the crash has gone now but still unplayable framerates on 256 maps  .