With me it is the right flipper, usually once every time I play straight jacket with stacked multiball.

But in my Case it's the whole Ball Long... every 1-5 Seconds it changes the Flipperpower.

I'm not sure If I should buy a meanwell powersupply and test this one.

Or the machine i played Had a New Beta Code.

At the Moment It's very Strange and I hope it can be fixed cause i Like this game and don't Want to sell it.

I dont think it's all power related.

I think its driver congestion/log jam.
Some operations are interrupting the instructions to the flippers.

More power can make a computer faster or more sprightly and handle a bigger load but, it's not the whole picture.

Maybe driver optimisation or faster memory, or faster computer.

This can happen with the 3d printer I have (Ender 3). The solution appears to be slightly slowing down some operations, which could apply in this case by allowing the flippers to override at all times, and always keeping the available power to a level that can tolerate continuous flips.

That was also an Idea. Maybe it helps to Gear Up the Computer like the Dialed in where it helped alot

I absolutely love this game and I've been hesitant to post this because of that but it really does need a pretty significant code update. It does not seem to do a great or even adequate job of really tracking how many balls are in play, how many should be and correlating the two. It also should have some better logic with regards to certain events. I keep my game extremely well maintained and it's in my house not on route (never has been) but if I'm playing a marathon session, have league or friends over, etc. I will have to reset it at least once almost every time because something has happened where it's lost it's mind with regards to ball positions. When this happens I go into switch tests and everything shows and works as it should. Last night I have the third lock shot lit and purposely start Bullet Catch, drill the innner loop and it goes all the way to the ball lock instead of getting diverted and over to the trunk. Okay I get it that maybe the lane switch didn't register because it was a fast shot but the game knows it's in that lock and awards the increased multiplier like it normally would then launches a ball out of the scoop (without warning as always) and STDM. I possibly could have caught it but I was distracted wondering why my awesome shot did not award the beautiful chaos I had purposely tried to create. This is just an example, there should be some logic to handle these kinds of things, instead of awarding the bonus increase it could / should compensate and award the start of Bullet Catch and Multiball, most other games do these things and have for decades. Still love the game but this and the flipper dropping under load at times prevents me from ever really trusting it.

Yep. All of that!

Yep!

Has it been longer for POTC or Houdini? Both games still kick ass - both could use a little bit of polish. Houdini still bolted down!

I am in the same boat. I have had a fair amount of resets , and it is always at the end of the game. Several times when I have already achieved all 7 letters of HOUDINI, and there is a mini-mode available . When I make the shot to start the mini-mode( most commonly the Jail hurry-ups), and avoid the shots that would start MM- disaster almost always follows with a reset.

IT is a great game and the one I play everyday, and I hate to jump on any airing of the grievances- that gets old quickly. I am somewhat comforted to hear others experiencing similar anomalies. I have always wondered how many balls are meant to be used in Trunk Multi-ball. 90% of the time I get 4, sometimes 3, and sometimes 2.I think when I first got the game it was 3, but after a few code updates- I am unsure.

I too experience some randomly added balls, but when you guys are saying “reset” do you mean that in the middle of a ball everything goes red and stops like the “end of ball” sequence once drained? I’m not getting a game reset. Just this weird end of ball thing. Everything seems to be working with the through mechanism, so I’m guessing it’s a software issue. It happens once in a while and rather randomly. I also get the occasional week flipper during some chaotic multi ball multi mode situations, but that’s not keeping me up at night. Game is exceptional and so I tend to overlook this for now, but I too am eager for an update if it remedies these issues. Still my favorite pin.

