[The E]

Yeah, that sounds all kinds of wrong

[Kolgena]

Well, it's only happened rarely, so I have no idea how to reproduce >.>

Seems to happen most often (which is not very often) on Terslashes on deimos in King's gambit.

Edit: K, got it to happen in one.



This was right after it made two consecutive salvos against the Typhon. Though I'm wondering if it's a possibility that it's shooting at that piece of Orion? (Why would it do that?)

[Yarn]

(I also have a checkbox with 44100 beside it. Not sure what that's for. I remember that EAX used to be this checkbox, but I don't know why it's instead listing the last set sample rate)

It's a bug; that check box is still used for enabling EFX. I posted this on Mantis (#2596) a few months ago.

As for which one is the one that is implemented by OpenAL Soft and which on is the original "Generic Software" one I have not had time to experiment.  I would assume that the one that you want is now called "Generic Software" and the original "Generic Software" from before is the new device.

I almost certain what used to be "Generic Software" is still "Generic Software." At least that's how it is for me.

[perihelion]

I am almost sure I'm doing something stupid, but I can't think what for the life of me.

I have tried all three Windows builds (I have a Phenom II processor, so I should have SSE2 and then some) and I have just upgraded to launcher 5.5g.  Previously had 5.5f.  Every time I try to select one of the 3.6.14 RC6 .exes in the launcher, the launcher crashes.  I just tried it with an RC5 build and the same thing happened.  Debug builds make no difference.  I have no trouble at all selecting the official 3.6.12r SSE build or a 3.6.10 build of uncertain pedigree that I still had floating around.

I checked the MD5 hashes on my downloads, and they all look fine.  The error spew I'm getting from Windows makes no sense to me as I am not any kind of programmer.
Nevermind.  I'm a dumbass.  I checked the release thread for RC5 and found that someone had a similar problem because of an openAL .dll hanging about in their FS2 directory.  I found one in mine as well.  Deleted it.  Problem solved.  Launcher no longer crashing.

[Jeff Vader]

[jg18]

(I also have a checkbox with 44100 beside it. Not sure what that's for. I remember that EAX used to be this checkbox, but I don't know why it's instead listing the last set sample rate)

It's a bug; that check box is still used for enabling EFX. I posted this on Mantis (#2596) a few months ago.

I took a look at the 5.5g code, found the problem, and posted on the ticket with a patch.

[Master_of_the_blade]

Im surprised no one posted this. Ive been facing this since RC4. I use the wxLauncher. When I launch a mod, the screen alternates very quickly between the start screen with the tip and the screen without. The sound also gets stuck at the same point. It basically looks and sounds like your heavily overclocked card just destabalized.
It only lasts for 1-2 seconds, though and doesn't break the game. Also, this happens only when I first launch the game and not when I return to the start screen later.

[FreeSpaceFreak]

Im surprised no one posted this. Ive been facing this since RC4. I use the wxLauncher. When I launch a mod, the screen alternates very quickly between the start screen with the tip and the screen without. The sound also gets stuck at the same point. It basically looks and sounds like your heavily overclocked card just destabalized.
It only lasts for 1-2 seconds, though and doesn't break the game. Also, this happens only when I first launch the game and not when I return to the start screen later.

Debug log please. And what exactly do you mean by 'tip'?

[niffiwan]

I thought Master_of_the_blade meant the window that displays a "tip" about playing the game, and the options for "next", and "never display this again".

[Master_of_the_blade]

I thought Master_of_the_blade meant the window that displays a "tip" about playing the game, and the options for "next", and "never display this again".

Exactly

Edit: I launched it again after a driver update and the problem is gone. Looks like it was a driver problem.

[Black_Yoshi1230]

This may be related to those beam disasters I see so much during War in Heaven... but... is it completely natural for two Deimos corvettes to start spewing out their green forward beams like crazy?

I was on RC6, and in stock FS2, defending the Lysander and Actium, they just spewed out their beams and they downed the first Raksasha in less than twenty seconds. On 3.6.12 and the retail version of stock FS2, it takes about a minute for it to die.

Also, the second Suicide Kings mission when you have to defend the convoy, I think something screwed up the flight itinerary of the vessel that deployed Theta Wing, as it got in the way of the Jooyun when it was next to the Capella Jump Node (the waypoint timer was stuck on the 29 second mark for a while because the ship was in its way).

Plus the second time the GVD Psamtik was deployed on the field, it completely refused to fire its beams for two minutes while an NTF Cruiser kept throwing beams around like mad.

Something's gone nuts. Oh, and Print Screen is the snapshot key, right?

[X3N0-Life-Form]

Crazy beam spewing definitively sounds like an anomaly.
I'm not sure what to make of the convoy thingy, but the Psamtik actually never fired its beams on the last Hammerhead mission, as the aren't beam-free'd after the Psamtik arrives.

[MatthTheGeek]

Oh, and Print Screen is the snapshot key, right?

Yup. Gets you a tga screenshot in your Freespace2/Screenshots folder.

[Kolgena]

This may be related to those beam disasters I see so much during War in Heaven... but... is it completely natural for two Deimos corvettes to start spewing out their green forward beams like crazy?

I was on RC6, and in stock FS2, defending the Lysander and Actium, they just spewed out their beams and they downed the first Raksasha in less than twenty seconds. On 3.6.12 and the retail version of stock FS2, it takes about a minute for it to die.

Also, the second Suicide Kings mission when you have to defend the convoy, I think something screwed up the flight itinerary of the vessel that deployed Theta Wing, as it got in the way of the Jooyun when it was next to the Capella Jump Node (the waypoint timer was stuck on the 29 second mark for a while because the ship was in its way).

Plus the second time the GVD Psamtik was deployed on the field, it completely refused to fire its beams for two minutes while an NTF Cruiser kept throwing beams around like mad.

Something's gone nuts. Oh, and Print Screen is the snapshot key, right?

2nd FS2 mission does not beamfree the Psamtik. It is supposed to kill the NTF cruisers with flak, AAA, and fusion mortars. At least, this is the behavior I noticed playing the mission many times over the last 1-2 years.

I'm not sure about the Terslash behavior. Terslashes do have a very fast re-fire rate on insane IIRC. Regarding the Rakshasa: depending on how many wingmen engage the Rakshasa, it can go down fairly quick. A bunch of fighters chain firing hornets can really up the DPS against that cruiser.

[Black_Yoshi1230]

I'm not sure about the Terslash behavior. Terslashes do have a very fast re-fire rate on insane IIRC. Regarding the Rakshasa: depending on how many wingmen engage the Rakshasa, it can go down fairly quick. A bunch of fighters chain firing hornets can really up the DPS against that cruiser.

Yeah, the funny thing is I played through the mission on Hard and just said "defend these guys." I never saw any pummeling from Hornets.

Another thing I want to address:

I get "death ghost duplication" from capital ships. Either my laptop is a POS graphics-wise and can't deal with crap or something else is up (I only noticed this with stock FS2 so far, I'd have to get other pictures from other mods).

Since I can't say it in plain terms, here are links are for The NTD Uhuru from The King's Gambit, and The Sathanas from High Noon. Both are in 1280x720.

Didn't happen in .12, and I hate to be so nutsy and compare .14 RC6 against .12, but it's the most stable-ish to test against.

[Iss Mneur]

Can some windows users please test this new build?  It is RC6 with OpenALSoft built into it.  I am also looking for feedback from those of you have do have good sound cards to make sure that this build doesn't break anything for you.  Please post a log if you have a problem.

EDIT: Add request for logs.

[Yarn]

Can some windows users please test this new build?  It is RC6 with OpenALSoft built into it.  I am also looking for feedback from those of you have do have good sound cards to make sure that this build doesn't break anything for you.

That build appears to disable hardware OpenAL acceleration, at least for my SB X-Fi Titanium.

[headdie]

On SB Audigy I get massive sound corruption, I'm trying to get a vid but the vid recorder is causing problems

[Iss Mneur]

Can you both post logs from a run where you notice the issue (a debug build is included)?

Headdie, can you describe the corruption in more detail?  Sounds missing? Doubles? Snapping? Popping?  What hardware (CPU namly) are you using?

EDIT: Specific questions for headdie

[headdie]

I have included the log for this build and for standard RC6.  I have managed to get a vid of the issue which I am uploading now and will post a link when I can.

edit:

my system is a first gen AMD 64 3200+ Newcastle core

edit: again:

here is a vid demonstrating the issue http://www.youtube.com/watch?v=JuEb1c_uRNo&feature=youtu.be

[attachment deleted by a ninja]