When you die you get a freez screen for a few sec. Befor the fix. Now that freez screen is gone. Is a good think but unnecesay at this stage
Ok, thanks. People frequently use lag wrongly when describing these problems. Good to hear that this has been fixed.
1 Like
i agree with that.
We’re still waiting for a new testlive-patch to make further tests to. I mean, like said, they are differences in builds between testlive and the standart build, and still more patches are added to the regular one.
Testlive isn’t ready to go live yet, that’s sure, but testing for testing brings nothing, and we all have mostly limited time and a rl life to.
2 Likes
Hi everyone,
before this thread completely gets derailed by the discussion about TestLive I would like to comment on a few things:
First of all, thanks for participating in conversations. Please keep in mind that we would like this place to be a welcoming and fun environment to be in. We do not take jabs and name-calling towards Funcom, our employees or other players, lightly.
Secondly, here is a clarification on what our TestLive servers are and why they exist.
We are very interested in working with you, our community, to improve Conan Exiles. Our TestLive servers, among many other things, grant you access to not yet released content. It is our way to let you give us feedback on new content as well as report on bugs, issues and concerns you might have BEFORE it goes out to our Live Servers.
If you are not interested in providing this type of feedback, that is totally fine. We won’t force you to play on these servers. We do, however, really appreciate any help and feedback on both bugs and new additions.
If we tell you that something is fixed on TestLive, it means both that we were aware of the issue and that it is fixed and will be patched out as soon as that game version is deemed ready and stable to deploy to the game for everyone. There is really no reason to repost issues we’ve already confirmed as being on TestLive. 
We are not deliberately holding back moving TestLive to Live. We are trying to make sure that once we do patch the game, it will be as stable as possible.
Do we always hit that mark? NO. Are we trying our best? Absolutely
Some smaller fixes will get immediately to Live (hotfixes) while others might go to TestLive even though a lot of player are waiting on a specific fix. That is because some fixes have much more dependencies and are not easily patched directly to Live. We try in general to patch as little as possible to Live directly and want to have more time to do additional testing on TestLive.
9 Likes
Thank you Tascha for the post, everything you’ve said is how I believed it to be, I think most of us knew this all along.
I think that where people are confused is that you say the TestLive is for testing the latest builds/fixes yet we don’t see any regular patches or updates to the TestLive server for us to actually test.
On release of the latest TestLive, we spent hours working through the game and reported back what we found to be fixed and what we found to still have issues. If Testlive is the latest build, why are we not given regular patches to test the next stage of testing?
We all want to see this game become what it deserves to be, many of us are willing to dedicate time to finding the issues and reporting, but since Christmas, we’ve had nothing new to test.
That’s all we’re complaining about 
2 Likes
The main reason is that we had to focus on hotfixes for Live for issues that affected a really big part of the community.
Some fixes for TestLive also have dependencies coming from different programmers working on different aspects of the same mechanic. TestLive updates right now are also quite bigger and cover several fixes for a specific area (ie AI improvements, or Purge fixes) and we need to deploy all those fixes together. Otherwise the mechanic per se wouldn’t work as a whole. That means sometimes we have to wait for an additional fix/code line to be ready to be deployed in a bigger batch.
Additionally, thanks to your testing we did see that the building optimization needs more work and fixes, which we are also working on. All of this is still going through our internal QA as well.
I hope that makes sense.
7 Likes
We’ve released a quick additional fix to this patch, but since it’s just one change we’re not making a new thread. The fix is as follows:
- Fixed an issue where players couldn’t add attribute points to their character
6 Likes
@Jens_Erik When will you do your next Dev Stream? Will it be with the next pig patch currently on Testlive or independent of it?
Hey, after the patch came through earlier the server I play on keeps on crashing.
I sometimes have a weird issue after the last hotfix where I’ll attack once with a bow then be unable to do anything including: dodge, attack, sprint, etc until I equip a new weapon. It doesn’t happen consistently as far as I can tell but its a pain during a fight. I’ve had it happen twice in the last two days.
Hm, should I open a store for yellow vests?
We dont have such errors on our official.
@Palm522 Try to report it for a server reboot. Maybe you can fix it that way!
I won’t need a yellow vest Other than the other annoying issues like foundations and stuttering, we can play just fine on our server too. Saying this, I’ve not received any requests to reboot our private server from players having the foundation issue for the past 10 days.
From last post i know, you have to report server to g-portal because funcom cant do anything (or maybe dont wont :)). anyway, i never seen g-portal react to emails or any reports from players so you are just spending time for nothing dud
It seems I am super lucky.
Some people experience crashed every 10 minutes now. Well. At least one guy.
Edit: He could work it out. After both repairing via steam and windows update…
If you are able to disable your automatic update checker it will fix your server from restarting. Funcom messed something up in steamcmd where it thinks there is a new version of the game but there actually isn’t. So if you have automatic update checks turned on, your server will continue to restart itself to try to update every time there is an update check. Funcom for the win!
Strange, during Openaccess g-portal was to be contacted regarding server issues. After launch you should contact Funcom via this form. Anyway, i made a ticket at -gportal for a server reboot of #1930.
EDIT: Server was restarted
4 Likes
The problem is that a lot of hosts run scripts that check your server for updates from Funcom every so many minutes (typically every 10 to 15 mins). Funcom did something this morning so when your server checks steamcmd for new updates it’s showing a version number that isn’t what we are all running. So it will keep trying to get an update that doesn’t exist every time your server checks for a game update.
For private server you have to contact gportal.
For official servers you should use the reporting form.
1 Like
Spoke too soon. Had to give our server another reboot tonight. It already auto reboots every day at 3pm, by 9pm we have to do it again.
@ 
Tascha if this is the best what you can do is not enough in 2019 we had beather 10 years ago. Gaming industry is going down (you know the statistics you are a part of the problem) . AAA company’s are going down cause they adopted the same strategy. Do not be cokey.
You say you do not admit offense. Why shod we accept incompetence? Are we at a lower level then you? At the end of the day you get pay from our pocket so you shod stop fretting us. Maind place mate.! We can let you out of your pay check. Do not be disrespectful to the hand that feed you. Blowers and Bethesda did that and they pay the price. I really hope you will not be the next in line.
All this will bite you on a long term.
2 Likes