[Trivial Psychic]

I still can't hear ogg sounds with this new build so I'm guessing either A), Taylor hasn't commited his ogg fix, or B), this build isn't based off latest CVS.

I haven't had time to give this build a real workout though.

[phreak]

A is the correct answer.

[taylor]

Originally posted by Trivial Psychic
I still can't hear ogg sounds with this new build so I'm guessing either A), Taylor hasn't commited his ogg fix, or B), this build isn't based off latest CVS.

The fixes should be in the updated build I think.  I added the last of the two fixes in early yesterday.  If it's still not working then get me something to test with (don't really need the sound files, just the tbl) and I'll have another go at it.

Another point is that I don't think this build is made with OpenAL support like WMCoolmon's build was.  My fixes were for OpenAL only so if it's not working here too then it's not something that is API specific.  There are only a couple of general places that can cause it to mess up though so that may be a good thing.

[Trivial Psychic]

From the TBP 3.2 Beta thread.  THIS zip contains many table files for it, including the music and sounds tables, which have the ogg references.

[taylor]

Nevermind, found the problem, I think.  I found a problem anyway and just had some Mudvayne playing rather than main_amb.  It was general (a file handle issue) so hopefully all is better now.  More mixup from when both WMCoolmon and I tried to fix ogg our own way.  We've learned out lesson now though, just missed this in the cleanup that followed.

[Psychonaut]

Clicking on the Techroom CTD, Clicking on Continue CTD, Clicking on Exit CTD, but i think it has to be this way ;-)

Sorry, but for me this build don´t work anyway

[Flaser]

Originally posted by Psychonaut
Clicking on the Techroom CTD, Clicking on Continue CTD, Clicking on Exit CTD, but i think it has to be this way ;-)

Sorry, but for me this build don´t work anyway

The same old mantra goes here:

Was it a release or a debug build?
What's your hardware and software configuration (CPU, Ram, VRam, GPU, OS)?
What vp-s were installed and where?
What campaign was loaded?
What mods did you use? (Anything beside main FS2 is a mod)

[SuperCoolAl]

Phreak, this build has the same stutter prob for me as the new inferno build you posted, whenever a fighter blows up, it stutters for about half a sec when its about to break into debris.

I've just checked with other builds that still work after the catalyst update and they work fine.

[redmenace]

Originally posted by Psychonaut
Clicking on the Techroom CTD, Clicking on Continue CTD, Clicking on Exit CTD, but i think it has to be this way ;-)

Sorry, but for me this build don´t work anyway

Try a new pilot?

[Psychonaut]

I´ve tried a new pilot.

And also i`ve posted my system specs that often that i didn´t remind to post them again

I´m sure this is not a hardware related thing, ´cause all other builds do work more or less properly.
I used the release-build and i´ve tried it with a lot of mods and campaigns always with the same results.

The flags i use are:
-spec -glow -jpgtga -nomotiondebris -2d_poof -pcx2dds -d3d_no_vsync -nobeampierce -dualscanlines -ship_choice_3d -targetinfo -orbradar -3dwarp -ballistic_gauge -smart_shields -snd_preload -env -fps -spec_point 6.9 -spec_exp 11 -spec_static 1.0 -spec_tube 4.4 -ambient_factor 75

I use them with every build.

The vps are more or less recent. I put some of "my" effects into the data-folder but again most of the time i havn´t had any problems.

Maybe it just doesn´t work for me?!

[phreak]

Originally posted by SuperCoolAl
Phreak, this build has the same stutter prob for me as the new inferno build you posted, whenever a fighter blows up, it stutters for about half a sec when its about to break into debris.

I've just checked with other builds that still work after the catalyst update and they work fine.

i think the studdering occurs when the ship textures are unloaded if the last one in the mission is killed.  Since this occurs during the mission, it may slow stuff down.

edit: between having all bitmaps unloaded at level close, as well as turning all debug info off, it seems to have sped it up a bit.

[Jonathan_S47]

I am having some problems with the capital ship lasers with this build. They fire but very randomly and often no where near their targets.

[phreak]

i think i fixed that after i posted the build.

[phreak]

Originally posted by Ransom Arceihn
Minor problem which seems to have been introduced with this, custom loading screens appear to be kinda broken. It seems that it only displays the loading screen for the prior mission to the one you're actually loading now, which means the first mission you load will never have a custom loading screen.

loading screens have been fixed.