Alright, got another one for you guys. It's weird. I was doing some Dark Brotherhood questing and I went to talk to the quester to get a job. The interaction window pops up like it should, but the kicker is that instead of freezing the world and activating the cursor like it should, it instead just superimposes the window over the game and lets me continue doing whatever. I "fixed" it by opening my inventory screen and closing it again, and then I was able to get the quest as normal. Still, thought this was an interesting one to bring to you guys.
This was the other day though. I wasn't sure if I should report it so I'm sorry for waiting so long.
I believe this is the output log from that, not sure though. Can't remember if I fired up the game again after that session.
I'm going to try to see if it happens again tonight.
EDIT: It did. Here's my output log.
Build 0.5.477: This is a strange one... [RESOLVED]
-
- Posts: 64
- Joined: Tue Feb 06, 2018 6:06 am
- Interkarma
- Posts: 7247
- Joined: Sun Mar 22, 2015 1:51 am
Re: Build 0.5.477: This is a strange one...
Thanks for posting. This is related to a problem where talk interface is crashing for some reason. Problem can actually originate in quest system or somewhere else that plugs into talk system.
We've fixed several of these already, and no doubt fixes will be ongoing all the way to finish line. Reports like this (with log and repro save) go a long way to helping us fix quickly.
Will take a closer look when I can. Cheers!
We've fixed several of these already, and no doubt fixes will be ongoing all the way to finish line. Reports like this (with log and repro save) go a long way to helping us fix quickly.
Will take a closer look when I can. Cheers!
-
- Posts: 64
- Joined: Tue Feb 06, 2018 6:06 am
Re: Build 0.5.477: This is a strange one...
No problem. So far I've only gotten this with the Dark Brotherhood; Knights of the Dragon, Order of Arkay, and the Fighters Guild seem unaffected.
- Interkarma
- Posts: 7247
- Joined: Sun Mar 22, 2015 1:51 am
Re: Build 0.5.477: This is a strange one...
I believe this issue is resolved now.