Nah i didnt overclock. in fact, you really dont need to to play the n64 emulator. and i believe it voids the warranty? i definetly wouldnt want to do that.
but im glad my problem was solved. it was the usb charger.
There is actually two answers to this.... the short and long.
The short is that USB ports are only designed to trickle charge, whereas a wall charger is specifically for charging at maximum speed.
The long, official USB specification says the current drain from the USB port must be somewhere between 100-500mA, this is generally on the lower end (100-200) for laptops... as they have to be more power conscious, whereas a desktop generally will see a little better (200-500), this actually depends a fair bit on there you plug it in also, plugging directly into the back of a PC will see a significantly more amount of current compared to the convenient ones at the front.
A wall charger, however, works with the premise it can drain as much power as needed. The Nokia AC-10 wall charger, for example, puts out 1200mA of charging output. As you can obviously do basic maths... thats more than 10 times the charging power.
This is why I'm always careful to get the best possible charger... as a lot of the Chinese ones will only ever put out 500-800 (haven't really looked to deeply into this) which limits me to a charger for a lot longer than I need be.
Originally Posted by
i dare all of you to play virtual chess 64. i only beat the computer one time and i played all day at work. its not fair when the computer can think multiple steps ahead. to beat it its like a big achievement. at least for me it was haha!
Just did, gave it to my father and he won 5 times in a row (he plays FICS almost 3 hours a day, he's obsessed with online chess) :P
Does the blight input plugin in theory have rubmle/force feedback support? I don't know how this works on linux but cwiid has rumble functions in wminput but I couldn't get it to vibrate in games yet.
It does. I've no idea if its managed to survive the port from Linux, to Pandora to here.... but it should. I've seen output attempt to find rumble on several occasions, usually failing to find it at /dev/input/eventX, maybe the joystick application has some use here?
Is the keyboard mapping in blight_input.conf?
How to know the value of keys?
I want to remapp some keys, becаuse Dpad dont work on the German Keyboard.
Hi, du kannst die Nummern der Tasten hier: http://www.theasciicode.com.ar/
ablesen. Für "ä", wo normalerweise die pfeiltaste oben ist, wäre das dann 132 (immer die nummer für die kleinen Buchstaben).
Du kannst die blight_input.conf mit leafpad öffnen und bearbeiten, oder die Tasten mittels GUI zuweisen, options und dann input settings.
I increased the default maximum angles by about the same amount in the new release today. It also adds ~20% deadzone (might be too much...feedback appreciated) and adds a calibration button to the GUI.
It also makes that script i gave many pages back for automating its startup with mupen a bit wrong. If anyone is using that let me know for updated version.
Have updated and eager to test but now accelemymote is no longer found under mupen controller plugins as before. Has the procedure for launching accelemyote with mupen changed with the update?
Nothing happend when selecting set origin but sometimes when minimizing accelemymote to select mupen I get a notification that origin has been set to 0 but still no accelemymote in mupen.
Have updated and eager to test but now accelemymote is no longer found under mupen controller plugins as before. Has the procedure for launching accelemyote with mupen changed with the update?
Nothing happend when selecting set origin but sometimes when minimizing accelemymote to select mupen I get a notification that origin has been set to 0 but still no accelemymote in mupen.
I had to reinstall mupen64 after installing the new accelemymote, otherwise I got a sigsev error when trying to play any game.
I had to reinstall mupen64 after installing the new accelemymote, otherwise I got a sigsev error when trying to play any game.
I have had this error randomly occur prior to the update. Seems to happen when switching from one rom to another rom with larger file size. Also error message says is due to trying to access unaccessable memory or something along those lines.
Problem solved.
Dont know how exactly. Just uninstalled some unused apps and cleaned up root memory before reinstalling accelemymote.
Yeh, I have had this error but only when hotswaping between all my roms as I was testing them. I found just simply turning the emulator off and starting over cured the problem.
Under normal use I would imagine the sigsev error is very rare.
For anyone interested.. just to tease you. Super Smash Bros now works in the new version... along with a 3-4 fps increase in several games.
Been playing SSB for the last 2 hours at full speed, aside from the fact none of them have eyes: it runs perfect.
Now we just need javis to compile and release for you guys :P
As for the SIGSEV error, its a very, very broad error and can mean many things. The most common is the emulator has some weird memory stuck somewhere: just close GUI and re-open. It can also mean the ROM doesn't work, is corrupted or just hates you :P If you know the rom should be working (be sure to try both NTSC and PAL versions), reinstall as posted on the first post at the bottom.
