We have a really weird bug in out game where when we upload it into Beta and send it out through test flight, so phones play the game as intended and other phones have a weird issue pictured below:
From the image you can see the problem. One it does a ghosting type of thing with the characters as they move. Two, it acts like no scene is actually closing, but keeps stacking them on top of each other.
This problem does not occur on iPhone 6s or iPad Pro. It also doesn't occur on Android. We have only seen it on 5S and iPads.
We have looked at versions and that doesn't seem to be an issue either. We are using Unity 5.3 for this build (we reverted to this build as we felt it was the most stable, just to make sure that wasn;t an issue)
Anyone have an idea of what could be causing this problem?
Keep in mind that the things that are being seen are in different scenes.
in your camera settings you probably set clear flags to Dont clear set it to Depth only
Related
I have developed a small dice rolling app using SceneKit. While everything works correctly on device my dice nodes are shown as black shapes in the simulator. This used to work fine before but I stopped working on the app for a year and Xcode updated since. You can find screenshots of the issue below.
I tried using an other version of Xcode (11 beta). I tried deleting everything Xcode and Simulator related and reinstalling. I tried disabling every fancy effect on my dice nodes but nothing seems to have an impact, the issue really seems to come from the simulator rendering.
As anyone ever encountered a similar issue? Any help on how to fix it would be appreciated as I use Fastlane Snapshot to generate new screenshots when I release.
Simulator Screenshot:
Device Screenshot:
I made it work by trying random stuff: the culprit seems to be my SCNLight node that lights the scene. My light type was set to .spot but if I set it to something else my dice appear correctly in the simulator.
I've developed a game in Cocos2d-X for iPads. I've tested it on several iPads and it worked great but after I published it to the App Store a few users complained that the game is completely unresponsive, meaning, all the animations are running but the game doesn't respond to touch events.
I have tried reproducing the problem but even if I use the exact same device with the exact same iOS version I still can't reproduce it. All the users who complained are running various versions of iOS9.
I have quite a few installs so it appears the problem only affects a small percentage of my users, but it still affects them. And for these users the game is always unresponsive, no matter how many times they run it or install\uninstall it.
I'm working with cocos2d-x 3.6.
Did anyone encounter such a problem or have any idea what might cause it?
Thanks!
Strangely enough, the problem was the MFMailComposeViewController. I mistakenly attempted to allocate it at startup without checking its canSendMail method. Apparently in iOS 9 it causes some kind of problem that blocks touches to my app.
I followed this tutorial for the first short bit on setting up a basic 2D game engine: Basic 2D Game Engine Tutorial and completed the first bit to render a basic image to the screen. It works fine on the iPhone 4s and iPhone 5 simulator but not any simulator newer than that.
I decided to download his finished project to see if it works on the newer devices and it does. To try and figure out what was wrong I slowly deleted everything to the bare bones on his project and it still worked.
The next thing I did was delete everything in his project and ported over my code into his project directly. It still renders the image fine! So now I have two X-code projects running the exact same code (I could change code in one project and it affects the other one.) Despite this it still works in one project on the iPhone5s+ device simulator but not the other one.
They both work fine on the iPhone 4s simulator (I changed the background color just to prove they are both running on the same code.)
This seems almost silly to me, they are running the exact same code and all of the settings are identical. Does anyone have any idea what is going on that could make OpenGL-ES not work on specific device simulators?
It might be some 64/32bit issue. Look for areas where you've cast pointers or where you used float instead of CGFloat.
I'm writing a game using sprite kit, first time so mistakes are inevitable :)
So running it in the simulator when certain events happen it's quite laggy (fps drops to 11 or less).
So I decided to see what happens on a real iPhone 5S.
Things run a little better: still lags at those events but not as badly.
However quite a few of my labels are missing: they appear fine in the Simulator but are completely missing in the physical device (just empty space where they should be).
Running ios8 in the simulator (5S) and on the 5S, code written in Swift.
Any hints at what I should look at?
Well, first you should try to isolate the problem. Try and see if the labels are indeed hidden or if they are behind a view. Download a hierarchy viewer such as Reveal App and try and find the UILabels. If they exist in both, the hierarchy viewer and the Simulator but not the physical iOS device, try and upload it to a different device. If it happens on the other device too, something is wrong with your code. We cant help unless we have something to work with. I recommend looking at https://stackoverflow.com/help/mcve to help with writing good questions.
I am currently working on an iPhone app where I use 2 main timers that make the game work as one piece. The only problem I've encountered so far is that when I run it on the iOS Simulator from Xcode the game seems to lag a bit, and all of the animations run slower. I'm not sure if this is a memory issue, but isn't the iOS Simulator supposed to run just as smooth as the iPhone? When I run it on my iPod Touch 4th Generation, I don't encounter this problem. Is there a way I can fix this, or does anyone know why this happens?
The frameworks are designed to work with specific hardware on device for graphics acceleration. This is not present in the simulator, so you'll see diminished performance on graphics-intensive applications. You might however see increased performance in the simulator in non-graphics related areas. The bottom line is always test on real hardware - the simulator is just a convenience.