Xian55 / WowClassicGrindBot

Highly configurable and responsive World of Warcraft Classic pixel Grind Bot - No DLL injection or memory tampering, just screen capture and input simulation.
190 stars 127 forks source link

Stuck on Frame configuration page #549

Closed YogurtBox123 closed 1 year ago

YogurtBox123 commented 1 year ago

Description

After installing the addon and moving to configuration screen I can see the pixel line of the addon blinking. But for some reason using automatic / manual config doesn't work. When using automatic configuration I just get stuck in game calling /{addonName} every few seconds. If using manual mode I get these messages: image . I've cloned the repo and tried debugging but due to lack of time didn't manage to find much. What I did find is that if I try to save screen.ScreenImage (which is used from manual configuration for GetDataFrameMeta() method in FrameConfiguratior) I get just a black screen. So I'm guessing that this might be an issue since screen data is not present.

Any ideas what could be wrong here?

A bit about my setup, I'm using a bit older PC with i5 and GTX 1070 with Wow running on HDD. Single monitor so I'm Alt tabbing between wow and chrome while running bot.

Oh and also I've searched for previous issues that might be similar, tried changing code a bit also (lack of time so I discarded my changes and got back to dev branch). I've also tried few different resolutions and windowed and full screen mode. Admin vs non admin running too. Also tried changing pixel size for addon from 1 to 9 with no luck, but due to that black screen I don't think that is an issue.

PS: you got awesome little project here :)

Addon Version

Last dev branch version

World of Warcraft Client

The Wrath of the Lich King Classic

Reproduction Steps

  1. Clone repo
  2. Follow steps
  3. Install addon
  4. Try to configure Frame Configuration
  5. Get stuck

Last Good Version

Screenshots

image

Logs

[19:10:10:593 I] [Startup ] hr 12.11.2023. 19:10:10 +01:00 [19:10:11:377 I] [Startup ] Pid: 18412 [19:10:11:377 I] [Startup ] Version: 3.4.3.51943 [19:10:11:892 I] [Startup ] Addon version: 1.7.50 [19:10:14:162 I] [Lifetime ] Now listening on: http://0.0.0.0:5000 [19:10:14:165 I] [Lifetime ] Application started. Press Ctrl+C to shut down. [19:10:14:165 I] [Lifetime ] Hosting environment: Development [19:10:14:165 I] [Lifetime ] Content root path: D:\Workspace\WowClassicGrindBot\BlazorServer [19:10:22:449 D] [WowScreenDXGI ] DataFrames 0 - Texture: 1x1 [19:10:22:620 I] [WowScreenDXGI ] Rectangle [ X=0, Y=0, Width=1920, Height=1080 ] - Windowed Mode: False - Scale: 1,00 [19:10:22:621 I] [Startup ] WowScreenDXGI [19:10:24:418 D] [WowScreenDXGI ] DataFrames 0 - Texture: 1x1 [19:10:24:419 D] [FrameConfigurator] ResetConfigState [19:10:24:422 D] [WowScreenDXGI ] DataFrames 0 - Texture: 1x1 [19:10:24:432 D] [FrameConfigurator] ResetConfigState [19:13:14:523 I] [AddonConfigurator] DeleteAddon -> Unique Addon Exists [19:13:14:531 E] [AddonConfigurator] Source directory does not exist or could not be found: .\Addons\ [19:13:14:664 I] [AddonConfigurator] CopyAddonFiles - Success [19:13:14:745 I] [AddonConfigurator] Install - Success [19:13:14:761 I] [ExecGameCommand] /reload [19:13:21:528 I] [AddonConfigurator] DeleteAddon -> Unique Addon Exists [19:13:21:539 E] [AddonConfigurator] Source directory does not exist or could not be found: .\Addons\ [19:13:21:573 I] [AddonConfigurator] CopyAddonFiles - Success [19:13:21:625 I] [AddonConfigurator] Install - Success [19:13:21:626 I] [ExecGameCommand] /reload [19:13:31:226 I] [AddonConfigurator] DeleteAddon -> Unique Addon Exists [19:13:31:239 I] [ExecGameCommand] /reload [19:13:38:465 E] [AddonConfigurator] Source directory does not exist or could not be found: .\Addons\ [19:13:38:495 I] [AddonConfigurator] CopyAddonFiles - Success [19:13:38:548 I] [AddonConfigurator] Install - Success [19:13:38:555 I] [ExecGameCommand] /reload [19:14:35:817 I] [AddonConfigurator] DeleteAddon -> Unique Addon Exists [19:14:35:830 I] [ExecGameCommand] /reload [19:14:53:154 E] [AddonConfigurator] Source directory does not exist or could not be found: .\Addons\ [19:14:53:208 I] [AddonConfigurator] CopyAddonFiles - Success [19:14:53:304 I] [AddonConfigurator] Install - Success [19:14:53:308 I] [ExecGameCommand] /reload [19:16:39:648 D] [WowScreenDXGI ] DataFrames 0 - Texture: 1x1 [19:16:39:652 D] [FrameConfigurator] ResetConfigState [19:16:51:397 D] [WowScreenDXGI ] DataFrames 0 - Texture: 1x1 [19:16:51:402 D] [FrameConfigurator] ResetConfigState [19:17:56:354 I] [Startup ] hr 12.11.2023. 19:17:56 +01:00 [19:17:56:539 I] [Startup ] Pid: 18412 [19:17:56:539 I] [Startup ] Version: 3.4.3.51943 [19:17:56:652 I] [Startup ] Addon version: 1.7.50 [19:17:57:027 I] [Lifetime ] Now listening on: http://0.0.0.0:5000 [19:17:57:030 I] [Lifetime ] Application started. Press Ctrl+C to shut down. [19:17:57:030 I] [Lifetime ] Hosting environment: Development [19:17:57:030 I] [Lifetime ] Content root path: D:\Workspace\WowClassicGrindBot\BlazorServer [19:17:57:623 D] [WowScreenDXGI ] DataFrames 0 - Texture: 1x1 [19:17:57:632 I] [WowScreenDXGI ] Rectangle [ X=0, Y=0, Width=1920, Height=1080 ] - Windowed Mode: False - Scale: 1,00 [19:17:57:633 I] [Startup ] WowScreenDXGI [19:18:04:684 D] [WowScreenDXGI ] DataFrames 0 - Texture: 1x1 [19:18:04:685 D] [FrameConfigurator] ResetConfigState [19:18:04:690 D] [WowScreenDXGI ] DataFrames 0 - Texture: 1x1 [19:18:04:697 D] [FrameConfigurator] ResetConfigState [19:18:17:857 D] [WowScreenDXGI ] DataFrames 0 - Texture: 1x1 [19:18:17:863 D] [FrameConfigurator] ResetConfigState [19:18:23:308 D] [WowScreenDXGI ] DataFrames 0 - Texture: 1x1 [19:18:23:314 D] [FrameConfigurator] ResetConfigState

