Base rendering - performance issue / bug

[Multigun]

@Kaziklu

“the Chosen” saying that shouldn’t be believed and these issues might not be fixed.

@Kaziklu

Then we will give a time frame and when someone that isn’t the chosen gives the actual information provided by a Funcom Community Manager we will dispute that because we don’t want the community to actually think we will delivery what is said to be coming.

Huh, I don’t recall disputing Tascha’s timeframe. Be sure to include the evidence of where I said that in your follow up post.

Tascha wasn’t the only person to give this timeline by the way, Jens repeated this timeframe too. Since you feel that 2 weeks isn’t fast enough, the reason that it will take 2 additional weeks to get what’s on testlive now out onto live, is that Funcom is getting another testlive update ready that needs testing in order to help things “work right.”

@Kaziklu

Harvest bodies or low rocks, twigs, etc with the picaxe or the combo tool when I log in until I use the mirror.

Jens discussed this in the hotfix thread.

PC Hotfix (23.01.2019) - Crash fixes

I checked in with one of our coders and ran some tests in the game as well. The “aim-bug” that would cause the camera to bounce when locking onto an enemy as been fixed. The hatched issue that you’re referencing is still being worked on.

@Kaziklu

Right now every time I log in I have to wait up to a minute before for sound syncs and graphics fully load I have build my base in a way to I hope deal with Purge AI

As Funcom has discussed several times, they are working on various performance improvements.

Performance issues Feedback thread - Stuttering, lag

Hey everybody, We added a fix to the “death lag” issue in our latest hotfix following our community’s feedback. Could you confirm if this has fixed this problem for you? We are still working on additional improvements for performance, but this was the first step towards that objective. Thanks everybody for sharing your feedback with us

There is an improvement on testlive already to help with the load times.

Here’s a preview for what’s coming:

Before:

https://media.giphy.com/media/NS68fwWYgDzdyf2or7/giphy.gif(image larger than 29.8 MB)

After:

https://media.giphy.com/media/3d4Fh86PXXzrconJGn/giphy.gif(image larger than 29.8 MB)

In the article you referenced the timetable Tascha wrote, she stated, and I’ll cut out the relevant part:

@Tascha

CURRENT MAIN FOCUS

• More performance updates

@Kaziklu

Conan could be the best game I’ve ever played if they’d just fix the bugs that impact game play.

Like the Purge?

@Jens_Erik

• Fixed an issue where the Sixth wave of Frost Giant purges referenced itself as the next wave to start
• Knocking out an NPC from a purge will no longer halt the purge - instead, it is treated as if the NPC had been killed.
• Human NPCs spawned through the purge system no longer spawn naked
• Fixed an issue with the purge that would prevent it from spawning for certain building configurations. The purge should now happen more reliably.

I fail to see how any of these things, or the dozens and dozens of bug fixes on testlive now and more coming, don’t fit your criteria for bug fixing when they specifically are addressing, or working on, some of your biggest annoyances. And instead are, “new stuff” or “sexy stuff”, and make you feel that, “bug fixing is still secondary” with Funcom.

Returning to the topic now.

@fenix_svk

I cant agree with your answer because sometimes are buildings rendered normal, sometimes like this. Server 1116, clan The Patriots, base in Mounds of Dead next to the river… There is bigest base what i seen ever (30.000+ foundations and other structures), when its loading ofcourse i have huge fps drop but its loading normal, doesnt matter if server is full or empty. I mean, sometimes is rendering working good, later like this but definitely its broken and i hope it will be fixed because most time i am spending to solve bugs and other mistakes, not for playing

I think I may have misunderstood your original post fenix_svk. Is your problem similar to the problem reported here by this player? If you had a chance to play on testlive (and if not that’s okay), are you seeing similar problems there? I still believe that the performance update that’s coming out next after testlive goes live will fix the problem here, but it certainly doesn’t hurt to report this new issue.