Topic: To: David Farrell (Read 5171 times)

Jackal99 · « **on:** February 04, 2003, 12:16:21 pm »

Hello Dave,

first, thanks for posting the readme of the latest patch revision.

after reading it, I haven´t found a fix for two very ennoying bugs that were reported for nearly 2 month now.

1. stardate is stuck after loading a saved single player CONQUEST game
2. the so called "starship exploding bug", where sometimes one of your ai fleet members (or other ai ship/station) is destoyed in the moment something explodes.

maybe i missed something or it isn´t fixed yet, either way PLEASE let us know.

Best
Jack

p.s. people, please, i don´t want to see any replies other than from Dave here (bumps are always welcome

). These two bugs being fixed is very important to me and some other guys as well, because i / we love it playing a modded single player conquest game beside d3.

Thanks in advance.

David Ferrell · « **Reply #1 on:** February 04, 2003, 12:34:15 pm »

1) I think #1 is fixed (did you try the Beta patch? anyone?).

2) We think this is related to memory corruption. I was unable to reproduce
it on my system, but I have a gig of main memory in mine.

Thanks,

Dave

Scarrita · « **Reply #2 on:** February 04, 2003, 12:40:17 pm »

1. The stardate issue is not fixed
2. Ships still explode

Yes, I have the beta patch installed

And although I do not have a Gig worth of memory I do have 640 MB... One would thing that it is enough.

And I did do a complete reinstall.

Toasty0 · « **Reply #3 on:** February 04, 2003, 02:24:52 pm »

Dave,

This was a problem right up until build 500. If my memory of testing serves me correctly it should be cured...errr...fixed in the version we're waiting to be released/approved by Activision.

Best,
Jerry

Jackal99 · « **Reply #4 on:** February 04, 2003, 05:06:20 pm »

Hi Dave,

1. isn´t fixed in the beta

2. I have 512 MB RDRAM (4x 128 Samsung Original Pc 1066).. should be good enough

I have an idea what is causing that bug, maybe i am totally wrong.

in my opinion it could be a bug in the ship/shuttle automation. -> when a ship has launched shuttles and is beaten, the shuttles are destroyed in the SAME moment their "mothership" is exploding, regardless their status. That´s EXACTLY what happens to your ai team mate (and other ai ships/stations as well): it will be destroyed when something is exploding.

Best Jack

p.s
System Specs (just in case)

- P4 3,06 with HT ( 2,26 in another pc, same results in the game)
- 512 MB RDRAM
- Asus P4T 533-C

Jackal99 · « **Reply #5 on:** February 04, 2003, 07:07:17 pm »

bump

555TORP · « **Reply #6 on:** February 04, 2003, 10:33:11 pm »

2) ships explode, I have 1024 MB RD-Ram 1066

Alexander1701 · « **Reply #7 on:** February 05, 2003, 12:27:05 am »

I don't know if I speak for the spirit of things at Taldren or Activision, but I can speak for myself when I say that if these issues are not fixed by the patch, they can wait. They aren't exactly crucial (almost trivial, for the first one), and I think all of us are in a state of anticipation over the release of the patch. It solves the vast majority of known issues. Its good for now.

This is all assuming approval by Activision. It is, after all, possible, though highly implausible, that they may send it back.

Alexander

Fire_Spy · « **Reply #8 on:** February 05, 2003, 06:10:18 am »

I am sorry but when the stardate stops moving....You DO NOT get any new ships in the ship queue, All enemy ship movements CEASE. No new AI ships are built..So i think that the stardate freezing is a LARGE problem..

It is certainly big enough that i have removed sfc3 for the moment until and IF I hear this has been fixed in the patch when it gets released.

Jackal99 · « **Reply #9 on:** February 05, 2003, 06:25:57 am »

I absolutely disagree with you, Alexander1701!! fixing the stardate bug should have the highest priority beside d3 issues! Many people like playing in conquest mode and a conquest game, modded or not, can´t be finished in a few hours.
be serious.

Dave, any thoughts on my reply (ship/shuttle automation)??

Best
Jack

AlphaMeridian · « **Reply #10 on:** February 05, 2003, 07:30:53 am »

I also disagree with you, alexander. As i said in the thread by David, I'm on a 56k, and I effectively cannot participate in the online battles on D3 and gamespy. The stardate bug is _crushing_ to the single player conquest missions. It makes them effectively BORE CITY. I"m sure that's not what the taldren devs had it mind when they put it in there.

As it stands, like the poster above, it's because of this bug that I just don't play SFC III anymore. The only reason I havne't uninstalled it is becuase the patch was coming out *soon*. At the very least, it's out of taldren's hands now, but that doen'st negate that If it's not fixed, i'm going to feel very devalued as a customer by the people that i gave money to for the game.

-Alpha

Jackal99 · « **Reply #11 on:** February 05, 2003, 01:23:35 pm »

final bump

Jackal99 · « **Reply #12 on:** February 04, 2003, 12:16:21 pm »

Hello Dave,

first, thanks for posting the readme of the latest patch revision.

after reading it, I haven´t found a fix for two very ennoying bugs that were reported for nearly 2 month now.

