Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 241 Big Data Appliance
- 1.9K Data Science
- 450.4K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 546 SQLcl
- 4K SQL Developer Data Modeler
- 187.1K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 443 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Java Puzzle Ball Basic #10 Bug

Blue bumper and rotation wheel seem to have a bug. Placed rotation wall and blower in their respective slots on the blue wheel. Not sure what I did. The blue wheel showed the rotation wall and blower but the bumpers did not have any wall or blower attached anymore.
Setting the ball in motion ended up with the ball getting stuck in the first blue bumper in its path. No deflection obviously due to no walls being present. The blue bumper continued to emit a sound until I clicked stop.
Any idea what could cause this?
Best Answer
-
It's ok. I appreciate the help with the research and debugging. I don't think we'd have to go any further, since there's enough good data suggesting the bug is super rare. If I has to guess the cause, I'd have to say it's some weird and obscure concurrency issue where the game can't remove the collision lines because it believes it's already removed the object... I used to be able to recreate this bug by dragging an icon really fast, back and forth, over a slot. I've tried to smarten up the code since then
I think the collision detection lines for Duke only extend two boxes. In other words, a rectangle stretching from his feat to the tip of his head. The solution to this puzzle means you'll get to hit Duke between the eyes.
There's a secret way to clear the save data. This can be done by going to the credits screen and pressing Esc on the keyboard.
Answers
-
The blue bumper is outside the path of the balls initial trajectory. The only thing I can think of is the rotation wall was not showing on the game area.
-
Odd... Could you post a screenshot? There is a very rare bug where bumpers sometimes retain a behavior, even after an icon is removed from the wheel. Maybe that's what occurred?
-
I am trying to reproduce it, but like I mentioned I am not sure what I did or clicked on to get this effect. Will keep on trying and try capture screenshot. It was weird.
-
The strange this about this is that the icons remained in the wheel slots. They had not been moved nor did they appear in the initial placement slots at the start of the puzzle. It was just that they were not visible on the play area but may have had the effect you described earlier.
-
-
Trying to get the game to repeat the problem is proving to be as difficult as solving this puzzle. I have tried clearing out the save files to start from a clean slate but to no avail.
-
It's ok. I appreciate the help with the research and debugging. I don't think we'd have to go any further, since there's enough good data suggesting the bug is super rare. If I has to guess the cause, I'd have to say it's some weird and obscure concurrency issue where the game can't remove the collision lines because it believes it's already removed the object... I used to be able to recreate this bug by dragging an icon really fast, back and forth, over a slot. I've tried to smarten up the code since then
I think the collision detection lines for Duke only extend two boxes. In other words, a rectangle stretching from his feat to the tip of his head. The solution to this puzzle means you'll get to hit Duke between the eyes.
There's a secret way to clear the save data. This can be done by going to the credits screen and pressing Esc on the keyboard.
-
Purely for curiosity I will try and get the scenario to repeat itself, knowing it may take a lot of footwork.
Thanks for your responses.
I must compliment you on the humour in the program when you click on Duke. "Ha ha, That tickles!"