ValveSoftware / ValveSoftware/Proton
Viva piñata
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
Compatibility Report
- Name of the game with compatibility issues: viva piñata
- Steam AppID of the game: Non-steam game
System Information
- GPU: steamdeck
- Driver/LLVM version: steamdeck
- Kernel version: steamdeck
- Link to full system information report as Gist:steamdeck
- Proton version: 3.70
I confirm:
- that I haven't found an existing compatibility report for this game.
- that I have checked whether there are updates for my system available.
Symptoms
there's a native pc port of viva pinata and ive been trying to get this to run for hours. got the .dll file that strips away GFWL and everything. works fine on my windows 10 pc with it showing the launcher and you can launch the game fine but on steam OS beit steam's proton or ge proton, it just takes me to the launcher and the launcher is broken with it being a blank static image with no way to click "play". I'm assuming this is a proton problem and i should just wait?
Reproduction
go to old games download and download the game, install it on a windows machine, transfer it to steamdeck, get the gfwl removal patch here https://community.pcgamingwiki.com/files/file/576-bulletstorm-xlivedll/, paste it in game folder, add "startup.exe" as a non steam game, use any version of proton, click on "yes" and it'll take you to the static launcher with no words.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named. Start by reproducing the startup.exe launch on SteamOS with Proton 3.70 and collect the requested Proton log; the report would need a confirmed compatibility cause and a scoped fix or documented workaround before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100