Do your ships stop when fired upon?

Slonor · Post by **Slonor** » Mon, 16. Jan 12, 06:15

I noticed that some blue ships stop when fired upon even if they were in flight before attacked. When they turn red they sometimes resume flying and start fighting. Anyone had this happen?

chrispw · Post by **chrispw** » Mon, 16. Jan 12, 12:44

I've lost a load of UTs recently due to all commands canceling when they get shot.

Usual scenario is:

"One of your ships is under attack"
Find a UT with 2/3 of shields left, loads of ecells
Order the UT to return home (home base of one of my trading stations)
"One of your ships is under attack"
Damn thing has stopped. Order it to jump to the next sector.
"One of your ships is under attack"
Stopped again, now taking hull damage. Order it to follow me (I'm OOS and auto-jump is turned on).
Stoped again. Ship death.

I've also seen this happen in system, mostly my M7M getting fired on by fighters while I'm trying to board a carrier - can't get it to follow me, jump out of the system, anything really. I usually end up reloading if I've screwed up enough to get my M7M fired on; I know I'm not going to be able to save it, even if it is still at 90% shields.

facetious1 · Post by **facetious1** » Mon, 16. Jan 12, 13:06

Just to add some info, I did have a TS that dropped all its drones to protect it...

Did you give it the full 10 seconds for the jump when you initated the first command???-- maybe you overrode the auto jump?

chrispw · Post by **chrispw** » Mon, 16. Jan 12, 13:08

Plenty of time given, checking the ship commands they appear to be getting canceled.

One moment they will be "Jumping to sector XX" or similar, then standby shortly afterwards

Zetoss · Post by **Zetoss** » Mon, 16. Jan 12, 13:38

I have seen some odd behavior regarding this too, my ship was chasing an M5 but stopped over and over again forcing me to issue the command to attack about 10 times, even that the command actually wasn't cancelled the ship simply stopped moving and didn't fire or do anything at all even if I waited for over 3 minutes... Never even got that little bastard btw, some patrol decided I was taking too long and launched a few missiles. I have also noticed several ships sitting in random positions near gates for more than 48 game hours, granted I have only seen a few but you tend to remember things like a "Split Mapping Service Iguana" sitting in exactly the same spot where you pass by every few hours so I'm certain it's the same ones staying for very long times...

Semi-off-topic: Anyone else have problems with the turrets? Could be a mistake on my part but the turrets seemed to be even more reluctant to fight than my ship was, I had them set to an advanced command but they should have sprayed away unless a missile was close and there weren't any, they still didn't attack more than every now and then even when the target was right up in my face. Hopefully the upcoming patch will solve these problems but if not we better let ES know...

Post by **Alan Phipps** » Mon, 16. Jan 12, 14:17

Similar thread including a link to another.

Virtualaughing · Post by **Virtualaughing** » Mon, 16. Jan 12, 17:55

Im not 100% but if you strip their weapon slots they won't try to fight back....
If any ship stop moving when fired upon that can be the results of low quality CPU installed in your PC...

Slonor · Post by **Slonor** » Tue, 17. Jan 12, 06:10

Virtualaughing wrote:Im not 100% but if you strip their weapon slots they won't try to fight back....
If any ship stop moving when fired upon that can be the results of low quality CPU installed in your PC...

I've had this happen in assassination missions. I'd approach the blue target ship and after I attack it immediately stops. Then they obviously read me their warnings, last warning, then sometimes after they turn red they start to move again.

Could you clarify how this could be the result of a low quality CPU? I have an e8400.

Raize · Post by **Raize** » Tue, 17. Jan 12, 15:25

Slonor wrote:
Could you clarify how this could be the result of a low quality CPU? I have an e8400.

That's a slow CPU with a third of the cores they have nowadays from two generations ago... of course it could be a result.

RoverTX · Post by **RoverTX** » Tue, 17. Jan 12, 15:56

This game's base code, which is more optimized now, is from like what 4 generations ago?

Post by **Alan Phipps** » Tue, 17. Jan 12, 16:00

.. also the number of cores (above 2) does not matter, the effective clockspeed does. X3's .exe file only runs on one core, the rest mainly run drivers and OS services or idle.

Vicke · Post by **Vicke** » Tue, 17. Jan 12, 17:33

Slonor wrote:I've had this happen in assassination missions. I'd approach the blue target ship and after I attack it immediately stops. Then they obviously read me their warnings, last warning, then sometimes after they turn red they start to move again.

This has happened to me several times. I usually kill the blue target before it turns red. Easy money.

Virtualaughing · Post by **Virtualaughing** » Tue, 17. Jan 12, 20:45

Sure i have no idea what CPU you have but low Q CPU will overcalculate and the ships start freezing...

Slonor · Post by **Slonor** » Wed, 18. Jan 12, 03:12

Raize wrote:
Slonor wrote:
Could you clarify how this could be the result of a low quality CPU? I have an e8400.
That's a slow CPU with a third of the cores they have nowadays from two generations ago... of course it could be a result.

That makes no sense. From what I've read X3 only uses 1 core anyway. At best a dual core will be a benefit because the drivers and other background programs will run on the second core, but X3 itself is not optimized for multiple cores. Most modern processors now have multiple cores, but they are not rated much higher than 3.0 GHZ anyway which is what the e8400 is. This is partly why "bulldozer" was a failure despite its 8 cores compared to Intel's 2- and 4-core processors. Cores beyond 2 only matter for video games optimized to use 2 or more cores. Otherwise anything beyond 2 cores is a waste for the most part.

X3:TC and X3:AP also use the same graphics engine as X3:R (they're expansions) and that was released in 2005. The e8400 "Wolfdale" was released in 2008.

How can a high performance Intel processor released 3 years after the engine for X3 was made be too slow for that engine? Did they work to make X3 less efficient in the expansions? It really makes no sense.

Xander Cade · Post by **Xander Cade** » Thu, 19. Jan 12, 23:41

I don't know if this is the best thread for this, it just happens to be the most recently posted in that I could find on the subject.

This issue hasn't been very prominent in my game, but in the last hour I have had two very noticeable instances of it.

1. CAG goes into Zyarth's Dominion for some unknowable purpose, where it is accosted by a flight of Xenon. I had to give it the jump command no less than seven times before it finally jumped because it kept reverting to the None command every time it got hit.

2. A Pirate Dragon was prowling around CBSW causing some problems for my CAGs. I jumped in and fired a single Hornet. Dragon stopped dead. It did not move again until my turrets came into range and it was hit again. I then watched it decelerate after just starting to move twice before it was destroyed.

Post by **Cycrow** » Fri, 20. Jan 12, 00:07

if anyone can reproduce the problem, or better yet, have a save game where it always happens in, then it'll be most welcome

pr0nflakes · Post by **pr0nflakes** » Sat, 21. Jan 12, 18:32

Cycrow wrote:if anyone can reproduce the problem, or better yet, have a save game where it always happens in, then it'll be most welcome

With pleasure.
https://rapidshare.com/files/2727224422/X04.sav

And heres a post with an earlier save i made in tec support.
http://forum.egosoft.com/viewtopic.php? ... highlight=

Slonor · Post by **Slonor** » Sat, 21. Jan 12, 20:22

I'm glad to see I'm not the only one with this problem. I don't see how it can be an issue with the processor. Usually processor problems lead to crashes/blue screens/FPS drops. This reminds me of a problem I had with X3R a long time ago on a different computer. I downloaded the Xtended mod, uninstalled it after using it a bit and then had a strange problem where Xenon would not move at all when attacked. The only solution was a total reinstall and new game. But I have no third party mods installed in my current game so that cannot be the cause.

Post by **Cycrow** » Sat, 21. Jan 12, 22:34

Slonor wrote:I'm glad to see I'm not the only one with this problem. I don't see how it can be an issue with the processor. Usually processor problems lead to crashes/blue screens/FPS drops. This reminds me of a problem I had with X3R a long time ago on a different computer. I downloaded the Xtended mod, uninstalled it after using it a bit and then had a strange problem where Xenon would not move at all when attacked. The only solution was a total reinstall and new game. But I have no third party mods installed in my current game so that cannot be the cause.

i think some people are confusing it with another problem that is related to the processer.

this is where all ships would stop and not much.
the difference being it wasn't effected by attacking and the commands didn't reset, they just didn't move

its more common in a modified game thou when theres more for the processer to do

pr0nflakes · Post by **pr0nflakes** » Wed, 25. Jan 12, 19:18

Has this been looked into?
Is there any news on a fix?
Is it confirmed as a bug?

Any news would be great because this is really effecting my gameplay.