Hard Light Productions Forums

Hosted Projects - Standalone => The Babylon Project => Topic started by: Vengence on December 16, 2005, 04:49:18 pm

Title: Just plain annoyed
Post by: Vengence on December 16, 2005, 04:49:18 pm
Yeah, its said it was fixed but it wasn't on my machine. Yet again its the Nightmare Scenario. Some guy at Mantis said to use another build but I didn't know where to find it, I installed different fs_open builds but it didn't fix (in fact it worsened it), I searched here only to find dead links to fixes, and now I'm getting impatient. Will the RW 2.1 patch fix this problem? If not what do I get to fix it? I'm doing a complete reinstall of all files of TBP and adding the patch and if it doesn't work... well then there is going to be more complaining. I ran a debug of the mission game crashed before it even went to the briefing screen without leaving a log. Previous debugs said that there were table problems but I'm sure those are fixed by now.
Title: Re: Just plain annoyed
Post by: Prophet on December 17, 2005, 02:55:12 am
Quote from: Vengence on December 16, 2005, 04:49:18 pm
Some guy at Mantis said to use another build but I didn't know where to find it,
Have you tried checking the Source code projects site? (link at HLP main page)
Or the recent builds threads at the SCP boards? (here at HLP forums)

BTW. What is your problem?
Title: Re: Just plain annoyed
Post by: Col. Fishguts on December 17, 2005, 04:42:27 am
Quote from: Vengence on December 16, 2005, 04:49:18 pm
Will the RW 2.1 patch fix this problem?

Yes, that's what it's actually there for. Install the correct version of the path, depending on your SCP build, and it should work.

Have you read through the sticky RW 2.1 thread ? There are several useful hints in there.
Title: Re: Just plain annoyed
Post by: Vengence on December 17, 2005, 11:55:41 am
I found the SCP homepage and got the latest build and didn't fix it. And Guts, the problem that actually left a log said something about a ship having something 0 when it should at least be 1. It was lost somehow but I reinstalled everything and installed the patch for the old build that came with TBP so hopefully it works now.
Title: Re: Just plain annoyed
Post by: Bobboau on December 17, 2005, 01:58:48 pm
yes your problem can be fixed easily, by fixing it.

isn't vagueness fun! :)
Title: Re: Just plain annoyed
Post by: Vengence on December 17, 2005, 03:55:57 pm
Not really. Whats really fun is laughing the hell out of yourself when you point your finger and laugh at a once unpassable level because of a bug and rejoice in glory as you conquered an annoying blockage to your progression in your most favorite mod! Its finally fixed.
Title: Re: Just plain annoyed
Post by: Bobboau on December 18, 2005, 01:02:48 pm
ok, because you seem to be about as dense as a brick wall:

WE HAVE NO ****ING IDEA WHAT YOUR PROBLEM IS

_TELL_ _US_ WHAT THIS BUG OF YOURS _*IS*_!
[/color]
Title: Re: Just plain annoyed
Post by: taylor on December 18, 2005, 02:04:05 pm
Quote from: Vengence on December 16, 2005, 04:49:18 pm
Some guy at Mantis said to use another build but I didn't know where to find it, I installed different fs_open builds but it didn't fix (in fact it worsened it), I searched here only to find dead links to fixes, and now I'm getting impatient.

Quote from: My Mantis Bug Response
Are you using 3.6.7 or a different build? I think this has been fixed recently, if that's a red alert mission. Anything newer than 20051117 should have the fix but that bug did slip into 3.6.7 without anyone noticing it. Try a newer build, one of the CVS releases, and report back as to whether it works now or not.

And after about 2 and a half weeks without response from you it was assumed fixed and the bug was closed.  Did you even read the ****ing thing?  Not only did you waste my time by filing a bug report and not keeping up with it but now you come here and ***** about it.  I'll be sure to ignore each and every problem you report from now on since you were kind enough to ignore my attempt to help fix the problem.  :mad:
Title: Re: Just plain annoyed
Post by: Vengence on December 18, 2005, 02:58:11 pm
Your solution didn't work. Plain and simple and I lost faith in mantis and took the problem into my own hands. And to anwser, I have no idea what the bug was. It just crashed without leaving a crash log. And it took a while for a response and look at this: 7 replies in a few days compared to a single relpy in 3 days or somewhere around that.
Title: Re: Just plain annoyed
Post by: karajorma on December 18, 2005, 03:19:47 pm
Seriously Vengence you need to use Mantis if you want coding bugs resolved. A bug like this can only be solved by giving us as much useful information as you can but yet you haven't even linked to the mantis report which means you're expecting us to all dig through Mantis to find what you're on about.

The fact is that you may have gotten more attention with this thread but it's all been negative. Even after reading it I'm still not much the wiser about what your problem actually is, let alone what I can do to help you solve it.
Title: Re: Just plain annoyed
Post by: PSI-KILLER on December 18, 2005, 07:41:19 pm
Vengence I hope you get it fixed, That level has some great freding and great voice acting all thrown into one!!!

 :pimp:

 :yes:

 
Title: Re: Just plain annoyed
Post by: Trivial Psychic on December 18, 2005, 09:19:43 pm
I'm not sure if Vengance openned a bug report in the SCP Mantis, but he did open one in the TBP Mantis (http://keepersdomain.net/tbp/mantis/view.php?id=10) (11/19).  That bug report has been closed, but after making the initial bug report, Vengance didn't provide any feedback from Taylor's suggestions (11/21), so he closed the bug report (12/06).
Title: Re: Just plain annoyed
Post by: Goober5000 on December 19, 2005, 01:08:20 am
Either use Mantis - http://lore.maxgaming.net/~scp/mantis/login_page.php - or don't complain.  And put forth a little effort to help us out, for goodness sakes.

If you won't see fit to cooperate with us, I see no reason to allow you to waste our time on the forums.

Thread closed.