[ME$$ENGER]

I know some are really annoyed by the bug, but you should realize that:

1. These guys don't get paid for what they do. SCP is created by fans of the game just like you and me out of their enthusiasm.

2. With the addition of new features (such as OGL env mapping), it's bound to have new bugs. Sometimes it's not even a bug in the particular build but rather a specific hardware/driver combo. Whatever it is, I highly doubt that it could be intentional.

Now back to the topic. Another member (Wanderer) has experienced the same bug and he's using a *relatively* similar graphic card (Radeon 9600) as I am. Given the bad record of ATI's OGL driver and taylor's comment about this being a pretty old glitch, I would say it's probably related to the R300/350 line of graphic cards and the catalyst driver. Perhaps all those that are experiencing the problem should post their hardware spec and relevant driver versions so we could at least have a good sense about who are affected.

I might try some OGL driver switch in the future and see if there's a particular version that cures this problem.

[pecenipicek]

this build nor taylors nightly from 13th may work for me. no error message, nothing, they simply dont start.


openal is the most recent and everything is more or less up to date. i think. the voice recognition build works on the other hand.

[karajorma]

The voice recognition build is ancient. Try the 9th May build so we can establish whether or not it was the OpenAL/Envmapping changes that are the cause of your problems.

[pecenipicek]

link? i cant be bothered to look for it right now.


i think it has something to do with openal, as when running the debug build, the log stops at "Initializing OpenAl..."

[karajorma]

It's not hard to find. It's about 2-3 threads down from this one.

[pecenipicek]

it works. the 9th may build. anything after doesnt work.

env mapping is off.

altough, where is the defaut cube map for env mapping? it isnt in the file with taylors 13th may nightly build as expected and advertised...
i've also tried this build without anything activated and with only the mv_core.vp, it still doesnt work.

Code: [Select]

==========================================================================
DEBUG SPEW: No debug_filter.cfg found, so only general, error, and warning
categories can be shown and no debug_filter.cfg info will be saved.
==========================================================================
Passed cmdline options:
  -cache_bitmaps 
  -jpgtga 
  -mipmap 
  -glow 
  -spec 
  -dualscanlines 
  -orbradar 
  -rearm_timer 
  -targetinfo 
  -3dwarp 
  -ship_choice_3d 
  -mod mod\derelict, ,Media_VPs
  -fps 
Building file index...
Searching root 'E:\freespace2\mod\derelict\'
Searching root pack 'E:\freespace2\mod\derelict\DerelictSCP.vp'
Searching root pack 'E:\freespace2\mod\derelict\DerelictSCP1.vp'
Searching root pack 'E:\freespace2\mod\derelict\DerelictSCP2.vp'
Searching root pack 'E:\freespace2\mod\derelict\DerelictSCP3.vp'
Searching root pack 'E:\freespace2\mod\derelict\DerelictSCP4.vp'
Searching root 'E:\freespace2\ \'
Searching root 'E:\freespace2\Media_VPs\'
Searching root 'E:\freespace2\'
Searching root pack 'E:\freespace2\mv_adveffects.vp'
Searching root pack 'E:\freespace2\mv_amodelspatch.vp'
Searching root pack 'E:\freespace2\mv_amodelspatch2.vp'
Searching root pack 'E:\freespace2\mv_core.vp'
Searching root pack 'E:\freespace2\mv_effects.vp'
Searching root pack 'E:\freespace2\mv_models.vp'
Searching root pack 'E:\freespace2\mv_music.vp'
Searching root pack 'E:\freespace2\mv_textures.vp'
Searching root pack 'E:\freespace2\root_fs2.vp'
Searching root pack 'E:\freespace2\smarty_fs2.vp'
Searching root pack 'E:\freespace2\sparky_fs2.vp'
Searching root pack 'E:\freespace2\sparky_hi_fs2.vp'
Searching root pack 'E:\freespace2\stu_fs2.vp'
Searching root pack 'E:\freespace2\tango1_fs2.vp'
Searching root pack 'E:\freespace2\tango2_fs2.vp'
Searching root pack 'E:\freespace2\tango3_fs2.vp'
Searching root pack 'E:\freespace2\warble_fs2.vp'
Searching root 'h:\'
Found 27 roots and 12058 files.
Setting language to English
soundcard = EAX
Initializing OpenAL...


[Mongoose]

Just wanted to say that this is the first CVS build I've used since one all the way back from February, and it runs as smooth as silk.  I'm still trying to get over how cool that env mapping looks on cockpits.

[DaBrain]

it works. the 9th may build. anything after doesnt work.

env mapping is off.

altough, where is the defaut cube map for env mapping? it isnt in the file with taylors 13th may nightly build as expected and advertised...
i've also tried this build without anything activated and with only the mv_core.vp, it still doesnt work.

Looks like an OpenAL problem to me... Try updating your OpenAL version.

Edit: Does your soundcard/soundcard driver support OpenAL? Try updating your drivers. If crashes after initializing OpenAL, this might just be the problem.

[ShivanSpS]

Theres is some problem which this and Kara 4/25 and 4/29 builds, I didnt tested the 9th.

The problem is the loadout.... there is some key missed weapons in some missions in the campaing, for example, No Stilettos II in the enif station mission... and No Harppons in the Repulse mission.

I retry which the 3/23 build and that missiles are there....

[karajorma]

Try the 9th. Both the 25\04 and 29\04 builds included early versions of my team loadout changes and that could easily cause problems.

[pecenipicek]

it works. the 9th may build. anything after doesnt work.

env mapping is off.

altough, where is the defaut cube map for env mapping? it isnt in the file with taylors 13th may nightly build as expected and advertised...
i've also tried this build without anything activated and with only the mv_core.vp, it still doesnt work.

