[Cobra]

was getting these weird-ass bugs when i took out mv_effects to preserve FPS:

[Trivial Psychic]

You appear to be getting ship maps as effects.

[WMCoolmon]

Try taking out mv_textures. It's the only other mediaVP that might have a table file that would do something like that.

I would guess it's a memory problem, though. (ie lack of memory)

[Cobra]

when i played FSO right after i started up my computer for the day?

[CP5670]

If it runs out of memory, is it supposed to just show random graphics?

[Cobra]

oh, and i almost forgot, i can't view any ships in the techroom besides the ulysses. i try to view, say, the hecate and i get a memory reference error or a cannot initialize graphics error. debug builds don't seem to give me an error message, either.

and the SCP Media VP's i put in a separate mod folder (that's selected) don't work.

this problem appeared in the 20051129 and 20051209 build. i'll try to play a mission.

[Cobra]

oh, and i almost forgot, i can't view any ships in the techroom besides the ulysses. i try to view, say, the hecate and i get a memory reference error or a cannot initialize graphics error. debug builds don't seem to give me an error message, either.

and the SCP Media VP's i put in a separate mod folder (that's selected) don't work.

this problem appeared in the 20051129 and 20051209 build. i'll try to play a mission.

[EDIT] Jesus ****ing christ!


messed up perseus with a radar for a logo


at least i know where my perseus textures went...


explosions are ****ed...


charybdis got a makeover

[StratComm]

Wow, that's a lot of random graphics.  Which build are you using?

[Cobra]

20051209.

[taylor]

Post the debug log file.

[Cobra]

which is that, again? (and if it's errorlog.txt, it's about 550 kb... but it's debug_filter.cfg, right?)

[taylor]

fs.log, or fs2_open.log if you aren't using Windows.

[Cobra]

er, it's an MB in size. should i post it as is or delete it and run FSO again?

oh yeah, almost forgot:

The unviewable ships/sentries are the GTSG Alastor and the GVS Nephthys.

and this may be because i put Admiral Nelson's nameplated ships campaign in, but i can't view the barracks nor the mission simulator now.

[karajorma]

Pick the FS2 campaign from the campaign room and then try.

To be honest though Cobra judging from the amount of weird errors you post with all of your programs I suspect a reinstall of Windows might be called for.

[Goober5000]

To be honest though Cobra judging from the amount of weird errors you post with all of your programs I suspect a reinstall of Windows might be called for.

He's probably right.

[taylor]

er, it's an MB in size. should i post it as is or delete it and run FSO again?

Just load and play one mission, make sure it has the problem, exit the game, zip up the log and post it.  A basic log will be around 1meg so that's not unusual.  Compressed it would be much smaller though since text compresses well.  Just be sure to use a current CVS build since I recently made changes to some of the debug output which can greatly help us determine problems.

[Cobra]

FS Log

more *sigh* screwups o_O

instead of particles i get blobs:


i got a texture instead of a glowing ball! yay?


subspace flash replaces explosion effect:


oh yeah, and i get subspace warp effects whenever i destroy a subsystem.

[taylor]

FS Log

Don't see anything totally obvious yet but I only have given it a quick look so far...

 - Upgrade your OpenAL version, 1.1 is current and I'm pretty sure that's what redmenance builds with which shouldn't matter but could cause some strange issues as I try to support both 1.0 and 1.1.

 - Upgrade your video drivers too, they are about 7 versions old at this point.

 - Make sure that your data\ directories in c:\games\freespace2 and c:\games\freespace2\SCP don't contain anything strange.  You should probably put axm_jad2eb.vp and Desperation.vp in a mod directory, or two.  That will make sure that you don't get any strange conflicts.

 - Don't use -tga16, I'm going to take it out soon.  It's useless with -img2dds anyway which is actually meant to replace any benefit of -tga16.  -img2dds also already turns on -jpgtga so you don't have to worry about that on either.  Try turning off -img2dds just to make sure you aren't somehow finding a bug with it.

I didn't see the main bmpman debug info that I was interested in.  Make sure that your debug_filter.cfg file contains "+BMP DEBUG" (with a + and not a -).

[Cobra]

here's what i have in my debug filter:

+BmpFastLoad
+General
+Paging
+wash
+Maps
+Sound
+network
+Parse
+AB TRAIL
+AI
+Model
+BmpMan
+Error
+JOYSTICK
+Warning
+lethality
+Particles
+Jim
+Physics
+Messaging
+EVENTMUSIC
+Alan
+missionlog
+BMP DEBUG
+BmpInfo
+Sandeep
+Weapons

and i do have OpenAL 1.1

[EDIT] i checked my SCP-3.6.7 folder and all i have are models. that's it.

[taylor]

Hmm, wonder why the extra bmpman debug info didn't show up then.

and i do have OpenAL 1.1

From your log file:
[q]Vendor     : Creative Labs Inc.
Renderer   : Software
Version    : OpenAL 1.0[/q]
From mine with current version from download link off of http://www.openal.org:
[q]Vendor     : Creative Labs Inc.
Renderer   : Software
Version    : OpenAL 1.1[/q]