1. stardate is stuck after loading a saved single player CONQUEST game
2. the so called "starship exploding bug", where sometimes one of your ai fleet members (or other ai ship/station) is destoyed in the moment something explodes.

maybe i missed something or it isn´t fixed yet, either way PLEASE let us know.

Best
Jack

p.s. people, please, i don´t want to see any replies other than from Dave here (bumps are always welcome

). These two bugs being fixed is very important to me and some other guys as well, because i / we love it playing a modded single player conquest game beside d3.

Thanks in advance.

David Ferrell · « **Reply #13 on:** February 04, 2003, 12:34:15 pm »

1) I think #1 is fixed (did you try the Beta patch? anyone?).

2) We think this is related to memory corruption. I was unable to reproduce
it on my system, but I have a gig of main memory in mine.

Thanks,

Dave

Scarrita · « **Reply #14 on:** February 04, 2003, 12:40:17 pm »

1. The stardate issue is not fixed
2. Ships still explode

Yes, I have the beta patch installed

And although I do not have a Gig worth of memory I do have 640 MB... One would thing that it is enough.

And I did do a complete reinstall.

Toasty0 · « **Reply #15 on:** February 04, 2003, 02:24:52 pm »

Dave,

This was a problem right up until build 500. If my memory of testing serves me correctly it should be cured...errr...fixed in the version we're waiting to be released/approved by Activision.

Best,
Jerry

Jackal99 · « **Reply #16 on:** February 04, 2003, 05:06:20 pm »

Hi Dave,

1. isn´t fixed in the beta

2. I have 512 MB RDRAM (4x 128 Samsung Original Pc 1066).. should be good enough

I have an idea what is causing that bug, maybe i am totally wrong.

in my opinion it could be a bug in the ship/shuttle automation. -> when a ship has launched shuttles and is beaten, the shuttles are destroyed in the SAME moment their "mothership" is exploding, regardless their status. That´s EXACTLY what happens to your ai team mate (and other ai ships/stations as well): it will be destroyed when something is exploding.

Best Jack

p.s
System Specs (just in case)

- P4 3,06 with HT ( 2,26 in another pc, same results in the game)
- 512 MB RDRAM
- Asus P4T 533-C

Jackal99 · « **Reply #17 on:** February 04, 2003, 07:07:17 pm »

bump

555TORP · « **Reply #18 on:** February 04, 2003, 10:33:11 pm »

2) ships explode, I have 1024 MB RD-Ram 1066

Alexander1701 · « **Reply #19 on:** February 05, 2003, 12:27:05 am »

I don't know if I speak for the spirit of things at Taldren or Activision, but I can speak for myself when I say that if these issues are not fixed by the patch, they can wait. They aren't exactly crucial (almost trivial, for the first one), and I think all of us are in a state of anticipation over the release of the patch. It solves the vast majority of known issues. Its good for now.

This is all assuming approval by Activision. It is, after all, possible, though highly implausible, that they may send it back.

Alexander

Fire_Spy · « **Reply #20 on:** February 05, 2003, 06:10:18 am »

I am sorry but when the stardate stops moving....You DO NOT get any new ships in the ship queue, All enemy ship movements CEASE. No new AI ships are built..So i think that the stardate freezing is a LARGE problem..

It is certainly big enough that i have removed sfc3 for the moment until and IF I hear this has been fixed in the patch when it gets released.

Jackal99 · « **Reply #21 on:** February 05, 2003, 06:25:57 am »

I absolutely disagree with you, Alexander1701!! fixing the stardate bug should have the highest priority beside d3 issues! Many people like playing in conquest mode and a conquest game, modded or not, can´t be finished in a few hours.
be serious.

Dave, any thoughts on my reply (ship/shuttle automation)??

Best
Jack

AlphaMeridian · « **Reply #22 on:** February 05, 2003, 07:30:53 am »

I also disagree with you, alexander. As i said in the thread by David, I'm on a 56k, and I effectively cannot participate in the online battles on D3 and gamespy. The stardate bug is _crushing_ to the single player conquest missions. It makes them effectively BORE CITY. I"m sure that's not what the taldren devs had it mind when they put it in there.

As it stands, like the poster above, it's because of this bug that I just don't play SFC III anymore. The only reason I havne't uninstalled it is becuase the patch was coming out *soon*. At the very least, it's out of taldren's hands now, but that doen'st negate that If it's not fixed, i'm going to feel very devalued as a customer by the people that i gave money to for the game.

-Alpha

Jackal99 · « **Reply #23 on:** February 05, 2003, 01:23:35 pm »

final bump

News:

Topic: To: David Farrell (Read 5171 times) var addthis_config = {"data_track_clickback":true};

Jackal99

David Ferrell

Scarrita

Toasty0

Jackal99

Jackal99

555TORP

Alexander1701

Fire_Spy

Jackal99

AlphaMeridian

Jackal99

Jackal99

David Ferrell

Scarrita

Toasty0

Jackal99

Jackal99

555TORP

Alexander1701

Fire_Spy

Jackal99

AlphaMeridian

Jackal99

Topic: To: David Farrell (Read 5171 times)