[Colonol Dekker]

What are the problem specifics / what's wrong with the Loki?

[Tahna Los]

Recently cleaned, also have the Catalyst 8.7 drivers (I have an X800 Pro).  As for FSO, I do have 3.6.9 but the version released last year.  Does anyone have a particular stable build to use with the new vps?  I've tried several, all had very weird problems.

[Vasudan Admiral]

Try the one from here: http://www.hard-light.net/forums/index.php/topic,55095.0.html (remember to get the shader VP there too)

[Tahna Los]

That particular build is quite slow on my machine.  Also, thruster effects are not working properly (taylor is aware of this) and ship name decals are not on the ships anymore.  Is there a more stable build than this or is there a workaround?

[colecampbell666]

An almost identical problem happened on page 23 of this very thread actually. That one turned out to be the graphics card overheating due to a clogged fan, but it's also possibly attributable to ATI cards, older FSO builds and possibly graphics card drivers.

So, first make sure your machine isn't overheating, then if that doesn't work or isn't the case grab a new FS build from Recent Builds. Failing that check your graphics drivers are up to date.

Wrong, VA. It is because of a driver bug, Backlash had the same problem. I don't know what causes it, but it mysteriously disappeared a while ago. (I think). All I know is that it wasn't the fan.

[Hellstryker]

He probably mentioned the fan since he said it was running slow.

[colecampbell666]

It was my fan, and it had stopped running.

EDIT: That comment made me look at my fan, and it has fallen out of the heatsink. Ah well, the card has presumably been like this for weeks, and the fan didn't work properly before that, so I guess it hasn't had much effect on the card. If it means it dies in 6 months instead of 7, so be it. My parents have been hinting at a new PC anyways, so hopefully...

[Vasudan Admiral]

Meh, I just went with what you said.

Got the fan to work, and the weird lines have disappeared. Thanks.

[colecampbell666]

Well it did work, but I had to push it slightly into the right position, and it went off sometimes anyways. I left it because I didn't notice any problems.

[MechMantis]

EDIT3: Time for more experiments. Removing report until I can figure out exactly what's wrong.

EDIT4: Well.

Tests say that some ships (The Orion, Argo, and Iceni, for example) dislike normal maps, and they then eat up all available CPU, causing a crash.

Huh.

Using this build, but I might try one of the later ones in a bit. Don't think it's hardware related, but just in case

AMD Athlon 64 3500+
ATI Radeon X1650 Pro (Driver: Omega 3.8.442 [I should update these, shouldn't I?])
2 gig DDR2 RAM
Not entirely sure on the motherboard, but it's a Biostar K-800something

[chief1983]

Use this.

Latest trunk build that's been posted, and no other tweaks.  Any bug reports should be done based on a recent trunk build, since they're trying to wrap up 3.6.10 for a release now.  I just hope we can get another MVP beta before 3.6.10, so we can make sure there aren't bugs in one or the other.

[blowfish]

I just hope we can get another MVP beta before 3.6.10, so we can make sure there aren't bugs in one or the other.

There was talk of a gamma release.  The main problem was organizing it, since that is not an easy task, and it would probably fall on DaBrain to do it

[MechMantis]

Use this.

Latest trunk build that's been posted, and no other tweaks.  Any bug reports should be done based on a recent trunk build, since they're trying to wrap up 3.6.10 for a release now.  I just hope we can get another MVP beta before 3.6.10, so we can make sure there aren't bugs in one or the other.

Well, with this build normal maps just don't work at all, flag checked or no. I remember trying it earlier.


Would that be considered a bug?

EDIT: I'll try this one, maybe that'll solve the problem.

EDIT2: Same problem. Normal maps simply don't work. Needs to be an actual Xt release or nothing.

[chief1983]

Sorry, since you were using such an old build, I forgot.  The shaders aren't built in anymore, you have to download the shaders vp file too, and put that in your FS directory.  The build I linked you to is essentially what's in the one you just referenced, and some other bugfixing since then.  Plus it was after Taylor added it to the main source base.

[MechMantis]

^^I had tried the one you linked me to, and just to make sure I tried it again. Nothing. With either of the shader VPs (the simply named shaders.vp or the sdr1119.vp)^^

Got both the old shaders VP and the new VP in there. Tried one, then the other, then both together. Nothing.

[chief1983]

What's in the fs2_open.log?

[MechMantis]

An old crash, nothing recent. The game doesn't "crash", per say, it just eats all CPU and does nothing with it, forcing a ctrl-alt-del out. Lock was the term I should have used.

[chief1983]

Are you running a debug build?  It should just dump output to it.  Use one, and maybe even turn on the debug window.

[MechMantis]

Warning: Too many beam sections for weapon BFRed - max is 5
File: Weapons.cpp
Line: 3021


Call stack:
------------------------------------------------------------------
    parse_weaponstbl()    parse_modular_table()    weapon_init()    game_init()    game_main()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816fd7()
------------------------------------------------------------------


This is new. Debug EXE of the latest trunk build, that is, one without the locking problem. Now, the standard EXE just goes on it's merry way and plops me at mainhall. Debug EXE gets a nice instacrash.

[chief1983]

Try no mods, and see if the debug output tells you anything about whether or not OpenGL loads successfully.  It should, and if it does it's probably a MediaVPs bug.