Homebrew [RetroArch] Nightly builds here!

[aliaspider]

anyone with a n3DS with emunand and some free time is able to run some tests ? would help me greatly in making more memory available for fba_neogeo/cps2 .cia builds.
these are the tests : http://buildbot.libretro.com/.aliaspider/tests.zip
there are 3 files, I need to know for each :
- if it can run.
- the value displayed in front of 'appmem'
- if you get kicked back to sysnand when you exit retroarch normally.

also, to help with correcting the analog sticks behavior, I need to know the minimum and maximum values displayed for X/Y for both the c-stick and the circle pad, when you push those completely up/down/left/right.
(doesn't matter which of the three .cia you use for this)

thanks

 

[xXDungeon_CrawlerXx]

anyone with a n3DS with emunand and some free time is able to run some tests ? would help me greatly in making more memory available for fba_neogeo/cps2 .cia builds.
these are the tests : http://buildbot.libretro.com/.aliaspider/tests.zip
there are 3 files, I need to know for each :
- if it can run.
- the value displayed in front of 'appmem'
- if you get kicked back to sysnand when you exit retroarch normally.

also, to help with correcting the analog sticks behavior, I need to know the minimum and maximum values displayed for X/Y for both the c-stick and the circle pad, when you push those completely up/down/left/right.
(doesn't matter which of the three .cia you use for this)

thanks

Does it work on N3DS with SysNAND, too?
Would be cool if you can make more memory available for pcsx

 

[NostalgicMillennial]

would emulation benefit it I updated my N3DS from 9.0 to 9.2 (somehow if possible?) or would it not matter

 

[aliaspider]

it will work for sysnand too, but you can't test if you get kicked from emunand or not there .

 

[doctorgoat]

would emulation benefit it I updated my N3DS from 9.0 to 9.2 (somehow if possible?) or would it not matter

why would it matter

 

[daxtsu]

anyone with a n3DS with emunand and some free time is able to run some tests ? would help me greatly in making more memory available for fba_neogeo/cps2 .cia builds.
these are the tests : http://buildbot.libretro.com/.aliaspider/tests.zip
there are 3 files, I need to know for each :
- if it can run.
- the value displayed in front of 'appmem'
- if you get kicked back to sysnand when you exit retroarch normally.

also, to help with correcting the analog sticks behavior, I need to know the minimum and maximum values displayed for X/Y for both the c-stick and the circle pad, when you push those completely up/down/left/right.
(doesn't matter which of the three .cia you use for this)

thanks

Here are my results:
test 0:
Runs? Yes, it runs
Appmem? 0x05000000
Kicked back to sysnand? No, it exits fine back to emunand

test 6:
Runs? Yes, it runs
Appmem? 0x07C00000
Kicked back to sysnand? No, exits fine back to emunand

test 7:
Runs? Yes, it runs
Appmem? 0x07C00000
Kicked back to sysnand? No, exits fine back to emunand

C-stick doesn't respond in any of the three tests (did you forget the ir:rst service in the RSF?).

Circle Pad:
Left: X: -153 Y: varies since it's hard to move the stick perfectly to the left, but it's usually between +6 and -7
Right: X: 152 Y: Same as left
Up: X: 0 to +2 Y: 151 to 153
Down: X: -7 Y: -157 to -158

Keep in mind that the circle pad values might vary between each N3DS, and if people have calibrated theirs or not. Also, if you meant if I get kicked back to sysnand when exiting retroarch in general, no, it doesn't kick me back to sysnand either.

 

[aliaspider]

excellent, thanks a lot !
EDIT: oh looks like I forgot to add the service xD

 

[daxtsu]

excellent, thanks a lot !
EDIT: oh looks like I forgot to add the service xD

You're welcome, and that's what I figured, lol.

 

[JJTapia19]

anyone with a n3DS with emunand and some free time is able to run some tests ? would help me greatly in making more memory available for fba_neogeo/cps2 .cia builds.
these are the tests : http://buildbot.libretro.com/.aliaspider/tests.zip
there are 3 files, I need to know for each :
- if it can run.
- the value displayed in front of 'appmem'
- if you get kicked back to sysnand when you exit retroarch normally.

also, to help with correcting the analog sticks behavior, I need to know the minimum and maximum values displayed for X/Y for both the c-stick and the circle pad, when you push those completely up/down/left/right.
(doesn't matter which of the three .cia you use for this)

thanks

Test 0
- it can run.
- 'appmem' value 0x05000000
- No it stayed in emunand

Test 6
- it can run.
- 'appmem' value 0x07C00000
- No it stayed in emunand

Test 7
- it can run.
- 'appmem' value 0x07C00000
- No it stayed in emunand

C stick didn't work on those 3
Tested on new 3ds 9.5 emunand

 

[aliaspider]

ok, uploaded a corrected http://buildbot.libretro.com/.aliaspider/test7.cia file. this will hopefully be the last test needed for this
(use http://buildbot.libretro.com/.aliaspider/test6.cia for the c-stick test in case the first hangs)

 

[daxtsu]

ok, uploaded a corrected http://buildbot.libretro.com/.aliaspider/test7.cia file. this will hopefully be the last test needed for this
(use http://buildbot.libretro.com/.aliaspider/test6.cia for the c-stick test in case the first hangs)

The new test7 didn't hang:
Runs? Yes
Appmem? 0x07C00000
Back to sysnand? No, goes back to emunand fine

C-stick:
Not touched at all: X: 0 Y: 0
Left: X: -100 to -120 (varies wildly), Y: 40 to 90 (it's sort of hard not to also be pressing it slightly upward due to it being like a Thinkpad nub)
Right: 100 to 142 (varies depending on pressure, it seems like?), Y: 20 to 40
Down: -70 to -110

It's sorta hard to get accurate readings from the c-stick, heh. It's not as easy to use as the Circle Pad.

 

[JJTapia19]

ok, uploaded a corrected http://buildbot.libretro.com/.aliaspider/test7.cia file. this will hopefully be the last test needed for this
(use http://buildbot.libretro.com/.aliaspider/test6.cia for the c-stick test in case the first hangs)

Test 6
- it can run.
- 'appmem' value 0x07C00000
- No it stayed in emunand

Test 7
- it can run.
- 'appmem' value 0x07C00000
- No it stayed in emunand

C stick Is working on both!
Tested on new 3ds 9.5 emunand

 

[aliaspider]

@daxtsu and @JJTapia19 thank you both !

ok this means that we can only get 124MB on n3DS, I was hoping to get 178MB, is probably possible but i have no clue how.
this is cool though, 124MB should be plenty for the cps2/neogeo cores, and it is nice that you don't get kicked back to sysnand like on o3DS when you request more memory.

 

[daxtsu]

and it is nice that you don't get kicked back to sysnand like on o3DS when you request more memory.

Oh, this sounds like the Smash Bros problem. Try pressing home and opening something like Health & Safety (or AlbertoSONIC's Quick Reboot, or my Smash Dummy Rebooter), then quitting that.

 

[Stack3r]

So gpsp is outplaying mgba now right? I'm getting 59 and small drops on fire red, but on mgba it's a constant 57 with sound issues and stuff, also what's the best settings to put for retroarchs refresh rate, and is there a way to have different configs for each core?

 

[aliaspider]

yeah I know that workaround, but no need to make it necessary unless the extra memory is actually needed, which is only the case with the neogeo/cps2 cores currently.

 

[daxtsu]

yeah I know that workaround, but no need to make it necessary unless the extra memory is actually needed, which is only the case with the neogeo/cps2 cores currently.

Yeah, that's true.

 

[Shadowrun97]

Does it really make sense to concentrate on the c-stick support if pcsx is the only emulator that has an advantage by the c-stick? I mean ...doesn't make it more sense to focus your energy on the stability of the emulator firstly to run the games with decent speed? ...and then optimize things like the c-stick control?

I've no idea of programming and much respect. I just want to understand your workflow/priorities.

 

[daxtsu]

Does it really make sense to concentrate on the c-stick support if pcsx is the only emulator that has an advantage by the c-stick?

Assuming Retroarch lets you bind functions like saving/loading states or fast forward/slowdown, you could use the C-stick for an extra four "buttons", so it certainly doesn't hurt anything.

 

[teampleb]

Does it really make sense to concentrate on the c-stick support if pcsx is the only emulator that has an advantage by the c-stick? I mean ...doesn't make it more sense to focus your energy on the stability of the emulator firstly to run the games with decent speed? ...and then optimize things like the c-stick control?

I've no idea of programming and much respect. I just want to understand your workflow/priorities.

Implementing the c-stick is a lot easier then that stuff. Mind as well get the easy stuff out of the way.