| 22 Mar 2025 |
 olivia | no device lost? | 01:20:43 |
 Sean | it was device lost the other day, but I was overclocking and removing it fixed that. thought it was the same thing but idk | 01:21:55 |
| olivia | the EXCEPTIONACCESSVIOLATION is all wine stuff, not even necessarily graphics-related | 01:22:50 |
| olivia | the EXCEPTION_ACCESS_VIOLATION is all wine stuff, not even necessarily graphics-related | 01:22:57 |
| Sean | I think that's just another error | 01:23:04 |
| olivia | wait so is your observed behavior still this? ^ | 01:24:22 |
| Sean | https://p.seanbehan.ca/88dc1 | 01:26:27 |
| Sean | yes | 01:26:30 |
| Sean | this is a better log | 01:27:23 |
| olivia | so I believe the first number on those logs is a timestamp in seconds, so all of these messages would be within one millisecond. I'm not familiar with the wine seh stuff, but it's possible this is all part of a single unwind or something like that | 01:33:37 |
| olivia | this looks like probably a proton bug to me, in absence of other information | 01:33:51 |
| olivia | it never worked before for you, right? | 01:33:55 |
| Sean | no never worked | 01:34:08 |
| Sean | how do I turn off libunwind so I can see the logs properly? | 01:35:23 |
| olivia | wine has a bunch of debug flags | 01:35:43 |
| olivia | one sec | 01:35:44 |
| olivia | WINEDEBUG=-seh I think | 01:36:06 |
| olivia | (it's very possible that the seh messages are related to the actual root cause here) | 01:36:17 |
| olivia | but I think it's worth trying with them hidden to see if something else is visible | 01:36:30 |
| Sean | oh, okay | 01:36:30 |
| olivia | https://gitlab.winehq.org/wine/wine/-/wikis/Debug-Channels <- here's an (incomplete) list of the debug channels | 01:36:51 |
| olivia | I've never actually found a complete listing lol | 01:37:19 |
| olivia | you find out about ones that aren't on this list by reading the source code or https://source.winehq.org/WineAPI/ :( | 01:37:52 |
| Sean | https://p.seanbehan.ca/f9ba6 | 01:39:08 |
| Sean | this is what I was talking about | 01:39:14 |
| Sean | vram bloat expected hmm | 01:40:18 |
| Sean | does that just mean I need to run with lower settings? | 01:40:31 |
| Sean | I don't think so. I mean the vram target is way below my total vram | 01:44:20 |
| olivia | yeah, it's not something to be concerned about. It just means that your driver/card doesn't support sparse binding for whatever format the application is trying to use, which prevents dxvk from fragmenting the image's memory. This is just a 3840 x 1600 image, so nothing significant is being lost here | 01:47:35 |
| olivia | oh, this is vkd3d, not dxvk | 01:48:30 |
