![Game Developer Logo Game Developer Logo](https://eu-images.contentstack.com/v3/assets/blt740a130ae3c5d529/bltb8149045ecc9add6/664670498df30a26f54d5ed4/GDBlogs_Logo_FINAL.png?width=700&auto=webp&quality=80&disable=upscale)
Featured Blog | This community-written post highlights the best of what the game industry has to offer. Read more like it on the Game Developer Blogs or learn how to Submit Your Own Blog Post
42 Problems and a Fix Ain’t One: Fixing Tokyo 42’s Camera
I discuss how game developers should approach receiving feedback and solving problems, in the context of an attempt to address issues with Tokyo 42's camera
![](https://eu-images.contentstack.com/v3/assets/blt740a130ae3c5d529/bltba62518415cda0e2/652fe6ddbc479f8697ef691f/default-cubic.png?width=1280&auto=webp&quality=95&format=jpg&disable=upscale)
When there’s a problem with your game, there are four questions you need to ask:
Can I solve the problem?
Is the problem worth solving?
How do I solve the problem?
How do I communicate the solution?
Here’s a look at an issue with Tokyo 42 and how its developers, Sean and Maciek at SMAC Games, attempted to deal with it.
We posted a really significant update to the game yesterday. Here’s a video:
This update takes a meaningful step to address one of the most common criticisms of the original game. I’ll let a selection of reviewers and users describe it:
“I’ve died many times purely because the camera got in my way.” (Alec Meer, RockPaperShotgun)