In 'OnFrame': DrawImageQuad() argument 10: expected valid stack index <= 1, got 2 stack traceback

[hurafloyd]

Check version

• I'm running the latest version of Path of Building and I've verified this by checking the changelog

Check for duplicates

• I've checked for duplicate open and closed issues by using the search function of the issue tracker

What platform are you running Path of Building on?

Windows

Screenshots of crash/graphical issue, version and options menu

Error:

In 'OnFrame': DrawImageQuad() argument 10: expected valid stack index <= 1, got 2
stack traceback:
[C]: in function 'DrawImageQuad'
Classes/PassiveTreeView.lua:1415: in function 'DrawQuadAndRotate'
Classes/PassiveTreeView.lua:611: in function 'Draw'
Classes/TreeTab.lua:440: in function 'Draw'
Modules/Build.lua:1362: in function 'CallMode'
Modules/Main.lua:372: in function <Modules/Main.lua:342>
[C]: in function 'PCall'
Launch.lua:111: in function Launch.lua:108
v0.16.0 master
Press Enter/Escape to dismiss, or F5 to restart the application.
Press CTRL + C to copy error text.

What are your system specifications and configuration?

OS: Win11
Graphics: Nvidia 1660 OS

How to reproduce the issue

I have a very old build (from around version 0.2) that I tried to update. I can't go into the application because I get blocked by the provided error message. Just launching the application with the aforementioned build will cause it.

PoB for PoE2 build code

https://pastebin.com/JDqaas5N

[hurafloyd]

I would recommend to make PoB (1 and 2) load into the Build selection menu instead of loading the latest build itself, or perhaps add an option that allows the user to choose the loading method, although if something like this happens where the user gets blocked from the application, a "Return to Build selection menu" option in the error message would be good too, since the Enter/ESC and F5 didnt help in this situation.

EDIT: Thankfully, removing the .XML file of the build from the folder allowed me to launch the application again, although detrimental to the user, may be the option of deleting the buggy .XML file can be a solution too in case that it cannot be recovered.

EDIT 2: Although removing the .XML solved the issue of loading the app again and lets me load previous build files from the build selection menu it won't allow me to create new builds. This is a copy of the error from the loading screen:

--- ERROR ---
Critical error at address C162BB2Fh:
Access violation: attempted to read from address 00000008h