Could Xcode 6 Beta effect app in Simulator?

Hello, when running our app on my colleague’s Corona Simulator, we are getting some odd visual results, which do not occur when we run the app on my Corona Simulator, another colleague’s simulator and on our test devices.

He currently has Xcode 6 Beta installed on his machine, which my other colleague and I do not have. Is there a possibility that this could be reason for the odd results occurring while running the app on the Corona Simulator on his machine?

I doubt that Xcode 6 has anything to do with the Corona simulator.  It could affect the build process when trying to build the app.

Can you describe the problem in more detail?

Rob

@Rob Miracle,
 
Thank you for your response. Here’s an image regarding the issue

 
When making a hole for a puzzle piece to be put into, we typically have something like on the left side of the image (the good version).

My coworker is currently getting the right image (the bad version) on his simulator. We can’t seem to replicate the issue anywhere other than his machine. We’ve tried several different Corona builds both on his computer and my computer. Still, I can’t replicate this issue while he continues to get it.

Would you have any idea why something like this could happen only on a particular Simulator?

Just in case it might help you… we create this hole by taking the related puzzle piece image and using setFillColor(0,0,0,1) to make the black part. The white part is made by taking another instance of the puzzle piece image, offsetting it and giving it a “filter.brightness” effect.

Can you tell me more about his Mac?  Version, OS, what Graphics card is installed? 

What versions of Corona SDK are you using?  Is he a starter account?

Sure thing. So on Pro accounts, it has worked on:

  1. MacBook Pro, Retina, 15-inch, Late 2013, OSX 10.9.3, NVIDIA GeForce GT 750M 2048 MB

2. Mac Mini, mid-2011. OSX 10.8.5, AMD Radeon HD 6630M 256 MB

The issue occurred on the following:

3. MacBook Air 13" mid-2011, OS X 10.9.3, Intel HD Graphics 3000

Most recently we tried Corona build 2014.2332 on machines 1 and 3. But, we also gave 2014.2272 a shot on those devices. On both Corona builds the issue appeared on machine 3 and the issue did not appear on machine 1.

I’m the user with the simulator problem. I made a test app to illustrate the issue. It only happens on my machine. My coworkers can’t reproduce it and it works fine on my device (tested on iPad 3). I’m not sure if I should file a bug since no one else can reproduce this… Basically the brightness filter turns the transparent areas black (running Corona 2014.2336).  When I downgraded to the last public build (2014.2189), the transparent areas turned white instead of black, so that was interesting I guess?  I’ve included screen shots from both tests.  As stated above, my machine is a MacBook Air 13" mid-2011, OS X 10.9.3, Intel HD Graphics 3000.  Thanks for any help.

Can I go ahead and get you to file that as a Bug Report?  Engineering has asked for it…  Can you also provide the System Information for your computer.  We will see if we have a hardware match in the office.

Please post the bug # back here when you get the email.

Thanks

Rob

Bug filed. Case 33481

It looks like my computer only supports Open GL 3.3 whereas my coworkers’ computers support Open GL 4.1.  Not sure if that’s the issue or not, but it’s suspicious enough to note.  Please pass that along to the engineers as I didn’t put that in the bug report.

http://support.apple.com/kb/HT5942?viewlocale=en_US&locale=en_US

We require OpenGL 2.0 or later (well 2.1 is better), so you should be good there, but it could be a driver issue, which is why we are trying to collect information from you.  When we’ve seen issues like this when using advanced graphics filters, its usually the hardware can’t handle a feature we are trying to use.

Rob

I doubt that Xcode 6 has anything to do with the Corona simulator.  It could affect the build process when trying to build the app.

Can you describe the problem in more detail?

Rob

@Rob Miracle,
 
Thank you for your response. Here’s an image regarding the issue

 
When making a hole for a puzzle piece to be put into, we typically have something like on the left side of the image (the good version).

My coworker is currently getting the right image (the bad version) on his simulator. We can’t seem to replicate the issue anywhere other than his machine. We’ve tried several different Corona builds both on his computer and my computer. Still, I can’t replicate this issue while he continues to get it.

Would you have any idea why something like this could happen only on a particular Simulator?

Just in case it might help you… we create this hole by taking the related puzzle piece image and using setFillColor(0,0,0,1) to make the black part. The white part is made by taking another instance of the puzzle piece image, offsetting it and giving it a “filter.brightness” effect.

Can you tell me more about his Mac?  Version, OS, what Graphics card is installed? 

What versions of Corona SDK are you using?  Is he a starter account?

Sure thing. So on Pro accounts, it has worked on:

  1. MacBook Pro, Retina, 15-inch, Late 2013, OSX 10.9.3, NVIDIA GeForce GT 750M 2048 MB

2. Mac Mini, mid-2011. OSX 10.8.5, AMD Radeon HD 6630M 256 MB

The issue occurred on the following:

3. MacBook Air 13" mid-2011, OS X 10.9.3, Intel HD Graphics 3000

Most recently we tried Corona build 2014.2332 on machines 1 and 3. But, we also gave 2014.2272 a shot on those devices. On both Corona builds the issue appeared on machine 3 and the issue did not appear on machine 1.

I’m the user with the simulator problem. I made a test app to illustrate the issue. It only happens on my machine. My coworkers can’t reproduce it and it works fine on my device (tested on iPad 3). I’m not sure if I should file a bug since no one else can reproduce this… Basically the brightness filter turns the transparent areas black (running Corona 2014.2336).  When I downgraded to the last public build (2014.2189), the transparent areas turned white instead of black, so that was interesting I guess?  I’ve included screen shots from both tests.  As stated above, my machine is a MacBook Air 13" mid-2011, OS X 10.9.3, Intel HD Graphics 3000.  Thanks for any help.

Can I go ahead and get you to file that as a Bug Report?  Engineering has asked for it…  Can you also provide the System Information for your computer.  We will see if we have a hardware match in the office.

Please post the bug # back here when you get the email.

Thanks

Rob

Bug filed. Case 33481

It looks like my computer only supports Open GL 3.3 whereas my coworkers’ computers support Open GL 4.1.  Not sure if that’s the issue or not, but it’s suspicious enough to note.  Please pass that along to the engineers as I didn’t put that in the bug report.

http://support.apple.com/kb/HT5942?viewlocale=en_US&locale=en_US

We require OpenGL 2.0 or later (well 2.1 is better), so you should be good there, but it could be a driver issue, which is why we are trying to collect information from you.  When we’ve seen issues like this when using advanced graphics filters, its usually the hardware can’t handle a feature we are trying to use.

Rob