User talk:Silentgamepls

According to some PCGW guidelines, it is not wise to add compilation fixes (fixes that contain multiple pre-existing fixes for multiple issues combined, while not really replacing previous fixes) to pages. Additionally, if someone reverts your changes and you think you're right to revert the revert, please supply reasons in the comment of the contribution then and try to take feedback into account.... or better; discuss it on a talk page or Discord. Then we can both contribute to better PCGW pages :) Your fixes are totally not wrong, but in my opinion there are several reasons not to include them, see my revert comments.

Thanks no need.

Hey, could see from my notifications that at first your message here was quite different. Just wanted to let you know that you can feel free to discuss this matter further if you want? :) Because even though I think that your supplied fixes show some overlap with already pre-existing ones on the page, doesn't mean I'm right of course. So, feel free to disagree with me and discuss it if you want.

Edit: just looked at the history of this page; some of your points might be valid, wanna discuss it?

Sure,let's just add the fixes that you see fit,the Hitman 2:SA is the only one that works with GOG and Steam versions atm on both Windows 10 and Windows 11,it uses the same Wine Vulkan API Wrappers that the Manhunt Manual Fix for Windows 10 does.

Credit on all my github readme.md's in repos goes to the people that took part in different parts of time creating these fixes like AJ Collins with his closed gate patch fix for Manhunt,ermaccer for his audio fix and Thirteen AG with his WS fix,respectfully,as well as reshade for dual-GPU wrapper.

Also I have a lot of feedback from users that prefer to install the fixes for Manhunt manually and look at the code of what they are installing.

Hope it makes sense!

Ok, can you clearly explain the difference between each of your fixes compared to the pre-existing ones on this page? And in what ways do they literally contain the same files from fixes that are already on the page? (so, how much of it is actually a compilation of other fixes?) Please explain this separately for Manhunt and H2:SA in detail. Then we can look what could be possibly included and what not. Also, saw in your repositories that you mainly upload DLL-files. The code itself is thus not open source really right? So, in what regard do your fixes contain (DLL-)files from other fixes on the pages and on the internet?

I'm not a mod or staff here or anything, but just want to avoid giving people too many options to fix the same issues as that could easily confuse people with questions like "Well, applied fix 1 and 2, should I still apply fix 3 or does that overlap?" and "Do these fixes work together correctly? Are they compatible?"

And btw, agree with offering users the option to manually apply fixes (especially for Steam Deck for example), but in very bad cases of a game with many issues (like Manhunt and H2:SA maybe???), an automatic fixer might be preferred.... idk, we'll see :)

Yep the main difference is that I rely mostly on Wine Vulkan API wrappers as opposed to others,but I make exceptions in case of really really borked games like Manhunt since when I put up the fix there was/still is feedback on my YT channel regarding different HW configurations.

So in some cases I am getting creative and trying different combos/even versions of wrappers for example with Intel dual GPU laptops for Manhunt. Also when I hit a dead end while testing on Windows 11 with Vulkan API wrappers then I need to switch to ThirteenAG's fix so it is mostly GPL with some exceptions where the credits go to the original creators.

The Linux side,this is universal,currently none of the fixes,including ermacerrs work properly without doing a bunch of manual tinkering,there I would prefer to create automated scripts for deployment then test,the problem is with stuff like limiting FPS all Linux distros including Arch that the Steam Deck is based upon require libstrangle which might work might not work and requires more manual intervention from the users.

Regarding the Wine Vulkan API wrappers I use,they are open source,they are limited by using a dx.ini file,on Thirteen AG and reshade the FPS is limited in the DLL's by default. All of these fixes are under GPL,the main goal is to provide users with more or less universal option to play these very broken,but very good games from the PS2 era.

The problem with autofixers,they can work in one case,but not work in others,so I prefer doing more or less manually everything,depending on the HW/OS scenario at hand,also gives more control on viewing the code and what is being installed on the end-point.

Ok, thus your fixes work on Steam Deck then? Did you keep in mind that some fixes don't work on Steam Deck because of the need to set a WINEDLLOVERRIDES? But can't you use ThirteenAG's fix then on both Windows 10 AND Windows 11 to keep the fix more universal? You also explained your fixes and your fixes require putting the files manually in place, but still my major question remains: In which way does your fixes improve and overlap on the already existing Manhunt Fixer, more manual Manhunt Audio Fix, d3d8to9, Elisha's Windows 10 Patch, DX8 to DX9 enb convertor, frame rate limiter etc. for both Manhunt and H2:SA?

And if a pre-existing fix did not work, can you define if you tried it on Linux or Windows, because then we can probably find a solution and I'll help testing pre-existing fixes to verify if they work really or not.

The goal is to make these fixes work on Linux as well,so far I am hitting a wall with all wrappers during transition scenes in level 2 on Manhunt.

As for Hitman 2:SA I will check it against a Linux build it should work,also keep in mind the Wine DX Vulkan API wrapper on Hitman 2:SA does not require an FPS limiter,no issues have been reported so far.

The only game that requires an FPS limiter is Manhunt and also Max Payne,Linux fixes are universal,so if it runs on Arch Linux/Debian then it will run on the Steam Deck,which is Arch-based.

If you can help with testing that would be great!

So, your fixes fully overlap iwth pre-existing fixes then or what? Because you didn't really answer my question haha. Please do. Also: "Did you keep in mind that some fixes don't work on Steam Deck because of the need to set a WINEDLLOVERRIDES?"??? (While running through Proton/Wine of course) And I thought H2:SA required an FPS-limiter in some cases where the FPS get really really high and only then causes issues, like slowdown and other issues like described on the PCGW page, right? Btw, adding info for making the game run on Windows and Proton maybe is good, but good Windows fixes shouldn't be removed of course just because they aren't compatible with Proton haha. Only would replace them if the new fixes ALSO then work better than the original fixes on Windows.

