Hey everybody !
I’ve been testing my game for several days now and everything seems to work fine except one thing : the game doesn’t run as smooth as in the simulator. Once the Win 32 app is built, it seems that it’s a LOT slower.
So, i was wondering : is this normal ? Is this is because it’s still a beta and can we expect better performances ? Or is there a problem with my laptop (I’m using a Surface Pro 2) ?
Thanks in advance !
It typically runs faster than the the Corona Simulator.
You should check for any errors that might be happening at runtime. You can do so by looking at the std::out of the application, which is where all of your Lua print() statements and Corona log output is outputted to by default. The simplest way to view std::out is by opening the Windows Console (aka: DOS box), “CD” to the your application’s directory (where the *.exe file is at), and type in the following at the command line…
YourAppName.exe > log.txt
…where you would replace “YourAppName.exe” with the name of your app’s EXE file name. After closing your app, all of the std::out messages will be outputted to the “log.txt” file. Just double click on it to view the output. From there, see if there are any errors that might be slowing your app down.
I just realized that I installed Windows 10 yesterday on my Surface Pro… And it may be (one of) the reason my game is slow.
Thanks a lot, I’m gonna be able to investigate thanks to the log.txt (didn’t know we were able to do that !).
If your app doesn’t use any plugins, then it might be faster for you to test your project using the “Corona.Shell.exe” that’s included with the Corona SDK for Windows. It’s kind of an Easter Egg at the moment, but what it does is it runs a Corona project in Win32 desktop app (like you Win32 built app), except that you can point it to a Corona project’s “main.lua” file like how you do it with the Corona Simulator. This makes debugging a bit faster because you don’t have to rebuild your app. But you still have to go out of your way to view std::out like I’ve mentioned above. If it helps you any, it’s installed next to the “Corona Simulator.exe”, which by default is installed under…
C:\Program Files (x86)\Corona Labs\Corona SDK
It typically runs faster than the the Corona Simulator.
You should check for any errors that might be happening at runtime. You can do so by looking at the std::out of the application, which is where all of your Lua print() statements and Corona log output is outputted to by default. The simplest way to view std::out is by opening the Windows Console (aka: DOS box), “CD” to the your application’s directory (where the *.exe file is at), and type in the following at the command line…
YourAppName.exe > log.txt
…where you would replace “YourAppName.exe” with the name of your app’s EXE file name. After closing your app, all of the std::out messages will be outputted to the “log.txt” file. Just double click on it to view the output. From there, see if there are any errors that might be slowing your app down.
I just realized that I installed Windows 10 yesterday on my Surface Pro… And it may be (one of) the reason my game is slow.
Thanks a lot, I’m gonna be able to investigate thanks to the log.txt (didn’t know we were able to do that !).
If your app doesn’t use any plugins, then it might be faster for you to test your project using the “Corona.Shell.exe” that’s included with the Corona SDK for Windows. It’s kind of an Easter Egg at the moment, but what it does is it runs a Corona project in Win32 desktop app (like you Win32 built app), except that you can point it to a Corona project’s “main.lua” file like how you do it with the Corona Simulator. This makes debugging a bit faster because you don’t have to rebuild your app. But you still have to go out of your way to view std::out like I’ve mentioned above. If it helps you any, it’s installed next to the “Corona Simulator.exe”, which by default is installed under…
C:\Program Files (x86)\Corona Labs\Corona SDK