[General Battuta]

No, this is correct behavior.  The previous behavior was a bug.

The simulated speech messages wait their turn before playing because that's what voice-acted messages do.  If you have too many messages strung together in too short a time, then you should space them out, just as you should with voice-acted messages.

I just find that this behavior makes is MORE difficult to synch up my messages.  For a polished product, it wouldn't make any difference, but the creation process benefits from knowing exactly when the next message is supposed to fire.  You can make a better estimate when you know at what point the previous message gets cut off.

Why not use TopAce's approach? You should be doing this anyway as it's important if the campaign is VA'd.

[cyrus41592]

Hope all is well for the RC. Hit a bit of a snag. Over the last couple of RC builds i haven't been able to get Blue Planet running. I can typically get into a mission, but it will stop and go unresponsive in the middle of the mission. I have used the RC debug builds and it will run just fine, but quite slower than the SSE2 builds. I'm attaching the fs2 log. Its based on RC4 debug because the RC5 debug won't run. Hope some one can help, thanks for all the hard work you guys have been putting in on FSO.

[attachment deleted by a ninja]

[FreeSpaceFreak]

Code: [Select]

ERROR: Unknown Language Checksum: -1162327434

Interesting... What language is your original FS installation?

"Stop and go unresponsive" - do you mean it just freezes and does nothing anymore, or does the game continue to run but not taking inputs anymore? I'm asking because from the log you posted, it appears the mission ran correctly (with you getting shot to pieces in the end). Keep in mind that the log you post should contain the problem you're experiencing.

If RC5 debug won't run, a log from it would still be interesting; it should be generated whenever you try to run it, and we can usually figure out why it won't work. The fifth line should read "FreeSpace 2 Open version: 3.6.13.8528", that's the RC5 revision number.

[cyrus41592]

I ran the install in english. As far as the game going unresponsive, it freezes in the middle of the mission and then the program crashes. The oddity is that this only occurs when not running a debug version. When running a debug version it runs fine, albeit slowly. I am attaching a new log after having run it with RC5 debug. When I run RC5 Debug it will briefly show the splash screen and then it will go back to the desktop and goes into the debugger. After breaking into the debugger, the program stops working. hopefully the log shows this. Thanks for the help in advance guys.

[attachment deleted by a ninja]

[Jeff Vader]

When I run RC5 Debug it will briefly show the splash screen and then it will go back to the desktop and goes into the debugger. After breaking into the debugger, the program stops working.

Just a side note. The debugger is a programming thing. That is, if you have your development environments 'n **** set up properly, you can break into the debugger when an error occurs and do some srs 1337 h4x0r magic to try and find the cause of the crash. If you're just a normal player playing FSO, you most likely do not have the necessary tools so you can't even use the debugger and therefore you shouldn't bother trying to break into it.

[headdie]

BP has been causing issues with the current RC cycle, I thought most of it had been sorted for 5, or is it 6/final where it is going to be resolved?

edit

unless you are modding i strongly suggest using the non debug build

[FreeSpaceFreak]

Here, toss this hotfix TBM into blueplanet2/data/tables and it should work alright under RC5.

[attachment deleted by ninja]

[Renegade]

Hello Guys,
i have a little problem with all builds after 3.6.12 Final.
I am playing FSO with 1920*1080 Resolution. The Game running smooth but... when the chatter Video playing (top left) then the gameplay will be jerky. OK i want look what says the FPS and activates show fps in HUD. With Fps showing i have no jerky gameplay.

Then i tyred 3.6.12 Final - No issue !!! With or without Comm video played smooth gameplay.
I hope this will be fixed in 3.6.14 Final.

A i forgot this issue is only when Vsync is active (60Hz)

My Computer:
Intel Core i7 2600, 8 gig Ram, Nvidia GTX 570 (1280 MB) <--fast enough for FSO i think

[Thaeris]

Keep in mind FSO only runs on a single core.

[Iss Mneur]

