I guess getting rid of Windows won't be so easy after all.
-
I explicitly had to go against literally all guides which tell you to disable DXVK and enable it. Now the Nvidia GPU shows up in the list. Next dilemma: Affinity under WINE doesn't save settings, and I have no idea what the XML file is supposed to look like, so I have no way to set it manually.
@volpeon I know you probably have Affinity running on Windows yourself, so this might not actually be helpful, but if you need I can give you my settings xml files and folder structure as I'm running Affinity on my Windows machine. ^^'
-
@volpeon@icy.wyvern.rip did you install the proprietary nvidia drivers? By default it will use Neuveu which are really slow.
Though, I heard newer nvidia GPUs have official open-source drivers, not sure what they're like.
Sorry if you know this already just thought I'd check
@Baa I installed the open source nvidia drivers. It's actually the only choice CachyOS leaves me with my GPU.
-
@volpeon I know you probably have Affinity running on Windows yourself, so this might not actually be helpful, but if you need I can give you my settings xml files and folder structure as I'm running Affinity on my Windows machine. ^^'
@SteffoSpieler If you mean Affinity V3, then that would be super helpful.
It would be a pain to revert the GPU changes, install Affinity in the VM and apply them all again
-
@SteffoSpieler If you mean Affinity V3, then that would be super helpful.
@volpeon oh, yeah of course I mean V3
Just tell me what you need (I don't think the whole .affinity folder is required?) and I can send it to you somehow :3
-
@volpeon oh, yeah of course I mean V3
Just tell me what you need (I don't think the whole .affinity folder is required?) and I can send it to you somehow :3
@SteffoSpieler It looks like the file should be at
C:\Users\<username>\AppData\Roaming\Affinity\Affinity\3.0\Settings\Application.xml
-
@SteffoSpieler It looks like the file should be at
C:\Users\<username>\AppData\Roaming\Affinity\Affinity\3.0\Settings\Application.xml@volpeon I don't have an affinity folder inside AppData, but I have the same file in this path: "C:\Users\<username>\.affinity\Affinity\3.0\Settings\Application.xml"
-
@volpeon I don't have an affinity folder inside AppData, but I have the same file in this path: "C:\Users\<username>\.affinity\Affinity\3.0\Settings\Application.xml"
@SteffoSpieler This must be it then
-
I explicitly had to go against literally all guides which tell you to disable DXVK and enable it. Now the Nvidia GPU shows up in the list. Next dilemma: Affinity under WINE doesn't save settings, and I have no idea what the XML file is supposed to look like, so I have no way to set it manually.
Uuuh, this outline doesn't match at all what's rendered? I know from experience that especially the right curve doesn't behave like it should
-
Uuuh, this outline doesn't match at all what's rendered? I know from experience that especially the right curve doesn't behave like it should
@volpeon Lol? I hope that's an issue with AffinityOnLinux and not Affinity itself
-
@volpeon Lol? I hope that's an issue with AffinityOnLinux and not Affinity itself
@SteffoSpieler Guess I won't get around trying it on Windows after all
-
Uuuh, this outline doesn't match at all what's rendered? I know from experience that especially the right curve doesn't behave like it should
It's a Wine issue. V2 has the exact same problem
-
@Baa I installed the open source nvidia drivers. It's actually the only choice CachyOS leaves me with my GPU.
@volpeon @Baa oh but, that does really affect how well the GPU operates ;;
like i get why because the open drivers are much less painful to work with in every way possible.
but they're an entirely reverse engineering based effort, Nvidia does not at all help these people, if anything they've been encrypting their firmware since the GTX 980 so it's exceedingly hard to actually make proper drivers for it.
i don't want to be 'that person' but please don't blame linux for nvidia's shitty actions.
-
@volpeon @Baa oh but, that does really affect how well the GPU operates ;;
like i get why because the open drivers are much less painful to work with in every way possible.
but they're an entirely reverse engineering based effort, Nvidia does not at all help these people, if anything they've been encrypting their firmware since the GTX 980 so it's exceedingly hard to actually make proper drivers for it.
i don't want to be 'that person' but please don't blame linux for nvidia's shitty actions.
@anthropy @Baa The driver is literally developed by Nvidia? github.com/NVIDIA/open-gpu-kernel-modules
-
It's a Wine issue. V2 has the exact same problem
@volpeon that's sad to hear. just out of curiosity, is this WINE or Proton? if not Proton, it might be worth trying it there, as Valve has added many tweaks for these kinda issues.
It's super easy: just 'Add a game' and select the binary of the program you want to run so it shows up in the Steam games list, then rightclick on it, -> properties -> Compatibility -> 'Force the use of a specific Steam Play compatibility tool' to activate Proton. It's just like with some native steam games basically
-
@anthropy @Baa The driver is literally developed by Nvidia? github.com/NVIDIA/open-gpu-kernel-modules
@volpeon@icy.wyvern.rip @anthropy@mastodon.derg.nz @Baa@mk.absturztau.be the open/closed only relates to the kernel part of the driver, userspace is proprietary. and you can use the legacy (aka closed) on cachyos (which still sometimes works better and the open ones only target rtx20/gtx16 and newer)
-
@volpeon@icy.wyvern.rip @anthropy@mastodon.derg.nz @Baa@mk.absturztau.be the open/closed only relates to the kernel part of the driver, userspace is proprietary. and you can use the legacy (aka closed) on cachyos (which still sometimes works better and the open ones only target rtx20/gtx16 and newer)
@volpeon@icy.wyvern.rip @Baa@mk.absturztau.be @anthropy@mastodon.derg.nz ok guess you’re on rtx50xx
-
@anthropy @Baa The driver is literally developed by Nvidia? github.com/NVIDIA/open-gpu-kernel-modules
-
-
@volpeon@icy.wyvern.rip @anthropy@mastodon.derg.nz @Baa@mk.absturztau.be the open/closed only relates to the kernel part of the driver, userspace is proprietary. and you can use the legacy (aka closed) on cachyos (which still sometimes works better and the open ones only target rtx20/gtx16 and newer)
@volpeon
Oh, my bad, I initially misread and thought you were using Nouveau...The Nvidia OpenSource driver is also problematic though indeed, the userspace is still proprietary, and idk how far it has come since I initially heard this announced, but back then it was still fairly unstable.
Then again I guess Nvidia in general has been less smooth on Linux than AMD in a lot of ways, but I do get why people buy the hardware, so I'm unsure what to advise there in that case.
-
@volpeon@icy.wyvern.rip @ada@ublog.kimapr.net @anthropy@mastodon.derg.nz a Pro model
Might be worth trying the driver from their website if Catchy aren't packaging the proprietary driver https://www.nvidia.com/en-us/drivers/details/257493/
No expert in this realm though, good luck
