(Topic ID: 162838)

AcDc premium amazing un-believable bug.


By rai

3 years ago



Topic Stats

  • 10 posts
  • 9 Pinsiders participating
  • Latest reply 3 years ago by rai
  • Topic is favorited by 1 Pinsider

You

Linked Games

#1 3 years ago

A few months ago I began to have an issue while playing on the lower PF on AcDc premium.

whenever I would be in the lower PF the kicker would fire constantly (well only when I was hitting a flipper) if I didn't hit anything, the kicker worked fine just kicked the ball whenever the ball was in the trough. But when I was playing the ball not in the trough I would hear the kicker firing constantly.

So I have several good Pinside friends and they were all good enough to help me out. First people said it sounded like an opto problem so we re-flowed them and finally after talking to Stern support we ordered new opto and new opto board. The weren't sure either but this was what they thought.

Still nothing, then I had another Pinside friend over thinking we were overlooking something. But still it was the same thing. we were thinking maybe a vibration or a lose connection or maybe a bad driver board. Anyway we were stumped. Then we had yet another Pinsider this a pinball tech and electronic tech. We were on that problem for hours, couldn't find what. Only clue was that the error didn't occur when we were in test mode, everything was ok, but whenever we played the lower PF we got the constant kicker.

Finally, the last tech said (as he was leaving almost as an afterthought) that it sounded like a software error, he didn't know what but suggested I reset the factory defaults or maybe load the latest code (I'm still on 1.65 because my song modifications).

I just reset the settings to factory default and the bug went away, everything is working fine.

The last settings I changed, were that I lowered the voice and raised the music settings. And probably that caused the bug. I can't even recall what the settings were.

Maybe I'll fiddle around with the sound levels and see if this is re-producible but I'm just glad to have the pin back in ship shape.

I'm thankful for all those who helped me. But I'm so puzzled how such a thing like that happened. It's very bizarre.

#2 3 years ago

That's one dramatic thread title.

Cool your pin works, but until you can reproduce it by changing your settings, it's not a bug.

#3 3 years ago

Good reason to always use the latest code

#4 3 years ago

I read your original post and unfortunately I could not think of anything to help you ? I could not wait to see what the outcome was. So glad you got this back to normal!!!

#5 3 years ago

You are running modified unsupported software and you imply it's Stern bug

#6 3 years ago

There was also some kinda video mode examples that was done using pinballBrowser that would activate when balls went into saucers, scoops, etc...
Maybe the rom you had previously, had some tweaking done to it?

#7 3 years ago
Quoted from gtxjoe:

You are running modified unsupported software and you imply it's Stern bug

The game code is exactly the same no matter what song is playing.
Still not saying it is a bug. But I highly doubt a song change would cause it.

#8 3 years ago
Quoted from Arcade:

The game code is exactly the same no matter what song is playing.
Still not saying it is a bug. But I highly doubt a song change would cause it.

Unless the function, class, variable or object names used in the custom code conflict with the base code's programming.

#9 3 years ago
Quoted from Arcade:

The game code is exactly the same no matter what song is playing.
Still not saying it is a bug. But I highly doubt a song change would cause it.

Wrong.

When you change a song, you are injecting a new song into the code base. In theory that's all that should happen. But there is a lot more to it. In some cases pointers get changed and memory locations for things altered. That alone could cause this. Not to mention, earlier versions of pinball browser didn't calculate crc and you'd get a programming error on flash that you should ignore. It's possible there was a real programming error in this case.

Also due to the lack of crc, defaults weren't loaded causing the nvram to be out of sync with the code. That can also cause general memory corruption. My guess is that was the real culprit here.

This is definitely not a stern "bug". On non modified software update, the crc would be verified preventing bad code load. And the factory settings are restored on each update - which that alone was the solution to this problem.

#10 3 years ago

I didn't say it was a Stern bug, a program bug that (it appears) was only influenced by a setting in the menu (my case was voice or music volume level). It just seems so unrelated in my mind and a lot of other people too were thinking along the line of a hardware bug or even a mod that might have some electrical feedback to the kicker mechanism.

I mean the modified code works fine except in this one instance I described (I mean the music level change). I never even considered that a menu setting could cause this type of behavior, as the menu setting is not related to the lower PF or the kicker.

Just goes to show me that these games are extremely complex. We much prefer when there is an obvious problem like I need new opto or something like that. This was maddening to diagnose.

Promoted items from the Pinside Marketplace
$ 9.95
From: $ 40.00
Lighting - Interactive
Professor Pinball
$ 90.00
Lighting - Under Cabinet
Rock Custom Pinball
Wanted
Machine - Wanted
North Mankato, MN

Hey there! Got a moment?

Great to see you're enjoying Pinside! Did you know Pinside is able to run thanks to donations from our visitors? Please donate to Pinside, support the site and get anext to your username to show for it! Donate to Pinside