Search results

I've had this issue since the shipyard update. It was in the bugtracker, but was archived. Solution: Buy a newer videocard.

This graphics shader error is still present on v0.19476 for Nvidia 6000 and 7000 series video cards.

It sounds like you're stuck in the carrier. Try doing "/change_sector x y z", move a little bit then /change_sector back.

The game freezes or the whole computer freezes? If it's the whole computer you need to check the integrity of the new RAM modules (run memtest).

This used to be part of the game. It was removed, and thank god it was. Salvaging is for salvaging, not for fighting. Kill the ship first, then salvage up the left overs from the overheating ship.

Still no answer on this error? I never used to get it previous to the shipyard update. It would be good to be able to play on my work computer again. ***EDIT: I've also sent in error reports from my kid's computers. Same graphics error. Effected videocards here: Kids - EN7800GTX, EN7900GTX...

Well that's kinda silly then... You can attack and kill the station with ease and without any back up. Get out of your ship, pay to remove the decayed station status, salvage it for the blocks at your leisure, then fly away the other direction and never encounter the 'support' fleets at all...

Where is the documentation for this feature? What do the difficulty levels mean? Is 1 harder, or are higher numbers harder? What ship size does the game mechanic intend for each difficulty level? The wave manager fleet settings do seem to work as far as the fleet will spawn in. The fleet...

In my opinion the regeneration of asteroids was only causing an issue when people built custom asteroids with 1000's of extra blocks on them (mostly shield and adv armour), these would then respawn after the player jumped between two locations, a custom asteroid built in each location. The lack...

Here's my error log. This one is upto date with the latest version (0.19431), but the same graphics crash.

I'm having this same issue with one of my computers. Same errors in the log file. Same crash at 100% loaded. There was no issue before the shipyard update. From what I can see it's videocard or driver related as all the errors relate to "graphicsengine.shader.ShaderException". Videocard is...

Faction and Home Base were both true. Enemy and Others was set to false. I have them all set to false now. It was still making new blueprints and uploaded blueprints set auto to enemy. Changing slots to 0 prevents the save to server. That stopped it! Stops you adding new blueprints too and...

It is.

Since the 0.19318 (+ hotfixes) update, every new blueprint that has been saved or uploaded to the server has automatically been set to enemy usable. This is a major issue that crashes the server when huge ships decide to spawn in waves for the pirates. We have no choice but to disable the...

DireVenom was not banned. His whinge has nothing to do with any actions of admin. He had his non-homebase destroyed by a non-admin player and wanted to complain about. He has got it into his head that admin means were used to find his 'hidden' base which was really in plain sight to any...

Funny is how when the facts do truly show what happened you then resort to personal attacks.

You were not just banned when I replied to the ticket. You were set Persona-non-grata. No chance of redeeming yourself. My reply was to close the ticket from the system, not for your benefit.

You should read your own client's chat log and see who it was throwing the verbal abuse. I'm not the faction leader, nor am I the one who sets or unsets enemy. A kill order was given and I just did what was expected from the faction leader. He would have flown there himself if it wasn't so...

When you speak lies do i have any choice but to defend myself? Ticket lodged on May 5th 3:19pm. Added to Persona-Non-Grata list May 7th 11:40pm. I replied to the Ticket 27 minutes later. Sucks when things keep time stamped logs hey.

Shock horror! PvP on a PvP server between non-admin players. Hey, I'll put a bounty up on ships that aren't in line with the rules for the server. Take a screenshot (F6) before you destroy it to show it was indeed against the rules, then a 2nd screenshot to show it's been destroyed, then post...