Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GameVersion error #3

Open
moth1995 opened this issue Dec 21, 2020 · 1 comment
Open

GameVersion error #3

moth1995 opened this issue Dec 21, 2020 · 1 comment

Comments

@moth1995
Copy link

Hi!

i notice that when kitserver5 its attached to WE9 it get recognize as PES5, i made test with many executables and its the same all the time, i notice this bug when i was using the network module because i was getting a 404 and then i made some test first to discard error at my server i made an curl request from another server and i was getting 200, then with wireshark filtering by http protocol, i get notice that the folder that was requestion was pes5 and not we9, then i opened the log and found this line

{KLOAD} Game version: PES5 PC

is this an important bug? or is nothing we should really care because they share the same memory address?

thanks!

@moth1995 moth1995 changed the title GameVersion error tag:bug GameVersion error Dec 21, 2020
@moth1995 moth1995 changed the title tag:bug GameVersion error GameVersion error Dec 21, 2020
@juce
Copy link
Collaborator

juce commented May 5, 2021

yeah, i think there are lots of we9.exe files on the internet, which are actually not real executables from Winning Eleven 9, but copies of a no-dvd version of pes5.exe. Since both games are 100% compatible in terms of data (but not compatible with WE9LE), you can use the exes interchangeably. Kitserver does not look at the filename, but seaches inside the exe for the information - and is therefore detecting it as "PES5 PC". I don't know if i saw ever saw a proper no-dvd we9.exe that was true we9 and not a copy of pes5 exe. (If you try it with original we9.exe from dvd disk, with securom protection and such, then kitserver should recognize it as "WE9 PC").

And that is why the network module does what it does.
Not sure we can call it a bug, but yeah, it's a bit confusing behaviour for sure :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants