Quoting: ShmerlClipboard is still broken in Wine Wayland.

this is dont only broken thing on wayland, have many things to solve

View this comment - View article - View full comments

Quoting: whizseAs for Wine development, I'm mostly looking forward to Wayland support being finished and made default, and the progress of winesync.

Quoting: iodAlso waiting for generally better Wayland support because old XWayland games set the fullscreen resolution incorrectly.

Wine devs seems hard working on wayland however needs more time

Other issue and on this stay very interested is how Mike Blumenkrantz and Joshua Ashton work can improve lacking things on wayland

https://www.supergoodcode.com/My-Wayland-Your-Wayland-Our-Wayland/

https://www.phoronix.com/news/Mesa-frog-fifo-v1-MR

Another thing is winesync aka NTSync but in kernel 6.12 dont stay maybe for kernel 6.13 or 6.14, in both cases this seems appear in someplace of 2025

Almost forget in my case since wine 9.17 (new wow64) trials in sky dont begin but now with 9.19 stay working again







cinematics work too, begin cinematic (this cinematic stay in avi)



i stay using remi bernon ffmpeg implementation



another thing i update ffmpeg from:

https://launchpad.net/~ubuntuhandbook1/+archive/ubuntu/ffmpeg7

and run newer titles like this without esync (esync dont seem stay in wine new wow64 aka ./configure --enable-archs=i386,x86_64)

View this comment - View article - View full comments

​This wine version add more work related remi bernon ffmpeg implementation, in my case tomb raider angel of darkness cinematics (mpeg format) stay work



sadly wmv+audio still dont work in my case

View this comment - View article - View full comments

Quoting: Avehicle7887

Quoting: mrdeathjrAt simple seek vram usage down around 200mb

I guess your mileage may vary depending on the game. For low end GPUs this can mean a night and day difference.

I have a separate system with a 2GB RX 560. Many games are playable (if you temper your expectations), however performance tanks hard once it reaches the 2GB VRAM usage mark.

Yeah in lower specs seems show more improvements

Back to test another progress of memory rework part 1 and 2 appear in CarX Street


2.4.1




Memory Rework




in this title vram usage down around 200mb with similar gpu usage but fps up around 5-6fps

​

View this comment - View article - View full comments

Testing lastest master (memory rework part 1 and 2 merged) show this:


2.4.1






Lastest Master






At simple seek vram usage down around 200mb

View this comment - View article - View full comments

Quoting: BlistoNote that the memory referred to in the reworks is mostly video memory.

and huge work seems very active today in

https://github.com/doitsujin/dxvk/commits/refs/heads/memory-rework-pt2/

Im very interested because doutsujin write this:

https://github.com/doitsujin/dxvk/pull/4293

QuoteSlightly higher memory usage again, but also 20% higher frame rate

View this comment - View article - View full comments

This dxvk version in my case run some newer games: memory usage and gpu usage remains similar

2.4






2.4.1






in other things can run other newer titles






sadly seems rewrite memory allocator dont be merged in this release like doitsujin write here:

QuoteFirst part of a massive rework. Not going to merge this until after 2.4.1, and this needs a lot of testing anyway, especially on Nvidia and in more memory-constrained scenarios.

https://github.com/doitsujin/dxvk/pull/4280

according dxvk actions: Rewrite memory allocator is merged after 2.4.1 like as doitsujin write



rewrite memory allocator appear 1 hour after dxvk 2.4.1 release in actions

View this comment - View article - View full comments

Quoting: LeprottoObviously this won't fix all MF issues by kind of magic. But the advantage of using FFMPEG as a backend is that it's native, so if something broke is your implementation.

Before remi bernon ffmpeg implementation stay merged

https://gitlab.winehq.org/wine/wine/-/merge_requests/6442

elizabeth figura seems dont agreed with ffmpeg for various reasons

however other alternative is good because can give better results in certain scenaries

gstreamer is native too however also have various issues according remi bernon

almost forget in my case this wine solve two annoying issues with dxvk (this games run with wined3d but dont with dxvk)

dungeon siege III always show a begin error (related d3d9compiler_47) and after this close but now works again



and magical battle festa this title have a config menu but this menu dont appear with dxvk (however with wined3d appear) and now appear with dxvk

View this comment - View article - View full comments

Quoting: KlaasDoes it work with gstreamer as well or is this something new?

I had hoped for some (more) examples of things that suddenly work, but nevertheless I think that ffmpeg will be a more reliable option going forward.

yeah but before week have much movement and when you use registry key showed in my first post, wine begin use ffmpeg

remi bernon have many activity in last week, i think compile wine 1 time each day in lastest 6 or 8 days but since around 3 days remi bernon add commits to begin use ffmpeg implementation

for this reason test various type of cinematics for see how work ffmpeg

and i think similar than you around maybe can solve some issues in actual wine gstreamer implementation

personally wmv+audio is very problematic in actual wine gstreamer, if ffmpeg implementation can solve wmv+audio issues will be a huge progress

View this comment - View article - View full comments

Quoting: ShmerlNew ffmpeg backend doesn't seem to help videos in Blood West yet.

Yeah and elderborn cinematics stay in same situation

View this comment - View article - View full comments