[TL]

More info about this bug. I've opened "Proving grounds" (SM2-03.fs2) with FRED and there's a set of chained events. I think the problem is in Delta wing Departure. It is triggered by:

Code: [Select]

$Departure Cue: ( is-event-true-delay "Abort" 5 )
But they just stay still. As the event "Beta Departs" (although the wing name is Delta) depends on it, the mission fails.

I can confirm that RC7 works.

EDITED -------------------------------------------------------------------

Do not Mantis it. It seems the same issue as my recently posted bug Mantis 1133. I'm updating this info to that bug. Wait till Goober, Taylor or any other SCP guy says something about it.

Hey.

Thanks for pointing me to the bug report. You say in the report it works in RC7dot8 - so was it introduced in RC7dot9?

I'm just glad RC7 worked so I could get past the mission. I'll keep watching your bug report out of curiosity. I was wondering why Delta was staying still... Thanks.

[Riotta]

Hello, I wonder if there is a possibility to compile this sourcecode under Linux with support for first Freespace or it only support Freespace 2 or maybe the binaries are universal and only data matters?

Regards

[Goober5000]

FreeSpace 1 missions can be played in FreeSpace 2 using the FSPort.

If you're looking for a Linux build that plays FreeSpace 1, try here.

[asyikarea51]

Odd as it seems, I think the game actually goes faster on my side when I ran RC7.9 over RC7. I've never tried RC7.8 (I should have it somewhere on my HDD).

Not using adveffects though. I'm aware of the AI docking bug in 7.9, but I'm not going to go back to RC7 because 7.9 appears to fix the camera crash bug that's been plaguing me as of late (I think Kara knows what I'm talking about).

[taylor]

Just a quick FYI,  the rc7dot9 build will be updated shortly to be current 3_6_9 CVS and have most/all of the recent AI issues fixed.  The link will be the same (in which ever thread/post I actually posted it) so just re-download to get the fixes.

