crash with Windows 10 and Public Build 2015.2646

Solar2D Daily Builds and Public Releases
#1

Hi,

When I try to run my game in Windows 10 using Corona Sim with 2015.2646 the sim crashes. 

I updated to daily build 2706 which builds and runs my game fine.

But am I asking for stability problems because its a daily build?  (I released on Android, and it seems like Physics is shutting down in the middle of the game)

Thanks for any feedback, Greg

#2

2710 is pretty stable. There may be some issues with scrollViews but I’ve not heard any other complaints about it.

#3

Hi Rob,  Thanks for the idea but

#1 2646 doesn’t work on Windows 10

#2 I’ve tried .2706, .2710 and they both are causing me huge problems with transition freezes and physics dropouts. 

I’ll try re-installing 2646 on a Windows 10 machine and hopefully I can build from there, I’ve got some angry reviews!

Thanks, Greg

#4

I rolled back to Windows 7 and .2646 and was able to build and deploy a stable version of my game!

#5

Do you know if you were getting any errors running on Windows 10?

Rob

#6

When I updated Corona with the .2700 series versions Corona ran fine in Windows 10.  The types of problems that I was having were with transitions,such as:

    transition.to(player,{time=400,xScale=.10,yScale=.10 })
     _G.GUI.Set(“cmd”, {caption= "WE SEEM TO BE ENTERING A SPACE-TIME WARP! FA-CINA . . . "})
    timer.performWithDelay(1500, function() relocateplayer() end, 1)

in this example, my ship would shrink down to a dot to enter the black hole, but then it would error out, saying can’t scale by zero.  This code works fine in .2646.  I use quite a few transitions, so I suspect alot of my problems were transition related. 

I tried several projects on Windows 10 with .2646, they all caused a general Corona Crash when launching the simulator ‘Corona has Crashed’  This was before the project was launched.  I tried with 'Run as Admin and using Windows 7 compatibility but it made no difference.

Thanks, Greg

#7

For the crashes, were there any messages in your command window that opened in the background?

We have made quite a few updates to transitions since 2646.  I suspect the scale can’t be 0, is to prevent a divide by 0 issue and is probably just a warning.

#8

HI Rob,  the command window never opened up.

The scale wasn’t zero, it was .10, the thing is, after the transition the code

timer.performWithDelay(1500, function() relocateplayer() end, 1)

never executed.

Thanks, Greg

#9

Do you get the same behaviors with 27xx on Windows 7?

Generally if a line of code doesn’t happen, there was probably a fault that stopped that block of code. We would need to see the error. I know you said it was an error about not being zero, but there is usually a full back trace with an error message. We need the error copy/pasted, not hand typed.

If you can reproduce the error, it would be helpful.

Rob

#10

I didn’t try any 27xx versions on Windows 7 yet.  I’ll get to that this week.

Also, I’ll get the full error for you, that was just an example where the interpreter stopped executing on a transition, the ship shrunk and the call to relocate player never happened, so you were turned into a dot, albeit a powerful one :) 

Corona didn’t crash, the app was still running, just the behavior became screwier and screwier.

Thanks, Greg

#11

In Lua when there is a runtime error, the block that is currently executing. Other things will still run, like a button that executes a different function. So finding out what the runtime errors can help us track the problem.

Rob

#12

If you go back to Windows 10, can you try some of the sample apps?

Rob

#13

HI Rob, I will get back to do some testing with Windows 10 as soon as StellarTrek is stabilized again!

Thanks, Greg

#14

I have the same problem with 2646. I tried running a number of samples, and SimplePool crashes immediately, in case that helps you pin down the bug.

#15

Everyone,

The last release version of Corona (build #2646) will crash on the *release version* of Windows 10 if your app uses MP3 files.  We’ve resolved this issue in daily build #2682.

   https://developer.coronalabs.com/release/2015/2682

It’s technically a bug in the release version of Windows 10’s DirectX audio decoders.  As in it wouldn’t crash with the beta versions of Windows 10.  But that’s life for you.  :stuck_out_tongue:

#16

2710 is pretty stable. There may be some issues with scrollViews but I’ve not heard any other complaints about it.

#17

Hi Rob,  Thanks for the idea but

#1 2646 doesn’t work on Windows 10

#2 I’ve tried .2706, .2710 and they both are causing me huge problems with transition freezes and physics dropouts. 

I’ll try re-installing 2646 on a Windows 10 machine and hopefully I can build from there, I’ve got some angry reviews!

Thanks, Greg

#18

I rolled back to Windows 7 and .2646 and was able to build and deploy a stable version of my game!

#19

Do you know if you were getting any errors running on Windows 10?

Rob

#20

When I updated Corona with the .2700 series versions Corona ran fine in Windows 10.  The types of problems that I was having were with transitions,such as:

    transition.to(player,{time=400,xScale=.10,yScale=.10 })
     _G.GUI.Set(“cmd”, {caption= "WE SEEM TO BE ENTERING A SPACE-TIME WARP! FA-CINA . . . "})
    timer.performWithDelay(1500, function() relocateplayer() end, 1)

in this example, my ship would shrink down to a dot to enter the black hole, but then it would error out, saying can’t scale by zero.  This code works fine in .2646.  I use quite a few transitions, so I suspect alot of my problems were transition related. 

I tried several projects on Windows 10 with .2646, they all caused a general Corona Crash when launching the simulator ‘Corona has Crashed’  This was before the project was launched.  I tried with 'Run as Admin and using Windows 7 compatibility but it made no difference.

Thanks, Greg