I don't think I've had the game do an actual reset on me in a long time, like several code revisions ago. When I say reset I mean I power cycle the game to get it back on track with regards to proper ball tracking, this may not always be necessary but especially if we're playing league or competition I'm doing so just to make sure because I have seen it carry over from game to game. My issues are mainly too many or not enough balls in play or the game not recognizing that a shot has been made. The scoop is definitely one of the biggest contributors to this or so it seems. For instance a couple days ago I had SEANCE MB going and down to two balls. I had one go in the Magic Shop Hole and nearly simultaneously I hit the scoop with the other. It ejected one ball out and continued in SEANCE MB with only one ball until I drained it then it ended the ball, scored bonus, etc. The next ball played fine. Clearly the switches in the scoop were working properly (again, I've fine tuned it more times than I can count) so they game should have been able to detect that only one ball was in play.

Trunk MB should always be three balls to start unless it's stacked with something else.

For me- the game just stops completely- lights out no screens, and the computer starts the re-boot process

Most of my resets were fixed with the last code update and upgraded power supply.

But for some they still persist.

I'm curious if they are software or hardware related at this point.

In betting driver issues.

What code are
You on? Is this with 2 player games or just 1?

That was a dead short in my game. A wire got nicked in the ball loading area and it would randomly short out.
I noticed the spark watching looking thru the open coin door.

I have v19.4.7 and it has done this in earlier updates as well. It has always happened in the end game at either 6 or 7 Houdini letters, weird.

Whoops , I forgot to add- this has always occurred on single player games.

Interesting. A way earlier update would do something similar when you hit the master magician mode, but it’s been months since that was fixed

I would open s ticket and maybe thank to barry.

API is really good about support.

Anyone else having issues with the sound. If I leave the game on for awhile, the sound will "shrink" and become tinny like if you've blown a speaker. Then after it's been off for awhile, it will be fine. I do have a powered subwoofer attached, so I'm wondering if that has something to do with it.

No. Never, and I too have a powered sub.

Never heard of this either. This is the in-game sound, not just attract mode?

I’ve left my games on for a couple days and not had this happen

When it happens next, send me the logs and we can see if sheds any light.

How many Houdini owners on this thread have also purchased a Oktoberfest?

If so, was wondering how you feel that code "performs" compared to Houdini's most recent code, which hasn't been updated in awhile (4/7/19).

I too am hoping Rosh or possibly Ferret for more polish or optimization to the code.

My Houdini has some slowness getting the balls to come out after starting Seance Multiball (sometimes takes 10 seconds to get two more balls fired out onto the playfield). Used to be a lot quicker than that.

I've never had that issue. I've got a Polk powered sub on mine. Maybe the amp is faulty. I believe that amp is really cheap to purchase. Maybe worth while just to get another one.

My son has been complaining about the ball tracking. I do see issues ever so often as well. Seems a little more testing and code tweaking might need to be done. We do have the latest code.

Hello.
I have a houdini pinball since 3 days. Everything worked fine the first day but now I have a problem. If the ball comes into the scene it gets stucked and no mission is being launched. I've tested the scene motor and everything works fine (open curtain, close curtain, captive ball up and down).
I've also tested the switch and they do work (front of stage, stage, back of stage, stage exit do react when I put my hand in front of them). But when in the game there is no reaction when the ball comes into the scene hole. I've tried with a paper and sometimes the curtain closes itself but very hardly and I need to try several times
Please help
Thank you

I too have noticed that when I shoot a ball into the stage to start a mode , like Metamorphosis, the stage door will not close until after the onscreen introduction. Then I see the ball sitting on top of the captive ball start to descend as the stage door shuts.
Is this normal or was the function changed in the 4/2019 code?
I seem to remember the stage door always shutting first before on screen intro.

I just found out my mistake : I didn't know thé stage calibration option. Now everything works fine

Is that possibly my issue as well?

Maybe, its worth s shot to try it.

I thought the stage/curtain adjustment/calibration option was removed in the last code update?

Great game, isn’t it? I’ve started only doing the flippers double reversed during the escape act. Great practice for master magician. Actually getting better at it. Still suck, but less and less

Yeah the MM rules should pause per page and let you flip through them via the flippers.

I think that the open hole in the stage should be used more in the game. Maybe an escape or something.

I'd like to see more code refinement with things like this in mind.

The game has the potential to he one of the best!

Massive code update please.

The hobbit was utilitarian at best for 2 years. Now after the massive code update, its world class, really nice.

New code update (prediction) October 31 2019!

Inspired guess

I'm guessing and betting with the anniversary of Houdini's death on October 31st, we shall be in for a great update code surprise with many great features on that day!

I'm guessing when Rosh feels like it...

Ferret: Are you allowed to tinker with the Houdini code or is that Rosh's baby?

I suppose I’m “allowed”, but it wouldn’t make much sense... I’ve never touched it, so the vision and code is all Josh.

Josh stated that he can only work on the game "in his spare time", which I took to understand that since Houdini is no longer manufactured, he's got other responsibilities right now. Would love to see some of those final things get worked out but it's all off the books

Finally got around to installing the EOS switches and knocker last night.

I also reset the settings to the “home” preset, where before I had customized a bunch of rules and coil settings (I can’t remember what preset I started from)

I played about 2 games, and suddenly the game rebooted! I checked my installation job and I don’t think that’s shorting or anything. But that only leaves the settings which caused the issue. Anybody have this happen too?

I just noticed I’m on the 3.24 beta code, so I’ll update to the latest first, but that was really surprising!

Interesting.
Try updating to the current code and try again?

I'm on highly adjusted factory settings but, that shouldn't matter.

I know, that’s what I thought. But I guess it’s possible there some combination of settings and gameplay that causes the reboot. I have NEVER seen the game reboot before, except once when I got to MM mode on early early code.

Most likely it’s the new stuff I added, obviously, but i don’t think it’s my installation - or at least I can not see any obvious shorts and I am certain I followed the directions.

send me the logs

Yes sir!! I have not yet updated to the latest release (still apparently on the March 24 beta). I’ll remove the update so I can make sure the logs copy to the drive. Thanks josh !!

Update! Has not reoccurred, and I think it may have been related to my settings: once I set the knocker to “ mechanical “ in the menu, things seem more stable

Update 2: rock solid for
The past week. Got me excited enough to add a knocker to my MB too!

Great to hear its behaving again.

Still it points to evidence that drivers or something in the code has to be sorted out.

Yep, I am reasonably sure that this was just a conflict with the knocker installed but not activated. I didn’t send the logs to Josh yet though, and I can’t be certain what happened