Emulator Trouble

[Tinnitus]

I don't know where else to put this, but it has to do with smash 64, so its here.

This started yesterday, I was playing Super Smash Bros on Project64 1.6
Then just randomly, it wouldnt let me smash, run, or dodge roll. The controll stick was ste as a tilt, no matter how hard i smashed it. I changed my controller plugins joystic range from 60% to 100%, the problem was still there, i restarted the emulator, still there, restarted my computer, nope, cant smash.

It only happens with smash 64, all other games work fine, so does anyone have any solutions?

The controller plugin I use is N-Range's Direct-Input8 V2 1.80a

 

[DMoogle]

Are you playing with a controller or a keyboard? If controller, then re-calibrate it (select Game Controllers from Window's Control Panel). If keyboard, I have no idea...

 

[Battlecow]

^^If you read the OP it says controller.

Out of deadly superstition, I'm going to mention unchecking raw data, but you've already done that, right?

Did this happen midgame or in between games or when you opened the rom or what? This is offline, right?

Maybe it's a hardware problem; I don't think this could happen, but have you tried the controller on console?

 

[Korrupshen]

^^If you read the OP it says controller.

Out of deadly superstition, I'm going to mention unchecking raw data, but you've already done that, right?

****it Battlecow u beat me to it to his possible solution

 

[Tinnitus]

^^If you read the OP it says controller.

Out of deadly superstition, I'm going to mention unchecking raw data, but you've already done that, right?

Did this happen midgame or in between games or when you opened the rom or what? This is offline, right?

Maybe it's a hardware problem; I don't think this could happen, but have you tried the controller on console?

Yes, I have already unchecked raw data.

It happened midgame, between matches, one match was normal, the next I set up, the problem had been born. And yes, it was offline.

I'm gonna try to download a new SSB64 ROM to see if the problem goes away.

 

[Sempiternity]

Did you try recalibrating the controller like DMoogle said? My controller wouldn't work initially because the computer was only recognizing full movement as like quarter movement.

 

[Korrupshen]

Things u can do

1. Make sure your analog range isn't zero [recommended range is 100 with (real n64 range checked)

2. Make sure your dead zone isn't zero [recommended deadzone is 10]

3. Make sure you click save when you change controls and setting, maybe your raw data is still checked but you forgot to click save.

 

[Tinnitus]

Did you try recalibrating the controller like DMoogle said? My controller wouldn't work initially because the computer was only recognizing full movement as like quarter movement.

Forgot to mention that, I tried that, it didnt work, still downloading a new ROM.


[EDIT] @ post above:
1. Doing that now.

2. Deadzone is already 10

3. I click save every time, even when I dont change anything, raw data is unchecked for sure.

 

[Korrupshen]

Well....the only thing I can think of now is reinstalling your controller drivers. Did you check to see if your controller is selected under device and that you checked the plugged box

 

[Tinnitus]

Ok get this, I downloaded a new SSB64 ROM, the exact same one I currently have, I deleted the old one, rplaced the new one, re-set the directories, and it wont even load now!

I think Windows Vista is the problem.... lol?

[EDIT] Windows was the problem on that one, the download didnt finish properly so I had to start it over.

But the problem of no smashing still exists, did I mention the computer players cant smash either?

 

[Korrupshen]

Did I mention the computer players cant smash either?

WTF!!!!??? Never heard of a problem that Cpus can't smash

 

[Tinnitus]

WTF!!!!??? Never heard of a problem that Cpus can't smash

You read right, me nor the cpus can run, crouch, sheild dodge, smash attack, or up jump.

I never use up jump, but I'm just saying.

It makes no sense!!!!

 

[Korrupshen]

Try my project64 see if that helps
http://www.4shared.com/file/GDMh7Hlz/Project64k.html

EDIT: It has the roms and everything both fo both JP and NSTC Super Smash Bros, so just start it up and configure the controls. I prefer Project64KVE its meant for vista and win7

 

[Sempiternity]

Wow, what the hell!?

Try a different emulator and see if the problem persists.

EDIT: And by different, I mean not another build (although you could try that), but like Mupen or something.

 

[Tinnitus]

Thanks for all the help and suggestions guys, I came to the right place.

But get this, I erased my smash 64 data and the problem was fixed.......

Now I just have to re-unlock everything, but thats what cheats are for amiright? Still though, I want to further look into this to see exactly what caused it.

This better not happen to my Ocarina of Time.....

 

[andrewajt62]

A bit off-topic, but, that's nothing, my Legend of Zelda NES cart just had all it's data erased when I tested it out on my NES with a new connector installed (I usually play on my toploader NES). Over ten hours of work gone. Also my Pokemon crystal cart's battery is dead, so it lost all data and no longer saves. Losing data sucks.

 

[Sempiternity]

Haha, NES carts are just for looking at these days.

Or bashing to smithereens with a golf club.

Ah, regrets...


And I believe the lifespan of the Generation II Pokemon batteries is about seven years. Mine are on the brink as well. Gold doesn't pass time when the game is off, only when turned on...

 

[SuPeRbOoM]

Things u can do

1. Make sure your analog range isn't zero [recommended range is 100 with (real n64 range checked)

2. Make sure your dead zone isn't zero [recommended deadzone is 10]

3. Make sure you click save when you change controls and setting, maybe your raw data is still checked but you forgot to click save.

1. 100 range is way too much. Having high range means you can DI far too easy compared to normal. For my adapter I use 77 because it feels the most like console, the range will vary by controller/adapters, I use n64/psx adapter.

2. Recommended deadzone is 4-5

 

[DMoogle]

1. 100 range is way too much. Having high range means you can DI far too easy compared to normal.

Err why is that a bad thing?

 

[Tinnitus]

1. 100 range is way too much.

I agree, after a bit of experimenting, I find my best range is 64 (no pun intended) because I have a very sensitive joystick.

 

[Battlecow]

I agree, after a bit of experimenting, I find my best range is 64 (no pun intended) because I have a very sensitive joystick.

That is so totally what she said.

 

[SuPeRbOoM]

Err why is that a bad thing?

Because it's fake?

 

[Tinnitus]

That is so totally what she said.

You just made my day

 

[Korrupshen]

1. 100 range is way too much. Having high range means you can DI far too easy compared to normal. For my adapter I use 77 because it feels the most like console, the range will vary by controller/adapters, I use n64/psx adapter.

2. Recommended deadzone is 4-5

Well I use the gamecube controller for the Project 64 until I get that n64 to pc ****. Without 100% range I can't even quick attack with pika twice for some reason.....