imgui.h assertion failed

[v1ckxy]

// First of all: Thank you for your work.

So I had just found that using the experimental version with the overlay, in a complete random way, throws this error from time to time when moving around the overlay. If you click on ignore it will keep working, but I'm unable to figure out why the lib throws the error in first place. 😑

Assertion failed!

Program: [...]\steam_api64.dll

File: gbe_fork\build\deps\win\vs2022\...\imgui.h
Line: 2078

Expression: i>=0 && i < Size

I was checking imgui.h and it looks like the library had a LOT of commits in the last regarding that file in the last weeks: https://github.com/ocornut/imgui/commits/cb16568fca5297512ff6a8f3b877f461c4323fbe/imgui.h

Including:

• Some kind of error handling for recovery
• And one of them that talks about assertion issues. I'm not sure if it's related or not: "Tables: fixed assertion related to inconsistent outer clipping when sizes are not rounded."

I would try it if it weren't for the fact that I'm going to be a few days without access to VS or a compiler :S

[Detanup01]

Yup I having the same problem in some times. Try not using any Overlay things (ie: Rivatuner, GeForce Experience) and maybe will work. Some games works, some not, its a mistery.

In GitHub if you enable Actions you can build it without need of VS, complier.

[v1ckxy]

I think is related with activity inside the overlay; Moving inside in-out the app window and hovering around elements/buttons ends up triggering it, I saw that the cursor tends to be placed in a fixed place -where the game cursor is- when moving out of the window, but I don't know how it can trigger the issue.

Regarding actions, thanks, I saw it a few hours afterwards opening the issue; I've compiled a new library (size differs so I'll think has new dependencies inside it -as I don't fully understand how the workflow is done, if gets the latest build of the deps or not, never used this thing inside github before), but I was testing it and looks like has the same assertion problem.

As I don't have the debugger installed here, I'm SOL right now :D

Regards!

// There are no overlays running in this env, right now I'm testing on a mobile device so everything's installed to a minimum.

[otavepto]

what appid caused this?

[v1ckxy]

1702330

BTW... I think is related with the mouse cursor. When the error triggers, app cursor becomes dettached from the overlay

After error, mouse cursor becomes two: System (blue one) and overlay. You need to close overlay, open it again and mouse will be ok again.