- mwha2.JPG
- (5.28 KiB) Downloaded 87 times
Planning for 0.77 Release
Moderator: Moderators
Re: Planning for 0.77 Release
All the icons are using the old first generation icons. There are shiny new icons, they need to be used, if only because there are icons in the current generation that do not exist in the first generation and the consistency.
Re: Planning for 0.77 Release
AF: +1
I think it's time to merge some recent fixes and make an RC if we're going to make it in August.
I think it's time to merge some recent fixes and make an RC if we're going to make it in August.
Re: Planning for 0.77 Release
tasclient should be ready to be included in the 0.77 installer :
http://tasclient.it-l.eu/TASClientLatest.7z
http://tasclient.it-l.eu/TASClientLatest.7z
Re: Planning for 0.77 Release
Aus: suggested merges before RC release:
- 6254 (you made it)
- 6255
- 6259 unless jk gets to do whatever he has in mind before you take a look at this post - with a registry change this fixes major display issues on some cards
- 6260
- 6261 (delete vs. delete[])
- 6263 - only adds #includes in several files so it compiles cleanly in gcc 4.3-mingw
- 6271 + 6266
- 6272 + 6273 - the only large change, but description sounds like it's worth having
optionally:
- 6262 + 6243 - looks fixed
those are basically all engine-related commits since the last merge - no new features except 6262+6243, and it's not a big one. I'd say that applying all those will give a nice release candidate.
- 6254 (you made it)
- 6255
- 6259 unless jk gets to do whatever he has in mind before you take a look at this post - with a registry change this fixes major display issues on some cards
- 6260
- 6261 (delete vs. delete[])
- 6263 - only adds #includes in several files so it compiles cleanly in gcc 4.3-mingw
- 6271 + 6266
- 6272 + 6273 - the only large change, but description sounds like it's worth having
optionally:
- 6262 + 6243 - looks fixed
those are basically all engine-related commits since the last merge - no new features except 6262+6243, and it's not a big one. I'd say that applying all those will give a nice release candidate.
Re: Planning for 0.77 Release
If there's going to be a release candidate before the actual b1, I'd
rather have it based on trunk/ head so that the last two pre-freeze
features added (6235 + 6236, 6243 + 6262) can get some testing
exposure too; they're both minor and the decision to withhold them
from .77 can always be made later anyway.
rather have it based on trunk/ head so that the last two pre-freeze
features added (6235 + 6236, 6243 + 6262) can get some testing
exposure too; they're both minor and the decision to withhold them
from .77 can always be made later anyway.

Re: Planning for 0.77 Release
got .77 running.
Framerate improvements of @ 30-60 fps from ~15-20ish
I can run dynamic water at about 24 fps from 1 with glitching.
Framerate improvements of @ 30-60 fps from ~15-20ish
I can run dynamic water at about 24 fps from 1 with glitching.
Re: Planning for 0.77 Release
Is there any progress on 64bit unitsync?
Re: Planning for 0.77 Release
unfortunately not yet. didn't get around to installing any kind of 64bit OS on a new box, and am somewhat scared at getting all the dependencies in 64 bits, too.
Re: Planning for 0.77 Release
I thought 32bit OS could compile 64bit program? I know it cant run 64bit program but there's no reason why it couldn't compile it.
Re: Planning for 0.77 Release
Cross compiling isn't easy (or should I say: extraordinarily hard?), in particular if you also have to cross compile a whole dependency chain.
Re: Planning for 0.77 Release
As I said here, you can try to cross-compile Spring with mingw64 just by joining #buildserv channel and hitting "!rebuild sys=windows64" (it will upload the resulting binaries automatically if build process succeeds...). However, mingw64 is in alpha stage, and using experimental gcc 4.4, so don't expect it to work perfectly right now, but that's all I can do personally...AF wrote:Is there any progress on 64bit unitsync?
-
- Spring Developer
- Posts: 1254
- Joined: 24 Jun 2007, 08:34
Re: Planning for 0.77 Release
New version: http://planetspring.free.fr/spring/inst ... 0.77a1.exe
I copied _all_ patches over from trunk because the latest patches are a pain to backport, and hopefully nothing will break.
Call it a release canidate, or don't. But please help with testing.
PS.: I'm on 82.239.138.44:8300 tomorow evening, ready to play testgames.
I copied _all_ patches over from trunk because the latest patches are a pain to backport, and hopefully nothing will break.
Call it a release canidate, or don't. But please help with testing.
PS.: I'm on 82.239.138.44:8300 tomorow evening, ready to play testgames.
Re: Planning for 0.77 Release
I'll try to be there. BA doesn't work (Noize hint hint), so I guess we're left with CA when it comes to TA mods (dunno about XTA, never played it TBH.) KP also has some issues I think.
Re: Planning for 0.77 Release
What timezone? And would you be willing to test P.U.R.E. & World Builder?tomorow evening
Re: Planning for 0.77 Release
I'll definatly come play if I have time then (depends on timezone) Google_frog is asking me for a game everytime I almost have to go or when i'm not around, so I've played pure only once so far 

Re: Planning for 0.77 Release
SpringDownloader is not included in the installer (and it should check for .NET framework)
edit : checking CA in the mod list should install the latest stable CA. SpringDownloader must be a different option next to TASClient
There is no option to use SpringLobby instead of TASClient ...
LuaUI is not enabled by default
and BA works i just made a quick test and didn't get any crash nor error
edit 2 : and the Python dir from the TASClient 7z should be included too
edit : checking CA in the mod list should install the latest stable CA. SpringDownloader must be a different option next to TASClient
There is no option to use SpringLobby instead of TASClient ...
LuaUI is not enabled by default
and BA works i just made a quick test and didn't get any crash nor error
edit 2 : and the Python dir from the TASClient 7z should be included too
Last edited by Satirik on 20 Aug 2008, 20:44, edited 2 times in total.
Re: Planning for 0.77 Release
There is already .net check and .net install if you select CA mod in current installer -> this should be instead moved as prerequisites for tasclient and latest springdownloader installed
(from
http://files.caspring.org/caupdater/Spr ... loader.exe)
also when you check CA mod it should not install outdated CaDownloader but instead get the latest stable version of CA from
http://files.caspring.org/snapshots/latest.sdz.php
(from
http://files.caspring.org/caupdater/Spr ... loader.exe)
also when you check CA mod it should not install outdated CaDownloader but instead get the latest stable version of CA from
http://files.caspring.org/snapshots/latest.sdz.php
Re: Planning for 0.77 Release
Regarding LuaUI - springdownloader asks to enable lua and tells people they can configure widgets using F11, but imo it should be on by default anyway.
Re: Planning for 0.77 Release
mmmh springdownloader should not do that ... springsettings should or the installer itselfLicho wrote:Regarding LuaUI - springdownloader asks to enable lua and tells people they can configure widgets using F11, but imo it should be on by default anyway.
Re: Planning for 0.77 Release
I agreeSatirik wrote:mmmh springdownloader should not do that ... springsettings should or the installer itselfLicho wrote:Regarding LuaUI - springdownloader asks to enable lua and tells people they can configure widgets using F11, but imo it should be on by default anyway.