Also, one of my issues; including pre-existing fixes can be problematic in the future if you would stop updating your fixes as it then would contain outdated pre-existing fixes. Hence for example on the Command & Conquer Generals page I pushed to keep the separate fixes and not make people to solely rely on a automatic fixer/collection of pre-existing fixes.

Even if I wanted to stop,I can't I get feedback from my Steam Community and YT sources constantly,so if something does not work,I have to retest,then deploy newer versions.

Well, if you just don't want to or want to put more time into other hobbies, you could of course just stop haha. Many people did that before, sadly letting good fixes go to waste.

Nah,I am an ex IT OPS Manager for Malwarebytes,mostly work from home for myself now and run my YT channel,so fixes I can handle as well as feedback and updating the github repo.

Have perhaps a url to your YouTube channel so I can take a look around?

Btw, Manhunt fixer's maker also put manual instruction on the Steam Guide the link from PCGW points to: https://steamcommunity.com/sharedfiles/filedetails/?id=2166039806 These should of course be included on the PCGW-page (can do that once we have a good conclusion in this discussion), but this is the "manual solution" we were looking for right... for Manhunt at least....

Here are both my fixes at Steam Community:

Manhunt (it was done before ermaccer came into play when the game was completely borked) https://steamcommunity.com/sharedfiles/filedetails/?id=1937021594

Hitman 2:SA

https://steamcommunity.com/sharedfiles/filedetails/?id=1977708024

Nice videos on that page haha. But can you still answer my questions from my other response 19 hours ago?: https://www.pcgamingwiki.com/w/index.php?title=Topic:X2xb51vse75tqjoo&topic_showPostId=x32lp9vr7xt2qvc5#flow-post-x32lp9vr7xt2qvc5 Additionally: this is gonna sound rude, but you being first with a fix says nothing about the quality of it haha. We're here to evaluate which fixes should be included on the PCGW pages or not based on quality, ease of use and ability to be able to apply each fix also manually. Also: don't really get why both games need separate fixes for Windows 10 and 11? So far almost all fixes work for both OS's as they are very similar tech-wise.

Edit: don't have the time to evaluate your fixes now, can maybe do that later today or later this week.

Ok sounds good.

Ok, I'm honestly done with this discussion: you just don't answer the questions I'm really asking that are actually important for evaluating your proposed fixes repeatedly. This way we can't evaluate in what way your fixes improve and overlap with pre-existing fixes. In this way we also can't incorporate your fixes in the articles. I for now see no use in incorporating your fixes for the following reasons: overlap with already existing fixes, separate fixes for Windows 10 and 11 while that shouldn't be needed usually and insufficient argumentation about in what way it improves over already existing fixes.

I'll add the separate manual fixes to the PCGW-page from the Manhunt fixes in case people wanna do it manually or on Steam Deck (where Manhunt Fixer doesn't seem to work) in the coming few days. I'll also add pieces that are included in Manhunt Fixer also separately as mods, so people can install those without using Manhunt Fixer. I'll also cleanup the H2:SA page more and test which fixes work and which don't (Same for Manhunt and maybe also for Manhunt 2 if I feel like it).

Sorry that this discussion ended this way, but just can't evaluate your fixes if you systematically don't answer/avoid some questions even though you seem to have good intentions.

Up to you,I have answered all the questions so far in my comments,I am currently too busy doing other things as well,Hitman 2:SA fix works across all devices and does not overlap with existing fixes,you have the links to these fixes in the Steam Community and github pages.

I am not just a fixer upper for old games,I have other obligations like running my YT SilentGamePLS gaming channel,fixes are just things that I have to do,when I see that the older games do not work with what is provided in pcgamingwiki or steam community,if the game does not work,I just try different combos/methods and add them to my github repos under GPL license and create YT videos for people to understand how to use them,that is it.

These fixes can overlap with older/other fixes when it is required. Regarding why ThirteenAG patch is required on Windows 11,because some Windows things,same happened on Windows 10 build 1903 once over two years ago,it must be a Vulkan API support issue,when Vulkan based wrappers are not very well supported,MS developers will have better answers to why scene transition breaks with a Vulkan API based wrapper on Windows 11 for Manhunt,but works fine on Windows 10 21H2 build than I do,eventually it will start working on Windows 11 as well,when it gets more polish or Windows 12.

It is up to you as the maintainer of pcgamingwiki to add the fixes that were proposed out of good will to save people some time making these older games work or not to add these fixes,I have other things to do than just waste time on pointless discussions,you have the links and the info for testing,that is it from my side.Other than that it is up to you.

Have a nice day.Cheers.

We seem to be in disagreement here. But ok, I'm not gonna incorporate your fixes atm. If someone properly arguments otherwise I'll be completely open for it of course. So, please leave this discussion open for further reference :) Have a nice day too!

"I'll add the separate manual fixes to the PCGW-page from the Manhunt fixes in case people wanna do it manually or on Steam Deck" This is done now, will add the optional mods/enhancements at a later time separately and make some minor improvements maybe along the way. Posted this just in case someone ever looks at this discussion and wants to know if it was done or not :)

Btw, this was done in close collaboration with Ermaccer (Maker of Manhunt Fixer) and testing by me. I was in contact with Ermaccer through Steam and Twitter for the last few days and he better explained his fixes to me, technical side etc. so I could better inform people about it on the PCGW-page. Trying to look at his fixes as objectively as possible, I would generally regard them as good quality. Except, I doubt the need of the d3d8 wrapper in many cases (60 fps lock works properly without it on my system, thus no reason to needing it. And it also seems to cause issues on Steam deck, see notes on PCGW page).