Test builds for people who have issues with game speed

[Shadow Wolf TJC]

i think hard to catch good results without special testing maps (where warzone loaded enough).
Without testing maps i think impossible get lower than 60 fps without long game.

If Contingency is usable on any of these builds, then perhaps a high-oil AI match, consisting of equal numbers of NullBots, perferably NullBotSWs, being pitted in teams against eachother, on a big map such as 10c-Emergence or 9c-Windfury, could bring valuable performance data in terms of which builds lag more than others, since you're pretty much guaranteed to see over 800 units moving about the map at any given time?

[NoQ]

Shadow Wolf TJC: It will interfere with javascript lag that has nothing to do with the problem.

[Ezio]

using reg312 map, not moving around, nullbot, and running all test at once
640x480
2048 tex res
AA 8x
and shaders

t1 3-4 fps
t2 ~15 max seen 25 after 5 mins and 30 at 7 mins
t3 ~8
t4 a bit stable than T2, but max and min almost same so i cant really differentiate it

can i pick more than one?
edit: add attachment

*offtopic

Spoiler:

u can't/shouldn't run all of them at once?, got error when closing

Code: Select all

--- Starting log [C:\Program Files (x86)\Warzone 2100-3.1.0\Warzone 2100 3.1\logs\WZlog-0303_023534.txt]---
info    |02:35:34: [realmain:1145] Using C:\Program Files (x86)\Warzone 2100-3.1.0\Warzone 2100 3.1\logs\WZlog-0303_023534.txt debug file
info    |02:35:35: [pal_Init:51] Buffer overrun reading palette data
info    |02:35:35: [pal_Init:51] Assert in Warzone: piepalette.cpp:51 (lenLeft >= 0), last script event: ''

Code: Select all

-------------------

Error occured on Sunday, March 3, 2013 at 03:02:03.

Program: C:\Program Files (x86)\Warzone 2100-3.1.0\warzone2100_portableT4.exe(warzone2100)
Command line: "C:\Program Files (x86)\Warzone 2100-3.1.0\warzone2100_portableT4.exe" 
Version: Version 3.1.D - Built Feb 27 2013
Distributor: wz2100.net
Compiled on: Feb 27 2013 20:49:32
Compiled by: GCC 4.7.0
Compiled mode: Release build
Executed on: Sun Mar 03 02:38:57 2013

Pointers: 32bit

Compiled against PhysicsFS version: 2.0.3
Running with PhysicsFS version: 2.0.3

Misc Data:
[02:38:58]Video Mode 640 x 480 (window)
[02:38:58]OpenGL Vendor: NVIDIA Corporation
[02:38:58]OpenGL Renderer: GeForce GT 555M/PCIe/SSE2
[02:38:58]OpenGL Version: 4.3.0
[02:38:58]GLEW Version: 1.7.0
[02:38:58]OpenGL GLSL Version : 4.30 NVIDIA via Cg compiler
[02:38:58]OpenAL Device Name: DirectSound Default
[02:38:58]OpenAL Vendor: OpenAL Community
[02:38:58]OpenAL Version: 1.1 ALSOFT 1.13
[02:38:58]OpenAL Renderer: OpenAL Soft
[02:38:58]OpenAL Extensions: AL_EXT_DOUBLE AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_MULAW AL_EXT_MULAW_MCFORMATS AL_EXT_OFFSET AL_EXT_source_distance_model AL_LOKI_quadriphonic AL_SOFT_buffer_sub_data AL_SOFT_loop_points
[02:38:58]Using Backend: SDL
[02:38:58]Using language: System locale
[02:42:38]Current Level/map is NTW_FPStest-T1


C:\Program Files (x86)\Warzone 2100-3.1.0\warzone2100_portableT4.exe caused an Access Violation at location 5e750be3 in module C:\WINDOWS\SYSTEM32\nvoglv32.DLL Reading from location 791d84d0.

Log message: info    |02:38:57: [realmain:1145] Using C:\Program Files (x86)\Warzone 2100-3.1.0\Warzone 2100 3.1\logs\WZlog-0303_023857.txt debug file
Log message: info    |02:38:58: [pal_Init:51] Buffer overrun reading palette data
Log message: info    |02:38:58: [pal_Init:51] Assert in Warzone: piepalette.cpp:51 (lenLeft >= 0), last script event: ''
Log message: info    |02:39:50: [loadMapPreview:456] Loading map preview: "Sk-Rush" builtin t2
Log message: info    |02:39:54: [loadMapPreview:460] Loading map preview: "NTW_FPStest-T1" in (C:\Program Files (x86)\Warzone 2100-3.1.0\Warzone 2100 3.1\)"maps/10c-NTW_FPStest.wz"  d23838cfea6589e5c70a81065ba28527d8fc10489b317563bf15312c736426ed t2

