Miserable framerate in recent builds.

Starting from daily build 15.2631, my simulator is having framerate issues. It affects my apps, and all the sample apps too. The frame rate drops to at best a few a second, and often seconds without any frame update. Everything else is working fine, though. If something on screen is set to move, it will be in the right place when the frame is finally updated. So it seems to be a purely graphical issue. Also of note, is that there is no such issues with text fields, which display as they should and update as you type. The notes for build 2631 aren’t too informative, though:

CoronaSDK 2015.2631

Post date:Fri, 2015-05-08 10:53

Release notes for build 2015. through 2015.2631

  • Core: Modified display.newLine() to support fractional stroke widths. (Allows you to set width in pixels whlie content scaling is enabled.)
  • Windows: Maintenance

I’m on windows vista, so I’m assuming something in the windows maintenance has messed things up for me.

What is your video card setup like and have you updated your drivers?

Also, how is the performance on test devices using the same version of Corona to build with?

One more thing… not to poke here, but is Vista supported officially by Corona?  The last update for Vista was in 2009 so it is possible that it is no longer able to deal with some of the needs of Corona, especially as they roll in new features for Desktop.

Please note.  If your hardware will support it, you can upgrade to windows 10 for free. (Users as far back as XP can get the upgrade.)

PS - Before you consider upgrading I’d make sure your drivers and stuff are up-to-date.  I’d also pursue this to its end and see if something else is happening.  Because, upgrading to Win 10 may be free, but if you’re like me, not all of your tools may be compatible with Win 10 and that costs money to fix.

What’s your system? Mac or Windows? What version of OS, what hardware? Roaminggamer, the build notes talk about Windows, but the OP doesn’t state his system is WIN.

thomas6, are you asking the question to whom? hasty, said it was on windows vista.

Sorry, my bad, I didn’t read the line underneath the quote. Vista it is then.

Hasty, I’d suggest updating the display drivers as well.

Thanks for the replies, everyone.

My machine’s an acer aspire with Nvidia GeForce Go 7300 graphics. The Nvidia website suggests I use the latest driver given on the manufacturers website, which does not solve the problem. I tried the latest driver from Nvidia as well, but no good.

Good to know I can upgrade to windows 10, I didn’t know about that. Unfortunately, there doesn’t appear to be any drivers for it, so it probably wouldn’t solve my problem.

I would like to pursue this problem, as you suggest, but unfortunately I really don’t even know where to begin. I’d be grateful if you have some suggestions on where to get started. Thanks.

** UPDATED ** See addtional notes below

That starting point is probably, creating a super simple-test case that replicates the frame-rate issue.  That way, you can verify it with an independent test and then have something to submit with a bug report.

Also, you might consider trying to profile the game and see if there are hotpots are: http://www.mydevelopersgames.com/profiler.html

Additional Notes

  1. You said the sample apps are behaving badly too?  If so, you don’t need to write a test case.  

  2. Are you sure nothing else has changed in your system?  i.e. Did you make any other changes or additions recently.

I have to think more about this so it may be a bit before I can present any debug steps to you.

What is your video card setup like and have you updated your drivers?

Also, how is the performance on test devices using the same version of Corona to build with?

One more thing… not to poke here, but is Vista supported officially by Corona?  The last update for Vista was in 2009 so it is possible that it is no longer able to deal with some of the needs of Corona, especially as they roll in new features for Desktop.

Please note.  If your hardware will support it, you can upgrade to windows 10 for free. (Users as far back as XP can get the upgrade.)

PS - Before you consider upgrading I’d make sure your drivers and stuff are up-to-date.  I’d also pursue this to its end and see if something else is happening.  Because, upgrading to Win 10 may be free, but if you’re like me, not all of your tools may be compatible with Win 10 and that costs money to fix.

What’s your system? Mac or Windows? What version of OS, what hardware? Roaminggamer, the build notes talk about Windows, but the OP doesn’t state his system is WIN.

thomas6, are you asking the question to whom? hasty, said it was on windows vista.

Sorry, my bad, I didn’t read the line underneath the quote. Vista it is then.

Hasty, I’d suggest updating the display drivers as well.

Thanks for the replies, everyone.

My machine’s an acer aspire with Nvidia GeForce Go 7300 graphics. The Nvidia website suggests I use the latest driver given on the manufacturers website, which does not solve the problem. I tried the latest driver from Nvidia as well, but no good.

Good to know I can upgrade to windows 10, I didn’t know about that. Unfortunately, there doesn’t appear to be any drivers for it, so it probably wouldn’t solve my problem.

I would like to pursue this problem, as you suggest, but unfortunately I really don’t even know where to begin. I’d be grateful if you have some suggestions on where to get started. Thanks.

** UPDATED ** See addtional notes below

That starting point is probably, creating a super simple-test case that replicates the frame-rate issue.  That way, you can verify it with an independent test and then have something to submit with a bug report.

Also, you might consider trying to profile the game and see if there are hotpots are: http://www.mydevelopersgames.com/profiler.html

Additional Notes

  1. You said the sample apps are behaving badly too?  If so, you don’t need to write a test case.  

  2. Are you sure nothing else has changed in your system?  i.e. Did you make any other changes or additions recently.

I have to think more about this so it may be a bit before I can present any debug steps to you.