Request: 0.76b2

[ZellSF]

this isn't a matter of time tables, people are doing this work in their spare time. They cannot just say, hey let's make a push for a release because X person wants it. Believe me, I just found a fucking fail new bug just last night, I would love to see a fix with roll out but it is not that simple. With all fixes and improvements can come new bugs, some of which may make spring less stable.

FURTHER MORE if the developers push themselves to hurry up and make a release it will take an emotional toll on them. NOT ONLY are they giving up their spare time but you want them to hurry it up? Shit dude, that is a good way to loose volunteers. Rushing a timetable only ever means putting more man hours in over a shorter period of time.

In the terms of a regular work week you are asking for over time. and you are asking for it from volunteers.

You seriously need to relax a bit O_o

All I said was, that I want a release, not that I demand one, I'm sure everyone wants a new release, no need to get all defensive when someone actually says so. Just ignore it, like I'm sure most of the devs do :p

No one's expecting them to do more work than they want to.

[Acidd_UK]

The point I was trying to make is that at this stage, I feel that a pretty widespread and significant bug has been found and fixed, and that another beta/bugfix release would be worth while. As has been said, imbaczek has done a lot of the hard work already in backporting all the bugfix commits to his test branch. 'All' it needs now is for someone to rubber-stamp it as an acceptable release and update the website etc. I am not demanding this is done (which I hope noone thought), but for thos of us playing and enjoying the game, this will be a nice stopgap while we wait for all the sexy new features to be more stable.

I have some other ideas but I will leave them for now, don't want to sound too demanding !

[smoth]

I'd hate to even pressure them zell, I want them to take their time and not feel any pressure. I am sure they want to release the new fixes just as much as we would like to see them.

[el_matarife]

What tasks are required to make a "real" release anyway? We have buildbot to build test releases, we have a bunch of willing community volunteers to test those releases, what else is needed? I mean sure, there's probably going to be some bugs that have to get fixed once we find them, but if we can pull off a proper really stable bugfix release there wouldn't necessarily need to be another new release for months and months until there's some compelling feature that everyone thinks should be released to the public at large. Honestly, scheduling releases for every 6 months like clockwork might not be such a bad idea either given lots of open source projects do that now.

[YokoZar]

The point I was trying to make is that at this stage, I feel that a pretty widespread and significant bug has been found and fixed, and that another beta/bugfix release would be worth while. As has been said, imbaczek has done a lot of the hard work already in backporting all the bugfix commits to his test branch. 'All' it needs now is for someone to rubber-stamp it as an acceptable release and update the website etc. I am not demanding this is done (which I hope noone thought), but for thos of us playing and enjoying the game, this will be a nice stopgap while we wait for all the sexy new features to be more stable.

I have some other ideas but I will leave them for now, don't want to sound too demanding !

By the way, if you are on Ubuntu Hardy this has already been done. All the changes are in unsynced code, so play with others on 0.76b1 works fine except you crash a lot less. Took me all of an hour to do.

[Acidd_UK]

Legendary. Sadly I only have Ubuntu installed on my media box in the lounge, but I do have a spare hard drive in this PC....

[KDR_11k]

So that means the impulsefactor fix for melee weapons is not included?

[imbaczek]

unfortunately yes, as isn't area reclaim bug fixed.

[ZellSF]

Uh? I'm pretty sure I read it was fixed, or at least made less likely to happen

[imbaczek]

it's fixed in svn, but cannot be fixed in 0.76b2 without breaking sync (that is, replays.)

[Acidd_UK]

I think imbaczek means it's not fixed on his branch, as opposed ot the main svn.

Edit: Damn, too slow.

[KDR_11k]

I'd prefer a 76b2 that was based on the current SVN instead of a backport of a small number of fixes.

[Acidd_UK]

/me screams.

[LordMatt]

I'd prefer a 76b2 that was based on the current SVN instead of a backport of a small number of fixes.

Then it will be ready in several months vs several weeks.

[ZellSF]

http://gitorious.org/projects/spring-sv ... /logs/next

please use this as a reference, perhaps maybe create your own tree on gitorious.

EDIT: a new build: http://spring.jobjol.nl/show_file.php?id=997

If I understand this right, this is supposed to sync with 0.76b1? If so, how do I get TASClient not to crash horribly with this?