Looks like an OpenAL problem to me... Try updating your OpenAL version.

Edit: Does your soundcard/soundcard driver support OpenAL? Try updating your drivers. If crashes after initializing OpenAL, this might just be the problem.

i've tried updating all the drivers, still doesnt work even tho all the most recent drivers were installed.

the soundcard is ManLi CMI8738, and is actually doing the EAX processing. i've got an idea how to try to run it. i'll try changing the sound vendor to directsound instead of EAX.


[edit]nay, doesnt work...

[taylor]

the soundcard is ManLi CMI8738, and is actually doing the EAX processing. i've got an idea how to try to run it. i'll try changing the sound vendor to directsound instead of EAX.

[edit]nay, doesnt work...

'Cause it has no affect when OpenAL is used.  If the build is for OpenAL then it's OpenAL, period.  There is no way to make it do anything else.  Either don't use it with sound (with -nosound in the Launcher) or wait for the next build.  I've made some changes that should either give a better clue of what the problem is, or fix it entirely.

[pecenipicek]

yeah, its an openal problem, i've punted -nosound and it works properly, but, hey, why not use the build that works for me without a hitch?

[taylor]

yeah, its an openal problem, i've punted -nosound and it works properly

It's most likely an issue with your system setup and/or normal sound drivers.  OpenAL is just acting as a front end to your normal DirectSound drivers.  I know that OpenAL works with that particular card which means it shouldn't be a general conflict.  What driver version are you using for the C-Media card?

why not use the build that works for me without a hitch?

Because it might be the last build which works for you without a hitch.   We're moving everything to OpenAL so if we can't get it working for you then it's a good bet that the May 9th build will be the newest one you ever get to use.  There is a chance (since the in-developement sound code allows it) that a future build can be either OpenAL or DirectSound with just a selection from you, but as we move more code from Windows specific to cross-platform, that may be more work to maintain than it's worth.

[pecenipicek]

It's most likely an issue with your system setup and/or normal sound drivers.  OpenAL is just acting as a front end to your normal DirectSound drivers.  I know that OpenAL works with that particular card which means it shouldn't be a general conflict.  What driver version are you using for the C-Media card?

i got that driver version from windows update. if you got any newer ones, i'm willing to take... i'll do a search right now for a newer version of drivers...

Because it might be the last build which works for you without a hitch.   We're moving everything to OpenAL so if we can't get it working for you then it's a good bet that the May 9th build will be the newest one you ever get to use.  There is a chance (since the in-developement sound code allows it) that a future build can be either OpenAL or DirectSound with just a selection from you, but as we move more code from Windows specific to cross-platform, that may be more work to maintain than it's worth.

damn

[edit]i've tried the newest findable drivers on the net, the ones i had ended in .643, the newest are .644. still doesnt work.

probably something with the overall configuration. should i post the whole configuration?

[Rook]

An issue I brought up in ShivanSpS's 1.5c thread...

When running 5/17 r in D3D I get the following error

Error: bad DDS file compression.  Not using DXT1,3,5 cubemap.dds
File:D:\C++\Freespace\fs2_open\code\graphics\GrD3DBmpman.cpp
Line: 503
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------

The FreeSpace SCP logo is missing from the initial loading screen, the video plays with sound but no visuals, and when I get to the pilot select screen I see nothing but while with blue squares on clickable items. If I can manage to stumble blindly into getting the mission to play I can see my hud but none of the text. I don't get this issue in OpenGL but I was primarily using D3D for it's higher resolutions and FSAA.

[ShivanSpS]

D3D has been abandoned, yo can force FS in OpenGL but not AA :S not yet...

[taylor]

@Rook:
Both D3D issues have been fixed in CVS.  It should work again for you in the next available build.  FSAA does work in OpenGL, but you have to use you video card's driver override to do it.  I prefer 4x bilinear filtering on my NVIDIA card since it gives me pretty good visuals with no noticable performance hit.  Also, OGL supports any resolution that D3D does, it's just that the current Launcher doesn't list them for you.  You can modify the video entry in the registry by hand and set any resolution that you want.  Unfortunately there isn't an easier way to fix it right now.

But, any future build which is OGL only (built without D3D support) will accept the D3D video settings as the settings for OGL.  With those builds you could select D3D and any resolution it supports, and when you run the game it will use that resolution but initialize OGL instead.  All of my future builds will do this but it's up to each of the other developers as to whether they do that for their builds too.

[ShivanSpS]

The AA is working?! since when?

btw, i having some problems which env mapping... I can only play one time, afer of that (reaload or next mission), the background graphs are corrupted...

and at the second or tree reload even menu texts are corrupted.

[taylor]

The AA is working?! since when?

Something in the OpenGL setup was screwing with AA at one point but that was fixed a while back.  I've been using FSAA for months without issue.  I know that it works fine for DaBrain and others as well (given the number of OGL screenshots that have been posted with FSAA enabled).

btw, i having some problems which env mapping... I can only play one time, afer of that (reaload or next mission), the background graphs are corrupted...

Got screenshots of the problem?  The default envmap looks a lot better than the in-mission ones since they look mostly squashed (though it's better than before).  I totally suck at math so I haven't figured out how to properly generate the scene, I've just left what Bobboau originally did and simply fixed the bugs in it.  The default envmap is only used at the start of the game, or if your video card can't make an envmap itself.  After that the envmap gets replaced by the one the video card makes (ie, the envmap in the techroom will be whatever came out of the previous mission played).

I'm not sure if that's what you are seeing though, doesn't really sound like it from your description.  I've never had a problem with it messing up from mission to mission though.