To supplement the comment I made on the bug tracker: I do have Creators Update installed (as I'm on the Slow Ring of Insider Preview builds).
And since I didn't mention it explicitly: Yes, I'm using the Vulkan backend (as it performs best of all the backends on my system).
I'm using Tomb Raider - Underworld (RH8P4F) for testing and it behaves like this:
- In its intro it plays 2 videos back to back.
- When I start with the overridden XFB settings (UseXFB = True and UseRealXFB = True) the videos play fine.
- When I switch XFB off or to virtual during the playback of the video, only the sound continues and the last displayed frame of the video will remain on the screen even when I switch XFB on/real again until the next video starts.
- When I switch XFB off or to virtual before starting the intro video, the screen will remain black for the duration of the video.
This is all expected behavior and shows that the game really needs XFB on real for its videos to work.
I'm going to try installing the 3D Vision components of the NVidia drivers after creating a restore point to see whether I can break XFB with that. (Remember the problems Minecraft players had in the beginning of the year with a particular driver version, but only when they had 3D Vision components installed?)
Update: Came up empty-handed. The game still displays ok, even with the 3D Vision components installed.
I wonder if something else is hooking into Dolphin and killing XFB Access/output...
Launching Dolphin from Steam's Big Picture mode with the Steam overlay activated didn't make any difference, either. Still working.
Also, NVidia ShadowPlay (or whatever it's called nowadays) is unlikely to be the culprit, as I'm using that here and it seems to work fine.
@Runo: As you suspect Creators Update having its fingers in the pie, maybe it's related to Game Mode, Game bar and Game DVR? I have most of this stuff deactivated here as I don't want it interfering. I believe at least Game Mode came with Creators Update.
I can confirm, on Tarzan Untamed and Donald Duck Goin Quackers, two games with intro videos that need Real XFB to play, having Real XFB enabled will play the videos for me (albeit seemingly with wrong colours?), and in every other situation the display will be black, on those game and any others. Naturally, if I play those games with Real XFB disabled, the intro videos will be black but the games will run normally, which is the expected output since those videos need Real XFB to be displayed.
That is what I finally discovered yesterday, and also why I thought earlier in this thread that my problem was fixed when it was really not. I now Immediatly open the Graphics Settings window when testing in order to prevent seemingly inconsistent behaviour, lol.
What is stranger to me is that now we have a behaviour that is seemingly an emulation issue, yet this is not reproduceable by most people. I will upload a short video later demonstrating this.
EDIT: Making my text clearer.
Also, yeah I also deactivate most invasive stuff, one thing I haven't tried is deactivating GameMode, will try later, jusg in case.
On my GTX 1060 Without creators update vulkan with real xfb works fine.
I was tending to believe it was related to the Creators Update, but since yesterday I think that's hardly the case.
I shall upload a video later today, then maybe we can think of something else.
EDIT: Maybe I can debug this somehow with a debug build? Dolphin's log shows nothing useful on this, even on the highest verbose level.
Finally, here it is!
Sorry for double posting, but I want you guys to see this. I've captured a video doing various tests, and showed all the weird behaviors I could notice.
I didn't edit it or anything, but it does its job, I reckon. The entire screen blinks every time I open or close Dolphin's output window, but that's some screw up on the recorder's end and didn't affect the tests.
Tell me if you find out anything or if I can do anymore to help, please!
https://youtu.be/9FVmfmt0F8I
Okay so I haven't even finished watching that video, I'm only about one minute in, but I have to say this: DO NOT open the graphics configuration windows while a game is running. If you want to change the settings, you have to stop the game you're running, go to the graphics config page, and then start the game again. If you open the graphics config page while a game is running, it overrides the gameini settings to whatever was currently checked when the page was opened. I don't know if this helps solve your issue or not, but you should never be doing this, it just fucks with everything.
It's OK to open the Graphics Settings as long as one is aware of the implications (which I assume Runo is). Besides, I don't think that's the issue here, as the original problem with XFB is not happening for me here even though I open the Gfx Settings while a game is running and fiddling around with it.
Also, the Graphics Settings being open and played around with in the video doesn't imply Runo does that all the time. It's just extremely inconvenient to restart the game 100 times for demonstrating different settings in a recording.
(05-25-2017, 06:31 PM)Kurausukun Wrote: [ -> ]Okay so I haven't even finished watching that video, I'm only about one minute in, but I have to say this: DO NOT open the graphics configuration windows while a game is running.
I actually opened it on purpose so I could show the effects of said settings on gameplay, so the viewer could be sure that any settings different from what he was seeing would have been overriden.
It would take longer to just keep editing the game INIs back and forth.
Quote:Also, the Graphics Settings being open and played around with in the video doesn't imply Runo does that all the time. It's just extremely inconvenient to restart the game 100 times for demonstrating different settings in a recording.
This ^