Registers:
eax=791d84d0 ebx=05757aa8 ecx=05757aa8 edx=00008246 esi=00000438 edi=0028f3b4
eip=5e750be3 esp=0028f344 ebp=0028f354 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00210202

Call stack:
5E750BE3  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E750BE3
5E6BB154  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E6BB154
5E6BB53B  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E6BB53B
5E059E35  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E059E35
5E059C7B  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E059C7B
5E08C26B  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E08C26B
5E6E8DBA  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E6E8DBA
5E089BF1  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E089BF1
5E01C975  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E01C975
5E6B9365  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E6B9365
5E846910  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E846910  DrvPresentBuffers
5E7EACFF  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E7EACFF
5E7F7274  C:\WINDOWS\SYSTEM32\nvoglv32.DLL:5E7F7274  DrvDeleteContext
6315C25D  C:\WINDOWS\SYSTEM32\OPENGL32.DLL:6315C25D  wglDeleteContext
0068A469  C:\Program Files (x86)\Warzone 2100-3.1.0\warzone2100_portableT4.exe:0068A469  SDL_iconv_string

[vexed]

Interesting results.

No, you can't vote for more than one build...
I see we have at least 5 downloads for each, but only 2 votes.

About that crash,

Spoiler:

That looks like it crashed in the nvida drivers

I guess I should have mentioned to list your machine specs as well.

[Reg312]

vexed what machine you have? may be your machine too strong to make lags visible in T1 build?

[Per]

i think hard to catch good results without special testing maps (where warzone loaded enough).
Without testing maps i think impossible get lower than 60 fps without long game.

Thank you for making this test map. I agree it is hard to do a test without a specific map to test on.

Here on my wintendo laptop, T1 is slower than the others by a factor of two (starting at 35 fps vs 70-80 fps for the others).

[vexed]

BTW, what is the reason of making a 10p map, if you only enable 2p ?
And that unit count is way over the limits.

My system is a lowly 3.8GHz quad core slouch.

[Originway]

vexed make us some test builds for http://developer.wz2100.net/ticket/3748 please!

[Ezio]

vexed make us some test builds for http://developer.wz2100.net/ticket/3748 please!

seriously??

[effigy]

I still haven't done a thorough test, but just wanted to comment that the T4 build seems to run a lot faster than the 3.1.0 release.

It seems like MP lags are merely connection based with this build. The game does get lower performance as time goes on, however screen stutters are pretty consistant with seeing "zzz" in relation to another players ping.

I'm running the exe directly in the root folder of my portable warzone. So new maps are being downloaded to .\Warzone 3.1.0\Warzone 3.1.0\Maps, and likewise for the config, though my sta and map files from the existing portable warzone intall are are accessible.

Operating System
MS Windows XP Professional 32-bit SP3
CPU
Intel Core Duo T2600 @ 2.16GHz 24 °C
Yonah 65nm Technology
RAM
2.00 GB Dual-Channel DDR2 @ 333MHz (5-5-5-15)
Motherboard
AOpen i945GTm-VHL (Socket 479) 36 °C
Graphics
Default Monitor (1680x1050@60Hz)
128MB Quadro NVS 285 (nVidia) 50 °C
Hard Drives
78GB Seagate ST3808110AS (SATA) 36 °C
1954GB Western Digital WDC WD20EARX-00PASB0 (SATA) 30 °C
Optical Drives
NEC DVD_RW ND-2510A
ELBY CLONEDRIVE SCSI CdRom Device
ELBY CLONEDRIVE SCSI CdRom Device
Audio
Realtek High Definition Audio

[NoQ]

It seems like MP lags are merely connection based with this build. The game does get lower performance as time goes on, however screen stutters are pretty consistant with seeing "zzz" in relation to another players ping.

Which may just mean that some player on the other end has more performance issues than you, being unable to run the game at a speed of one second per second. Not necessarily a network issue (?)

[Originway]

vexed make us some test builds for http://developer.wz2100.net/ticket/3748 please!

seriously??

what is wrong with asking?
they can make test builds as seen in this thread

[Ezio]

nevermind

[effigy]

It seems like MP lags are merely connection based with this build. The game does get lower performance as time goes on, however screen stutters are pretty consistant with seeing "zzz" in relation to another players ping.

Which may just mean that some player on the other end has more performance issues than you, being unable to run the game at a speed of one second per second. Not necessarily a network issue (?)

I agree.

[Berg]

I have to agree also with NoQ
But a lot of my issues was deleted when vexed gave me a Linux version of these windows builds so for me its better.