-
Notifications
You must be signed in to change notification settings - Fork 24
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
steam no longer opening after applying cxpatcher to a cs2 bottle #230
Comments
did you enable dxmt when patching? |
this is strange it works just fine for me, does it run and then quit or does it show an error window? |
Steam icon shows up in the dock then closes after a few seconds, no errors. |
did you give up immediately? or did you try again after the steam quits? Have you tried wait some seconds after steam quits to see if it re-launches? |
I have tried waiting, restarting app, deleting and repatching, nothing worked. I am using fresh bottle, so far so good. What options would you recommend for cs2? I am running default patcher settings
…---- On Thu, 06 Feb 2025 14:17:48 +0100 ***@***.*** wrote ----
did you give up immediately? or did you try again after the steam quits? Have you tried wait some seconds after steam quits to see if it re-launches?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
first thing make sure you are using a separate bottle for patched and unpatched which is causing 90% of the issues. |
I think there's a bigger issue then and it's probably not cxpatcher. |
I need more information about your setup and the steps to replicate and possibly the cxlog when steam doesn't start. |
let me know what I can do to help, however at the moment unpatched works and patched does not, so idk how I can get you logs. |
enable "use separate bottle path", that's causing your issue on steam, you need to use a separate bottle path with patched crossover. |
that option was selected when patching |
it's disabled here #230 (comment) |
since opening this issue I have done the following: deleted the patched crossover 2, patched it again with default settings, successfully played cs2 with many lag spikes (fresh install inside of the new bottle) with ESync. Turned off the computer for the day, and then it stopped opening here: #230 (comment) |
The issue is titled "steam no longer opening after applying cxpatcher to a cs2 bottle" So for completeness sake, let's address the main issue: Your issues with steam are caused by not creating a separate bottle, which is recommended. (see: https://github.com/italomandara/CXPatcher?tab=readme-ov-file#new-bottle-path) then for the other issue:
|
should I want dxmt? will it make cs2 run better? |
Some users report dxmt works better but has shader compilation stutter at the beginning (dxmt doesn't have shader cache yet) |
DXMT is very complicated to manage tho at the moment (new users can have issues) and I'm discouraging new users to use it, the new upcoming crossover will handle dxmt better so it's worth waiting |
Macprotips has a tutorial for it https://www.youtube.com/watch?v=S98DF0MZxcg&t=215s (the tutorial is outdated but still good, now cxpatcher lets you set the framerate cap and metalfx for dxmt), or read here: https://github.com/italomandara/CXPatcher/releases/tag/v0.5.81 |
I enabled shared bottle because I did not want to reinstall steam + cs2 and steam no longer runs on the patched crossovers, the original works. I use D3DMetal + Msync.
The text was updated successfully, but these errors were encountered: