WineHQ

Shantae and the Pirate's Curse

No Screenshot

Submit Screenshot
Steam version

Application Details:

Version: 1.03
License: Retail
URL: https://wayforward.com/games/s...
Votes: 0
Latest Rating: Garbage
Latest Wine Version Tested: 3.14-staging

Maintainers: About Maintainership

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

Nothing

What does not

Launching game

Workarounds

What was not tested

Gameplay

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

Clean Wine prefix, crashes on startup with Context.cpp : CreateDeferredContext() failed E_NOTIMPL:

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
ShowAptosid x86_64Aug 28 20183.14-stagingYes No NoGarbageJared Hutchinson 
ShowAntergos x86_64Apr 11 20183.5-stagingYes Yes YesSilverCharadon 
ShowManjaro LinuxMar 12 20183.3Yes Yes NoSilverMaxim Pavlov 
CurrentDebian GNU/Linux 9.x "Stretch" x86_64Mar 28 20161.9.6N/A No GarbageFurude Rika 

Known Bugs

Bug # Description Status Resolution Other apps affected
44760 Shantae and the Pirate's Curse - Sprites not rendering correctly. UNCONFIRMED View

Show all bugs

Comments

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Framerate issues
by burningserenity on Wednesday March 14th 2018, 12:45
I can't post these as test results because wine-staging is no longer listed.
The game still works on wine-staging, not on regular wine.

Libstrangle is required if you're using proprietary NVIDIA drivers without Bumblebee. Bumblebee seems to correct the framerate problem without libstrangle.

If anyone has an AMD system and this game, please post your findings.
RE: Framerate issues
by Charadon on Sunday March 18th 2018, 18:47
I use AMD, and it seems to be fine framerate wise. However I am having issues with sprities looking garbled. I don't know if that issue is related to amd systems however.
No longer need libstrangle, but having another issue
by burningserenity on Tuesday May 2nd 2017, 19:23
As of Wine-staging 2.6, libstrangle is no longer necessary to correct the framerate. However, I now have an unhandled exception when trying to launch the game.

My setup is that I have an SSD with Linux on it, an HDD with a BTRFS partition with a Wine Steam library on it, an NTFS partition with Steam games that don't currently work in Wine, and a third drive which Windows boots from. The only way I can get the game to start now is by having it installed on the Windows boot drive and only having that and my Linux boot drive mounted.
RE: No longer need libstrangle, but having another issue
by burningserenity on Thursday May 11th 2017, 15:16
On Wine-staging 2.7, I found that I have to launch the game in a virtual desktop in order to work around the crash on start. The framerate seems fine without any help from libstrangle or any other tweaks.

I should also mention that I distro hopped from Ubuntu MATE to Deepin, which is based on Debian Sid.
Works with Staging 2.3; Work Around for Frame Rate
by burningserenity on Tuesday March 14th 2017, 15:15
This game worked with limited success for me using staging versions 2.0 and up. Previously, CSMT messed up the graphics to the point to where I could barely see anything, but now it works without any problems.

One problem still remains, in that the frame rate is way too high. A lot of Windows users also complained about this, so I doubt it's unique to WINE.

I searched for two months, and libstrangle by torkel104 provides an excellent work around, which can be found here: github.com/torkel104/libstrangle

Once you install libstrangle, simply run: strangle /path/to/wine-staging /path/to/shantae_and_the_pirate's_curse

I use 60 for my frame rate, but different frame rates may work better for other users.
D3D11
by Furude Rika on Monday March 28th 2016, 18:10
D3D11 appears to be the issue. I've attempted to use several different versions of d3d11.dll, but none appear to work.
Back