3.1 beta4 has been released! (And beta3 has been skipped.)

[Emdek]

zany, pick changeset after changeset and recompile and test every one after last point where you are sure that they worked properly (but don't go too far into past, as it could take weeks).

[cybersphinx]

http://linux.die.net/man/1/git-bisect

You take a working revision, a broken revision, and then try the middle. Repeat until you arrive at one commit.

[zany]

zany, pick changeset after changeset and recompile and test every one after last point where you are sure that they worked properly (but don't go too far into past, as it could take weeks).

seriously? if I could do that myself I wouldn't have asked

[zany]

http://linux.die.net/man/1/git-bisect

You take a working revision, a broken revision, and then try the middle. Repeat until you arrive at one commit.

this means nothing to me you guys need to make the program so we can test or it won't work! and how do I know what the working version was? 2.3.9 is what version in 3.1?

[Emdek]

zany, why you can't? You don't have root / administrator privileges on machine you are using to install compiler?

[zany]

zany, why you can't? You don't have root / administrator privileges on machine you are using to install compiler?

why do I have to learn how to do all that sh*t if you guys can already do it faster than me and have uploads ready instantly? I don't see the problem here just make builds like you guys normally do and we test. if you don't want people to test then say so and stop BSing us about installing compiler sh*t and do it ourselves

[Emdek]

zany, I doubt if any of developers has time to do that way.

The point is that you should finally learn that things you request aren't so easy to do.

[zany]

zany, I doubt if any of developers has time to do that way.

The point is that you should finally learn that things you request aren't so easy to do.

that isn't the point. the point is that if they want to get to the bottom of what is causing the problem the one I mentioned will find it. if not then they just sit here saying how they can't find the problem. if they don't want help then they should say so and we can all skip these releases since they won't be able to fix the problem

[cybersphinx]

http://linux.die.net/man/1/git-bisect

You take a working revision, a broken revision, and then try the middle. Repeat until you arrive at one commit.

this means nothing to me you guys need to make the program so we can test or it won't work! and how do I know what the working version was? 2.3.9 is what version in 3.1?

Well, if you're up to testing it, I'll compile stuff: viewtopic.php?f=6&t=9107

[zydonk]

@zany: I don't want to get drawn into a discussion I know little about, but it seems to me you need work up through the pre3.n masters to find the break in the savegame function. Working from 2.3.9 to 3.n makes no sense.

For my own part, I content myself with 239. I'm not hung up on terrain and the plethora of little numbers may be of benefit to mp - which seems to me counterintuitive (numbers require more interpretation that bar graphs) - but I find them fussy and distracting.

The loss of the 110 mod doesn't help, of course.

[Emdek]

zydonk, offending changeset is already identified and now only needs solution.

EDIT:
Apparently the solution is on it's way.

[cybersphinx]

Well, let's see if this is the solution:
http://wz2100.net/~cybersphinx/3200/war ... 5de09c.exe
http://wz2100.net/~cybersphinx/3200/war ... 5de09c.zip (not sure if this works with the data from beta4)
http://wz2100.net/~cybersphinx/3200/war ... 09c.tar.gz
It's the current bugfixes branch merged into current 3.1, plus Cyp's fix, and not pushed anywhere, so there's a tarball as well. Do your worst trying to break it.

[Emdek]

cybersphinx, it works (3 minutes of "playing" with single Nexus AI).

[zany]

Well, let's see if this is the solution:
http://wz2100.net/~cybersphinx/3200/war ... 5de09c.exe
http://wz2100.net/~cybersphinx/3200/war ... 5de09c.zip (not sure if this works with the data from beta4)
http://wz2100.net/~cybersphinx/3200/war ... 09c.tar.gz
It's the current bugfixes branch merged into current 3.1, plus Cyp's fix, and not pushed anywhere, so there's a tarball as well. Do your worst trying to break it.

works

[Lord Apocalypse]

Camera rotation is glitchy. Not entirely sure it has anything to do with camera angle or the zoom as was previously suspected. Anyone else experience this?

If you hold down right mouse button and try to rotate the camera it sometimes doesn't move or the movement get kinda jerky.