[The E]

That is correct and as intended.

[Vladislav]

Then what is different between 3.6.14 RC1 and the latest 3.6.13 builds, other than the sound code?

[The E]

The sound code.

The point is, this is a snapshot of the current svn, one we feel is stable and feature-rich enough to deserve the label "3.6.14". Barring some bugs appearing in there, that's what is going to be the next stable version.

[QuantumDelta]

And while it does deserve the label 3.6.14 the emphasis is on release CANDIDATE, it is still a developmental build, same as the .13 nightlies, do not confuse it with a release build.

[Nuke]

i think the reason it carries the 3.6.13 version number is so that it doesnt get mistaken for a release build (which i believe has happened before) causing support issues. so consider it an evaluation of trunk which may or may not become the 3.6.14 build of which there should only be one.

[Iss Mneur]

i think the reason it carries the 3.6.13 version number is so that it doesnt get mistaken for a release build (which i believe has happened before) causing support issues. so consider it an evaluation of trunk which may or may not become the 3.6.14 build of which there should only be one.

That is precisely the reason that the RC identifies itself as .13 and why we skip the odd numbers for the releases so that the version number is always increasing.

[Qent]

http://scp.indiegames.us/mantis/view.php?id=2509 still happens. http://pastebin.com/YHx5QhX3

[Iss Mneur]

http://scp.indiegames.us/mantis/view.php?id=2509 still happens. http://pastebin.com/YHx5QhX3

I have posted a reply in that thread.  Lets continue the debugging there.

If anyone else is able to replicate the issue that Qent is reporting please post in the linked thread

[The_Force]

Also This is still hapening http://scp.indiegames.us/mantis/view.php?id=2506

[The E]

Without more detailed information about how to reproduce that crash, there's nothing we can do to fix it.

[mjn.mixael]

That's a duplicate of this bug.

[Cyborg17]

I'm still getting the subspace flare issue on this build.

I couldn't find the Mantis issue, sorry.

[Spoon]

That's a duplicate of this bug.

Indeed
However with the RC1 build I still need to uncheck recheck the boxes for the ships to appear on the list, I can't get it to crash with this build though.
Still works fine with debug.

[Nuke]

i updated the rtt bug (#2400) with the most recent information i had about the issue.

[G0atmaster]

So how long for the .14 MVPs?
And will we release .16 when shadows are ready?

Also, when this does hit release, will the debug build be obviously labeled as such?

[chief1983]

So how long for the .14 MVPs?
And will we release .16 when shadows are ready?

Also, when this does hit release, will the debug build be obviously labeled as such?

Not relevant to this.
We already have more than enough stuff for the following release, so only if shadows are done in time, and if we want to add even more new features in.
Yes.

[Colonol Dekker]

Can has feature list link plox?

[Spoon]

ASSERTION: "num == bm_bitmaps[n].handle" at bmpman.cpp:2469
Int3(): From c:\code\fs2_open_3_6_14_rc1\code\globalincs\windebug.cpp at line 902

Is this one still not fixed? How long have we been encountering this one?

[karajorma]

That one does not have a single cause. Complaining that it's not been fixed is like complaining that sudden crashes while playing hasn't been fixed!

[Droid803]

What causes that!?