What voltage is a bill acceptor on a TNA?

The mystery spot should occasionally *take something away*. Just to screw with people. "Security walked by, reactor room locked". "Reactor cooled down".

Or perhaps "Never Gonna Give You Up" (and a music change..)

Factory voltage is 110v ac

I installed the v1.3.0 code today, and I noticed one instance where the left sling stayed in the active position for about half a second. It was so fast that it was impossible to know whether it was actually energized or if it might have been a mechanical issue. Anyone else seen this?

I saw it with the right sling during reactor 1, there were at least a few instances where that sling stayed pushed out for at least an extra second.

It also seems like some of the audio changed too? At least when you launch the ball the sound effect seems different. Maybe I'm crazy.

The orbit sound effect is so cool

Are the rubbers on TNA silicone?

Scott,

I installed the code yesterday and one thing that happened 3-4 times is this.

Let's say you have 2 tilt warnings. You then have a ball go into the locks and tilt at the same time. The machine indefinitely freezes up on the tilt screen. It then goes into ball search. Sometimes it unlocks the ball from the lock and continues the game and sometimes it doesnt and the game just endlessly sits on tilt and you have to restart the machine.

I noticed a few changes too. I think my right sling did what’s being talked about...stuck in the out position for a second. Weird.

Also, I think the beginning music is different. Not sure I like it.

My menu buttons inside the cabinet door are now all of a sudden super sensitive...touching button just a little will jump 2 or 3 spots instead of one push moving one spot like before.

Hmm, interesting notes. I will look into these and see what is going on. Thanks for the heads up.
--Scott

For the sling issue, make sure your switches are adjusted properly as it is just firing a PWM to the coil multiple times. This will not hurt the coil as it is not giving it full power. I can look to make a change in the future to prevent this on multiple fires from a flaky switch. The tilt thing is definitely a bug as it should know that the balls are locked in there. It monitors the lock mech constantly and will not drop properly locked balls, but it looks like you found a race condition that I need to find. This is all super helpful.

Also, I did not change the music at all. I did modify the orbit sound effect though.

Thank you again,
--Scott

Please let me know if you guys encounter anything else strange and I will dig into it.
--Scott

Minor bug encountered last night:

A) 2-player co-op game started.
B) P1 is playing, and has 1 reactor destroyed on ball 1. His score is, let's say, 300001.
C) While P1 is still up, I pressed the start button to join the co-op.
D) I was added and everything worked as expected, but...
E) The "1" got removed from the end of P1's score.

The playfield still showed that we were working on Reactor 2, of course. Over the rest of game, P1 destroyed another reactor or two, and his last digit increased each time but was always -1 from where it should be.

I'm not surprised that this wouldn't have come up before.

While we're talking code, here is a minor feature request.

When entering intials, press both buttons to go to End.

I reported this to Scott directly via email last night

This bug has been in for a while now and I am surprised 2 people caught it within a couple days of the new software! Crazy. Thanks for the report, I will get this updated in the next release, which will most likely just be a minor bug fix release. I am going to wait a bit though to make sure there are no other bugs in the game. I appreciate the non use of pitchforks here, I do not have a huge team of people helping me test.
--Scott

Dave reported it to you based on me reporting it to him last night.

So, we're only talking about 1 incident.

Ohhhh, that makes more sense. That was so close to one of my test scripts, just without the reactor blowing up thing.

I would contact service about that PC issue as it looks like the PC is losing power on you...

thanks scott for the code update! i took the opportunity to check my starposts and to install the rubber washers i ordered from amazon!

i have some slight playfield damage in the high impact area around the target bank, also the rubber next to the scoop was starting to crack and this starpost showed some cracking and was replaced. installed new purple rubber sleeves too.

i also found some damage beneath the starposts on both slingshots. the rubber washers cover it up perfectly though and i think it's going to contain the damage in the future. game number is 106.

have to say it does not bother me at all, i have way too much fun playing this baby than it can be dimished by these small cosmetic flaws

1E74986C-4137-4E94-8E75-E58DD8A96894 (resized).jpeg

4E157302-699D-4B67-8DDE-F30FB7F27C98 (resized).jpeg

C8EDCFC0-0DE1-41E7-BA9A-9624380946BD (resized).jpeg

DFAB7E69-90E2-43C7-A644-B3E278A1F3B6 (resized).jpeg

Yeah, please keep me updated so I can continue to discuss it with the cpu manufacturer

Correct URL for Spooky is spookypinball.com not spooky.com and I agree that their website seems a bit outdated. But hey... in their defense, they have the best website in Benton, WI!

I've played a bunch of games on the new code now. 1 issue I've seen so far is the left sling stuck on for longer than normal...good extra second or 2.

Yeah, I have a few more reports of this as well, but not on everyone's machine. How often is it happening? It is not dangerous to your machine since I am using a pulsed signal for the coil, but it seems I need to adjust something called a debounce for this to ignore flaky switch hits. I will put out a bug fix patch for this in a week or two.
--Scott

