It creates lot of files in my game partition that is mapped as D: drive in wineprefix with name rf????.tmp where ???? seems to be some hex number.
Im not sure when this started happening, might have been newest patch.
It creates lot of files in my game partition that is mapped as D: drive in wineprefix with name rf????.tmp where ???? seems to be some hex number.
Im not sure when this started happening, might have been newest patch.
The same issue was reported in #324 without a solution. I did yet not encounter it either, hence you might be best off to check the game file integrity and switch between Wine versions.
The same issue was reported in #324 without a solution. I did yet not encounter it either, hence you might be best off to check the game file integrity and switch between Wine versions.
That didn't help. But what did, i deleted that D: drive mapping, i think it might still be trying to create them on z: drive, but it will not have permissions to do that.
That didn't help. But what did, i deleted that D: drive mapping, i think it might still be trying to create them on z: drive, but it will not have permissions to do that.
For the record, this happens on my system(s) too, fully unpatched. I'm thinking this is one of the "side-effects" of the (theorized) Proton-allowing anticheat update (possibly).
Like, I haven't cleaned up for a while and now I have 4017 .tmp files:
cybik@chibe /Depot/Games/LinkedCompatData/4060946542/pfx/drive_c ls -l *.tmp|wc -l
4017
That, or there's some Windows code that expects to fail or just create a file in the ether, and then WINE/Proton has a different way of doing things entirely.
Though, as #324 actually points out, I am stubbornly using the game (and upstream launcher) through Steam. So it could be that this whole thing is technically Steam-related.
For the record, this happens on my system(s) too, fully unpatched. I'm thinking this is one of the "side-effects" of the (theorized) Proton-allowing anticheat update (possibly).
Like, I haven't cleaned up for a while and now I have 4017 `.tmp` files:
```
cybik@chibe /Depot/Games/LinkedCompatData/4060946542/pfx/drive_c ls -l *.tmp|wc -l
4017
```
That, or there's some Windows code that expects to fail or just create a file in the ether, and then WINE/Proton has a different way of doing things entirely.
Though, as #324 actually points out, I am stubbornly using the game (and upstream launcher) through Steam. So it *could* be that this whole thing is technically Steam-related.
This issue is happening bit differently than #324 and cybik for me, as i don't run it through steam, i am currently using https://gitlab.com/Ph42oN/qtlaunch to run it, but it also happened with lutris, and instead of C it was creating them on D.
This issue is happening bit differently than #324 and cybik for me, as i don't run it through steam, i am currently using https://gitlab.com/Ph42oN/qtlaunch to run it, but it also happened with lutris, and instead of C it was creating them on D.
I think it "simply" creates them in [workdir]/... Since through the upstream launcher on Steam, my workdir is the launcher directory, and that resolves to C:\Genshin in WINE, the TMP files get created in C:\, cluttering /Depot/Games/LinkedCompatData/4060946542/pfx/drive_c with noise.
I think it "simply" creates them in `[workdir]/..`. Since through the upstream launcher on Steam, my workdir is the launcher directory, and that resolves to `C:\Genshin` in WINE, the TMP files get created in `C:\`, cluttering `/Depot/Games/LinkedCompatData/4060946542/pfx/drive_c` with noise.
Now i went to test and confirm it tries to create them on Z, after running chmod o+w /, it will create those files on / that is mapped as Z. Maybe this is actually happening for much more people but as you wont have write permissions to root it can't create them.
Now i went to test and confirm it tries to create them on Z, after running chmod o+w /, it will create those files on / that is mapped as Z. Maybe this is actually happening for much more people but as you wont have write permissions to root it can't create them.
It creates lot of files in my game partition that is mapped as D: drive in wineprefix with name rf????.tmp where ???? seems to be some hex number.
Im not sure when this started happening, might have been newest patch.
The same issue was reported in #324 without a solution. I did yet not encounter it either, hence you might be best off to check the game file integrity and switch between Wine versions.
That didn't help. But what did, i deleted that D: drive mapping, i think it might still be trying to create them on z: drive, but it will not have permissions to do that.
For the record, this happens on my system(s) too, fully unpatched. I'm thinking this is one of the "side-effects" of the (theorized) Proton-allowing anticheat update (possibly).
Like, I haven't cleaned up for a while and now I have 4017
.tmpfiles:That, or there's some Windows code that expects to fail or just create a file in the ether, and then WINE/Proton has a different way of doing things entirely.
Though, as #324 actually points out, I am stubbornly using the game (and upstream launcher) through Steam. So it could be that this whole thing is technically Steam-related.
This issue is happening bit differently than #324 and cybik for me, as i don't run it through steam, i am currently using https://gitlab.com/Ph42oN/qtlaunch to run it, but it also happened with lutris, and instead of C it was creating them on D.
I think it "simply" creates them in
[workdir]/... Since through the upstream launcher on Steam, my workdir is the launcher directory, and that resolves toC:\Genshinin WINE, the TMP files get created inC:\, cluttering/Depot/Games/LinkedCompatData/4060946542/pfx/drive_cwith noise.Now i went to test and confirm it tries to create them on Z, after running chmod o+w /, it will create those files on / that is mapped as Z. Maybe this is actually happening for much more people but as you wont have write permissions to root it can't create them.
This issue is gone after 4.0 update.