i have a little problem with all builds after 3.6.12 Final.
I am playing FSO with 1920*1080 Resolution. The Game running smooth but... when the chatter Video playing (top left) then the gameplay will be jerky. OK i want look what says the FPS and activates show fps in HUD. With Fps showing i have no jerky gameplay.

Then i tyred 3.6.12 Final - No issue !!! With or without Comm video played smooth gameplay.
I hope this will be fixed in 3.6.14 Final.

A i forgot this issue is only when Vsync is active (60Hz)

My Computer:
Intel Core i7 2600, 8 gig Ram, Nvidia GTX 570 (1280 MB) <--fast enough for FSO i think

This sounds like it may be or be related to Bug#2417.

[Vip]

Hey there, just downloaded the 3.6.14 RC5 files, both SSE2 and NO-SSE versions. However, the launcher (5.5g, just downloaded as well) crashes every time I try to point it to the 3.6.14 exe. Tried it with both versions as well as with debugs, still the same. Tried manually updating the launcher6.ini, still crashes. However, it works like a wonder with 3.6.12 exes. It's the first time something like this happened, so I'm kinda clueless as to what to do.

Windows XP SP2, Core2Duo E6750 2,66GHz, 2GB RAM, GeForce 9800 GT.

[Alan Bolte]

Vip: Yeah, that's something people keep running into, but there should be an easy fix: make sure you have the very latest OpenAL installed, and make sure you don't have an old openal dll sitting in your fs2 directories somewhere.

[Vip]

Vip: Yeah, that's something people keep running into, but there should be an easy fix: make sure you have the very latest OpenAL installed, and make sure you don't have an old openal dll sitting in your fs2 directories somewhere.

Ghh, right. I knew I forgot something. Everything's OK now. That should teach me not to update FS when I'm sleepy Thanks!

[Echelon9]

RC5 on Mac 10.7 cannot go fullscreen, due to a deprecated function that SDL calls.

Latest trunk has a dedicated Xcode4 / 10.7 project file, which also includes the latest SDL v1.2.15. It can go fullscreen properly on 10.7

[Cyborg17]

I'm going to report a problem with breifing sounds and music, but I have to do more testing to figure out if it's corrupted files or not.

Also, if I wanted to get the latest exe where would I be able to find it? Would I have to compile it myself?

[Iss Mneur]

I'm going to report a problem with breifing sounds and music, but I have to do more testing to figure out if it's corrupted files or not.

Also, if I wanted to get the latest exe where would I be able to find it? Would I have to compile it myself?

The latest version of the RC is in the first post of this thread.  If you are talking about trunk then, yes, you need to build it yourself or ask someone else to build one for you.  The trunk nightlies will resume when 3.6.14 final is released.

[The Dagger]

I'd like to report some strange behaviour related to RC5.

Since nightlies 3.13 I've been able to have normal maps in my deplorable Mobile Intel 4 Series Express Chipset Family. Before that, they just didn't work. It kept working all the way to RC4. But since RC5 I'm back to square one, normals have no effect whatsoever.

It's not a big deal since I know my GPU is worthless. I've seen no other comments about this, so I'm pretty sure it's GPU specific and if that's the case, don't worry about it, I'll get a new computer soon. Nevertheless I thought that it may be of interest for you coders.

I've attached RC2 and RC5 debug logs. I used the exact same launcher configurations to create them.
I've tested r8095, RC2, RC4 and RC5. Normals work for all of them except RC5.

But in the end it's not a big deal... really...

[attachment deleted by a ninja]

[The E]

This is due to better capability checking in RC5. For all intents and purposes, your card should never have tried to run the shaders, as it only reports a max OGL support of 2.0, which is below the minimum we have set for shader support (which is OpenGL 2.1).

[chief1983]

Strange they worked at all then when the checking was broken.

[Cyborg17]

If you are talking about trunk then, yes, you need to build it yourself or ask someone else to build one for you.

Ok.  So would the process would go something like this:

download/buy a compatible compiler, get the SVN (which I already have set up), get the compiler to compile the code files together and then put the resulting files in the right place?