Feature Requests List (Sticky)

danfrw wrote:Hi there

I have an icontrolpad working fine with N64oid. But is there a way to swap the left and right analog sticks? It would be easier to hold the icontrolpad if you could use the right analog stick rather than left? Can this feature be added?

Many thanks

Dan

Will make an option to swap the left and right sticks. For now I suggest adding this to the feature list

yongzh wrote:

Admin wrote:"Android 4.0 Ready" in 2.5 - Assuming dual core support

It is not true. "Android 4.0 Ready" means N64oid will work properly on Android 4.0. Besides that I also added the (Xperia Play) touchpad support (but it can't be tested until the OS update comes to the phone).

It is almost impossible to make the CPU emulation core to run in multiple threads. The video plugin can be separated from the core thread, but it will need a lot of state copying here and there, which will slow down the emulator, and therefore I don't think it is worth a try.

Ok thanks for the info yongzh.

Add translations. (You could upload files somewhere and then people could send the translated files back to you)
And I want the old app icon back!

The video plugin can be separated from the core thread, but it will need a lot of state copying here and there, which will slow down the emulator, and therefore I don't think it is worth a try.

Would it be worth it with the Tegra 3/quad core chips coming out? If all the plugins were modular (video, audio, input), they could each run on a different core, because the raw clock speeds of the new chips don't seem to be going up as rapidly anymore, they're just adding more cores like desktops

I know someone already requested this but it really would be awesome to make the controls more customizable, like being able to put the controls anywhere you want on the screen. I'm using the small control size and I really want to be able to move A and B buttons because I think they are hard to reach. To have an idea of what I'm talking about anyone can take a look at the latest version of fpse which add this feature.

Admin wrote:Sony Google TV Honeycomb rom loading support (Roms currently can not be loaded)

The current Google TV SDK does not support native libraries, which is a necessity to all emulators. So I have to say it is not possible at least for now.

yongzh wrote:

Admin wrote:Sony Google TV Honeycomb rom loading support (Roms currently can not be loaded)

The current Google TV SDK does not support native libraries, which is a necessity to all emulators. So I have to say it is not possible at least for now.

Thanks for the input Yongzh.

It's just my opinion no offence at all but I find the new line-styled on-screen keypad too flashy. I prefer the old on-screen keypad because with high transparency the controls were barely visible. It would be nice to have the choice between the old and the new on-screen keypad and of course replace the transparency option.

I know I'm boring but is it possible to assign sensor as A and B button? For example it would be cool for Mario Kart to accelerate and brake by tilting the phone forward and backward.

+1 to the above!

Would it be possible for each game to store frameskip settings? For example on MarioKart and other racing games I have to have it on 0, as frame skipping can make you miss huge chunks of track, whereas in Perfect Dark/Goldeneye it has to be on 4 to give a nice smooth experience.

Gillou68310 wrote:It's just my opinion no offence at all but I find the new line-styled on-screen keypad too flashy. I prefer the old on-screen keypad because with high transparency the controls were barely visible. It would be nice to have the choice between the old and the new on-screen keypad and of course replace the transparency option.

New keypad is too visible and that's why it sucks. Add a choice between the old and the new on-screen keypad to next version.

Add support for translations. (You could upload files somewhere and then people could send the translated files back to you)
And I want the old app icon back!

Dude wrote:

Gillou68310 wrote:It's just my opinion no offence at all but I find the new line-styled on-screen keypad too flashy. I prefer the old on-screen keypad because with high transparency the controls were barely visible. It would be nice to have the choice between the old and the new on-screen keypad and of course replace the transparency option.

New keypad is too visible and that's why it sucks. Add a choice between the old and the new on-screen keypad to next version.

If you think the new keypad is too visible, I can add back the transparency option. Another solution would be to create a skin package (distributed as an apk as well) for the old styled keypad, so that users can install and choose their preferred skin.

Dude wrote:Add translations. (You could upload files somewhere and then people could send the translated files back to you)
And I want the old app icon back!

I uploaded the translation template file here:
http://sourceforge.net/projects/n64oid/files/strings.xml/download

Feel free to make a translation of that file, and send back to me. Make sure the XML syntax is correct, and the encoding is UTF-8.
Thanks everybody!

+1 to the 'moveable' buttons. 1st person shooters in particular tend to use the Z button for firing which is a total pain. If we could move it to the bottom centre for example (where the start button is) then you could fire easily with either thumb. Currently games like Turok and 007 World is not Enough run beautifully, but are unplayable purely because of the Z button position.

Id like to see older - faster graphics plugin as option, i know it takes time to port plugin, the one which lets load hires textures is for better/faster cpus from what i know, im not sure which plugin is fastest one at the moment.
Also fastest audio plugin with lower quality would be nice.
When playing then disable "back" button , the one on the bottom right when youre holding phone normally.
Enable it only in menu.I hit it accidentally during playing and game stops, we have menu button for menu so this one could be disabled.

2blackba wrote:When playing then disable "back" button , the one on the bottom right when youre holding phone normally.
Enable it only in menu.I hit it accidentally during playing and game stops, we have menu button for menu so this one could be disabled.

Are you on Ice Cream Sandwich? I used the 'back' button to show/hide the action bar, because on HoneyComb devices, there is no MENU button.

yongzh wrote:

Dude wrote:Add translations. (You could upload files somewhere and then people could send the translated files back to you)
And I want the old app icon back!

I uploaded the translation template file here:
http://sourceforge.net/projects/n64oid/files/strings.xml/download

Feel free to make a translation of that file, and send back to me. Make sure the XML syntax is correct, and the encoding is UTF-8.
Thanks everybody!

Could you add this "cheat" to next version?
https://androidemulators.forumotion.com/t22-zelda-oot-subscreen-delay-fix

yongzh wrote:

Admin wrote:"Android 4.0 Ready" in 2.5 - Assuming dual core support

It is not true. "Android 4.0 Ready" means N64oid will work properly on Android 4.0. Besides that I also added the (Xperia Play) touchpad support (but it can't be tested until the OS update comes to the phone).

It is almost impossible to make the CPU emulation core to run in multiple threads. The video plugin can be separated from the core thread, but it will need a lot of state copying here and there, which will slow down the emulator, and therefore I don't think it is worth a try.

If I'm right (I don't exactly remember what Schtruck said when I asked him, too technical for me, I should ask again lol), Fpse uses two threads now, but as you said not for the core, I don't exactly know what part of the emu is using the second thread....

I also think this "dual core" option implemented in Fpse mainly benefits for Asynchronous dual cores, like the Qualcomm's ones in HTC Sensation or Evo3D, not really for Tegra2 devices.

Just my two cents, as I really love these two emulators

Hey, love the work, but would it be possible to make the onscreen controller more flexible, i.e. to be able to place the Z button down the bottom right and A/B top left? Games such as Road Rash 64 use Z almost constantly, and would be much easier to use.

I apologise if this has been implemented in 2.6, I haven't had a chance to upgrade yet.

Marcus wrote:+1 to the 'moveable' buttons. 1st person shooters in particular tend to use the Z button for firing which is a total pain. If we could move it to the bottom centre for example (where the start button is) then you could fire easily with either thumb. Currently games like Turok and 007 World is not Enough run beautifully, but are unplayable purely because of the Z button position.

This seems to be requested a lot, so I added it to the list.

That's brilliant - thank you!

Yongzh wrote:

Dude wrote:

Gillou68310 wrote:
It's just my opinion no offence at all but I find the new line-styled on-screen keypad too flashy. I prefer the old on-screen keypad because with high transparency the controls were barely visible. It would be nice to have the choice between the old and the new on-screen keypad and of course replace the transparency option.

New keypad is too visible and that's why it sucks. Add a choice between the old and the new on-screen keypad to next version.

If you think the new keypad is too visible, I can add back the transparency option. Another solution would be to create a skin package (distributed as an apk as well) for the old styled keypad, so that users can install and choose their preferred skin.

+1 to the transparency option back.

A skin package seems a great idea

How about getting Pokemon snap to work. It's the one game I loved on the n64. Plz! Ill give u a cookie

yongzh wrote:

Dude wrote:Add translations. (You could upload files somewhere and then people could send the translated files back to you)
And I want the old app icon back!

I uploaded the translation template file here:
http://sourceforge.net/projects/n64oid/files/strings.xml/download

Feel free to make a translation of that file, and send back to me. Make sure the XML syntax is correct, and the encoding is UTF-8.
Thanks everybody!

Could you make a project to crowdin? Then adding new languages and updating the translations would be easier.
Finnish translation is in the works but the translator is busy atm

to boost performance a bit, its just small detail but eats a bit of resources.Make it optionable.