Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It looks like all the elements of my base that were built before patch 3.0. are faulty and have some strange collision. I would like to add that these are construction elements from the DLC.
So basically the whole game state is corrupted and I have to give it up.
I can confirm that it is not related to anything built before 3.0, as we started this server fresh after 3.0 came out, however I think you might be onto something with it being DLC block related. This issue did start when we started turning our base into DLC buildings away from sandstone..
I wonder if logging off atop non-dlc floors might remedy this problem.
Transport stones also disappear.
And the biggest problem is that Fancom neglects these fatal bugs.
Certainly it may be caused by logging off on the DLC floor.
It would be helpful if the story is true.
Thank you for giving me this information.
How ... Well, how are we supposed to participate since probably all the dlc building components are broken ?
They still function normally. It's just a weird thing when you log back in ontop of them - you need to then log back out and back in to be able to move again. But aside from that, they work as normal and as expected. Just dont' log out standing on one of them. logging out on furniture (like carpets) ontop of them is fine though.
So in the past the game allowed you complete freedom when logging in, which allowed for some severe exploits, like for example walking into bases before their walls rendered and looting all the chests (since they rendered sooner).
What you're experiencing is more than likely this same system that immobilizes your character until everything around you is loaded.. except that with 3.0 and new stuff added.. things tend to load a lot slower at the start and this thing suddenly became way more noticeable.. especially if you don't have top-notch connection to the server.
I even get this locally for like 4-5 seconds if I start the game up on the server, but it goes away very fast there... on official servers... it lasts a lifetime sadly :D
Bottom line... there is really nothing you can do on your end except optimize your network.. but given that official servers are hosted on gportal it's very rare that the bottleneck would be on your end... so.. yea we're back to "you can't really do anything about it except beg Funcom to optimize"
Well, yeah? Ofcourse the server is going to try to load collisions before anything else, that's a given. Doesn't even have to specifically do with "exploiting", even if there was nothing to exploit, failing to load collisions before anything else would bring about a multitude of problems. Loading collisions is always the most important thing to load first.
I'm not sure why you'd say something like "it's a feature, not a bug". All bugs are components of features that are going awry, it's specifically that unintended behavior that makes a bug So yeah, bug, not feature.
There is something wrong with those DLC floors that is "hitching" or failing to finalize the collisions on those floors. The server end just fails to load them and gives up. It has nothing to do with ping or network as I can confirm that through our own server, which is hosted for 3 people spread out across the world, and it will impact people with far less ping than others, and -only- on those floors. Even a rug on the ground will stop it from happening.
At one point instead of logging out and back in, i just opted to dismantle everything around me, leaving a giant gaping hole in my structure, with the intent of just simply replacing it after it "let me go", but all it did was rapidly rubberband me in the air as I was "trying" to fall. I figured this would atleast correct the collision or update it, but no-go. The server was absolutely hitched on something and wouldn't finish it or let it go.
---
Also... just remembered.. another thing to note is that this may not even just be about collisions at all. an effected player can still take actions, and all their animations play on their screen, but someone else watching just sees that player standing still do nothing at all. If it was just about collisions, one would still see them "jumping" "rolling" and attacking, but it doesn't show anything for others. They are completely innert.
We can further say that it is infact the collisions that is triggering it, since this behavior does not occur anywhere else in the world, and only on DLC floors. This means that the server end is detecting that the player is touching that collision on loading, and is "immobalizing" while it attempts to make sure the collision is validly loaded before letting the player move, and fails to do finish that check.
I know what you were talking about. Doesn't change the idea that loading the collisions seems to be the issue here.
But the point was that there's not much the users can do about it, like uninstalling mods and reinstalling the game and stuff like that doesn't help.. what helps a bit is faster loading ofc and what would help is redesigning some of these loading checks and how the collisions get initialized.