So, after many hours of googeling and doing stupid stuff, I decided to downgrade to 1.6.Why not ask here instead of wasting your time and take bad decisions? ;)
Okay, so the reason why I am still using 1.6 instead of 2.0 is because it wont bloody work on my pc.Do you use the RC? Does it happen with the precompiled examples too?
I have the problem where moving the mouse or pressing buttons makes the app freeze.
I understand other people were having these issues as well, but I don't grasp the idea behind solving this thing.You can try two things:
Why not ask here instead of wasting your time and take bad decisions? ;)Well I saw several topics on the problem and after trying all the solutions offered I didn't feel the need to create a new topic.
Do you use the RC? Does it happen with the precompiled examples too?I did use RC and it does happen with the examples and anything else that is made in 2.0.
You can try two things:I already am making all the images nonsmooth.
- keep your images sharp (image.SetSmooth(false))
- round the view's coordinates to integers
This has made the scrolling clucky, however.Nah, you could still pre-render the map (that is, as much as you can see on the screen, +1 tile left and right) to a RenderTexture and make a sprite of it which again you can move smoothly.
At this point I may have to abandon the sexy smooth scrolling entirely :(
Nah, you could still pre-render the map (that is, as much as you can see on the screen, +1 tile left and right) to a RenderTexture and make a sprite of it which again you can move smoothly.Or you could use the recommended way with a VertexArray which again is a SFML 2 feature. :)
But if I remember correctly, those RenderTextures are a SFML 2 feature... ;)
I'm pretty certain there's a fix for your freezing problem. Try providing a more detailed description of the problem and - like Laurent would say - give us a minimal amount of code that reproduces the problem.