But wait at least a hour from when I made this post before attempting to download (I've got a quite a few series of builds to do and this updated set is last).

[Tolwyn]

I've been wondering if the new build will fix the turret animation code on cap ships as well? In RC7dot9 they do not rotate properly

[Turambar]

using snd_preload crashes btrl for some reason

no specific error, just the standard windows CTD
turning it off fixes the problem, bud would you like me to run a debug build and get some detailed info for ya?

[taylor]

using snd_preload crashes btrl for some reason

no specific error, just the standard windows CTD
turning it off fixes the problem, bud would you like me to run a debug build and get some detailed info for ya?

I had this once too, but it turned out to be a corrupted OGG file and a delete and redownload fixed it.  I never did bother to figure out the actual file(s) that caused the problem though.  Not sure if that is the problem here though, there could just be an OGG file which is valid but the game has trouble loading.

Running a debug build to see if it gives any additional info would be helpful, so don't let me stop you from doing that.

I've been wondering if the new build will fix the turret animation code on cap ships as well? In RC7dot9 they do not rotate properly

I've seen this mentioned before, but haven't really had a chance to look into what the actual problem is.  So, can you elaborate a little on how it's broken compared to older builds?  I did make changes, but they should have done nothing except for when you make use of a new subsystem flag.  If something is affecting turrets in general then it's a bug that I need to be able to test and fix (this weekend at the latest).

[Tolwyn]

I've been wondering if the new build will fix the turret animation code on cap ships as well? In RC7dot9 they do not rotate properly

I've seen this mentioned before, but haven't really had a chance to look into what the actual problem is.  So, can you elaborate a little on how it's broken compared to older builds?  I did make changes, but they should have done nothing except for when you make use of a new subsystem flag.  If something is affecting turrets in general then it's a bug that I need to be able to test and fix (this weekend at the latest).

I've been told that turrets aren't moving on all capships, I never looked into this issue properly, Starman did though. He can surely explain it better

[Tolwyn]

And another very ... weird issue:

on some GPUs there are issues rendering the asteroid field. Asteroids will pop up in a certain distance (Geforce 6800), cause severe slow downs (Geforce 6200), render only the lowest lod (Intel 845 shared memory/asteroid field worked before) and then vanish completely (i.e. they are not invisible, they are no longer in the mission's area)

[Starman01]

I noticed similar slowdowns, but not only in the asteroid field. Sometimes it happens when shinemaps will be visible, and sometimes even when I fire the weapons into empty space. Sometimes a reboot fix that though, reminds me of the old memory leak.

As for the turrets, I will first it again with the newest exe posted here in the first post. But they seem to have a problem with facing the enemy. Sometimes they rotate , but they seem to be able now to fire on their backside without rotating the arms to that vicinity.

[kmunoz]

- Mac OS X (Universal Binary)

Don't mean to sound like a prick here but could this info possibly be moved or copied to the Cross-Platform Development topic, as well as notices of all future non-Windows builds? I just now discovered that there have been 3 Mac OS X builds since the build I last downloaded, including this one... and AFAIK there was no notification in the other topic (where I expected to find it) and the server and directory where the builds are now being deposited has changed since may (again, without any notification that I could find). I'm not ungrateful for all the work, and I know you all have more important things to do than pretty up the website organization for us non-coder Mac types unused to the culture of CVS, but finding this stuff is sometimes needle-in-a-haystack-like.

[taylor]

I'm not ungrateful for all the work, and I know you all have more important things to do than pretty up the website organization for us non-coder Mac types unused to the culture of CVS, but finding this stuff is sometimes needle-in-a-haystack-like.

And that's why I moved everything to the same basic places as the Windows builds, so that everyone just has to look in the same place for new builds.  It's also a little bit easier for me to keep up with that way.  Complaint noted though, and I'll sticky a topic in cross-platform dev for keeping track of all future stable and unstable builds that are made.  I probably should have just done that in the first place.

I do typically announce every build on the IMG forums and Mac Forums as well.  The FreeSpace2 threads on those two forums seem to be rather popular and I've gotten a lot of great feedback from all of them.  The OS X builds came a long base because of their help.

Oh, and I started moving/keeping some builds to the warpcore server (where all of the Windows builds are kept) since I don't like taking up disk space on icculus.org for things that aren't icculus.org related.  I'll keep putting major releases on icculus.org, as well as warpcore, but with everything on warpcore I'll be more comfortable keeping older builds available rather than erasing them on a regular basis like I do on icculus.org.  I think that icculus might be happier that way too.

[ARSPR]

One bug I feel you already know. So I'm posting it instead of mantising.

If you set time compression to something higher than 8x, the game starts loosing accuracy. I mean, ships do not follow their exact waypaths, beams miss their supposed targets and so on.

[kmunoz]

I'm not ungrateful for all the work, and I know you all have more important things to do than pretty up the website organization for us non-coder Mac types unused to the culture of CVS, but finding this stuff is sometimes needle-in-a-haystack-like.

And that's why I moved everything to the same basic places as the Windows builds, so that everyone just has to look in the same place for new builds...

I do typically announce every build on the IMG forums and Mac Forums as well.  The FreeSpace2 threads on those two forums seem to be rather popular and I've gotten a lot of great feedback from all of them.  The OS X builds came a long base because of their help...

Ah, I didn't realize you were posting on the other forums - I've never been to them. But now I'll keep an eye on those discussions, too, since the Mac-specific info will be easier to locate. One of the interesting oddities of forum-based volunteer game development websites that I encounter frequently is an allergy to maintaining a page on which the versions and release dates (and links) for all current files (including CVS builds) are prominently organized and displayed. This isn't a complaint - just an observation. I notice the same thing over at the Europa Universalis II forums, Hearts of Iron II forums and the Babylon 5 Wars tabletop game forums, among others.

And then it's times like these I wish I had any talents useful to the project. But unless someone decides to make a Freespace 2 conversion for Greco-Roman religion and culture and needs a consultant, I'll have to continue to be a passive observer only.

[ARSPR]

And then it's times like these I wish I had any talents useful to the project. But unless someone decides to make a Freespace 2 conversion for Greco-Roman religion and culture and needs a consultant, I'll have to continue to be a passive observer only.

Hey, you can be the Bible for Terran ship class names. If you also know about Ancient Egypt, Vasudan team will love you. 

[ShivanSpS]

The RC7dot9 breaks some retail missions, like in the Pegasus test, when the Shivans attacks Delta will NEVER change their order of "Attack Oberon", so their NEVER dock to the Aquitane, and nothing happends.

And when a fighter is launched from a hangar their will NEVER get out unless you give then an order... their just sit there inside the hangar xD!...

And i need a fix to the red alert bug, try this...

End of Mission 1:

-Cruiser 1 on fly, on escort list, 90% hull
-Frieghter A 70% docks to Player 80% hull ->send red alert

Mission 2: Seted in fred to Cruiser 1, Freighter A, and player to 100% hull, player docked to freighter A.

-Cruiser 1 on fly... BUT ONLY THE NAME APEAR ON THE ESCORT LIST! and its at 100%, the ship is not ingame... the name is on escort list, but you cant target it, and you cant see it either.
-Freighter A... same as Cruiser 1.
-Player: Apears on fly and 80% hull.

[CP5670]

And when a fighter is launched from a hangar their will NEVER get out unless you give then an order... their just sit there inside the hangar xD!...

Download 7dot9 again. The original one had that problem but Taylor replaced it with a newer one that fixes it.

[ARSPR]

And when a fighter is launched from a hangar their will NEVER get out unless you give then an order... their just sit there inside the hangar xD!...

Download 7dot9 again. The original one had that problem but Taylor replaced it with a newer one that fixes it.

You actually need 7dot9u (or 7dot9x, a fully new build). The 7dot9 (second version) still has the bug for ships departing to hangars.

[PSI-KILLER]

I am getting an error were it is saying I need OpenAL drivers better then 1.1.  I did download the latest from the .org web site.  But it still is not working. I am now using fs2_open_3_6_9 RC7.    If i missed this problem allready being addressed just point me in the right direction.