cepheni

With the new update to the beta branch Intel cards receive some love. If you wait one or two days they will come to stable branch and you might give it a try. Maybe your problems will be resolved with the new update. Something else: Both logs detect Windows 7 on your machine, so you could try the update of the amd-driver. Or did I miss something?

In a way this exists but not completely like you suggested it. So there is the iterating through important targets with 'G'. That contains all ships and stations but no asteroids. For the stations alone there is the trading upgrade that lets you see all stations willing to trade (which is every station) of the sector you're in. Other than that there is no listing done yet. How and if it will come is not yet clear, but many people would like to see something along those lines.

This topic has been moved to User Guides. [iurl]http://www.avorion.net/forum/index.php?topic=2913.0[/iurl]

Ah ok, indeed I missed that it was the fighters you were talking about, sorry.

you can add that option from within steam. Just go to your library, right-click on Avorion and in properties click on the "set launch options". Add it in the box that appears when you do that and start the game.

One of you needs to host a multiplayer game, uncheck the box "list publicly" so that only you and your friend can connect. The non-hosting party can now join the friends game by using steam's "join game" in the steam friend list.

If you have more than one ship following you some get currently lost. As they were spawning all on the same position and with that destroying each other, the jumps got delayed a bit. Now they are not quick enough and loose target. You can work around it by having a chain of escort commands, so ship1 follow ship2 follow you. I already spoke with the dev regarding that topic and he will work on it.

You have to at least once shoot your weapons close by a xsotan, then they become a red outline (although the relations are still neutral) and your independent weapons will target the xsotan. If that doesn't happen, or you can't shoot first, then tell your turrets to attack that target while having the xsotan selected.

Can you do us a favor and rerun your client with the launch option "-t all" (without quotes) and repost the entire log via pastebin or something similar? "Generic Error" is sadly not very telling what went wrong..

Thanks for reporting that, we will look into it!

In these logs you are playing on the default branch and all I can see is, that your server takes relatively long to start up. It might be just that your client doesn't attempt to connect long enough. This time window for connecting has been increased on the beta branch. Could you give it a try? Make a backup of your galaxy and then update Avorion to beta branch and start it. It will automatically update.

I asked the dev if he plans on doing something like that and he said no. For one the ARM itself would definitely struggle with the server load and the second reason, a more corporate one: If we ship something (like a build for ARM) we need to be able to certify the stability of it. Which would mean testing that requires hardware and time. And with the current status we won't able to do that.

Hi there, we know of the issue with the incorrect distances on the crafted turrets. All turret types have that problem as you found out yourself. The crafting of the turrets will be revised and improved by the dev, it is however not clear when that will be (but of course before the final release).

I think you have the Xsotan in mind, right? They will always be neutral, and your autofire turrets will not target them until they actually fire and hit your ship.

That's good to hear :)

Was this on beta or stable? Because on beta it should be fixed as of patch 10.5 as stated in the patch notes here:

I already deleted it, but it was a different gpu anyway. I used lspci to find out what type of gpu it is and filled out the survey to "manually select" the driver on the above linked page. From there it gave me the option to download a .tar file which worked fine for me.

If you had loads of items in your inventory that could be causing this issue. The client then takes too long to connect and the server thinks the client died and closes the connection. There is currently no way to delete items from your inventory from outside the game.

I managed to reproduce that bug on our new AMD system, and fixed it by using the propriety driver from the AMD homepage http://support.amd.com/en-us/download. Can you try to update your driver and report back with the results?

There is no way to edit the inventory from outside the game, for one to make cheating harder and what's more important: Keep players from destroying their savegames :)

There are already some things planned that would fall into this category. Later on it will be possible to build docking blocks of higher level that would increase the distance needed to dock. Or for picking up loot there will be a special fighter class/drone class. So that the player doesn't have to fly to every bit anymore. Additionally the dev wants to have a favorite function for turrets and upgrades, that will make the quick transition a lot easier.

Thanks for reporting, I passed in on to the dev!

There is only what is in the FAQ, no real bug list. The issue is already fixed on the beta branch (see here for more detail: http://www.avorion.net/forum/index.php/topic,2349.0.html), so it will come to stable soon :)

This is a known issue. The timer is started as soon as the player enters that sector, and in other cases is there to clean up clutter from the sector. You are right, the timer has to be reset or made longer for big wreckages.

What you are suggesting is basically already in game. You can go to the strategy mode and select multiple of your ships and order them to escort you. If you then warp or fight they will do the same. Just as you stated are the limitations on that dependent on your weakest member regarding jump range and hyperspace recharge time.