One of us - is already on new win10. And corona win32 builds are failing on his computer.
Does that our fault or corona?
Here is error window.
Here is win32 build - https://www.dropbox.com/s/981fkucc59ulcpf/Royal%20Heroes.Win32.zip?dl=0
This is most likely caused by an OpenGL video driver issue on that system. As in the crash is likely coming from the driver. This is pretty typical when upgrading to a new major Windows OS, because it is up to 3rd party manufacturers (not Microsoft) to provide updated drivers for the system’s hardware when upgrading. Microsoft is pretty good about providing working/compatible Direct3D drivers, but OpenGL drivers have to come from the manufacturer (AMD, Nvidia, Intel). You may want to ask this person to double check if he/she has downloaded the newest driver for that system for Windows 10.
You *might* find clues in what gets logged by your app as well. Try launching your app on that Windows 10 machine at the command line as follows:
[NameOfYourExeFile] > log.txt
The ‘>’ symbol tells the command line to output all stdout and stderr messages (such as what gets outputted by your Lua print() functions) to a file named “log.txt”. After your app exits/terminates, double click on the “log.txt” file. It’ll show the same information that you see in the Corona Simulator’s console. I doubt it’ll find the reason for this particular crash since this is better at finding Lua runtime errors, but it doesn’t hurt to check. However, we do log the OpenGL driver name being used by the system at the top, which may be good to know.
You might also want to try building our “GettingStarted/HelloWorld” sample app and running it on that Windows 10 system too. By running a much simpler app, this will help confirm if this is in fact a driver issue. However, if the sample app runs fine, then it’s not a driver issue and it might something else, such as perhaps a plugin.
Hey Joshua, tnx for answer. Here is our response:
WIn10 openGL version - 4.4
log.txt file from RoyalHeroes is empty.
HelloWorld app is working on win10, log.txt: Platform: Not Supported Yet / x64 / 6.2 / GeForce GTX 760/PCIe/SSE2 / 4.5.0 NVIDIA 355.97 / 2015.2656
HelloWorld is working on win7 and win10 without problem.
RoyalHeroes is working on win7, but failing at start on win10.
links to builds:
https://www.dropbox.com/s/wecm79qsm6hfn2x/HelloWorld.Win32.zip?dl=0
https://www.dropbox.com/s/981fkucc59ulcpf/Royal%20Heroes.Win32.zip?dl=0
That’s good news. Since a simple sample app works fine on Windows 10, then that means its not an OpenGL driver issue.
I’ve searched our daily build release notes and noticed that we have one Windows 10 crasher that we’ve fixed/worked-around on our end involving loading MP3 files. This issue was fixed in daily build #2682. Since you are using an older daily build, I’m guessing that this might be the issue.
This is most likely caused by an OpenGL video driver issue on that system. As in the crash is likely coming from the driver. This is pretty typical when upgrading to a new major Windows OS, because it is up to 3rd party manufacturers (not Microsoft) to provide updated drivers for the system’s hardware when upgrading. Microsoft is pretty good about providing working/compatible Direct3D drivers, but OpenGL drivers have to come from the manufacturer (AMD, Nvidia, Intel). You may want to ask this person to double check if he/she has downloaded the newest driver for that system for Windows 10.
You *might* find clues in what gets logged by your app as well. Try launching your app on that Windows 10 machine at the command line as follows:
[NameOfYourExeFile] > log.txt
The ‘>’ symbol tells the command line to output all stdout and stderr messages (such as what gets outputted by your Lua print() functions) to a file named “log.txt”. After your app exits/terminates, double click on the “log.txt” file. It’ll show the same information that you see in the Corona Simulator’s console. I doubt it’ll find the reason for this particular crash since this is better at finding Lua runtime errors, but it doesn’t hurt to check. However, we do log the OpenGL driver name being used by the system at the top, which may be good to know.
You might also want to try building our “GettingStarted/HelloWorld” sample app and running it on that Windows 10 system too. By running a much simpler app, this will help confirm if this is in fact a driver issue. However, if the sample app runs fine, then it’s not a driver issue and it might something else, such as perhaps a plugin.
Hey Joshua, tnx for answer. Here is our response:
WIn10 openGL version - 4.4
log.txt file from RoyalHeroes is empty.
HelloWorld app is working on win10, log.txt: Platform: Not Supported Yet / x64 / 6.2 / GeForce GTX 760/PCIe/SSE2 / 4.5.0 NVIDIA 355.97 / 2015.2656
HelloWorld is working on win7 and win10 without problem.
RoyalHeroes is working on win7, but failing at start on win10.
links to builds:
https://www.dropbox.com/s/wecm79qsm6hfn2x/HelloWorld.Win32.zip?dl=0
https://www.dropbox.com/s/981fkucc59ulcpf/Royal%20Heroes.Win32.zip?dl=0
That’s good news. Since a simple sample app works fine on Windows 10, then that means its not an OpenGL driver issue.
I’ve searched our daily build release notes and noticed that we have one Windows 10 crasher that we’ve fixed/worked-around on our end involving loading MP3 files. This issue was fixed in daily build #2682. Since you are using an older daily build, I’m guessing that this might be the issue.