I'm not sure but I think I noticed the same thing last night. Several times modes were started without myself knowing it. Maybe I hit the button but don't recall having something like that happen in 1.5. Usually the ball sits there for quite a while and it takes a few seconds to get to the point where you can select the next mode. Not a big deal for me, though. The goal is to work through all the modes and I don't play with a strict strategy.

Same thing here. I paused to get a drink and off she went.

I thought I saw a select timer now in the options menu to timeout mission selection. I think it was off by default but you might want to verify that it is off since it is a simple check. It might just be for autofire the plunger but I could see it affecting the VUK for mission selection for games on route.

--Kevin

Me too, automatically selected the next mission in the left ball lock/vuk. After it was lit as the final shot for KB1. And kicked it out into play. PD 1 mode was started.

...

I can't reproduce this nor is it being commonly reported. Perhaps you have intermittent switch issues rather than code bugs. If a switch is machine gunning the machine would do all the above.

...

turn the coil pulse to soft

Well others don't have this problem so it's not a code bug. Take code bug out of the equation and what are you left with?

...

Yours has scoring which means a switch is activating multiple times. There's are selecting missions on them which could be code. You may have multiple issues due to the scoring parts. Markmon is probably right.

I was going to explain this but you were already pwned by 85vett. I guess some people just don't like to be told the truth if it's something they don't want to hear . Meanwhile, others can enjoy their working machines.

No harm in downgrading code to sort out issues. I don't think 1.61 changed much - mostly fixed lv3 modes. The 1.60 update did change a lot and did fix some opto/switch issues people were having. I had an issue in 1.5 where flipper hits were tripping the bottom vengeance opto during a ball lock. The update seems to have fixed that. I played a handful of games last night and had no issues. You should get a video of the problem. If it's a bug we should document it in hopes of getting it fixed. That's how we got the 1.61 update.

Software is software. Either it happens to everyone, or there's a physical component. The auto starting mission thing isn't new, it's happened in the past. Always a switch problem. The new code may be more sensitive, so a borderline switch has turned into an active problem.

Kickback seems weaker....

Yes, but if it was a true software bug we'd all see it. Meanwhile people have had the exact same issue as that already, in older code. Was a switch problem.

Things can manifest during software updates, but it doesn't mean they're software bugs per se.

If it's software can you duplicate it every time with a particular order of things? Then other people could try it too.

I agree with Aurich on this, though I admittedly haven't pllayed 1.61 much yet. I did have issues with auto mission selecting and auto firing before but this was in old old code and turned out to be a switch. I forgot which one, I want to say it was my warp opto or vengeance opto. But it was over a year ago so don't remember. Sorry can't be much more help besides that.

I played 1,61 code all the day and I don't have this issue with my vuk on my LE
No bug for me

...

And yet, look above, it was his opto. This is something we've seen before, it's not a software bug. Or at least not a pure software bug, maybe the new code is more sensitive to optos for instance.

...

I spent my time explaining it wasn't a code problem and told you to eliminate software and see what else it would be. That wasn't being a jerk. I was being nice. Then you came back insulting me and calling me names. I cannot deal with thick headed people. But to also be wrong about it and so thick headed over it. Geez man. Really unbelievable

are you being serious? I honestly can't tell

Flecom - I'm not saying this to protect Markmon but I honestly didn't see any hostility from his post thus why i even posted in the first place. I really think your frustration about your game skewed your perception of what was said and how it was interpreted. Happens to the best of us (heck I think I did the same to him too on a different update for a different game). Glad you got it fixed and hopefully the other posters issues are simple fixes once discovered too.

pinballophobe - yours may be a hidden bug but I also wouldn't be surprised if you are having an intermediate switch issue to. I'm sure we'll find out soon if more have the issue. This reminds me of some BOP 2.0 issues. Several of us swore of a bug and it turned out to be just how the switch was reading in the new code that caused some flaky switch to start to cause issues.

Yes. Totally serious.

Ok here's an obvious bug that I am surprised that nobody has noticed. See feature adjustment #34 which is 'Nero 2 Timer'. Nero 2 doesn't have a timer! Or is it supposed to and it doesn't use one? This appears directly related to the inserts going into a fast flicker after a certain period of time. The mission itself isn't running off a timer, but the insert blink rate seems to be. I verified this by setting the timer to 10 and the inserts start to go crazy after about 10 - 15 seconds. Therefore I recommend setting Nero 2 timer to 60 so the inserts don't screw up for as long as possible. I bet this was also related to Nero 2 shots disappearing and not coming back..

There may be other timer adjustments for missions that actually aren't using a timer.

A suggestion to the OP that if you are going to have this thread, it would be nice to keep a list of verified bugs in the first post. This way it's organized and easy to digest instead of wading through countless posts.

Other bugs I noticed:

Missing crew callouts at the end of some missions, Nero 2 for example. (New)
Many crew combo callouts are unintelligible, low volume and almost never play in missions. (Old)

