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
No flamage needed. This stuff happens to the best of us. Glad you're good to go though...once the select button issue is resolved. All the best.
Puahahah this is rich
Let me give you some points, instead XD
My post wasn't even meant to be an outright accusation, I was simply stating that assuming that someone didn't make a VERY obvious thing was kind of an insult to their intelligence. You took it like an attack, lol
P.S. I've read the OP's update now. See? I was right, he just couldn't possibly not have sat at the grace XD
Smh
Kind of a late response though, no?
Also, as a point of order as well, this is why no one should assume anything when trying to offer solutions. The problem all along was a broken select button, and we never would have guessed that...assuming, as a base, that all other things were equal...one of which is a working controller. 🙄
You guys were fixated on the possibility of him just not sitting at the grace, even though the probability of it being the case we're incredibly close to zero.
You could instead start thinking about other possibilities beyond that. For example, I just assumed that the game could be bugged. I didn't think about the controller, but who knows, maybe one of you could have thought about it.
So yeah, usually ignoring the incredibly obvious things is fine.
It also depends on who's having the issue. If it were an old person, not at all tech-savvy, then considering them (the obvious things, I mean) would be fine. But the OP showed right away that he was able to try multiple potential solutions by himself.
We were fixated on it, because it wasn't explicitly mentioned up to that point that he rested at the grace. Even when it was mentioned, the OP only mentioned that it didn't work but without stating that he couldn't even pull up the map to actually verify if his resting at the grace actually solved the issue.
And that's the point; assumptions did him no justice. Not assuming anything doesn't insult the OP, and contrarily by design, it would have covered the necessary bases needed to troubleshoot. Plus, for you to assume it was a bug for him only and not anyone else, which is not probable in that mechanic, was clearly an over-assumption on your part that actually got in the way of finding a solution to the actual problem sooner.
I digress, but at the end of the day, I remain concluded that to assume is nothing more than a means to an end of making an ass out of you and me. Good news though: his problem has been determined, and the solution is now known.
I have enough experience with fromsoft games to have learned to expect anything XD
I've seen all kinds of one-time-only bugs due to probably memory leaks, in the DS3 forums.
P.S. the problem was not being able to open the map at all from the beginning btw. We were just assuming that there was some mob, somewhere, who was still in battle mode (due to a bug, could have been) that prevented the map from being opened. In fact I've actually had it happen to me that some mob would not stop being aggroed regardless of how far I went, even if I hid. I had to exit the game and load again. My assumption was that some mob was getting automatically aggroed from far away due to a bug, or something.
Teleport traps lock you out of quick travel until you rest at a site of grace.