[chief1983]

Yeah it is expected that as more people start looking at the builds, as is the case with the RCs, more things will get noticed.  Unless they're deal breakers though they'll just get slated for a future release.  Some of these even sound like retail behavior, so there's not much to worry about there.  Hopefully the legitimate concerns do get mantised though.

[Mongoose]

The "wingmen don't defend themselves" issue is definitely something straight out of retail (and retail FS1, for that matter); it's yet another quirk of the game's artificial not-so-intelligence.  As such, it isn't something that can really be "fixed," as it's how the game is supposed to behave.  One can often work around it with wingmate management; alternating orders between protecting a target and engaging the enemy is a decent strategy.  I would be interested in knowing whether or not this was something that tweaking AI profiles could alter, as it might be nice to play a campaign where your wingmen manage to cover their own asses while they're trying to cover someone else's.

[karajorma]

Allows you to assign a callsign to a ship which then appears on the HUD and in messages instead of/as well as the wing name. So instead of getting messages from Alpha 2 you get them from Iceman or Ghost or whatever.

heeey thats new

The original version has been in the code since the end of 2007. So no. It's not.

[134th Barracudas]

I'm testing the build this afternoon. Should I reply here for issues/problems/comments?

[karajorma]

Yeah. Although if you find a specific bug you might want to enter that in Mantis too.

[SypheDMar]

Not sure if it's related to this, but in FreeSpace Port Playing Judas, both the Lucifer and the Eva lack collision.

[134th Barracudas]

Yeah. Although if you find a specific bug you might want to enter that in Mantis too.

Ok, I'll do it. Thanks for helping

[BlackDove]

Here's my RC2 question refined from RC1 thread.

When is multiplayer going to act like PXO did? And is it at all?

What I mean by that;

Official updated missions.

Official allowed updated mods (Media VP's)

Official site where you register.

You get into the game, you type your username/pass in the multi options, then having assorted the files and updated them to the latest ones, you click on the hangar door, you get validated with the room server and dropped into #lobby from where you can go into games, host, etc. where other validation and checking processes (hacked tables data/saving stats) goes on until you finish the game.

Is that ever going to happen?

[karajorma]

That's been possible for ages. The only issue was that the mediaVPs weren't validated since the 3.6.8 ones were meant to be beta. I presume that they will be soon if they haven't been already for the 3.6.10 versions.

[chief1983]

Yeah we're probably just waiting on the patch to clear up the 3.6.10 issues, which they're waiting on us for I believe.  So the answer is, not long after final.  fs2netd.game-warden.com is already the official site to register and has been.

[Zacam]

The final release of 3.6.10 will see validation for the final version of 3.6.10 MediaVP's.

[Pizzi1]

hi, i am new on this forum ...yesterday i have tested this release candidate and i have seen slowdowns in same mission like "the great hunt(a nebula mission in freespace 2)" with the newest "media vp 3.6.10". There is a severe drop of fps  to 20 - 30 too
In the past i have used 3.6.9 official release and there are not slowdowns and the performance was ok.
Someone can explain me why there are so few fps?
I have a athlon 7750, geforce 8600 with 256m on board and 4G Ram.

[Rhymes]

Try removing the adveffects from the mediavp folders.  If that doesn't work, deselect the mediaVPs altogether.

[squidsquasher]

Hey! This may not be the proper place to post this because it is not really specific to this build, but not sure where else - it was something i had hoped this build would fix:

just tried 3.6.10 RC2 and seems like normal maps and GLSL now work on the mac! Bravo! Only problem is: This release still has a weird problem that has been cropping up more and more. Before it was only in 3rd party campaigns, but this is the first time it cropped up in the fs2 campaign (i.e. in Lion at the Door - when the wave of shivan fighters comes in after you have destroyed the freighters and the carthage is on its way). Here's what happens:

When a certain new ship comes into play (its random - sometimes its one ship, sometimes another, sometimes never happens), fps will slow from like 30 to 4 or 5, sometimes even 2 or 0 (no frame updates ever - in this case it does not even show the pause menu when i hit esc and i have to remember how many arrow key presses up or down, then hit return to get out of the mission).

When this new ship comes in, the fps slows when you are looking at the ship, and goes back to normal when you are not. I didn't get to see it with this build because when it happened the ship in question was too far away, but usually the texture of the offending ship is pure white. Then most head animations and hud images of ships go solid green (hud color) as if freespace suddenly cant find a bunch of textures. Its like FS is just no longer loading new textures and freaking out about it. It becomes nearly impossible to finish the mission.

I've tried all sorts of launch command line options, to no avail. Some missions it ALWAYS happens at one point or another no matter how many times i restart. I've tried switching pilots, clearing caches, etc. Right now I am downloading new mediavps and trying that.

I am running OS X 10.5.6 on a Jan 2008 Macbook Pro 2.4GHz with 256MB VRAM. Mediavps 3.6.10

Any ideas?

Thanks!

[Rhymes]

Sounds, again, like your computer can't handle the mediaVPs.  Therefore, I tell you this:

Try removing the adveffects from the mediavp folders.  If that doesn't work, deselect the mediaVPs altogether.

[Darklord42]

My MBP is a September 2008 one but I think it is mostly the same hardware.  Does yours have the Nvidia 8600 M 512mb card?  If so,  I can tell you that the game works perfectly fine on my laptop with all Mediavps, and even driver level enhancements like Antialasing set to 16Q and other things.  Never have I seen any slow downs.  Though admittedly I'm using the windows version. But I believe it is the same sourcecode.

[Echelon9]

just tried 3.6.10 RC2 and seems like normal maps and GLSL now work on the mac! Bravo! Only problem is...
...
I am running OS X 10.5.6 on a Jan 2008 Macbook Pro 2.4GHz with 256MB VRAM. Mediavps 3.6.10

Unfortunately, this is a known issue with the OpenGL GLSL (shaders) code on OS X. We got GLSL up and working (no more completely white textures), but there are performance issues, as you've noticed.

Simply put, the shaders are like small programs in and of themselves, which are run on the graphics card or should some failing occur, fallback to run on the CPU. Now the graphics card is optimised to run the shaders, and for some currently unknown reason the vertex shaders are falling back to run on the CPU instead when first loaded, killing FPS.

This occurs on hardware we know show be more than capable of running the GLSL shaders, as it works fine on the same Mac when a Windows partition is booted.

It only occurs for a couple of seconds when the model is first rendered on screen, and then the performance returns to expected. I'm still struggling to work out just why it happens, but to be honest, I don't think it will be fixed before 3.6.10. The bug can be tracked in Mantis 1881. I'd suggest running with the -no_glsl command line option until it is resolved on Mac.

[squidsquasher]

understood - however the main problem - that FS loses textures and the whole thing slows to nearly 0 fps, happens even with GLSL turned off, at least in previous builds. I have not tried this one with GLSL turned off yet.

I was using mvcomplete.vp as my mediavps, so i downloaded the separate files version of mediavps 3.6.10 and took out advanced effects. I played "A Lion at the Door" again and the missing textures did not happen - but that does not prove anything. I have yet to try one of the campaigns where it happened all the time since changing this.

[chief1983]

Yeah, for now, whichever works better - either removing the adv_effects or running with -no_glsl (which is a checkbox under Troubleshooting called "Disable GLSL" or something).  We do hope to get this fixed in the near future though, as a major goal was to at least not revert the graphics quality on any platform, even if we couldn't get the shaders working perfectly for all of them.  We got close I think.

[Oddgrim]

awesome , normal maps for me works now , didn't use too before