Search results

Well, what I did is fairly straight forward: I gave them stay-near-ship goal. The break & attack order is scripted, but you could as well make it dynamic. Either by allowing the player to order wingmen around or by using a couple of sexps including when-key-pressed. The second will allow...

I like the mission. However, if I may make a few suggestions: -the mission can become very difficult if your wingmen get killed, which happens very often, by the way. Better, guard a few wingmen with ship-guardian-treshhold SEXP. -disable built-in command messages To make your life a bit...

extract the Capture-Destroyer.fs2 file into WCS\data\missions folder (create missions folder if it doesn't exist). Then, in the tech room, select "mission simulator" (top left) and then "single missions" (bottom left). Capture destroyer mission will appear in the list.

it *should*

Vista is shipped with a very poor OpenGL support (*cough* DirectX10 *cough*). Latest drivers should offer proper OpenGL implementation though.

you aren't, by any chance, using Windows Vista?

probably. The Ticonderoga mission, for example, was first planned as coop mission for multiplayer. Probably the reason, why it is so damn hard :)

More like not exceeding certain velocity (overshooting jump node or being annihilated during the jump sequence)

just to clear up some misunderstanding with the news update on the front page: this is not a cgi clip, but ingame footage, where game engine sets several limitations :)

I've encoded the cutscene with xvid actually :) Theora codec is actually more efficient than xvid, but FS2 has several limitations including max resolution of 640*480.

Download I've recorded the sequence, the encoding quality isn't the best though

yeah, you can have both.

Hey, just drop me a line (tolwyn@gmxpro.net), and I'll help you. :)

It is still a question how we will release the game. Right now 20 out of 40 missions have been created, most of them have been outfitted with the new autopilot. You have to understand, that we have to script autopilot flyby scenes for each mission individually due to some cutscene code bugs...

For this week's update, the Wing Commander Saga team would like to showcase one of our in-game cutscenes. The following series of screenshots illustrates the "fleet jumping" cutscenes that are familiar to Wing Commander fans and that will play a transitional role in Saga's story, as well.

I have a similar configuration and I can run the game in OpenGL. In most cases outdated gpu drivers are the reason. Your best bet would be to download latest drivers from Intel's website.

Hey, please post your system specs. Also post your Saga's configuration. I can run the game on a fairly low end system with an onboard gpu, so I doubt it is a problem. Driver updates can do wonders some times as well.

We have two additional ships in the pipeline: namely the Sabre and the Rapier.

It won't work in the full release though, as I purged the weapons.tbl a few weeks ago.

bad choice for Saga - better mouse support is in the works, but it will take some months/years.