-
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
Assassin's Creed II (33230) #190
Comments
Possibly related: ValveSoftware/steam-for-linux#212 |
ok waiting for this issue for ac2 |
The bug exists since 2012, Valve doesn't seem to care about this issue. |
ok for me, the game working if you make this before starting steam |
The bug still exists in version 4-11-4 of Proton and running the beta version of Steam Client of 15th of September. |
bumping thread, has anyone come up with a solution? I've tried @jomarocas solution but it doesn't seem to fix it for me. Running elementary os. Odd thing is AC Odyssey, another uplay game works for me, but AC 2 doesn't. |
Compatibility Report
System Information
SymptomsWithout using the "sed -i 's/legacykeyregistrylocation/legacykeyregistrylocation2/g' ~/.steam/steam/appcache/appinfo.vdf" command in terminal before launching Steam, you will get this error message. Failed to request product key from Steam, please try again in a few minutes. VANILLA: Using the "sed -i 's/legacykeyregistrylocation/legacykeyregistrylocation2/g' ~/.steam/steam/appcache/appinfo.vdf" command in terminal before launching Steam will spawn UPlay, which installs, you then create an account and/or log in. Then UPlay launches without recognizing Assassin's Creed II. TERMINAL COMMAND FIRST: After exiting UPlay and opening up Assassin's Creed II a second time, UPlay will ask you to link your Steam account. I personally don't feel comfortable doing this, so I chose not to do this. You are then greeted by a screen to enter your CD key. This would be where you would enter the CD key that should display when launching the game, but its bypassed when using that terminal command at launch. When starting up certain games on Steam, another window will open up showing your CD key. Assassin's Creed II seems to be the only game that has issues with this, and requires a command to be executed in terminal before launching Steam, which doesn't show the CD key screen at all, and just launches the game. TERMINAL COMMAND SECOND: |
@shoober420 Doesn't work for me. Same thing displays with or without the command |
@Gaming4LifeDE Do you have Steam set to run at startup? If so, make sure all Steam processes are killed, then execute the command in the terminal, and execute Steam from that same terminal. |
Distro: Linux Mint 19.3 Tricia Using the "sed -i 's/legacykeyregistrylocation/legacykeyregistrylocation2/g' ~/.steam/steam/appcache/appinfo.vdf" command in terminal before launching Steam was working till 15/03/2020 ( i had 84 hours of play ). After that the sed trick isn't working anymore. Steam was not running when i launched the script. |
Confirming "sed -i 's/legacykeyregistrylocation/legacykeyregistrylocation2/g' ~/.steam/steam/appcache/appinfo.vdf" no longer works for me as well. |
So sad, I tested this game on Proton today, I confirm, the workaround above doesn't work. Any other solution ? |
only with the command sed before launch steam, will work, i tested in version before to proton 5.0.6 i suppose that this version no break nothing, i pass the game with version 4 you will try with this version |
I confirm that I'm pushing the command before launching Steam, same error, not immediately (Steam seems to looking for the key) then it fails. My config: I pushed same report on ProtonDB. |
I've tried some more stuff, like changing the I've also tried adding the registry entries from a Windows install (including a valid key) to Sadly none of this had a positive effect. |
I think I found the cause of this Problem. When installing Assassin's Creed 2 (https://steamdb.info/app/33230/) on Windows, it will only install the Windows CD Key DLC (https://steamdb.info/app/33361/), but not the Mac CD Key DLC (https://steamdb.info/app/33362/). It isn't even shown as an available DLC on the Windows Steam client. In contrast, when installing the game on Linux, both CD Key DLCs are installed as well, but the Steam client can only fetch the Windows Key, but also wants to get the Mac key, as When launching the game on Windows, the Steam client will thus only try to get the Windows DLC Key, but the Linux client is trying to obtain the Windows and the Mac key on launch, which fails. On Linux requesting the Windows Key with So the problem here is that the steam Linux client wants to request all DLC keys when doing I've also posted this information on ValveSoftware/steam-for-linux#5649 (comment) and ValveSoftware/steam-for-linux#5649 (comment). |
Great info, @cverstege. It helped me find a workaround. By running SteamEdit through Wine and changing the Mac DLC to Hidden,it is possible to start the game. Make a link from I have not found any other way to change appinfo.vdf without Steam overwriting it on startup. |
@grktavlov thanks for the tips. The tool actuallay just adds I also needed to install the Crypt32 DLL via protontricks for Uplay to update (stuck at looking for patches loop). Sidenote: When launching the game steam will crash when trying to fetch the DLC keys to show in the steam overlay. AC2 will still run fine though. AS a workaround just disable the ingame overlay for AC2. |
More precisely it seems to edit after the last "entry"
to
I assume that the sequence
Where the Actually SteamEdit adds more entries as well, some of type Using this information I came up with an even less invasive edit: I simply changed this from
to
for the DLC. |
SteamEdit does quite a lot of things. The VDF is basically a dictionary of nested dictionaries with the top-level key being the AppId. The structure looks roughly as follows for the macOS DLC: {
"appinfo": {
"appid": 33362,
"common": { },
"extended": {
"developer": "...",
"dlcforappid": "...",
"...": "...",
"visibleonlywhensubscribed": 1
},
"steam_edit": {
"is_hidden": 1,
"base_name": "Assassin's Creed 2 - Mac",
"base_type": "DLC"
}
}
} Each scalar key has the format
With \x02 ( Dictionaries have So the above looks roughly like:
Actually, only the |
Thanks a lot for your tips guys; I was finally able to get Assassin's Creed II running! Updating the appinfo.vd file is not that simple because the entries have a checksum. If the checksum is not correct, Steam will simply wipe out the file and start a new one. I wasn't able to figure out how the checksum is calculated, but SteamEdit is able to generate them correctly. So I grabbed SteamEdit's output to generate a very minimal appinfo.vdf with a single entry ("Assassin's Creed 2 - Mac"). Simply replacing the existing appinfo.vdf with this one does the job - Steam will append new game entries but leave the existing "Assassin's Creed 2 - Mac" entry untouched. |
The issue might be fixed, I updated my client (I'm on beta channel) and deleted the prefix and deleted the appcache.vdf (to clear any previous fixes) and I managed to start, update and play assassins creed 2 deluxe and brotherhood! Can others try to check the issue is resolved for them!! |
@smintman confirmed 👍 |
Maybe worth mentioning that I could not start a new game when Ubisoft Connect launcher was in offline mode |
I forgot to reply but it does indeed work now. |
So, right now we have only this problems:
Maybe anyone find a way? |
For alt+tab, try using gamescope. For the LOD, see if you can change that in the game's config files. |
Gamescope sounds like ultimate solution to solve this kind of problems. It's still not working with NVIDIA, but it will soon. About LODs, game doesn't allow to change that via config file. |
Well, for Linux you can use https://github.com/scanmem/scanmem as a replacement for Cheat Engine. It's the same thing, a memory editor. You will need to find the appropriate addresses and make the needed changes. |
Yes, I tried scanmem via GameConqueror and I can't find any addresses with constant 256, 512, 1024 or 2048 values. |
I also noticed a problem with alt+tab and read on ProtonDB [RADA77435] about virtual desktop mode, I enabled it by: |
@begin-theadventure glad to hear. But, next time try to use protontricks, it allows you to select game in GUI: BTW, I completed my AC2 walkthrough like this. It's still awesome game. |
Unfortunately, it appears this game's controller support has been broken as of Proton 8.0. It worked correctly in Proton 7.x. Playing on the Steam Deck, external controllers also do not work, and keyboard emulation is not an option because of the camera. |
Hello @Sterophonick, please copy your system information from Steam ( |
Done. |
Caused by weird prefix creation after using |
@Sterophonick I'm looking into this, and unable to reproduce the failure you are seeing. First - did you use the "Delete Proton files" option? Several folks used this when upgrading to 8.0-1, and unfortunately there is a SteamOS bug that was causing controllers to break. We have worked around this temporarily with the 8.0-1d release which is now live. If this is the case, you should be able to repair the problem by using "Delete Proton files" again and then launching on 8.0-1d again. If this does not work and you did use "Delete Proton files", I think it is worthwhile for you to try manually deleting the prefix before doing any other investigation. These questions are for follow up in the event that I was wrong about my hunch regarding Delete Proton files. Please disregard if the instructions above fix your error (but it would be great if you let me know) :) I'm assuming that controllers do not work at all, even on the menus for you starting with 8.0-1? What kind of controller are you using? Also, could you go into the controller settings and check the name of the controller layout(s) for each controller (including the built-in steam controller)? Also, if you haven't already done this, could you switch the proton version back to 7.0-6 to make sure the controllers are still working for you there? |
Swapping back to 7.0 actually fixed it. Proton worked around the SteamOS bug with that commit, so Everything is all fine now. |
Hello @Sterophonick, unfortunately, that response is ambiguous. I could mean that you switched to Proton 7.0-6 and called it good enough, or regenerated the game's wineprefix with Proton 7.0-6 and switched back to Proton 8.0-1 and called it good enough. Please make it explicitly clear if you tested having Proton 8.0-1d regenerate the game's wineprefix and then checked the game's behavior so that we can drop the regression label. |
Yes, I have tested having Proton 8.0-1d regenerate the prefix. |
After the most recent Ubisoft update, it doesn't work via any Proton version. However, not even Proton Experimental works either. It just boots, stays trying to boot there for a bit and says it's in-game, and then closes. Here are the log files of opening Steam via console.
I don't know why the newlines don't show it correctly in actual visual output. I'm not well-versed in Github unfortunately. However, this is what is there. I hope it's helpful for something. Here's a Pastebin link for easier reading: https://pastebin.com/VHf1rAPH |
@L7vanmatre The breakage from the most recent Ubisoft update can be fixed by just adding "WINE_SIMULATE_WRITECOPY=1 %command%" to your launch options. Could you test an older Proton version that used to work before the most recent update (like 8.0-3) with this command to see if the game was broken by an experimental update? If you get the same failure, could you please get a log with PROTON_LOG=1 %command% on experimental? Also, please also copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report. |
Trying to play Assassins Creed 2 on Steam Issue transferred from #7507. Hi, I'm trying to play Assasins Creed II on my PC using Linux, but every time I launch the game, I receive this uplay window and I get stuck in it even when my credentials to ubisoft are correct. How can I play this Game? I enjoy this game in PS4 and would like to play it again on STEAM now. My System info: System Details ReportReport details
Hardware Information:
Software Information:
|
@DrThomasXLight I was experiencing the same issue and solved it by installing Ubisoft Connect inside the Assassins Creed 2 prefix. I used protontricks for this. |
Let me try that.. I'll post how it goes.. wish me luck 👍
…On Mon, Feb 19, 2024, 16:58 Gijs Vermeulen ***@***.***> wrote:
@DrThomasXLight <https://github.com/DrThomasXLight> I was experiencing
the same issue and solved it by installing Ubisoft Connect inside the
Assassins Creed 2 prefix. I used protontricks for this.
—
Reply to this email directly, view it on GitHub
<#190 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANOXVBLVSHQPX4UCQT5LJFLYUPDJVAVCNFSM4FRCL5IKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJVGMZDANBRGM3Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@gverm could you explain how to do it?
|
Dude, It worked for me, but depends of the protontricks version you use.
It need to allow you to install the latest Ubisoft connect exe, did it
yesterday inside the AC2 proton config (bottle). After it updates, you cab
run AC2 as it should, you connect with your Ubisoft credentials, it
updates game stuff and voila.. AC2 starts 🙌
That was my experience and I'm enjoying again one of my favorite games in
history.. thanks to @gverm for the tip.. nice tip indeed
…On Sat, Mar 2, 2024, 04:23 Solandis ***@***.***> wrote:
@gverm <https://github.com/gverm> could you explain how to do it?
I was experiencing the same issue and solved it by installing Ubisoft
Connect inside the Assassins Creed 2 prefix. I used protontricks for this.
—
Reply to this email directly, view it on GitHub
<#190 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANOXVBORF5AVVLCQ2IQGNLTYWGLBTAVCNFSM4FRCL5IKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJXGQ3TINBQGA4Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Starting the game shows a Steam dialog:
Failed to request product key from Steam, please try again in a few minutes.
The text was updated successfully, but these errors were encountered: