Proton
Proton copied to clipboard
Spyro Reignited Trilogy (996580)
Compatibility Report
- Name of the game with compatibility issues: Spyro Reignited Trilogy
- Steam AppID of the game: 996580
System Information
- GPU: RX 580, GTX 770
- Driver/LLVM version: Mesa ACO Git (via GloriousEggroll copr), NVIDIA 430.26
- Kernel version: 5.2.8-201.fc30.x86_64, with fsync patches (via GloriousEggroll copr)
- Link to full system information report as Gist
- Proton version: 4.11-3
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
This log is from a GTX770 box...
Symptoms
Prerendered cutscenes do not run, as they appear to use a codec that's not yet supported. The game thankfully skips them, so the game should not crash or render anything incorrectly.
Reproduction
- Boot the game
- Endure the shader compile times...
- Start Spyro 1
- Note a single frame between two separate loading times during the intro
- Game otherwise runs!
The game skips all pre-rendered cutscenes. (Edit as it happens regardless of if you're using DXVK or not)
Game works entirely as expected, at least at a first glance...
@flibitijibibo Why open the report? Is the xaudio2 label to track games using xaudio2 rather than games with xaudio2 issues?
The game skips all pre-rendered cutscenes when run with DXVK.
It skips them no matter what. Even if you run it via PROTON_USE_WINED3D=1.
That might be related to #1464.
Confirming the same bug happening to me.
Possibly valuable info: the game uses H264 - MPEG-4 AVC (part 10) (avc1) video with fourteen 48000Hz MPEG AAC Audio (mp4a) channels - one of them is 32 bps, the rest 16 bps.
Updated the OP with an example of a missing pre-render. Somehow I missed this in my initial test. Aside from the pre-renders, everything else appears to work, including 5.1 support when setting SDL_AUDIO_CHANNELS=6.
How are other pre-renders handled?
From different games, well they use different file formats. Hitman 2 and 2016 use WebM if I recall.
Is shipping ffmpeg the solution here?
On Mon, Sep 9, 2019, 10:46 AM dribbleondo [email protected] wrote:
From different games, well they use different file formats. Hitman 2 and 2016 use WebM if I recall.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/3035?email_source=notifications&email_token=AAON37C3Y3TNHOXHYRFLUO3QIZOSVA5CNFSM4ITJCL2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6H3B3I#issuecomment-529510637, or mute the thread https://github.com/notifications/unsubscribe-auth/AAON37G2FI4HIT7HNHTCNIDQIZOSVANCNFSM4ITJCL2A .
Perhaps.
Ok, so I came across a guide on getting the cutscenes to work, compiled by Na Moogle on a spyro modding discord I'm a part of. Here's a pastebin of the instructions
@dribbleondo You forgot to include mfplay.dll
in your copy and override lists (at least it is required for me :/).
Hello @Waistless, your comment was removed because we can not condone the distribution of copyrighted libraries.
Ok, so I came across a guide on getting the cutscenes to work, compiled by Na Moogle on a spyro modding discord I'm a part of. Here's a pastebin of the instructions
You should attach that as a file here or use a gist. Pastebins delete content after a certain period of time.
It might be a good idea to submit this information to winetricks:
https://github.com/Winetricks/winetricks
If Dan can find a way to get the files from official downloads, then it would become possible to use winetricks via protontricks to do this workaround without much hassle.
I'll submit the workaround to winetricks.
@ryao @dribbleondo Unfortunately, winetricks can't do anything, because of the legal issues (https://github.com/Winetricks/winetricks/issues/1132) we need to find a public source from Microsoft for these dlls.
Literally just about to link that. Yeah, it is a bit of an unfortunate situation it seems.
Would this be of any help? From what i've read, it's used for installing media-related applications (including wmf seemingly) on Windows 10N systems.
Nope, it's a MSU file. I contains files compressed with Microsoft's "Intra-Package Delta" technology, which is yet to be reverse-engineered (as far as I know).
I posted it in the linked issue, but I will say it here too. The necessary files likely could be extracted from a Windows 10 development VM:
https://developer.microsoft.com/en-us/windows/downloads/virtual-machines
You can just extract it from Windows 7 or Windows 10 install disk directly, no need for virtual machines. Also, we need Win7 dlls (https://github.com/Winetricks/winetricks/issues/1132#issuecomment-438015780).
You can just extract it from Windows 7 or Windows 10 install disk directly, no need for virtual machines. Also, we need Win7 dlls (Winetricks/winetricks#1132 (comment)).
Have you confirmed that the relevant DLLs can be found on the ISOs? I ask because I recall there being issues finding certain DLLs that are part of a Windows installation on the ISOs in the past. In particular, efforts to find certain cryptographic libraries failed during the recent WoW classic issues. Those issues were later found to be TTL timeout related. They could not be found both as plain files and in various cab archives. Microsoft might be putting some DLLs on their ISOs in an odd way.
Also, does Microsoft provide a Windows 7 install disk ISO that people can download from a script?
DLLs can we extracted from ISO's wim
file using wimlib
. Sadly there's no way to acquire Windows 7 ISO without providing Microsoft with a valid Win7 key :disappointed:
Has anyone managed to make this game work on an Optimus laptop? Xorg consistently segfaults on my machine when game starts.
[ 208.145] (EE) Backtrace:
[ 208.145] (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x4d) [0x562a15c1469d]
[ 208.145] (EE) 1: /usr/lib/Xorg (0x562a15b62000+0xa8be8) [0x562a15c0abe8]
[ 208.145] (EE) 2: /usr/lib/libc.so.6 (0x7f703e892000+0x3a7e0) [0x7f703e8cc7e0]
[ 208.145] (EE) 3: /usr/lib/Xorg (0x562a15b62000+0x4b9bb) [0x562a15bad9bb]
[ 208.145] (EE) 4: /usr/lib/Xorg (miPointerUpdateSprite+0x1c6) [0x562a15cf4be6]
[ 208.145] (EE) 5: /usr/lib/Xorg (0x562a15b62000+0x196c10) [0x562a15cf8c10]
[ 208.145] (EE) 6: /usr/lib/Xorg (0x562a15b62000+0xf264b) [0x562a15c5464b]
[ 208.145] (EE) 7: /usr/lib/Xorg (0x562a15b62000+0x12695b) [0x562a15c8895b]
[ 208.145] (EE) 8: /usr/lib/Xorg (0x562a15b62000+0xb3a10) [0x562a15c15a10]
[ 208.145] (EE) 9: /usr/lib/Xorg (0x562a15b62000+0xb3ab8) [0x562a15c15ab8]
[ 208.145] (EE) 10: /usr/lib/Xorg (WaitForSomething+0x277) [0x562a15c168a7]
[ 208.145] (EE) 11: /usr/lib/Xorg (0x562a15b62000+0x37966) [0x562a15b99966]
[ 208.145] (EE) 12: /usr/lib/libc.so.6 (__libc_start_main+0xf3) [0x7f703e8b8ee3]
[ 208.146] (EE) 13: /usr/lib/Xorg (_start+0x2e) [0x562a15b9a3be]
[ 208.146] (EE)
[ 208.146] (EE) Segmentation fault at address 0x0
[ 208.146] (EE)
Fatal server error:
[ 208.146] (EE) Caught signal 11 (Segmentation fault). Server aborting
@gilbsgilbs I'm playing on an Optimus laptop without issues. But I don't use bumblebee, primusrun, nor the new offloading feature - the iGPU only works for screen output, so that may be the case.
This DLL extraction linked above works for me. Beautiful.
On Sun, Sep 15, 2019, 7:55 PM Kacper Herchel [email protected] wrote:
@gilbsgilbs https://github.com/gilbsgilbs I'm playing on an Optimus laptop without issues. But I don't use bumblebee, primusrun, nor the new offloading feature - the iGPU only works for screen output, so that may be the case.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/3035?email_source=notifications&email_token=AAON37DPVEZBS77V66E4GNLQJ3DQBA5CNFSM4ITJCL2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6X3W6Q#issuecomment-531610490, or mute the thread https://github.com/notifications/unsubscribe-auth/AAON37G5DBVZ6TERG3PZPCTQJ3DQBANCNFSM4ITJCL2A .
DLLs can we extracted from ISO's
wim
file usingwimlib
. Sadly there's no way to acquire Windows 7 ISO without providing Microsoft with a valid Win7 key 😞
Well, if the issue is that RtwqUnlockWorkQueue
and related functions need to be implemented to use the Windows 10 versions, then that is doable. Those are publicly documented API functions. I am familiar with the concept of a work queue from both Linux kernel work queues and OpenSolaris kernel task queues. If I knew which functions were required by Windows 10’s mfplat, I imagine that I could give implementing them a try in time for wine 4.18 (probably not 4.17).
Would someone produce a list of the unimplemented functions that the Windows 10 mfplat requires so that I do not need to inspect Microsoft’s binaries? You could probably use dependency walker to get a list of the functions needed:
http://www.dependencywalker.com/
I am new to contributing to wine. If I implement this and send the patch, I imagine that I would need to have a good answer to questions about whether clean room requirements were violated. Not having a good answer would likely prevent the code from being merged, which would make the effort a waste of time. It would be helpful to separate the work of finding out what is needed from implementing it to ensure that we do not end up with a patch that cannot be merged.
Also, be sure to make sure that the functions used are publicly documented before posting them here. For example:
https://docs.microsoft.com/en-us/windows/win32/api/rtworkq/nf-rtworkq-rtwqunlockworkqueue
If there are undocumented symbols required, then we would want to ask one of the main wine developers for advice on how to proceed. We would need to ask to be sure, but I should mention that there is a possibility that the person inspecting the binaries to allow for a clean room implementation of these functions so that we can have a workaround added to winetricks might never be allowed to contribute code to this area of wine due to wine’s clean room requirements. Hopefully, someone who doesn’t plan to ever learn C could volunteer to look. I am not comfortable volunteering to implement the entire RTWorkQ.dll API for this at this time, so I would need to know the subset used if I am going to try.
[996580] Spyro Reignited Trilogy - Problem with pad and keyboard on Spyro 2
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3216. @emmecii posted on 2019-11-12T22:52:56:
Compatibility Report
- Name of the game with compatibility issues: Spyro Reignited Trilogy, in particular Spyro 2
- Steam AppID of the game: 996580
System Information
- GPU: AMD RX560
- Driver/LLVM version: Mesa 19.1.2 - padoka PPA
- Kernel version: 5.0.0-32-generic
- Link to full system information report as Gist: https://gist.github.com/emmecii/167d67b4f801ccf992ee93e88e1208f9
- Proton version: 4.11-8
I confirm:
- [X] that I haven't found an existing compatibility report for this game. A compatibility report for this game already exist, but this new issue is particular and unrelated to Media Foundation issue
- [X] that I have checked whether there are updates for my system available.
Symptoms
Gamepad on Spyro 2 doesn't properly recognize the Y button on X360 pad contextually to the hovering action or sight-to-shoot action. The same function seems to be "transferred" pressing the right analog stick (but not for the hovering). Also the keyboard is affected, where spacebar and left mouse button doesn't work at all even if reassigned into the game tl;dr https://www.youtube.com/watch?v=IHerojeRuaM that part can't be done for the Y button bug
I noticed this issue appear only when i load a new world level. At startup, there isn't any issue. Seems also I am the only that have this issue, so this is why i am opening a new issue on this game because is unrelated to a previous issue posting for Spyro
At the moment i haven't found a level where hovering is necessary, but can be problematic
Reproduction
Load a world level passing through a portal, then try to hovering after gliding with Y, or sight in first person perspective or when you aim to an enemy with Y / try to use flame with left button mouse or jump with spacebar
Thanks @kisak-valve to put the reference to my report, it's my first time reporting issues for Proton and i wasn't sure if a new report was needed or continue the already existent