protonscr

Fight'N Rage

appid 674520 1 threads, 1 open 8 comments last activity 2020-05-08
Threads

Fight'N Rage proton open

#1492 · 8 comments · opened 2018-09-16 · last comment 2020-05-08 by madewokherd
Recent activity
  • madewokherd · 2020-05-08 · Fight'N Rage
    [code] This is caused by a known Mono bug that's been fixed Wine Mono 5.0.0. It should be solved next time we get a Wine Mono update in Proton.
  • McMarius11 · 2020-05-06 · Fight'N Rage
    [steam-674520.log](https://github.com/ValveSoftware/Proton/files/4588020/steam-674520.log) with Proton 5.0-7 it sadly does not work
  • KibaGasteiz · 2019-06-28 · Fight'N Rage
    Tried the game and i got this error (i have a 94MB log so pasting the important thing): log snippet > GL Bind Frame Buffer...Done! > OpenTK Implementation Initialized! > Running GameWindow! > 1697.522:0026:0027:fixme:win...
  • lucifertdark · 2019-04-20 · Fight'N Rage
    [steam-674520.log](https://github.com/ValveSoftware/Proton/files/3100266/steam-674520.log) The game is now fully working with no tweaks or workarounds with Proton 4.2-3.
  • nded03 · 2019-04-05 · Fight'N Rage
    A Gold report appeared on ProtonDB a few weeks ago and I can confirm that the game does launch and is perfectly playable on Proton with the workaround described. Added my own report with more detailed [instructions on ho...
  • darcalus · 2019-01-03 · Fight'N Rage
    Game won't start. Proton 3.16-6 Beta. System Info : https://gist.github.com/darcalus/708da494996a4e84312cc955fbd5bf62 Proton Log : https://gist.github.com/darcalus/56a33bcea9c48f4f7018cc4c1ca558d6
  • seadra · 2018-11-03 · Fight'N Rage
    Still not working with 3.16-4, but fails with different errors: > 786856.234:000f:0015:err:winediag:CorIsLatestSvc If this function is called, it is likely the result of a broken .NET installation and > 786856.237:000f:0...
  • seadra · 2018-10-13 · Fight'N Rage
    Getting `err:mscoree:CLRRuntimeInfo_GetRuntimeHost Wine Mono is not installed` with 3.16-1, [here](https://gist.github.com/seadra/0c0c6c824f97cffe6d9f6dad1a485786)'s the new log file. Relevant issue appears to be #18.

Proton versions over time

Launch lines, newest first

No launch lines posted.

DLLs