I've got 20 or so Asgard in groups of 4 assigned to the various Xenon core gates, and at least once a real-life day, one of them takes enough shield loss to ping the "under attack" talking head
So I teleport over to handle things in person, and there are 2 K and an I that cannot be targetted, are ignored by every allied ship, but are utterly trashing my Asgard!
Even the Asgard beam laser passess through them harmlessley, then they kill everything
Sometimes I can teleport out of the sector then back in to fix it, but the seconds that takes means at least one scrapped Asgard and 300 5* engineers gone
On a separate note: one in twenty times I climb into ANY S or M class ship and take off, it goes to full travel mode speed and cannot be stopped unless I exit the pilot seat. Great fun INSIDE an Argon EQ dock!
Xenon K and I untouchable when responding to attack
Moderator: Moderators for English X Forum
-
- Posts: 1524
- Joined: Thu, 29. Dec 05, 20:38
-
- Moderator (English)
- Posts: 31817
- Joined: Fri, 16. Apr 04, 19:21
Re: Xenon K and I untouchable when responding to attack
I have moved this over from Tech Sp as you are not providing any information for investigation.
If there are ships that cannot be targeted then something is wrong and I would suspect game corruption or mod issues. Verifying your game installation would be a good first step.
The other thing causing non-collision errors could be insufficient memory for the game, either VRAM on your graphics card, system RAM, or through a possible memory leak after really long continuous play sessions. Without information, we could not refine this possibility any further.
If you did wish this to be taken in Tech Sp then the devs would need the information detailed in the first Sticky thread there, and a link to a vanilla save showing the issue.
Just one issue per Tech Sp thread and as described in the thread title please.
If there are ships that cannot be targeted then something is wrong and I would suspect game corruption or mod issues. Verifying your game installation would be a good first step.
The other thing causing non-collision errors could be insufficient memory for the game, either VRAM on your graphics card, system RAM, or through a possible memory leak after really long continuous play sessions. Without information, we could not refine this possibility any further.
If you did wish this to be taken in Tech Sp then the devs would need the information detailed in the first Sticky thread there, and a link to a vanilla save showing the issue.
Just one issue per Tech Sp thread and as described in the thread title please.
A dog has a master; a cat has domestic staff.
-
- Posts: 151
- Joined: Sat, 31. Jul 10, 20:36
Re: Xenon K and I untouchable when responding to attack
I've also had this happen a few times and it's always been when a Xenon I has come through a gate.
It's impossible to give a save for this sort of behaviour as saving/loading fixes this for me, so all the devs would see is an I in front of a ship that you can hit. It has made me wonder if the invulnerable civilian ship that you get around stations could be related.
Files verified, 32gb system ram, 16gb vram and cannot recall how long the play sessions were when it happened.
It's impossible to give a save for this sort of behaviour as saving/loading fixes this for me, so all the devs would see is an I in front of a ship that you can hit. It has made me wonder if the invulnerable civilian ship that you get around stations could be related.
Files verified, 32gb system ram, 16gb vram and cannot recall how long the play sessions were when it happened.
-
- Moderator (English)
- Posts: 4936
- Joined: Fri, 21. Dec 18, 18:23
Re: Xenon K and I untouchable when responding to attack
Might be related to ships taxing after passing through a gate. Try pulling the Asgards back away from the gate.
For people encountering the issue, try saving before the K/I pass through the gate. It might be more reproduceable from the state that runs up to the issue happening rather than saving after the issue has happened, where it is being fixed on reload.
For people encountering the issue, try saving before the K/I pass through the gate. It might be more reproduceable from the state that runs up to the issue happening rather than saving after the issue has happened, where it is being fixed on reload.