Originally posted by duby229
View Post
Originally posted by Cybmax
View Post
Please note you don't have to have faster frame rate than windows. Frame rates being in what is classed as competitive for a lot of games over 60FPS is classed as competitive and once in that class the game developers anti-cheat will be looking for code path errors and will instant ban or disconnect(valve) on them.
Wined3d hindered performance means its normally outside the ban hammer range due to not in fact producing what is classed as competetive FPS as any code path errors the game does will not give you any playing advantage over another player so no ban hammer. This is how the ban systems horrible work.
Originally posted by Cybmax
View Post
Sorry to say this is EA we are talking about. They will drop the ban hammer on you for doing what you described is not probably will be hit by ban-hammer it that you will be hit by banhammer at some point. EA made games are not overclocking friendly. They are not the only game vendor like this.
You and I might not think this makes sense but its the reality of playing EA games and other vendors with rules like theirs.
Being better than windows is not exactly a good thing with games in a lot of cases.
I absolute stand by this statement. The reality is how touchy the different game vendor anti-cheats are. You make a system perform well better than the average. I should have wrote that more clear.
Being better than Windows with non overclocked parts is not exactly a good thing in lot of cases.<< This is what I should have wrote. This is a fact of playing games on windows. Then we have wine on top of that.
This is one of these horrible trade offs. If you are not exactly sure of how API/ABI should work be going after speed may not be the right thing.
Wine project is doing a lot to try to prevent users from getting banned. Slow development of dx12 support in wine is because wine developer are aware how touchy anti-cheat systems are. Some cases vkd3d has had extra debugging code put in to slow it down to where it was known not to be right so it would intentionally under perform to avoid the ban hammers.
duby229 you are really being dumb in a lot cases. Reality here is it not dumb to make under performing code when it results in user not been banned until you can get that section in fact working right. Welcome to the horrible trade off of working on wine graphics.
The reality of closed source gaming is a stack of stupidity that you have to work with to avoid end users getting banned. Yes some times giving people decent performance instead of poor performance is the wrong answer. Of course I wish the reality was that giving decent performance would never trigger game users to be banned but that is not the reality.
Leave a comment: