So, I was playing a game this morning through 2D Sim. I let it run at speed #7, and I pause on all stoppages. I do my own subbing, etc. I was leading in the game at about 5 minutes into the 2nd half, 65-47. Then, the strangest thing happened: We were on my end of the court, and when my guy shot the ball, it went to the OTHER END of the court (their basket). It gave my team the points though. Then, WE got the ball in bounds under the basket. The rest of the half went like this - other than sometimes we shot to our basket, and sometimes we shot to theirs. No matter what though, after we made a shot, we got the ball. The final score was 137-47. I'm thinking it has to be some bug in the logic, but I'm unsure. Because this is my very first season, and first time playing DDSCB, I'm unfamiliar as to if I might have done something to cause the problem.

Sounds exactly like the bug we have reported at speed 10 where the same thing happens. I don't think anyone has reported it happening in your scenario though.

Was it after a technical foul?

Come to think of it, I believe it DID happen after a technical foul was called. I'm not sure, but I'll be watching closely in the future.

I had this happen (on speed 10) but since getting the 1.2 full patch haven’t experienced it. It always happened after a technical, and the only way I would be able to get back to normal is either restarting the game or getting another tech.

Are you running the 1.2 version of the game?

Hey Gary - I *think* I was running 1.2. I have ensured that I am now, and will watch for the behavior again. It might have been that I hadn't applied the update properly, but I didn't look at the version number before I reapplied the update. Sorry! If I see it again, I'll post it here.

So were all the bugs fixed playing the game on speed 10? I thought i read someplace there was also an issue when a player would be left in the game after fouling out playing on 10 speed... are all the bugs fixed with using this speed including the blowout after technicals? I am using version 1.3

I haven't had anything else reported to me since the 1.2 update