I've only seen it once in about 10 games. But def an issue as I've seen a few people post about it, and I've never had it happen in over 500games before the code update.

We use debounce timers often in industrial automation programming. Basically, it’s a couple hundred milliseconds delay to make sure a process has been making a position switch before actually calling it at position.
Think of something actually physically bouncing and momentarily making a switch until it settles down and steadily makes the switch.

Please contact me via PM as I am unable to replicate this. Thank you,
--Scott

EDIT: Please also double check the version number you are on as this was an issue in earlier versions.

Seems like the damage to the playfields is from the star post being over tightend. You can tell from the indent on the playfield.

If anyone is having the slingshot issue and willing to try out the new beta code, please let me know if the updates I made eliminate the issue. Unfortunately, this is not happening on games I have access to, so I cannot replicate.

http://www.scottdanesi.com/?page_id=1724

Thank you,
--Scott

Game #333... My left slingshot started acting up right after the update.

Yeah, there is an issue in the code for certain machines, nothing dangerous. Please give the new beta code I just posted a try and see if that resolves it, if it does not, I will go nuclear on the issue.

http://www.scottdanesi.com/?page_id=1724

Thank you,
--Scott

I had the left sling issue a little bit ago, and also had something happen that never has happened before. Volume increased on its own up to 8 from 3 and 4, 3 games in a row after ball 1 or 2. Haven’t had it happen since.

I'm installing new beta now....

Only happened once in 24 balls, lower left reactor sling (video attached). Vastly improved, didn't encounter any on the lower slings.

I've had a few lock rejections, might be a Drop Target #3 issue? If I try to park one immediately after lighting locks, it will knockdown #3 rather than raise #2 (video attached).

Awesome! Thanks for the videos. So it still did happen with the new Beta v1.3.1.b1 software? If so, I may have to rework what I did for the v1.3.0 release...

The lock rejection is caused by the CPU not reading and responding to the opto beam quick enough. This happens once it a while if you really shoot it in there at full speed. I have seen this on my game, but there is not much I can do about it. There is even a stat in the audits to say how many lock rejects are happening. The software does it's best to keep this from happening, but it still can happen rarely.

If the lock rejects are becoming an issue, I can modify the lightshow to reallocate some of the CPU usage.

Thank you again!!!
--Scott

Occurred just the one time in v1.3.1.b1, much less than before. Happened right when reactor went critical too, not sure if that would have affected it. I'm going to try going back to the stock rubbers as well…the airball situation has mellowed considerably since adding the washers and updating the code.

Thanks for clarification on the quick lock shot. Felt like an "it's only pinball" sort of situation, glad to have that confirmed.

Thanks so much, Scott!

Do I have the new beta code world record? Mine hasn't done anything strange yet on new beta code. My righthand reactor sling was machine gunning a few times, but it probably just needs a leaf adjustment, one leaf looks like it could be a little to close I suppose.

20190106_145702 (resized).jpg

Oh ok, I am going to try one more thing before I scrap the new sling logic and start over. I will be uploading beta 2 tonight.

Let me know if the lock rejects during reactor critical become an issue. This is actually a CPU limit that I am pushing right up against. The compromise would be the lightshow during reactor critical would just have to pulse instead of move from bottom to top. I am still going to look into how to improve the performance other ways as well.

Thank you again for the help!
--Scott

Holy crap! 5.6 million???? You cheat Dr Jones.

Ha 7 reactors is my record on old code. I can play

I think the key thing here is that some games the sling switches are so tight that they machine gun and it is throwing off my new logic and pulsing out the sling. Please try and adjust the sling switches and let me know if it still happens. This may just be what the machine gunning sling looks like with this new pulsed code. That adjustment I made in the current beta code should help greatly though.
--Scott

Find me at a show, I can talk a bunch of friendly shit and probably get my ass kicked. I challenge you to a dollar game.

--Scott

On the beta before this I had the left sling stick on like in that video above, not machine gunning. Just to be clear

I'll adjust it and play some more tonight. I haven't had a sling stick on yet with newest beta.

Sweet, I'll give the b2 a test run when it's ready!

The lightshow coming out of the right scoop is mind blowing every time, BTW. I'll keep an eye out for odd behaviour during critical reactors.

I did notice some machine gunning, assumed that's what it was doing instead of staying stuck on now. Adjusted the switches to be bit less sensitive.

Happy to help, you're most welcome!

Default settings and outlanes? Wow.

You know, I think this is where I am going to leave it. In the current Beta (b1), if they machine gun fast enough, it just looks like it sticks. This should be rare, but it is indicating that a switch needs to be looked at.

Before I release an official patch for these bugs, I am going to wait a little bit to see if any more issues roll in. I am hoping not. (crossing fingers)

Thank you all for the help and feedback.

--Scott

Yeah I am definitely challenging him to a dollar game. I will report back how bad I got burned.

Is there a leaderboard for solo 4P co-op?

IMG_8629 (resized).JPG