[WMCoolmon]

Originally posted by WMCoolmon at the top of this page
http://www.evilnet.net/~mechwar3d/fs2_open.zip

Also located at http://fs2source.warpcore.org/mediaVPs/fs2_open35.zip

[Inquisitor]

That's just the vp files, exe coming soon, very soon

[Bobboau]

I just commited one last bug fix, fighter beams now record kills properly

[aldo_14]

Originally posted by WMCoolmon

Also located at http://fs2source.warpcore.org/mediaVPs/fs2_open35.zip

Does this have glow-pointed models, perchance?  

Also, what size is it? - I'm going to link to it on the Casualties website (now using some optional SC stuff)

[Inquisitor]

Build is tagged as fs2open_3_5

Compiling now.

Code freeze is off, go nuts again guys.

[Anaz]

w00000000t!!!

more SCP goodies!!

[Goober5000]

Not quite yet, it seems.  We still have to figure out what's causing the initial status bug - if you change your ship selection, you start out the game with the original ship's stats.  Thus, going from a Perseus default to a Herc II means you start out the mission with 74% hull and around 50% shields.

Soon as that's fixed, then we'll release it.

[Rampage]

Can you put a list here of all the bugs fixed and new additions of FS2 3.5?

I would like to verify it against my list.

[Solatar]

Originally posted by Rampage
Can you put a list here of all the bugs fixed and new additions of FS2 3.5?

I would like to verify it against my list.

Same here

[Inquisitor]

No, I'll put it in the readme that we are writing...



The 3.4 list actually has been kept up to date, so it's pretty accurate, I am also gonna package up a prelim launcher and the VP files that WM pulled together for us.

But, you guys have to be patient, and if you MUST now beofre that is ready, I suggest keeping up to date on the various threads here

And what list is that, Rampage?

[Bobboau]

I think the best candidate for the bug is in change_ship_type(), it is called by the mission select ui code to change the ship type, Goober modifyed this code so it could be used in mission, specificly:

Code: [Select]

// set the correct hull strength
if (Fred_running) {
objp->hull_strength = 100.0f;
} else {
// commented by Goober5000: we want to maintain hull strength
//objp->hull_strength = sip->initial_hull_strength;
}

// set the correct shields strength
if (Fred_running) {
objp->shields[0] = 100.0f;
} else {
// Goober5000 - again, we want to maintain shield strength
//set_shield_strength(objp, sip->shields);
}

I think the best thing to do would be to give this function a flag of some sort for reseting these values with a defalt value that leaves it the way it was

as for other bugs I have fixed a number of them in the fighter beam code, I added bank specific compatabilities, and a field of fire tag, and shield pierceing flag.

are we going to get a fred3.5 as well?
and what are all the things that fred now needs to take care of?(ex; nameplates)
and when is fred going to get merged back into FSO?

[Inquisitor]

There haven't been any committs to FRED recently, I was gonna flag and compile it anyway, but not of activity. This release has been a lot of bug fxing and core in-game stuff, not sure what is therer that is FRED related, I will review the logs.

As for when (or if) we merge back into the project from it's seperate module, lets discuss that after I get this thing packaged up.

[Goober5000]

Aha!  Bobboau, I think you have it!  Thanks.  It'll save me all that hunting. What I'll have to do is add a flag to the function call that only skips that code if change_ship_type() is called by the SEXP (which is the reason I commented it out in the first place).

As far as FRED, I think everything is in except for the nameplates.  I haven't figured out exactly how to add nameplate support in FRED because the texture replacement list could be any number of lines long.

[Goober5000]

Okay, I think I fixed it.  Can someone update their CVS and test it, please?  I currently don't have FS2 installed.

EDIT: And Inquisitor, check your PM.