Active Topics
-
[HOWTO] Comprehensive Firmware Flashing Guide for N9 (1,580)
to Nokia N9 / N950 by aspergerguy - 15 hrs, 37 mins ago -
Nokia N9-00 Prototype Build S1.12 (RM-680 codename "Dali") (250)
to Nokia N9 / N950 by en0s - 3 days, 12 hrs ago -
[Announce] Maebble - Pebble support for Maemo (118)
to Applications by glo-worm - 4 days ago -
Possible to flash Leste to eMMC? (6)
to Maemo 7 / Leste by Eri - 4 days, 14 hrs ago - more...
 |
|
2009-10-14
, 05:53
|
|
Posts: 2,669 |
Thanked: 2,555 times |
Joined on Apr 2007
|
#32
|
I get aproximately 30 fps.. but it's very stuttery for some reason. Attempting to fly in Super Mario Bros 3 (Super Mario All-Stars) is nearly impossible due to the framerate or possibly the lag with the Wiimote.
In general though, it works well enough and I'm glad to hear there's a lot of room for optimization.
In general though, it works well enough and I'm glad to hear there's a lot of room for optimization.
| The Following User Says Thank You to zerojay For This Useful Post: | ||
 |
|
2009-10-14
, 06:40
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#33
|
Originally Posted by zerojay
Oh, that's interesting. The auto frameskipper also sttuters here when using wiicontrol (briefly commented in some page on this forum). I think it's due to the constant task switching between python and the emu.
I uget aproximately 30 fps.. but it's very stuttery for some reason. Attempting to fly in Super Mario Bros 3 (Super Mario All-Stars) is nearly impossible due to the framerate or possibly the lag with the Wiimote.
btw, 30 fps is what I get in N810 with hw scaler, without stuttering.
 |
|
2009-10-14
, 06:56
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#34
|
The author of Wiiremote emailed me a couple of days ago stating that he would write a start up guide for us newbies.
Maybe this will drive some interest in him looking over his code again and making further optimizations for it.
Interesting about the results you two are getting in terms of fps.
Can you get full 60 fps in windowed (1x) mode with the same settings mentioned before?
Also, can you get full 60 fps full screen (2x) mode with sound removed?
Thanks for the replies guys.
Maybe this will drive some interest in him looking over his code again and making further optimizations for it.
Interesting about the results you two are getting in terms of fps.
Can you get full 60 fps in windowed (1x) mode with the same settings mentioned before?
Also, can you get full 60 fps full screen (2x) mode with sound removed?
Thanks for the replies guys.
| The Following User Says Thank You to Addison For This Useful Post: | ||
|
|
2009-10-14
, 07:02
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#35
|
The auto frameskipper may be the one to blame here, did you try without?
Originally Posted by zerojay
Ah well, that's the generic affirmation one always does...
I'm glad to hear there's a lot of room for optimization.
|
|
2009-10-14
, 09:07
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#36
|
I think that you guys misunderstood my question which really is my fault for not asking correctly.
I'm wondering what additional features need to be removed (scaling, sound, accurate graphics) to have this emu run at a decent speed on a N900 when forcing it to run at 60 fps.
I know that the human eye can only take in 24 fps so why is it that it looks so chunky at that speed?
The golden mark for new games released on modern consoles is 60 fps which looks fantastic, but why isn't 24 fps good enough for the human eye to enjoy?
Maybe I should google this because it doesn't make much sense to me and I'm sure others have been confused about this the same as me.
I'm wondering what additional features need to be removed (scaling, sound, accurate graphics) to have this emu run at a decent speed on a N900 when forcing it to run at 60 fps.
I know that the human eye can only take in 24 fps so why is it that it looks so chunky at that speed?
The golden mark for new games released on modern consoles is 60 fps which looks fantastic, but why isn't 24 fps good enough for the human eye to enjoy?
Maybe I should google this because it doesn't make much sense to me and I'm sure others have been confused about this the same as me.
|
|
2009-10-14
, 10:32
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#37
|
Originally Posted by Addison
Probably only super mario world reaches 60fps at full speed without any of them.
I'm wondering what additional features need to be removed (scaling, sound, accurate graphics) to have this emu run at a decent speed on a N900 when forcing it to run at 60 fps.
Originally Posted by Addison
Because the first assumption is not true at all, and chunkyness depens more heavily on the amount of motion blur each individual frame has (among other things) than the actual framerate.
I know that the human eye can only take in 24 fps so why is it that it looks so chunky at that speed?
That's why 25fps is sometimes more than enough and 200fps is sometimes not enough.
 |
|
2009-10-14
, 10:47
|
|
Posts: 2,121 |
Thanked: 1,540 times |
Joined on Mar 2008
@ Oxford, UK
|
#38
|
Originally Posted by Addison
On consoles connected to TVs, I can certainly tell the difference between 30 fps and 60 fps. In fact, I can even tell the difference between 50 fps (normal PAL games) and 60 fps (NTSC). So I don't know where this 24 fps thing came from.
I know that the human eye can only take in 24 fps so why is it that it looks so chunky at that speed?
The golden mark for new games released on modern consoles is 60 fps which looks fantastic, but why isn't 24 fps good enough for the human eye to enjoy?
Maybe I should google this because it doesn't make much sense to me and I'm sure others have been confused about this the same as me.
| The Following 2 Users Say Thank You to pelago For This Useful Post: | ||
|
|
2009-10-15
, 19:12
|
|
Posts: 345 |
Thanked: 467 times |
Joined on Nov 2007
@ Germany
|
#39
|
I just uploaded a patch for zeemote support to thefeature tracker of drnoksnes. I really think this is the way to go as the wiimote is just to big to be carried with a n900.
Anyone here with a zeemote (or better two) who wants to test the stuff? Also perhaps someone likes to donate a zeemote to javispedro so he can also test it. And if you'd like to donate a second one to me i'd be willing to add support for a two player setup (my zeemote drivers are in fact designed to run up to 4 zeemotes simultaneously, i just wasn't able to test more than one for obvious reasons).
Anyone here with a zeemote (or better two) who wants to test the stuff? Also perhaps someone likes to donate a zeemote to javispedro so he can also test it. And if you'd like to donate a second one to me i'd be willing to add support for a two player setup (my zeemote drivers are in fact designed to run up to 4 zeemotes simultaneously, i just wasn't able to test more than one for obvious reasons).
| The Following 3 Users Say Thank You to Master of Gizmo For This Useful Post: | ||
|
|
2009-10-15
, 23:01
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#40
|
So no more interest is supporting the Wii remote?
Well shoot.
Well shoot.
BTW, don't expect miracles. Sad truth is that the GP2x Wiz (arm9 550Mhz) plays Mario Kart at a similar* rate than the N810 (arm11 400Mhz), thus I don't expect a "giant" leap in the N900 (cortex-a8 = "arm11+1?" <550Mhz **) in this case.
*Personally verified. There's a little speedup for rest of games, including SuperFx ones.
**Yes, the processor won't reach 550Mhz (at least, not all the time) due to thermal/battery reasons.
edit: Of course, there's quite a bit of room for optimizations, how to make best use of the SGX, etc.
Last edited by javispedro; 2009-10-14 at 05:46.