Xian55 commented 1 year ago

👋 Hello,

while working on https://github.com/Xian55/WowClassicGrindBot/pull/548 i had similar issue, however after some local testing i concluded that i've managed to fix the issue, well it seems not.

I get just a black screen. So I'm guessing that this might be an issue since screen data is not present.

Actually reading about this, this might be a common problem with Blizzard games. While i was experimenting with different screen capture methods, i tried out OBS and with various settings, i had black screen as well. I'm not 100% sure that you have the same problem, but there's a common fix for this, if you type in google "obs world of warcraft black screen" you might find a solution, if i recall correctly you have to change DirectX settings or something similar, fullscreen or windowed.

Nonetheless, i'm going to conclude investigation in the code, a little bit later

YogurtBox123 commented 1 year ago

Awesome thanks for the quick response @Xian55 . I'll see if I can find anything. Let me know if you manage to find something that might fix it :)

NuckyDucky commented 1 year ago

Same issue.

Screenshot_wow_issue

I also tried changing pixel size as well as disabling other capture programs (like ShareX or OBS) and making sure my settings were correct. I tried looking for an 'obs black screen fix' and didn't find anything myself.

Settings: 2070 super 8gigs Client: Wotlk Classic

I echo YogurtBox123, this is a great project and I'll patiently await any fix. I love to automate things.

YogurtBox123 commented 1 year ago

Same issue.

Screenshot_wow_issue

I also tried changing pixel size as well as disabling other capture programs (like ShareX or OBS) and making sure my settings were correct. I tried looking for an 'obs black screen fix' and didn't find anything myself.

Settings: 2070 super 8gigs Client: Wotlk Classic

I echo YogurtBox123, this is a great project and I'll patiently await any fix. I love to automate things.

Nice to see I'm not only one, just to add a bit more info, I tried fiddling with DX settings in Wow but still no success

Xian55 commented 1 year ago

Hang on there, it was me who made a mistake, the fix is right on the way sometime soon, apologies.

Xian55 commented 1 year ago

It should be fixed by #550 let me know if the issue still persist.

Apologies for the inconveniences.

Have a gooday.

YogurtBox123 commented 1 year ago

It should be fixed by #550 let me know if the issue still persist.

Apologies for the inconveniences.

Have a gooday.

It seems to be fixed now, thanks for a quick fix :)