Keeps trying to connect about bf2autospectator

[cetteup]

What server are you trying to connect to? And does the game show any error messages?

I will build a new standalone version later today, since I made quite a few changes since the last release.

[Edwin-Sun]

Hi tired several servers. I tried our First-Legion server at ip: 5.79.100.144
Bf2 will start with the username and PW and I can see the mouse going to "Multiplayer" and refreshing the server browserlist but i stays there and my CMD screen keeps saying "re-connecting".

[cetteup]

The screenshot is good!

While I set up a new build, could you run the controller once with --debug-log?

And, just to make sure that's not an issue: I tried to send my own spectator to the server and it failed to join (Connection failed error). Can you manually join the servers you tried?

[Edwin-Sun]

I did what you said, putting --debug-log at the end but I dont see a log file

[Edwin-Sun]

I can log in normally whit the same account

[cetteup]

I did what you said, putting --debug-log at the end but I dont see a log file

It does not log to a file, but should log to stdout (the console) like the logs seen in the screenshot. However, a quick look at the code tells me that not much more is actually logged when debug logging is enabled.

I just released version 0.3.0 which contains many small improvements, some directly related to how the spectator handles the server join. Please test if that works better. If it does not, please let me know if you see anything relevant in the logs when running with --debug-log.

[Edwin-Sun]

I see version 3 is only the "main" version amd not the complete "stand alone" version?

[cetteup]

It's just a name change. If you download and run the executable, it works just like the old versions did.

[Edwin-Sun]

I noticed the standalone version has a lot more folders

[cetteup]

As mentioned in the release note, it's just a change in how it is distributed. Instead of building an .exe with a bunch of files around it, it now distributed as a single .exe that contains everything.

All in all, it's just a pyinstaller option, about you which you find more details in the pyinstaller documentation.

[Edwin-Sun]

Used the new exe file "bf2-auto-spectator-0.3.0.exe with the same arguments as before but i got the same problem. Bf2 will start and login to BFHQ but will not connect to gameserver. keeps re-connecting.

[cetteup]

Alright then, let's try and narrow this down.

1. What OS are you running?
2. Is your game set to English without any significant modifications to the locale file?
3. Have you changed anything else about the game/menu?
4. Have you checked the hints at the bottom of the readme? (100% scaling in Win10 etc.)
5. What GPU Brand are you using?

[Edwin-Sun]

1. Windows 10 2. English 3. Bf2 video resolution 1600x900 4. Windows scaling is default at 100% 5. Nvidia Verstuurd vanaf mijn iPhone

…

Op 22 mei 2021 om 08:23 heeft cetteup ***@***.***> het volgende geschreven:  Alright then, let's try and narrow this down. What OS are you running? Is your game set to English without any significant modifications to the locale file? Have you changed anything else about the game/menu? Have you checked the hints at the bottom of the readme? (100% scaling in Win10 etc.) What GPU Brand are you using? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[Edwin-Sun]

I had a quick look into the pythoncode ( I am not familiar with programming ) and it looks like it is not going to "connect_tp_ip_button_present" in gameinstancemanager.py arounf line 354
I can see the mouse moving to BFHQ and Multiplayer but it is stuck in a loop. It will go back to BFHQ and Mulitplayer all the time

[Edwin-Sun]

Update:
When I change my windows grapic settings to 1600 x 900 and add the --game-re 900p argument, I can see the program opening the "connect to ip" button and fill in the ip and port. It comes back with the following error:

[cetteup]

According to the logs/the last screenshot, it is detecting an error message in game (connection lost).

Is that accurate? Does the game show an error message when trying to join now?

[Edwin-Sun]

I don’t see the game ( map ) start loading. It ends with connection lost and it loops again Verstuurd vanaf mijn iPhone

…

Op 22 mei 2021 om 13:17 heeft cetteup ***@***.***> het volgende geschreven:  According to the logs/the last screenshot, it is detecting an error message in game (connection lost). Is that accurate? Does the game show an error message when trying to join now? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[cetteup]

Since I had similar issues with that server, could you please try with a server I know usually works and is definitely online:

31.186.250.239 (Super@ S2)

[Edwin-Sun]

I will check yiur server in 10 minutes.