[imbaczek]

bug satirik about it, or overwrite 76b1 unitsync.dll. dunno what exactly crashes tasclient.

[ZellSF]

I just tried one game of it. Very laggy, yet my ping showed up as 0ms... using 0.76b1 unitsync.

Lag might or migt not be related to it being a DeltaSiegeDryRevX game... though the ping times seemed fine.

Edit: also is it possible to make a SMP build that syncs yet?
Edit2: and I just got disconnected after alt-tabbing out and in of a game with a "Client read net wanted quit" message
Edit3: hmm lag in another game...
Edit4: are there some massive optimizations included or does it just seem like it?

It says test against 0.76b1, what exactly is supposed to be tested?

[imbaczek]

sync, mostly. it's supposed to be able to play against unpatched 76b1.

[ZellSF]

Sync seems fine so far. Lag was a little less last game, so maybe it's just crappy hosts. I would like to actually see my own ping though

[ZellSF]

Code: Select all

[Anneddielation] forcing game start by [lcc]jk
GameID: 84d71448d447eef9aaa121916dc92d27
GetLuaCmdDescList() non "actions" table
GetLuaCmdDescList() non "actions" table
GetLuaCmdDescList() non "actions" table
GetLuaCmdDescList() non "actions" table
Spring 0.76b1 has crashed.
Exception: Access violation (0xc0000005)
Exception Address: 0x006f6b36
DLL information:
0x00400000	spring
0x7c900000	ntdll
0x7c800000	kernel32
0x77dd0000	ADVAPI32
0x77e70000	RPCRT4
0x77fe0000	Secur32
0x73f10000	dsound
0x77c10000	msvcrt
0x7e410000	USER32
0x77f10000	GDI32
0x774e0000	ole32
0x76b40000	WINMM
0x77c00000	VERSION
0x68b20000	GLU32
0x5ed00000	OPENGL32
0x73760000	DDRAW
0x73bc0000	DCIMAN32
0x76c90000	IMAGEHLP
0x71ad0000	WSOCK32
0x71ab0000	WS2_32
0x71aa0000	WS2HELP
0x6ed80000	glew32
0x10000000	ILU
0x00c10000	DevIL
0x00da0000	SDL
0x7c340000	MSVCR71
0x6e140000	boost_thread-mgw43-mt-1_35
0x6fbc0000	mingwm10
0x66fc0000	freetype6
0x61b80000	zlib1
0x76390000	IMM32
0x629c0000	LPK
0x74d90000	USP10
0x01570000	SC2Hook
0x77120000	oleaut32
0x01790000	Pitadll
0x76bf0000	PSAPI
0x77f60000	SHLWAPI
0x73dd0000	MFC42
0x7c9c0000	SHELL32
0x773d0000	comctl32
0x5d090000	comctl32
0x77b40000	apphelp
0x755c0000	msctfime
0x69500000	nvoglnt
0x71a50000	mswsock
0x662b0000	hnetcfg
0x71a90000	wshtcpip
0x76c30000	WINTRUST
0x77a80000	CRYPT32
0x77b20000	MSASN1
0x72d20000	wdmaud
0x72d10000	msacm32
0x77be0000	MSACM32
0x77bd0000	midimap
0x73ee0000	KsUser
0x59a60000	DBGHELP
Stacktrace:
(0) C:\Program Files\Spring\spring.exe [0x006F6B36]
(1) C:\Program Files\Spring\spring.exe [0x00702932]
(2) C:\Program Files\Spring\spring.exe [0x006A7CAA]
(3) C:\Program Files\Spring\spring.exe [0x00408792]
(4) C:\Program Files\Spring\spring.exe [0x0040CA60]
(5) C:\Program Files\Spring\spring.exe [0x0040CDEA]
(6) C:\Program Files\Spring\spring.exe [0x0040CF68]
(7) C:\Program Files\Spring\spring.exe [0x00761710]
(8) C:\Program Files\Spring\spring.exe [0x0040124B]
(9) C:\Program Files\Spring\spring.exe [0x004012B8]
(10) C:\WINDOWS\system32\kernel32.dll(RegisterWaitForInputIdle+0x49) [0x7C816FD7]

CA crash.