[Tamor]

Ok, at the risk of being flammed I'm going to report a problem I've been experiencing. I've also read the topic "Report bugs to Mantis' and seen the problems that process has.

I've been playing FS2 for a day now. Started off with the stock game and then decided to look up some extra information. I found SCP and decided to give it a try (seeing as it's one of the very few FS2 sites still around). I downloaded fs2_open_267, mv_zpack, and mv_befix, as well as a few effects: NebulaPatch, Suns_FS2_2.0c, and HR_JuSUB1.0.

Now here's my problem, I created a new pilot and soon as I got into the first actual mission and destroyed the enemy fighters, the enemy 'big ship' waps in - the one that apparently is scripted to blow up - and upon blowing up, the game crashes. Through a form of inspiration, i figured that fs2_open_367_d.exe was a _debug program. I got this when I ran it:

Code: [Select]

Warning: Couldn't open texture 'HVasudan_Bitmap'
referenced by weapon 'Vasudan Huge Turret'

File:weapon/weapons.cpp
Line: 1425
[This filename points to the location of a file on the computer that built this executable]

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
I then found two files: errorlog.txt, and fs.log. I'm clueless as to what to do. My system specs are as follows (figured I'd post that before it gets asked):

OS: WinXP Professional 5.1 Service Pack 2 (Build #2600)
CPU: Intel Celeron , 2.67 GHz
Video: Plug and Play Monitor on Intel(R) 82845G/GL/GE/PE/GV Graphics Controller (1024x768x32bpp 60Hz)
Sound: Realtek AC97 Audio
RAM: 256mb


Edit:
Ok, i've found that it only crashes when I whitness the explosion itself, so it's a graphical error somewhere. Figured this out when I realised I wasn't LOOKING at the battleship when I heard "Belasarius has been neutralised" and decided to turn and look in the direction it was suposed to be, saw the flames and then game locks up and closes out.

[Wanderer]

Hmm... Well first i would recommend you to download 3.6.9 RC 7.8 builds, http://www.hard-light.net/forums/index.php/topic,41891.0.html

Then download 3.6.8 Zeta MediaVPs, http://www.hard-light.net/forums/index.php/topic,39905.0.html and the related mp-710 pacthes, http://www.hard-light.net/forums/index.php/topic,41891.0.html

And before you install any of those... remove the older additions (not the retail FS2 files though) that you downloaded. You shouldnt need those any more and they may cause problems such as you have now encountered.

And above all make sure you have read Karajorma's FreeSpace FAQ.

[staub]

This is a thread i started in the Babylon Project 3.4 Beta Bug report and they sent me to the SCP with that - the Bug is obviously known and related to intel graphics cards:

Programm crash upon explosion - here is what i encountered:

On my machine, the Beta (which is driven with Build 3.6.9 in OpenGL) seems very susceptible to explosions. It is obviously somehow ship-type and distance related. close targets and especially being shot down yourself (after changing to external view) seems to force the program to crash - the picture stops and sound hangs looped. Sometimes it's possible to exit via [esc] but i had severe computer lockups too.

Before going into Beta i was playing a few times the TBP 3.3a Base and the 2005-12-22 build and everthing worked fine - But: i was doing that with Direct3D and not with OpenGL - didn't test the build with OpenGL so far.
I tried to disable several graphics options in the launcher, but no success. And running 3.6.9 in D3D doesn't work at all

Wing Commander Saga Prologue works fine, but i guess it's not rooted on the latest fs-open build...

Any ideas how to troubleshoot the bug? Or is there any chance to get Direct3D runnning?

My System:
Acer TM 663 Laptop with 1.6 GHz Centrino, 1.23 GB Ram, Intel Extreme GM/GME video card with latest driver (not shure about vidmem: 64MB?), default resolution 1400x1050, external PCMCIA buscard soundprocessor (Creative Professional E-MU) - actually the whole sytem tweaked for music production, which should not be too bad for gaming performance, though it's not today's state of the art equipment...

[karajorma]

Wing Commander Saga Prologue works fine, but i guess it's not rooted on the latest fs-open build...

Umm. What? WCS uses a build of FS2_Open that was release literally days before 3.6.9 Official. Are you absolutely certain it runs without problem in OGL? And if so what happens if you steal that build and try to run TBP on it?

[colecampbell666]

I'd delete your whole FS2 install and start fresh with Turey's installer. (look at the stickies) Save only your pilot files.

oh, and

[Turey]

I'd delete your whole FS2 install and start fresh with Turey's installer. (look at the stickies) Save only your pilot files.

He doesn't want to do that. He's only interested in TBP.

[staub]

Thanks for the warm welcome 

Got to admit - i tested WCS only in D3D and not OGL. But i'm gonna try to substitute it with this build - ok!

For the reinstallation cause - ist it right that Turey's installer needs online connection? Because my Comp is not connected and i'm downloading with another (a Mac OS9 dinosaur  so thanks for the proper coding and design of your site - it has become unusual to see webpages the way they are thought to be...)

I'll give you some feedback as soon as i have some spare time to test it - i'm slow with such forum things, sorry.

[karajorma]

I think your only solution is to run in D3D for the time being. We really need to find and fix that Intel issue with explosions!

[staub]

I'll try to get an error message with the debugging version, if i can (if the crash is going to let me do this) - perhaps this will give you a hint to fix that intel bug.

Any other info that would help you?

Another thing: I wonder if it would be possible to make a mod wich leaves the space combat path and goes more into space racing. Do you think the FS2_open Engine is suitable for something like death star reactor run meets armed pod racer? A bit like going back to Descent - flying through the corridors of a huge space station. Can the engine bring a speed rush for a pack of six to eight racers plus racing course host-object including obstacles or would the frame rate be annoyingly slow? Is it possible to radically slim the thing down to throttle setting, afterburners, targeting and a pair of guns? Or are there better engines for this purpose?

[Turey]

Another thing: I wonder if it would be possible to make a mod wich leaves the space combat path and goes more into space racing. Do you think the FS2_open Engine is suitable for something like death star reactor run meets armed pod racer? A bit like going back to Descent - flying through the corridors of a huge space station. Can the engine bring a speed rush for a pack of six to eight racers plus racing course host-object including obstacles or would the frame rate be annoyingly slow? Is it possible to radically slim the thing down to throttle setting, afterburners, targeting and a pair of guns? Or are there better engines for this purpose?

*cough* there's at least one FS2_open Mod or TC already doing a racing mission... 

[staub]

ok, a few more infos:

I tested TBP 3.4 with the WCS FS2_open build, with exactly the same launcher settings as WCS defaults (except HUD and TBP features on and WCS features off).

What i can say is:
- the problem with the certain type of explosions in OGL persists
- it's definitely distance related (if you're close, it crashes, otherwise not)
- the TBP aurora fighter has definitely the critical kind of explosion (obviously not used in the first few WCS missions - i blew up that pirate capship and lots of fighters without crash)
- the program froze before the main explosion has become visible
- TBP 3.4 works with the WCS build in D3D - except for those white squares that occur in place of smoke (- i guess i'll find a thread to troubleshoot that somewhere...)

I guess, I should move this to mantis, should I?