So strange, I wonder what happened?!  

At least Tony is going to take a look at what happened and hopefully revert it back to how it was before this strange glitch.

I received a text from 2 people about an "older guy" inside the ITG 3 machine around 3PM yesterday. I just hope it wasn't some random person trying to gain entry into the machine that set this whole thing off.  

Waiting on Tony as of right now. Abbye and I texted Laura about this happening and she told Tony.

Tony said he'd take a look either last night or today, so I'm just hoping to hear from him with what happened. 

Machine should be all better software-wise now. Don't know exactly what happened, but roughly the same set of settings that change when throw Simply Love crashes were affected in addition to a handful of things that can be changes from the Op menu.

For reference, the things that were still messed up (and are now fixed) when I got there:
- Global Offset was changed from -6ms to 0ms
- Input debouncing was turned off
- Menu Scroll Rate was changed
- Dedicated Menu Buttons (navigate menus with the pads) was turned on
- Double costs two credits instead of one
- The theme was set to the wrong Chromatic version (I keep a backup on the machine in case I break something, but I haven't updated it for a while).

Normally, the telltale sign of a Simple Love crash is 10% BGBrightness, but the machine has been set up to revert any changes to that setting on reboot, so if it did do that, the change got blown away automatically. I'm going to be out of town on business tomorrow through Friday, but next weekend, I'll get some of the other settings set up to self-fix the same way, which should make it a lot harder for this to happen again.

Anyway, after all the fixes, I played without noticing any other software issues for a little over an hour, so I think we're good. If anyone goes find anything, let me know and I'll get it fixed as soon as I can.

While the software issues should be resolved, 2p down was giving me a lot of errors - mostly way offs and decents, which usually means it's oversensitive and getting ghost triggers from the panel bouncing around. Also, the 1p center panel was down to one of four screws, which caused it to bounce around under your feet while you play, so I moved a screw from one of the corner panels to fix it. We definitely want to make sure each of the blank panels has at least two screws, preferably on opposite corners for stability.

Awesome, thank you Tony for getting everything fixed up and ready to go!

As far as the panels go, I will fix them up ASAP. Not sure why the center panel on the P1 side only had 1 screw! I hope it wasn't anyone trying to temper with the machine... It seems unlikely but you never know.

Thanks again for your work.

So someone went and messed with the machine, but not only that, they also messed with the pads? That's going a bit too far. Those are in godly condition. They cannot be fiddled with.

How about checking the security footage from the arcade? There's a camera with a clear view of the machine, if I recall. It's not okay to just let people get away with fucking things up for everyone else without even owning the thing.

I actually agree with vyhd on checking the footage just rule out temperament to the cabinet. I mean the two scenarios are possible due to the rough est. of 3hr time gap.

A quick question for Tony,

Is there a possibility that the timing window was altered somehow when the ITG 3 machine glitched or whatever might have happened?

After the glitch/tempering happened, I noticed that timing anything seemed impossible on harder/faster charts, it just doesn't feel the same. I've redone the modding back to what I had it originally, just incase someone touched it, but timing just isn't happening. A lot of way-off and descent from both sides are incredibly annoying! Not sure if the timing window could've changed, so I thought I'd ask you since you know a lot more about the computer, etc.

I just asking because right before the issue occurred, I was SDEing 14's, now I can't even full combo them.

Has the global offset been fixed yet?

I don't know what the global off set is

Tony does

It's the syncing for the cabinet itself, rather than a specific song, you use it to sync the machine as you see fit, then you individually sync simfiles to fit the machine's sync through oITG or SM.

As far as I'm concerned the pads are unplayable. I've been at acme for the passed 3 hours just working on them and nothing's gotten better. I've modded the pads back to how they were before all this happened and its not triggering properly.

I know Kevin, Jacob, And Tuan can tell you, the pads were in pretty good shape. At the very least you were able to full combo songs, it's impossible now. Not exactly sure what happened but its pretty bad. I know that the pads would misfire once in awhile only on the P2 side but its nearly every other step now!

I don't know what to do!

No... don't.. tell me the best and only public access dedicab in the state may be fucked... software and hardware...

I don't visit here often, if ever, but man there seems to be a lot of drama over this place now.

I haven't been out there to play this past few days due to work hours being longer than the usual 1530 or earlier. Sounds like this machine got wrecked since I was last there. Chris, did have those pads pretty damn solid even though 2P did misfire due to how it was setup...I mean the panels were nearly flush (tis how Chris cheats and causes him to choke during streams to get "1"). From whats being said it sounds like a glitch but since there is idea of someone accessing the machine and messing with settings  then that could have been when the service tech was there doing his job. I believe Bill mention that his service tech had someone there noticing that "custom song" was turned off. Tony, mentioned it looked it like it had symptoms from the theme "SIMPLY LOVE"...i guess the other person could have noticed it if there is a theme switcher in the options of Chromatic and figured to switch and caused the machine to crash etc etc......either way I'm sure things are being looked at

@ Kevin + Jacob

The Software seems to be fine after Tony looked at it. Everything is back to normal as far as I can tell. All the songs/packs and the speed mods are all present. Back to normal!

The Hardware is where it was on Friday, when I last played. I played until about 10:30PM Friday night and nothing was wrong. Couple people played that night and we were scoring just fine, no issues at all. Then comes Saturday when I get a text from a friends of mine telling me that something happened to the machine at ACME. They told me that they were only getting decent/way-off and that the computer/cab has reverted back to post Sakuracon last year. Abbye immediately contacts Laura to inform her about the problem. Laura relayed that information to Tony. Soon after, Tony posted on the forums about what possibly could have happened. Sunday rolls around and Tony posts that he has fixed the problem and everything is pretty much back to normal.

I just can't figure out what happened to the pads... Nothing has changed between Friday ~ Sunday regarding the pads. No foam was removed, no tape was removed, etc., etc., etc.... I just did a little maintenance on them today, but nothing different.

When I opened it up today to take a closer took at it, I found absolutely nothing wrong. They were how they were on Friday night! Same foam, same tape, same everything. I guess I'm wondering if the timing window has changed at all. Considering on Friday, I was scoring in the 99.00-99.50% range on 14's - 15's and now I can't even combo an 11...

I even tried to play on recessed pads (little to no foam modding) today to see if it was the foam modding that caused the misfires. If it was I could adjust it and fix it to make sure the false triggers would stop. But, unfortunately they still false triggered...even without the foam...

I don't know what to do at this point! 

Any suggestions? 

Well, I'm going to go cry in a corner because I'm no help really, but do you have direct contact with Bill or Tony?

Are the pads registering on a shifted/offset timing window, or is it like it's shrunk/enlarged? Or just plain misfiring/missing?

When Abbye and I played today, our timing felt extremely off. We felt like we were moving to fast... everything seemed to register early on all of the faster BPM songs... namely, all of Ian's charts. Abbye and I have been working on FA'ing all of the Pendulum charts just last week and for us to come back this week and have literally 200+ excellents, and a hand of of decents/way-offs/misses, is very unlikely.

The pads are registering the hit/step, just early...seems very, very early... probably an issue with the timing window the more I think about it. 

So, if you stomp on the center metal panel, do you get misfires? If yes, then one or more of the sensors is over-sensitive or getting too much pressure.

If it does not misfire from this, then I assume it is triggering randomly? If that is the case, it could be an issue with the actual pad IO board or the debounce settings in the software.

If you feel it is early, someone might have accidentally messed with the machine sync. Play some official ITG or ITG2 charts and see how they feel. If they feel fine, then that deepens the mystery.

Abbye and I tried to test every possibility. Honestly, we were hoping it was the foam modding that was giving us some issues, since it would be easier to adjust/fix for us. We tried to stomp on the center panel on both P1 and P2, along with the corner panels, just in case the foam modding was putting to much pressure on the sensors and false triggering, but we didn't get any false triggering.

What we've noticed was that, when the BPM is slower (130-150 BPM) the false triggers don't happen as often (but they occur enough to prevent full combos).

As the BPM increases to around 170-200, it is almost impossible to play. As I mentioned in an earlier post, it is nearly every other step that gives you decents/way-offs/misses. I actually failed Encoder (13)! This is a song that I regularly score 99.60+! 

I guess the timing window just seems extremely earlier and really, really, really tight. 

Whatever is going on, I hope Tony or can give us some insight about what can possibly be wrong when he gets back. 

It definitively seems like a timing issue

So I can't remember if OITG has this or not but I remember older versions of SM had it. There was a judgement difficulty setting and a life difficulty setting. Those settings are normally next to the timer setting, is it possible that got affected/changed in the glitch? That would make the windows impossibly hard. I used to tighten my SM windows to work on FA.

The individual timing windows and the infamous JWA setting were fine when I looked last weekend. I restored input debouncing to what I believe is the default value, but that was from memory, so that's the most likely cause right now - this is sounding like the exact same problem we saw after Sakuracon last year, and that was purely the result of debounce getting set to 0 instead of 0.005 (I believe it's supposed to be 0.005, anyway - I'll confirm the correct value and make sure it's set to that).

I get back to Seattle tomorrow evening, so I'll try to take a look Saturday morning.

Ah... it's 0.05. That might be the cause

Also, I wanted to chat with you about setting up remote access so we can more easily debug things like this in the future. We can probably do that (the chatting) Friday night, if time allows!

Just wanted to make a quick post about the bar on the Player 2 side. It is shaking a lot as of late... Is there anyway to get this fixed soon?