Official

iGP Manager 3D - Bugs mega thread

There were specific reasons this update in particular was slow on Apple. They recently made drastic changes to how user data and privacy is handled. You will find many articles about this online, like this one. That impacted all developers and created some extra delays on iOS. We had to spend extra time complying with those new regulations in this update because it arrived at the same time as those changes, plus the review time, so that was the reason it was delayed relative to the Google Play update.

We are really focused on one issue in particular now - that is the reported crashes on Android. We can see that it has impacted a lot of users on lower end devices, and we are making good progress in to this today. That's the last critical "bug" type issue we have to get on top of before we can focus on gameplay.

I have begun compiling information on tyres, overtaking etc. and work will start on this soon. Starting with a clearer picture of what needs to change and how, we'll be able to make faster changes to balance gameplay. Frankly, it was unintentional that the update had some of the effects it had, but changing tracks and racing lines has obviously created a a series of outcomes (mainly near level 20) which will require rebalancing. That's coming in to focus now that we're wrapping up the initial patches on 3D.

EDIT: As you may have seen, we are also hiring to get more hands on these patches and updates so we can start bringing them to you sooner. I want faster progress and I know you do too, so I'm doing my best to strengthen the team in the areas that need reinforcements so we can pick up the pace.

A dev is assigned to work on this and it likely also has links to the way cars cut the corners on some tracks. While there is an accordian effect in real life too - at slower speeds the cars are closer and at higher speeds they are further apart - anywhere it doesn't seem accurate or true to the simulation / timing data is where we can find improvements.

My understanding is that it's a balancing act for the developers in that area to get the cars moving smoothly and accurately. It's easy to have smooth inaccurate movements or jittery accurate movements, but smooth and accurate movements are hard to achieve. It also has to compensate for any instability in the internet connection, which there can be a lot of on mobile networks. Imagine how much smoother car movements need to be with the resolution we offer now, and that makes the balancing act with accuracy that much tougher.

This is the simplest explanation I can give, because it's not simple, it's very complicated. We understand the challenge though and what needs to change to get higher accuracy. If there is too much "accordian" then the smoothing needs refining. Now that 2D and 3D are in sync anything we improve in one will also be improved in the other.