That connection problem has to do with PB enabled servers. I always have to login twice to connect to our PB enabled servers.
When I try a server without PB enabled ( just one of the BF2Hub un-ranked servers, it is connecting and loading the map.
The eror i get after laoding the map is:

[Edwin-Sun]

Using Super@ server:

[Edwin-Sun]

Update: I can connebt to PB enabled servers too ;)
But message about Spawn menu not vissible is still there :(

I noticed BF2 is tarted in windowed mode and it's not fully centered. I have 2 mm offset on the left and top of the BF2 window. Maybe it should start in Fullscreen mode?

[cetteup]

Ok, so some progress.

The game is intentionally started in windowed mode so you can see the console window.

But it now seems to not detect the spawn menu correctly. In order to be able to troubleshoot this, could you run it once with a working server and --debug-screenshot enabled? That will save all screenshots it takes into a folder as well as log all the OCR results.

Speaking of OCR, kindly let me know which version of Tesseract you have installed.

[Edwin-Sun]

The Tesserac version is v4.1.0.2019.0314 ( 64 bit )

I cant find any logfile?

[cetteup]

When running with --debug-screenshot, you should see a bunch of "OCR result:" log messages in the console.

I have been using version v5.0.0.20190623 lately, maybe try using that. You download the installer here.

Also, does it still log "game window is incorrect size" at the start?

[Edwin-Sun]

Downloaded and installed v5.0.0.20190623 version but problem still the same.

When i open console with "~" i see this:

[cetteup]

You mentioned before that you are using Windows 10, but the window frame in the screenshot looks like Windows 7.

Are you using some sort of skin/theme for Windows 10 that makes it look like Windows 7? If so, try resetting that to the default.

[Edwin-Sun]

No, it’s windows 10 without modifications Verstuurd vanaf mijn iPhone

…

Op 22 mei 2021 om 18:20 heeft cetteup ***@***.***> het volgende geschreven:  You mentioned before that you are using Windows 10, but the window frame in the screenshot looks like Windows 7. Are you using some sort of skin/theme for Windows 10 that makes it look like Windows 7? If so, try resetting that to the default. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[Edwin-Sun]

Change background from photo to default but still same problem.

[cetteup]

It's not the background that I suspect is causing the issue, it's the Windows theme. I suspect that the different theme is why the spectator keeps complaining about the window size as it shifts everything by a few pixels, which also messes with the OCR. This is what the window should look like on Windows 10:

What does the settings app say is your current theme? The default should look like this.

Also, please double check your exact version of Windows via "About your PC".

[Edwin-Sun]

This is my background / theme:

[cetteup]

The windows theme and background are two different things. Please check your theme settings instead of your background settings. I am not sure what "Theme" would be in NL, but it should the 4th option in the menu.

[Edwin-Sun]

I changed theme to Windows 10

[Edwin-Sun]

Problem is still there, player is not spawning

[cetteup]

Which theme were you using before? Please try with the "Windows" theme, which is the default.

Also, are you running BF2 with any compatibility options enabled?

[Edwin-Sun]

No change :(
Same problem at my laptop.

[cetteup]

Hm. There's not much I can do, unfortunately. I am pretty sure that the non-standard Windows 10 theme results in a different window size. The spectator logs something about an "incorrect window size" several times, which it should never do when starting the game itself. And due to the different window size, some of OCR attempts or game state detections in general fail.

[Edwin-Sun]

Windows display settings are 1600 x 900
Theme is "Windows"
I see the same offset left and top at your example picture, so i guess thats okay.
It keeps on drawing the hud and the hud comes up.
But the hud is not showing the complete map picture!

Maybe the OCR likes to see full Karkand map picture in the HUD?

[cetteup]

Which version of Windows 10 are you using?

And no, it has nothing to do with the map (it never looks at that). The issues are probably just caused by the different window size, which moves everything my a few pixels and thus messes everything up.

[Edwin-Sun]

[Edwin-Sun]

I chabged resolution from 900p to 720p.
I get an error message at the console:

[cetteup]

It will not work unless you manage to start the game in a normal Windows 10 window. The resolution does not matter.

If you have something like "Classic shell" installed, try removing it. If you are running BF2 in compatibility mode, try without it.

But other than that, I'm afraid I really cannot help you.