• 0 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle

  • NoXPhasma@lemmy.worldtoLinux@lemmy.mlvkd3d 1.13 Released
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    2 months ago

    The ultimate goal of the WIneHQ team is to have their own fully DX12 implementation. The reason why vkd3d-proton exists is that Valve didn’t want to wait for it to mature and AFAIK they did have differences in what should be included in vkd3d. Which is why they don’t work on the same project.









  • SFSE works fine for me, no issues at all. Make sure you download the latest version, to be compatible with the latest Starfield update.

    I’ve placed the dll and the exe next to the Starfield.exe in the game folder. And changed the Steam launch parameter to

    bash -c 'exec "${@/Starfield.exe/sfse_loader.exe}"' -- %command%





  • It’s not just random, it simply does not even work. Because they set this:

    +/*Preferred Core featue is supported*/
    +static bool prefcore = true;
    

    And later in the code they do the if condition wrong:

    +	if (prefcore)
    +		WRITE_ONCE(cpudata->highest_perf, AMD_PSTATE_PREFCORE_THRESHOLD);
    +	else
    +		WRITE_ONCE(cpudata->highest_perf, AMD_CPPC_HIGHEST_PERF(cap1));
    

    if should look like this:

    +	if (prefcore)
    +		WRITE_ONCE(cpudata->highest_perf, AMD_CPPC_HIGHEST_PERF(cap1));
    +	else
    +		WRITE_ONCE(cpudata->highest_perf, AMD_PSTATE_PREFCORE_THRESHOLD);
    

    There is probably even more wrong, looking at the code quality, but this at least makes the preferred core work.



  • Posting the required version to run the game is not trivial, as this is nothing we can just know, and it can also change with game updates. There is the Steam Deck verification information, which includes a Proton version, but this information is not reliable at all. Valve set Proton Experimental on all games that have not being tested, even on Linux native(!), so we can not take that.

    However, we are thinking of changes and collecting ideas at the moment and any constructive idea and critique is welcome. My personal idea about the working Proton versions to show is to simply have a graph, showing the available proton versions with a color code, depending on the reports and their rating. For example:

    And yes, people are reporting incorrect fixes, but this is the nature of user content. And it’s impossible to curate them all, it’s way too many. But you can always report a false/dangerous report on the discord or IRC (I wish we’ve had a report button on the page).


  • The rating is calculated by the report of the users, there is no manual rating done. GTAV works for most people, but some, so it ends up being Gold.

    However, these Medal ratings are carried over from the WineHQ rating, when ProtonDB was nothing more than a spreadsheet on Google Docs and was also used when Ratings were considered by the reporters itself. But this turned out to be a bad idea, as people tend to give platinum ratings, despite naming issues in their reports.

    So the attempt was to remove the manual rating and instead ask the users about their experience with several talking points and consider by that a rating. This would still use the old medal system, which of course does not work well for such system. That’s why a new tier system, which is more a representation between very good and very bad, was created, and you can see it on the dashboard (Change the Rating System to ProtonDB Click Play). However, this was considered as an internal test, but then the main developer was pulled away from ProtonDB for other work and all went basically to a hold.

    Now the developer is back at work on ProtonDB and this will hopefully lead to a new and better rating system.

    I hope this will shed some light on why it is what it is, and that no one is really happy about it.

    Source: I’m one of the administrators on the ProtonDB discord.