cepheni

huh, good catch there, guess we need to do something about that.

The AI sometimes stops following new orders, logging out and back in usually resolves that issue. We have not yet been able to track that issue down, but we know about it and will try to fix it.

mh, can you still post or link the full logs and include the server log? Does your friend's client crash, too?

Avorion was never intended to support big servers as the physic-calculations are pretty heavy. For now we suggest no more than 15 players per server. Performance improvements will come with the next update, we hope that Avorion servers will support more players then.

The error you are getting here could be related to mods. Do you have any active? Does the error persist without mods? The next update will change the saving of sectors and might help, too, if it is not mod related. @striker_lord: This error happens on line 716 in the sector-class not a specific sector, so deleting any sector will make no difference.

The issue you experience here could be because of mods. It would be really helpful if you could test that out for us. The way sectors are saved will change with the next update, so that might be able to help fix that problem, too.

Nice! And thanks for the xml :)

We are not sure what causes this error. Did you have that error already when you first played it? Or did it maybe only occur after a Windows update or something similar? Did you try to update your graphics driver?

nice post! :) And nice catch, we had a lot of people reporting the same issue but they didn't see that you have to press until loading screen, so this was really helpful, thanks!

@nivina: Quite a lot of what you are suggesting sounds really cool. We won't hard restrict movability of ships, because that is up to the player to build. After all, Avorion is a lot about enjoying to build exactly the ship you want. The size and damage (and range) is a good idea and we will keep it in mind for when Koonschi going to rework combat and turrets/fighters.

Koonschi says it's definitely planned :)

That looks like a file corruption, if you like you can send the entire galaxy folder to support@avorion.net and we will try to fix your game/find out which file causes the issue.

Can you please post the full logs? Just so that we can narrow done on which systems it occurs. The more information we have the easier the fixing will be. You can use pastebin or a similar service.

Is planned, no worries :)

Thanks, the dev is currently working on a way to make these error logs way more readable, I think we will have that error soon :)

ah ok, I understand. What do the new logs look like?

Sure, no problem :)

mh, dammit. Out of luck there I guess. But Koonschi is right now working on a way to better pinpoint what causes the errors. First tests have been successful :)

Can you please post one of your client logs and maybe even a server log via pastebin? That would help a lot in determining if it really is the xsotan causing this, or maybe just a symptom of something else.

There has been an update to the beta branch, that should fix most of the problems Intel cards made. Can you give it a try and report back wether it worked?

There has been an update to the beta branch yesterday, which should solve the majority of issues with Intel cards. Did it help your case? And if not can you please post a recent client log?

This bug should be fixed on the new beta branch and come soon to stable branch.

These errors are fixed on the new beta branch. If you haven't done already you can update to the beta branch or wait a few days until the update comes to the stable branch :)

Mh, this is a weird error, as usually it at least gets past that stage. So can you do me a favor and try to start the game on the beta branch as it recently got an update that should fix most Intel issues. If you still have the error can you post a new log?

Nah, no need, I have seen it :) but could you post a recent client log?