fast moving objects in 2d - horrbile ghosting, blurring

together with my son we are building a simple physics based game similar to the classic Pang game. All is going well, but we have serious issues with ghosting/blurring of the sprites. If we just take a single sprite and bounce it off the bounds of a screen we see horrible results. If we use Construct we don't see the ghosting. I don't even really consider this to be fast just a sprite with a gravity scale of 1 or 2 and we see poor results. Increase this to 5 and its pretty awful

We have read a lot of documentation and forum posts and whatever we attempt, eg set interpolation, fix camera size to match our resolution etc etc we cannot get any good results. Could anyone help us out, or maybe point us in the direction of some examples

 

Can you make a video showing the ghosting effect? I guess you mean there is some kind of visible trail directly behind the moving object.

 

hopefully this link works! http://1drv.ms/1tm5UH4

I get this effect on 3 different monitors and 2 different laptops

 

The video says it cannot play here. and also there is another video showing up at the bottom of the page with kids in it. You may want to remove that one or edit your post to remove the link. Unless you are fine with the other video being there too.

 

google chrom can open video, but i dont know what to do against ghosting. Maybe camera Clear Flag set to Skybox (if it is not)

 

To me it looks like your monitor has a slow response time. There's nothing in Unity that does this inherently and I've never seen anything similar personally.

--Eric

 

ok thanks for the feedback. But its odd we don't see the same behavior in Construct2 with similar moving objects, and it happens on 2 different laptop displays and 4 different monitors. Oh well maybe we will just add trails to the balls to mask the effect.

thanks for that, don't know how that got there!!

 

Unfortunately many monitors/display have a slow response time... even if the refresh rate is supposed to be 60z for example, instead of taking 16.7 milliseconds to completely remove a pixel color and replace it with another color, it can actually take several frames before `residue` from an earlier frame is completely eradicated. For pixels especially that are transitioning from high contrast, i.e. the value has to go from high red to no red, or a bright color on a black background for example, you can see several frames of ghosting. As you've found, it especially applies to fast moving objects, which makes it SUCK for fast 2D games. That blur can look like a motion blur, but unfortunately it also washes out all the smaller details of an object when it moves fast. I almost had to stop working on a game I was making because the blur was so horrible on my tv screen. If you go with a lighter/mid-tone background that can help some. It's especially bad with high-contrast colors.

I'm curious if you truly get zero ghosting from Construct2... are you absolutely sure it's exactly the same experiment, framerate, etc? If there is a way to get rid of this blurring I'd like to know about it. But I fear it's mainly the result of poorly responding display hardware, which unfortunately was not in the manufacturer's considerations when they decided to come out with all these flat panel things.

 

This is ghosting and if you're using the same images in construct, then it means that construct is either running at a lower framerate or its some sort of vsync thing.

 

With sync on or off I see the same effect. One way to diminish it a bit is to run at 30fps instead of 60fps... it `holds` the frame twice as long so doesn't streak as much, but then you notice the slight stuttering of the playback.

 

We've run the simulation again in Construct and in Unity and it seems like Construct is slightly better. we will change the graphics and see how we get on with that. Construct is quite nice but I like to write code

 

Does anyone have a solution to this? I have the exact same problem and I can't figure out how to fix it.

 

Get a faster monitor. Not being flippant; it's a hardware problem and needs a hardware solution. (Alternately, some monitors have an overdrive mode which makes pixels change brightness faster, at the cost of overshooting, which causes a different kind of artifact, but may look better in some cases.)

--Eric

 

I'm having a very similar issue. I'm making a mobile game, I imported the game to my samsung s3 and there seems to be no ghosting effect on the moving ball. I imported literally the same game on an iPhone 6 (expecting it to have a MUCH smoother play), it has a continuous ghosting effect somehow and the ball isn't even moving that fast. I don't understand how to fix it. Any help would be appreciated.

Thanks in advance.

 

Hi
I have similar problem but for me it's 100% not hardware related problem as mowing sprites seems to burn into the background. They are blurring when mowing but also leaves permanent almost invisible trace of it. I can see it looking for different angles.
All shadows disappear when I stop the game.

 

If you're able to capture that from the screen pixels themselves (ie not a photo of the screen) then its definitely not your monitor. Could be the buffer isn't getting cleared properly?

 

I know this is an older thread but for anyone who stumbles onto this issue I can suggest something that made it far less an issue for me. At the beginning of your game set the target framerate to 60. (Application.targetFramerate = 60; On a DontDestroyOnLoad object.) Hopefully this helps some of you!

 

That's not really a good idea, considering that 120Hz and greater screens exist, and will only become more popular. Don't hard-code framerates into a game; anyone who's expecting 120+ fps will be understandably annoyed if you force it down to 60.

--Eric

 

Sorry, the frame rate is set by default to 30 for iOS from what I understood. My issue was that setting was too low and it was playing at high rates on other platforms. It would be rather annoying if the platform could perform better and it didn't. Thanks for the input. I'll adjust it so it only happens on iOS.

 

iOS does 120fps, on the iPad Pro models.

--Eric

 

Anyone Got Solution?

 

Get a screen with a faster response time. It's not anything caused by Unity.

--Eric

 

Got the same problem 2020. It's weird because I haven't noticed this in other games apart from Terraria when the player runs fast... But I guess it must caused by high color contrasts together with screen with low response time (although my screen is very new and wasn't cheap).

 

This was just discussed in another topic and it was established that Unity does not in fact somehow magically add a blur effect. That would take a specific effort and can't happen on its own. If you take a screenshot (rather than taking a picture of the screen with your phone), you won't see any ghosting. It's an inherent problem with most LCD panels, expensive or otherwise.

--Eric

 

This is same think happening in my project, when a 2d ball moves in a speed above 12. I tried lots of ways to but neither of them is fixing my issue. Help Me if anyone one can.

 

Stop reviving old threads. Create your own please with more information than pictures.