Fireblaster
Smash Lord
Try a different browser
Welcome to Smashboards, the world's largest Super Smash Brothers community! Over 250,000 Smash Bros. fans from around the world have come to discuss these great games in over 19 million posts!
You are currently viewing our boards as a visitor. Click here to sign up right now and start on your path in the Smash community!
Absolutely. You can still use the site now!Is the site still getting updated? This has a ton of potential and an update would breath new life into the site (and hopefully smash 64 as a whole).
Sounds good! I'm looking forward to the changes/improvements!I've been busy and slowly working on a tournament app currently. I'm hoping to allocate enough time this week to finish the tournament app and then more work on the site can be resumed.
The glitch that Fireblaster found, happens to me too. Step by step:Yeah I can't seem to reproduce. If its you pressing forward while its playing and you think those buttons should be disabled then that is different.
I'll look into it.The glitch that Fireblaster found, happens to me too. Step by step:
1. go to The ssb64 website
2. click Frame Display
3. Click the single frame advance, button (or whatever you call it, the button Fire was clicking)
It screwed up for me on frame 22, started doing the back/forth thing like in Fire's .gif
tech info
using Google Chrome Version 38.0.2125.101
frame data was not playing in loop before I started clicking forward
I clicked/did nothing other than what was in those instructions I had written.
Does the glitch happen 100% of the time? What OS do you use? Have you tried with some chrome plugins disabled? Clear cache? I don't know, works fine for me on firefox and google chrome on Windows 7. I tried clicking on the next frame slowly, as fast as I could and it didn't glitch.The glitch that Fireblaster found, happens to me too. Step by step:
1. go to The ssb64 website
2. click Frame Display
3. Click the single frame advance, button (or whatever you call it, the button Fire was clicking)
It screwed up for me on frame 22, started doing the back/forth thing like in Fire's .gif
tech info
using Google Chrome Version 38.0.2125.101
frame data was not playing in loop before I started clicking forward
I clicked/did nothing other than what was in those instructions I had written.
Does the glitch happen 100% of the time? What OS do you use? Have you tried with some chrome plugins disabled? Clear cache? I don't know, works fine for me on firefox and google chrome on Windows 7. I tried clicking on the next frame slowly, as fast as I could and it didn't glitch.
I can't seem to recreate the glitch either. Tested on FF, Chrome, and IE. OS is Windows 8.1OS: Windows 8.1
Cleared Cache then reset browser, no change. (Except images now load slower obvs)
Turned off all plugins, no change.
Tried with Internet Explorer, frame display works perfect.
It seems the bug is only in Chrome, I don't have FF to test with but, meh.
I could certainly figure it out if I could sit down with your computer and use the chrome debugger. Interesting that it works on IE for you but not chrome, which suggests to me that something with your version of chrome isn't processing the javascript correctly. I did discover an issue with how chrome handles a variables scope and passing it by reference when first debugging the site so there could be some issue with both of your browsers (which is a google problem not yours). Remember that just because its google doesn't mean its flawless. These browsers are very complicated and theres a reason they're not on version 1.0 anymore and its because they are continually finding bugs that need to be resolved. For example, I discovered a couple bugs on the new IOS 8.0.2. So my guess is your version of chrome isn't handling the global variables properly and if I could debug your computer I could figure out a workaround. Otherwise I guess use IE and hope that when chrome automatically updates that problem will be fixed. You're also more than welcome to inspect the javascript source and see if there are any logical errors in the code and report it back here for updating.
here let me help youI`m in the process of assembling that already Steve. Got em all together, I think, just need to finish formatting.
I don`t know where we`d be without you, Steve.here let me help you
<html>
<body>
*all of the codes*
</body>
</html>
dont worry shears is doing it