Sorry about My English.
I developed 2D Platform game using Unity and its work perfect on Android and I publish it.
when I switched platform to iOS and test it on device the player run very very VERY SLOW when it on platform, but when player jump and try to move left and right while jumping its perfect move.
Help Please
So if I understand well, this is a side scroll game ?
And the 'slowness' problem happen only when you move on the ground ?
What do you use for the movement, a RigidBody2D ?
In that case perhaps you should look the settings of physics frictions.
Say me if that help
Related
When building a game with SpriteKit, with a platformer game (like Doodle Jump for example), is it preferable to move the camera up, or the background nodes down ?
What is the standard practice in other frameworks ?
MOVE THE CAMERA!!!
One of the weirdest things about 2D game engines is that it often takes them a series of versions to get a camera.
They should be born with them.
SpriteKit was no different, it took forever to get a camera.
Now that it has one, never ever think of not using it.
Will make your life a million times simpler.
I can think of no exceptions, but look forward to being proven wrong.
move background was HOTFIX until proper cam support added.
use the cam. its easy and fun. no reason to not imo.
I just want to say thanks in advance for anyone you can provide some help on this we're completely stuck at the moment.
Project Scenario : -> 2D side scrolling game with simple 2d sprites -> Camera is orthographic and stays in its place (camera doesn't move) -> My Character (A camel) is also static and does not move. -> The sprites (Platforms) move from right to left (movement done by script) -> Project Video is uploaded here (running on iphone5). It clearly shows the small hiccups and jerks.
Issue : The game works very smoothly on Android devices and Unity Editor (no spikes on the Unity profiler as well) But, when i run it on iOS devices (iphone5, iphon5s) the motion of my sprites is jerky. Like it will move smoothly for like 1 second and then a small hiccup/jerk of a split second occurs. This results in lag and lagging motion of the game which is very annoying as i am unable to get the right quality for iOS.
Things i have tried : -> I have studied many possible solutions on various threads and forums but none issue seems to be working for me :-( -> I have tried different scripting techniques like use Lerp function for movement, tried putting the code in LateUpdate and also FixedUpdate. -> I also turned off vSync in project Quality settings but no luck :-( -> I also tried the movement without the script by making an animation of the sprites to move from right to left. -> I tried making the project from the latest Unity 5.1 as well but still the same lag :-( -> I tried reducing the sprite sizes to very low (low quality pixels) but still issue prevailed. -> I also tried to change the camera to perspective view to see if it reduces the jerk or not
I am sure lots of other people around must have faced this issue while making a 2D game of such sort. I hope someone must have overcome the issue and can please help me with this. This has been an issue with me for long now ...
I would really appreciate any help ... any new technique in unity or any better optimised logic of making such a 2D game in Unity. Thanks.
Looking forward to everyones input.
YOUTUBE LINK TO VIDEO FOR REFERENCE - https://www.youtube.com/watch?v=cnST1QzoDw4
So we've built a game where the player is jumping (on-tap) and needs to go thru moving obstacles (from the right to the left and vice versa) without hitting them.
We had everything clear and no lags and lately we've started to see some random "lags attacks", so you can jump like 500 times without any lags, while sometimes you can start the game and experience lags straight away.
I'm assuming that this has nothing to do with how we draw our obstacles nor with how we handle the graphics overall but with some background process going on.
Language and Engine: Objective-C, Cocos2d with Chipmunk.
Currently running the game thru: TestFlight.
Tested devices: 3 different iPhone's 5
EDIT:
So we've tried disabling all the external libraries and SDK's, Lags are still there.
I have a made a game for the Xbox 360 using XNA and whilst testing the game the screen seems to dim every 30 seconds. The way it dims is as if I have been away from the Xbox for a while. If I press the Xbox guide it goes back to normal. I've tried googling this issue and i've found a few people who have had the same problem but I couldn't seem to find any replies on those posts. If anyone knows what the issue is and how I could fix it it would be of great help as this is the last kink i'm trying to resolve with my game.
Just to convert my comment into an answer:
Many modern TVs and some monitors have a "dynamic contrast" feature where, if the displayed image is predominantly black, the intensity of the backlight will be reduced.
(Often it's really annoying, just making high-contrast black-background scenes go dark for no reason.)
The backlight can also be turned down as a power-saving feature, kind of like a screen-saver.
You could test on a monitor without this feature, disable this feature in your TV settings, or use a scene that isn't so dark.
I'm writing a 3d car designer ipad app and I want to add a little "life" to it. I want it to be similar to what "3D Car Builder" iPad app does, in that from the moment the app starts, there's just the slightest amount of "movement" in the scene. Even if the iPad is sitting on the table, there's movement going on.
I'm testing on a 1st gen iPad, so whatever they've implemented, works on my device. I have (iOS 5 installed). I've looked up several things, thinking this was developed with the accelerometer, or possibly magnetometer, core motion of some sort...I can't figure out where to start. It might something as simple as moving the 3D scene in the x direction for a small amount, then y-direction, the negative x, then negative y. I dunno, it's something simple.
Anyone know how I/they might have implemented this?
Okay, nevermind...I figured this one out. Worked great using CCActionInterval