Arena crashing when asking about rumors in the wilderness.
Posted: Fri Sep 17, 2021 11:33 am
New bug found?
As per title, Arena crashes whenever you receive a rumor that would lead to a daedric artifact (have you heard that X is selling info about Y artifact at the Z inn?), if you get it from a npc out of the city walls.
It's the same as the "Who are you?" bug: the game just instantly crashes to desktop. Version is 1.07 from ArenaSetup.
I tried with every Dosbox version I could find. Be it with the official version, SVNs, and Dosbox-x. Both default settings and modified. It happens every single time.
I made the link with the "Who are you?" bug because in that bug the game checks for a list that can't find, so it crashes. So I thought that maybe this is a similar case, where the game checks for the location of the inn where the rumor is supposed to take you. But, being the npc outside of town, they can't find the list with the inn's name, and that makes the game crash.
I continued clicking on rumors for a while, and while the "regular" ones were fine, at some point, sometimes it would have been even the 1st rumor, it would always crash. So I returned to a city, and checked if I could find any rumors that would crash the game and, as I had imagined, I could get the artifact rumors just fine. No crashes.
It's important to note however that the bug, like it's presumed "Who are you?" relative, didn't occur on ver. 1.03, which I tried on an online browser. The people in wilderness would give indications as to which inn to go to begin the quest just fine.
I searched all around Google and in these forums for this bug and couldn't find anything. Could this bug have remained uncovered till now? Does this happen to you as well (CD ver 1.07)? Or do I have screwed my game somehow?
EDIT:
Ok I have determined when and how the crash happens. This is indipendently of the config used. Basically if you open the game, load a save in the wilderness, and ask for rumors until you should get one for an artifact, the game's gonna crash no matter what.
If you first load a save inside a city, or first you travel to a city and then return back to the same wilderness area where it would crash had you just opened the game and loaded a save in the wilderness, it won't crash anymore.
I've noticed the location where you're supposed to go change depending wether you load a save inside a city in the vicinity or you fast travel.
If you do the first, the the people are gonna direct you to an inn inside the biggest city in the area. If you do the second, then you'll be directed to the closest inns in the wilderness.
Remember that to replicate the crash one has to save a game in the wilderness, exit to desktop, and then load that save and ask about rumors.
EDIT2: This seems to happen in v. 1.03 as well. It gives a "Divide error C:>". Tested on a 1.03 version played on the browser.
I'm writing this down so anyone who has this bug and doesn't know if he messed up his install or something, if they stumble on this thread they may know that this bug happens to everyone (to other people on the Discord as well) and has to be considered the same way as the "Who are you?" bug in v. 1.07.
As per title, Arena crashes whenever you receive a rumor that would lead to a daedric artifact (have you heard that X is selling info about Y artifact at the Z inn?), if you get it from a npc out of the city walls.
It's the same as the "Who are you?" bug: the game just instantly crashes to desktop. Version is 1.07 from ArenaSetup.
I tried with every Dosbox version I could find. Be it with the official version, SVNs, and Dosbox-x. Both default settings and modified. It happens every single time.
I made the link with the "Who are you?" bug because in that bug the game checks for a list that can't find, so it crashes. So I thought that maybe this is a similar case, where the game checks for the location of the inn where the rumor is supposed to take you. But, being the npc outside of town, they can't find the list with the inn's name, and that makes the game crash.
I continued clicking on rumors for a while, and while the "regular" ones were fine, at some point, sometimes it would have been even the 1st rumor, it would always crash. So I returned to a city, and checked if I could find any rumors that would crash the game and, as I had imagined, I could get the artifact rumors just fine. No crashes.
It's important to note however that the bug, like it's presumed "Who are you?" relative, didn't occur on ver. 1.03, which I tried on an online browser. The people in wilderness would give indications as to which inn to go to begin the quest just fine.
I searched all around Google and in these forums for this bug and couldn't find anything. Could this bug have remained uncovered till now? Does this happen to you as well (CD ver 1.07)? Or do I have screwed my game somehow?
EDIT:
Ok I have determined when and how the crash happens. This is indipendently of the config used. Basically if you open the game, load a save in the wilderness, and ask for rumors until you should get one for an artifact, the game's gonna crash no matter what.
If you first load a save inside a city, or first you travel to a city and then return back to the same wilderness area where it would crash had you just opened the game and loaded a save in the wilderness, it won't crash anymore.
I've noticed the location where you're supposed to go change depending wether you load a save inside a city in the vicinity or you fast travel.
If you do the first, the the people are gonna direct you to an inn inside the biggest city in the area. If you do the second, then you'll be directed to the closest inns in the wilderness.
Remember that to replicate the crash one has to save a game in the wilderness, exit to desktop, and then load that save and ask about rumors.
EDIT2: This seems to happen in v. 1.03 as well. It gives a "Divide error C:>". Tested on a 1.03 version played on the browser.
I'm writing this down so anyone who has this bug and doesn't know if he messed up his install or something, if they stumble on this thread they may know that this bug happens to everyone (to other people on the Discord as well) and has to be considered the same way as the "Who are you?" bug in v. 1.07.