If the hud shows then dxvk should be working fine.

If nothing else in the environment is specified then dxvk itself default sets the log level to info. Which should create a basic log file.
In proton it is set to none per default unless you have PROTON_LOG enabled
Lutris, if i understand the code correctly, defaults to not show debug information which also disables dxvk logging.
(I have never really used lutris so don't know when the above code comes in to play, but it is for the wine runner)

Maybe you messed with debug information in lutris or ran your game from outside lutris the time it showed up?

Hope this helps.

Good thoughts; appreciate the input, but I don't think so. I have changed nothing in Lutris from when the log was created (older versions of Wine) to now, when it's hit or miss (mostly miss) that a log gets created. Also, I always launch via Lutris.

But, you said DXVK should be working fine, so that takes care of my concern. I just thought not generating a log implies DXVK is not working right. I mean the docs say to verify DXVK is working by looking for the log. They also say to look for the HUD. So... whatever.

What was the content of the log?
Just the regular info lines?

The readme refers to how dxvk works with default environment. Like just standard wine.
If lutris sets up any variables away from default, as it looks like in the code above, then that doesn't fully apply anymore.
I would think it should never make a log when run through lutris unless debug information is on. But i haven't dived deeply into dxvk or lutris code.

Maybe a dev can provide more info.

I actually didn't open up the log the one time it created one. I haven't changed Lutris settings from when it did create a log, but Lutris did update since then. So, maybe code changes. I'll turn logging on and see if anything changes. I doubt it though. DXVK should operate mostly independent of Lutris. Lutris just launches it.

It's all good as long as DXVK works. The HUD works, so it's probably fine. I hope. I'm in trouble if I need to troubleshoot though.

I have tried launching a old dx9 game i installed in my wine prefix through lutris around 10 times and it did not create a log file. As i would expect.
I then in lutris went to the games configurations and under Runner options set Output debugging info to enabled and launched again. It now made a log. Also as i would expect. Is this not what you are observing? :thinking:

Was this issue solved? 👀

They wanted to make sure dxvk was functioning properly even tho it didn't generate logs, since the readme says you can check if app is using dxvk by bringing up the hud or looking for the logs.
The hud is working so i said it should be working correctly yes.

The rest of the issue was just a back and forth of why dxvk didn't make logs to begin with but on their 6th or 7th attempt did make one.
The lutris wine runner by default disables logging unless debugging info is enabled so i would say it is expected behavior for there to be no logs.
Why it at one point made one i don't know but i dont think theres anything wrong with dxvk from my dive into the code here and in lutris. Also did some testing.

Well, I've been away from the particular D3D9 game I posted about, but launched it today after seeing these posts (sorry for not responding earlier), and it created a log. It's been over a month and I don't remember if debugging was enabled or disabled in Lutris last time I tried. I tend to keep it enabled, but I don't remember. Maybe I was troubleshooting something and it was disabled (wouldn't think so because you want logging for troubleshooting). So, I don't know.

Roger.
If you run in to trouble again or have any questions don't be afraid to make a new issue 🙂

Will do. Thanks for your help, @Blisto91

@K0bin Can be closed.

Oops, my bad. Brain fart.