Please, for the love of all that is holy, tell us this is at least KNOWN about by the devs. (Telling support doesn't accomplish anything.) I see us all talking about it here on the forums and in LFG in-game. I know it's not just a few people. It happened maybe once a month pre-5.6. With the release of 5.6, it happens every hour for me. There is no pattern. I can be in a big instance, like siege, or I can be standing still in the broker, halfway afk and playing on my phone. Without fail, the screen will freeze for 5 seconds and then the client will close out with that stupid send log error that we all loathe. To add insult to injury, we then have to wait 5-7 minutes to get back into the game because it starts the progress loading bar (which inevitably stalls at 64%); this wait time can kill a group, and we'll usually get kicked out of the group, thus ruining one of our instance entries. Is this being looked into at all?
@Londonrain-DN I'm the OP of this thread. Since it was posted a couple months ago, I've tried several things since then. Here is what I found to help IMMENSELY. It does not complete rid me of sendlogs, but now instead of sendlogging 1-2 times per day, I only sendlog 1-2 times per week.
I have put my graphics settings back where they were, and instead of lowering them, I've changed my graphics card's battery usage. My card (Nvidia GTX 1050) was auto-set to battery save mode in the Nvidia control panel. This prevents Aion from exceeding 30fps. I have turned it to max battery usage mode because I always have my laptop plugged in. Now Aion can go up to 100fps if it wants (although that only happens on FTS; standard server in Norsvold keeps me around 40-50 lol). I don't know why because I'm not a techy, but that has greatly diminished the amount of sendlogs I get. Give it a try!
Regarding how long it takes to get back online after a sendlog, there is a fix for that. See this video below and then here are my added comments to it, copy-pasted from a FB thread I commented on earlier today lol:
"To add, inside the config file, the number after "NormalStop=" should be 1. (It will be 0 if you have sendlogged.) So you will need to start and end your client so that you have a clean log, which will make it say NormalStop=1. If it says NormalStop=0, you'll still have the loading screen. So make sure it says 1 before you set it to readonly.
Also, this will not prevent the client from showing the loading bar on Wednesdays after maintenance. It will still show then. It only prevents it after improper closure of the client (sendlogs)."