Replies: 8 comments 18 replies
-
That is not correct. Where did you see that command listed? Did you follow the development setup guide? Also, you do not need to be running Powershell with admin privileges, and doing so may cause you other problems. Was there something in the Axmol documentation that indicated this needs to be done on Windows? The actual command to create a project is: For example, the following will create a folder named "MyProject" in the current folder (indicated by the Go into the "MyProject" folder, then type: |
Beta Was this translation helpful? Give feedback.
-
Are you using the latest version from the |
Beta Was this translation helpful? Give feedback.
-
Issue with
|
Beta Was this translation helpful? Give feedback.
-
The libEGL.dll, libGLESv2.dll is auto built and dist by https://github.com/simdsoft/1kiss/releases from google webgl implementation angle library should work on any windows 7+ systems, that's strange not work on you system. axmol render path windows: axmol --> angle(copmpiled from google official sources with d3d11 only) --> d3d11 |
Beta Was this translation helpful? Give feedback.
-
The
|
Beta Was this translation helpful? Give feedback.
-
Possible reason is dll mismatch, possible solution is call win32 API: |
Beta Was this translation helpful? Give feedback.
-
while, your system is next windows11 preview build which we are never runs on |
Beta Was this translation helpful? Give feedback.
-
After several attempts to fix the issue with The only change that occurred (without my intervention) was a Visual Studio 2022 security update (version 17.12.5), which was installed automatically via Windows Update. Before realizing this, I followed the same process I had been using to reinstall Axmol: I deleted the folder, cloned the repository again, and followed the standard setup. To my surprise, this time everything worked fine. I checked Axmol’s GitHub repository for recent changes, but there were no functional modifications—only minor updates related to donations. I also examined my development environment and found no relevant changes. However, Windows Update showed a quality update for Visual Studio 2022, although its changelog does not mention anything that seems directly related to our issue. Successful Compilation LogsFor reference, here are the compilation logs after the update: Axmol 2.3.2 (Release)
Axmol 2.3.3-528660e (Git Clone)
Final ConclusionSince the only real change was this security update, we can infer that it indirectly fixed the issue. Axmol now compiles correctly and generates If anyone encounters this issue in the future, I recommend checking if their Visual Studio installation is up to date. Thanks to everyone for your help in this thread! 🚀 |
Beta Was this translation helpful? Give feedback.
-
Hello, I'm trying to run a Lua project on Axmol 2.3.2 on Windows 11, but the program doesn't start correctly. I've followed the installation and setup steps to the letter, but the project gets stuck on a screen without specific errors. Below, I detail the steps I've taken and relevant information:
Steps taken:
setup.ps1
in administrator mode.axmol new -l lua
to create a new Lua project.build.bat
(also triedaxmol build -p win32
) in administrator mode.build/proyectname.sln
with Visual Studio 2022.bitop
, I implemented the proposed solution).Issue:
The program doesn't start and gets stuck on the following screen:
No additional error messages are shown, and I'm unsure if the issue is with my environment or the Axmol build.
Environment information:
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.42.34433\bin\Hostx64\x64
C:\Program Files (x86)\Microsoft Visual Studio\Installer
Additional attempts:
Questions:
I'm not sure if this is an issue with my environment, a misconfiguration on my part, or a bug in Axmol 2.3.2. Could someone guide me on how to proceed or point me in the right direction? Any help would be greatly appreciated!
P.S.: I also tried compiling the Axmol engine directly using the same CMake command (
cmake -S . -B build -G "Visual Studio 17 2022" -A x64
) and then runningcmake --build build
. However, the generated executables (including the test programs) do not work correctly. This makes me wonder if there's a broader issue with the build process or compatibility on my system.Beta Was this translation helpful? Give feedback.
All reactions