Error when run debug windows

[NgVThangBz]

• axmol version: 2.2.1
• devices test on: windows 10
• developing environments
  • NDK version: r23c
  • Visual Studio:
    • VS version: 2022 (17.12.3)
    • MSVC version: 19.39+
    • Windows SDK version: 10.0.22621.0+
  • cmake version: 3.31.2
    Steps to Reproduce:
• setup.ps1
• axmol build
• run ok in release
• in debug i received the error(0xc000007b):
  

[halx99]

two possible reason:

• directx runtime not ready
• vc runtime incorrect: system32 folder contains 32bit runtime dll or SysWow64 contains 64bit runtime dll

[NgVThangBz]

@halx99 so, how fix it?
delete vcruntime140d.dll?

[NgVThangBz]

this log:

[halx99]

try uninstall and reinstall vcredist

[NgVThangBz]

it doesn't seem to work for me

[NgVThangBz]

• uninstall and reinstall vcredist ( x86 and x64)
• run DirectX again
  but not work, has any ideal?

[rh101]

Just out of curiosity, if you put a breakpoint on _tWinMain() (or main(int, char**), depending on which one is active) in proj.win32/main.cpp, does it actually hit the breakpoint before it crashes?

[NgVThangBz]

@rh101 it not come to breakpoint

[rh101]

Is this something that just started occurring, and if so, have you checked the most recent changes you made to the application to see if that is what caused the problem?

Have you also tried deleting the build folder and regenerating it with the axmol build command?

[NgVThangBz]

I tried deleting the build folder and using axmol build many times, but the problem is still not solved.
maybe the problem lies in my dll files, but i cant figure out exactly why

[rh101]

Can you try a new project? Create one via axmol new etc., and see if the debug build works for that.

[NgVThangBz]

i also tried creating new, same error.
maybe it's the environment(dll) of the device i'm using

[rh101]

maybe it's the environment(dll) of the device i'm using

What do you mean by this remark?

Is this a local PC with Visual Studio 2022 installed? Have you tried repairing the VS installation?

[NgVThangBz]

What do you mean by this remark?

@rh101
i think have some dll file incorect

and
I have tried other types:
[x64-debug] not work
[x64-release] work
[win32-debug] work
[win32-release] work

[halx99]

Try use wsls-arch to detect all dlls bitness in folder: C:\Windows\system32:

https://github.com/simdsoft/wsls/releases/download/v3.5.3.1/wsls-3.5.3.1.7z

[NgVThangBz]

Try use wsls-arch to detect all dlls bitness in folder: C:\Windows\system32:

https://github.com/simdsoft/wsls/releases/download/v3.5.3.1/wsls-3.5.3.1.7z

How to set it up?
i try open file.exe and bat?

[halx99]

the package contains wsls-arch.exe which is a independent program, only accept one parameter to specify dll file path for detecting and will print x86 or x64.

[halx99]

you can write a .bat or .ps1 to iterate dlls in C:\Windows\System32\ and invoke wsls-arch.exe

[NgVThangBz]

The problem is still not solved, however I think this is not axmol's problem, so I will close this issue,
if necessary I will ask for everyone's opinion in the Discussion
thank for all

[Ts-pe]

Aren't you trying to “Axmol build” inside the engine folder? (it is not very clear where you are doing the axmol build, but from the name of the error window it looks like you are doing it in a new project and not in the engine).

Try this command “cmake -S . -B build -G “Visual Studio 17 2022” -A x64” (in a new project), open the solution (.sln), it will default to debug/ x64. just hit start debugging (it will take a while).

PS: you need to delete everything you have done with your engine version (reinstall axmol), another option would be to upgrade the engine (you can always go back to a previous version by reinstalling axmol, but you must be careful that the folder is always named the same or you will have many axmol folders in your environment variables, although it is not difficult to remove them, just extra work).