Hum so i have to compile the current trunk version of the SVN, right ?Buginator wrote:Sure thing!Zoloom wrote:I'm on Ubuntu 32 bits and i'm currently to the first mission against the collective.
I found one bug here : viewtopic.php?f=19&t=2064
Can i become a beta-tester for helping you yo find some bugs ?
Thanks ^^
We are always looking for testers!
If possible, it would be best to play 2.1 branch, and not the current beta 4, since that is fairly old now, and lots of bugs in that have already been fixed.
Beta-testers for campaign needed
Re: Beta-testers for campaign needed
French helper / Assistant Français (envoyez moi des messages privés si vous cherchez des réponses en français (dans la limite de mes capacités)).
Xfire : zoloom
"Software is like sex, it's better when it's free"
Xfire : zoloom
"Software is like sex, it's better when it's free"
Re: Beta-testers for campaign needed
Zarel wrote:Is there a difference between that and trunk? Where do I find that?Buginator wrote:Sure thing!
We are always looking for testers!
If possible, it would be best to play 2.1 branch, and not the current beta 4, since that is fairly old now, and lots of bugs in that have already been fixed.
Trunk is: http://svn.gna.org/svn/warzone/trunk (svn co http://svn.gna.org/svn/warzone/trunk)Zoloom wrote:Hum so i have to compile the current trunk version of the SVN, right ?
2.1 is http://svn.gna.org/svn/warzone/branches/2.1 (http://svn.gna.org/svn/warzone/branches/2.1)
In this case, since we are going to release another beta (or perhaps a 'stable') 2.1, that is the one that needs testing.
Then once 2.1 goes 'stable', then we need testing on trunk.
If on linux or macs, then yes, you need to compile your own builds.
If on windows, then there is a nightly build available in another thread.
Hope that clears everything up.
Re: Beta-testers for campaign needed
Ok thanks to you.
I will check this out when i will arrived to compile the 2.1 -.-"
I will check this out when i will arrived to compile the 2.1 -.-"
French helper / Assistant Français (envoyez moi des messages privés si vous cherchez des réponses en français (dans la limite de mes capacités)).
Xfire : zoloom
"Software is like sex, it's better when it's free"
Xfire : zoloom
"Software is like sex, it's better when it's free"
-
- New user
- Posts: 5
- Joined: 21 Aug 2008, 05:30
Re: Beta-testers for campaign needed
I would like to help out with campaign testing on beta 4.
1. what do i need ( just the beta 4 DL)?
2. how do you get in debug mode?
Thanks
1. what do i need ( just the beta 4 DL)?
2. how do you get in debug mode?
Thanks
Re: Beta-testers for campaign needed
let me quote myself:Dragonspider wrote:I would like to help out with campaign testing on beta 4.
1. what do i need ( just the beta 4 DL)?
2. how do you get in debug mode?
Thanks
If you can help, then please don't test with beta 4. There have been tons of bug fixes that were already found & fixed. We need testing on http://svn.gna.org/svn/warzone/branches/2.1 .Trunk is: http://svn.gna.org/svn/warzone/trunk (svn co http://svn.gna.org/svn/warzone/trunk)
2.1 is http://svn.gna.org/svn/warzone/branches/2.1 (http://svn.gna.org/svn/warzone/branches/2.1)
In this case, since we are going to release another beta (or perhaps a 'stable') 2.1, that is the one that needs testing.
Then once 2.1 goes 'stable', then we need testing on trunk.
If on linux or macs, then yes, you need to compile your own builds.
If on windows, then there is a nightly build available in another thread.
Hope that clears everything up
You want the debug builds (which can crash more than release builds, since it has extra checks in it to catch 'bad' values).
We don't want you to use debug mode or cheats while testing though. Those can & do cause issues if you don't know what your doing.
Thanks!
- psychopompos
- Trained
- Posts: 470
- Joined: 08 Nov 2007, 09:18
- Location: UK
Re: Beta-testers for campaign needed
i might be able to do that, as i just went from 2.0 to 2.1 b5 on Thursday.Buginator wrote: You want the debug builds (which can crash more than release builds, since it has extra checks in it to catch 'bad' values).
We don't want you to use debug mode or cheats while testing though. Those can & do cause issues if you don't know what your doing.
Thanks!
is it simply playing & reporting annoying stuff?
or are there specific things to do?
----------------------------
mission one annoyances noticed.
unable to set multiple structures with shift key.
queue orders doesn't seem to be working at all actually.
could it be that i changed the key mapping?
the build menu behaviour doesn't change regardless of being set to reopen or not.(it just wont re-open)
might i suggest its behaviour is changed to "closes" or "stays open until closed/replaced"
path finding is feels more responsive, though seems dumber.
after exiting game in windowed mode & restarting with normal shortcut, game resumes in windowed mode.
game wont start if you specify "--fullscreen"
have to change it back to fullscreen in video options.
specify that the game launches fullscreen unless specifically told not to?
.......
alt-tab caused a hang of some kind
game became unresponsive
curser changed in reaction to the edge of the task bar & the buttons(smils etc) on this page, yet visually the game did not exit.
ctrl+alt+del did not bring up task manager, at least not visually.
winkey + L / L to log off & log on again to get back to desktop, didnt work, winkey + U / U didnt work.
had to hard off the system.
though this might be due to ati.