Rob

I've had a couple games now where the auto-plunge doesn't always occur after getting GAT. Just played DTD which has Galactic Spinner. It gave me the intro text and hoopla but I had to manually plunge. I thought I'd give it a few seconds but when I saw the timer ticking down I gave up.

If nobody else has seen this then it's possible my shooter lane switch is going bad, so maybe you can chime in if you've ever had it happen.

I think it's probably a bug. I've had the ball fail to autolaunch in 1.60 once already. It's not common, but it does happen. I have a feeling that minor things like this are never going to be fixed.

Rob

Oh one last thing, does anyone think 1.61 is the last version, barring any major bugs or scoring exploits found?

And... do you think timers should have just been removed from tier 2 and 3 missions if they hold progress and don't restart? Or perhaps if the mission restarts, the shot counter goes back to a minimum 3 shots?

Rob

I played many games tonight and didn't have any launching problems. I did see one hiccup where vengeance battle was started even though the game failed to trap the ball behind the drop target. Other than that, everything played great. I defeated the vengeance and got a nice 20+ million award. That was cool. Love the new code!

Not sure if this is a bug, because I dont know the exact circumstances. But this is what I figured happened so far. was playing Nero 2. After finishing KM wiz mode.

Started klingon multiball during nero2. While the klingon ships came on the DMD it was still playing nero phaser shots in the background.(was actually cool sounding)

I was playing both nero 2 and klingon multiball. I got the gold medal for nero 2 callout and thought the mode was finished. As no inserts were flashing or lighting purple/red like when I started.
I got down to one ball left (klingon multiball was over, no more red inserts) and no purple inserts were lit, but nero was still running on the DMD. And no mission start or away team lit to pick next mode. I eventually drained and then The nero insert was lit solid it was registering finished. I was able to then shoot the mission start shot and pick the next mission.

Do you think bug or possibly something else?

I have also had vengence multiball start 3 times so far out of maybe 20 games without the ball on the magnet.
It just went in the vengence, came out. And another ball went into the shooter lane like normal. But the initial ball didnt stick to the magnet.

I can't ever recall it happening before the update.

Also I started the vengence hurry up.
Shot the drop. But then it reset cuz I missed. I did this 4-5 times, missed my next shot each time, it reset like its supposed to. Then everytime I hit the drop after that it didnt drop. 3 times in a row. It still said shoot the drop on the DMD. But it would not go down.

After draining and starting regular play every shot at the drop worked like its supposed to

On Nero 2 issues, has everyone verified that it's not just expecting you to shoot the upper ramp shot only? If I remember right, it seemed like all the lights were out but the purple upper ramp is a bit hard to see lit.

Im pretty sure as once I drained Nero 2 was considered complete. I was also awarded the gold medal for nero 2. Before that nero was still on the DMD but nothing was lit. Even mission start was out.

As soon as I drained and my bonus was added nero 2 lit solid and mission start lit up with the ball in the shooter lane.

If the mode is not finished mission start could have still lit up. And let me pick it again. But nero 2 lit solid. And I could then pick nero 3.

A gold medal does not mark the end of the mode as far as I know.

Possibly but still, once I drained, nero 2 was considered finished.
I should have been able to select it again if it was incomplete. Not been able to then pick nero 3.
And mission start was then lit. If it was finished mission start should have been lit before draining.

It only happend after stacking it with Klingon multiball.

What are the circumstances where what happened makes sence in the rules?

Does anyone else think there is a delay between shooting the needed shot to achieve a medal and the animation and sound? It seems like I make the 3rd (or 6th or 9th) shot during a mode and maybe 5 seconds later I see/hear the award, which sometimes makes me wonder "what triggered that?", since the ball is then in a different area (like the pops).

Yup, but there's so much going on that it has to delay. I don't mind it.

Rob

As far as i registered a gold medal sets the mode timer to 1

As far as issues like auto launch etc, down grade back to version 1.50 (I think it was).
Play it a bunch of times. Does it still auto launch?

I realize upgrading / downgrading takes some time, but its the only way you can tell if its a software issue or something else.

I have a question about this. I have this setting set on but it can be set to off so that a gold medal will not end the mission. I'm still figuring out scoring with the new code and have yet to make it to KM (so close last night but drained first so no cash-in on my medals...ugh!).

From a scoring perspective, is it better to leave this setting on so that a gold medal ends the mission? Thanks.

The longer the mode is running, the more points you can make. So from this perspective it's better to set it to off.
BUT...the longer the mode is running, the higher is the chance to loose the ball and loose the big cash-in on the wizard modes...

That was kind of my thinking. I'll leave mine to on as me getting to KM at all is quite the feat! (only done it maybe 4-5 times at most)

So, overall, is it worth making a change to 1.61 or just leave it at 1.60 for now?

You can leave it but I see no reason to. 1.61 fixes bugs in 1.60 and it's easy to install.