-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SpellForce: Platinum Edition (39540) #686
Comments
Confirmed. Distro: Linux Mint 19 Tara |
Confirmed, works good. Distribution: openSUSE Tumbleweed Full specs: https://gist.github.com/buschmann23/f0040553d4bc4bdeb567778bd52f7946 |
Whitelist Request
System Information
I confirm:
Issues
|
My mouse pointer is blinking... Am I the only one? |
just checked with current proton beta and nvidia 410.66, does not happen to me. even tried vsync on/off and "avoid input lag" on/off - no issues. anything with "error" in your proton log? |
Nvidia 410.66 too, I'm on Arch. The only error I have in the log is this one:
|
Hello @NerosTie, that message is harmless. Did you add |
Hello @kisak-valve, yes this is how I've got the log. Every |
My issue is fixed, I don't have an issue with my cursor anymore =) |
It doesn't work anymore with Proton 5.0 (black screen then it crashes). Have to be launch with Proton 4.11. Tested with DXVK and WINED3D and in windowed mode. Log: My config: |
It's a bug in the game. When your system reports too many resolutions (multiplied by supported d3d9 formats) the games does something weird and corrupts the stack. DXVK reports more supported formats than wined3d so it's much easier to hit this bug. Wine 5.0 had suffered from another regression that was fixed in 5.14 with the patch introducing XRandR 1.4 support. It's cherry-picked to Proton 5.13 so if you force wined3d the game should work assuming the monitor is not 8k with too-many-supported-resolutions. Adding the following key to the registry in the game's prefix with Proton 5.13 should make it work for both wined3d and DXVK no matter what monitor you have connected.
|
Yes! It works! 🥳 So, DXVK can't do something about that? I have few other games in my list that might have the same issue.... |
I don't think DXVK can help much with games having bugs. They honestly list the supported formats and resolutions they get from DXVK would need to start limiting number of exposed formats / resolutions for certain games in config.cpp like they do with other kinds of workarounds - there are no knobs for that yet and we already do cap resolution list in proton ValveSoftware/wine@ac123a4 which works for both DXVK and wined3d. Entry for SpellForce will likely make it in the next dash release of Proton 5.13. Any reason you would like to have it in DXVK instead? |
I have no idea what is the best choice 🤷 @Joshua-Ashton should know better than me. |
SpellForce: Platinum Edition (39540) Issue transferred from #4873. Compatibility Report
System Information
I confirm:
SymptomsWhen right- or middle-clicking, the click does not release anymore. ReproductionPerform a right or middle click in the game (menu is fine) that lasts longer than a couple milliseconds. If you almost instantaneously release the mouse button, the click releases normally. NotesThis only happens with Proton Experimental, with other releases this issue does not exist. |
I experience the game crashing when trying to save it from the menu. I saw similar reports on Steam forums (link) and on ProtonDB (link 1, link 2), but no mention here, so I figured I'd report it. SymptomsAfter clicking Menu -> Save Game, the game crashes with a pop-up saying The issue also happens in Campaign Mode when clicking Esc (when "Are you sure you want to quit the game?" message is supposed to appear). It seems to be the same root cause, since the workaround below behaves exactly the same in both scenarios. ReproductionGo into Free Game Mode, start a single-player game, click Menu, then Save Game. WorkaroundLaunching the game with System Information
It doesn't look like Proton logs contain any useful information, but I'm attaching them just in case. |
Good news, the above issue was fixed in DXVK 1.10.2: |
Performance is very bad. When I slide a map I see a lot of jumps/stuttering. When battle is starting with 20+ units I also see a big performance drops. With PROTON_USE_WINED3D11=1 situation is little better, however 40 FPS with drops to 15 FPS is horrible bad result (1920x180 + max settings, vsync disabled -> switch to min settings doesn't help much). I have Ryzen 7 3800XT + Radeon RX 6600XT. |
Performance really seems to be a serious issue with this game. I'm playing on a 6950XT and a 5800X3D and get everything from 144 FPS to 10 FPS (in battles, but also when just moving the camera). Does anyone know what even causes this? Is this something that could be improved with reasonable effort? Is there anything I can contribute with no knowledge of low level programming that could help? |
With latest Proton 8.0-4 and Fedora 39/Wayland + Radeon RX 6600XT game doesn't even run. Just small black screen in the corner and nothing more. |
Just a little update, with Proton-GE 8.32 and |
Issue resurfaced using Wayland, black box opens then closes as described before using proton experimental, 9.0-4, 8.0-5, ge-proton9-21. Does work on proton 7.0-6 Wayland but with heavy lag and low performance and works on X11 on any previously mentioned proton versions without issues (low performance on 7.0-6). Also tested on 2 other systems with AMD and Nvidia cards all running Arch Linux with same results. |
The game launches with Gamescope under Wayland and GEProton9-22 and Proton 9.0 / Experimental. Also had to enable force-grab-cursor to get the cursor to not snap miles away when trying to scroll the screen holding right mouse. Game works smoothly otherwise |
I finished whole Shadow of the Phoenix extension few days ago without perf drops, stuttering etc. with Proton 9.0-4 and PROTON_USE_WINED3D11=1 parameter. Without PROTON_USE_WINED3D11=1 game didn't start. I have Radeon RX 6600 XT and Fedora Silverblue 41, so Gnome + Wayland + Steam via Flatpak. |
Steam - System Information
The text was updated successfully, but these errors were encountered: