Homebrew 3dmoo - New 3DS Emulator

Status
Not open for further replies.

ichichfly

Well-Known Member
Member
Joined
Sep 23, 2009
Messages
619
Trophies
1
XP
1,075
Country
Gambia, The
I have assumed this to be fake as there are no downloads on that site and no one is mentioning it apart from you.

I'd love to be proven wrong though.

EDIT: Got the download, it's:

http://trondsemu.byethost15.com/emu1001.zip

Running yeti3DS-master.bin makes the emulator lock up before anything is displayed on screen.



Running yeti3DS-master.elf on 3dmoo gives this error repeated and a white screen:



Has anyone been able to run yeti3DS.elf, yeti3DS.bin or yeti3DS.3ds on Citra, 3dmoo or TronDS?

that are no error that is debug output try to wait a little longer (the new Version has a faster display reload timing)

also this is the decrypted Version from GW http://www.mediafire.com/download/r4kzeh5gd6p75jd/yetidecry.3ds this at last work on my Version of 3Dmoo.
 

Snailface

My frothing demand for 3ds homebrew is increasing
Member
Joined
Sep 20, 2010
Messages
4,324
Trophies
2
Age
40
Location
Engine Room with Cyan, watching him learn.
XP
2,255
I have assumed this to be fake as there are no downloads on that site and no one is mentioning it apart from you.

I'd love to be proven wrong though.

EDIT: Got the download, it's:

http://trondsemu.byethost15.com/emu1001.zip

Running yeti3DS-master.bin makes the emulator lock up before anything is displayed on screen.



Running yeti3DS-master.elf on 3dmoo gives this error repeated and a white screen:



Has anyone been able to run yeti3DS.elf, yeti3DS.bin or yeti3DS.3ds on Citra, 3dmoo or TronDS?
They both work. 3dmoo is reeeaalllly slow though. Citra is slow too but getting faster.

http://filetrip.net/dl?m1r8kVtGmC
(couple of working builds for lost souls)
 

ichichfly

Well-Known Member
Member
Joined
Sep 23, 2009
Messages
619
Trophies
1
XP
1,075
Country
Gambia, The
If you run decrypted roms on this emulator you won't get past the sound init

GPUwritereg32: GPU write 00000000 to 00400478
GPUwritereg32: GPU write 18000000 to 00400468
GPUwritereg32: GPU write 18046500 to 0040046c
GPUwritereg32: GPU write 18119400 to 00400494
GPUwritereg32: GPU write 1815f900 to 00400498
loader_LoadFile: Name: <snip>
loader_LoadFile: Code compressed: YES
loader_LoadFile: ExeFS offset: 00002c00
loader_LoadFile: ExeFS size: 001c2a00
loader_LoadFile: ExeFS section 0:
loader_LoadFile: name: .code
loader_LoadFile: offset: 00000000
loader_LoadFile: size: 001927a4
loader_LoadFile: Decompressing..
loader_LoadFile: .. OK
loader_LoadFile: ExeFS section 1:
loader_LoadFile: name: banner
loader_LoadFile: offset: 00192800
loader_LoadFile: size: 0002c750
loader_LoadFile: ExeFS section 2:
loader_LoadFile: name: icon
loader_LoadFile: offset: 001bf000
loader_LoadFile: size: 000036c0
loader_LoadFile: RomFS offset: 001c7000
loader_LoadFile: RomFS size: 0c071000
threads_Switch: Trying to switch to current thread..
svc_Execute: -- svcCreateAddressArbiter (0x21) --
svcCreateAddressArbiter: Create AddressArbiter 0FFFFFE0
svc_Execute: -- svcConnectToPort (0x2d) --
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_RegisterClient
svc_Execute: -- svcGetResourceLimit (0x38) --
svc_Execute: resourcelimit=0fffffe0, handle=ffff8001
svc_Execute: STUBBEDsvc_Execute: -- svcGetResourceLimitCurrentValues (0x3a) --
svc_Execute: values_ptr=0fffffd8, handleResourceLimit=deadbad0, names_ptr=0fffff
e4, nameCount=1
svc_Execute: STUBBEDsvc_Execute: -- svcCloseHandle (0x23) --
intern:148: svcCloseHandle undefined for handle-type "misc".
svc_Execute: -- svcControlMemory (0x1) --
svcControlMemory: op=COMMIT (3), addr0=8000000, addr1=0, size=2000000, perm=WR
(3)
svc_Execute: -- svcControlMemory (0x1) --
svcControlMemory: op=COMMIT GSP (10003), addr0=0, addr1=0, size=2000000, perm=WR
(3)
svc_Execute: -- svcDuplicateHandle (0x27) --
svc_Execute: -- svcQueryMemory (0x2) --
svc_Execute: -- svcGetThreadId (0x37) --
svc_Execute: -- svcDuplicateHandle (0x27) --
svc_Execute: -- svcGetSystemTick (0x28) --
svc_Execute: -- svcGetSystemTick (0x28) --
svc_Execute: -- svcCreateMutex (0x13) --
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcCreateThread (0x8) --
svcCreateThread: entrypoint=0013dbf4, r0=005ed3f0, sp=005ed3f0, prio=18, cpu=fff
ffffesvc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=APT:U, namelen=5, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
apt_u_SyncRequest: apt_u_GetLockHandle, flags=00000000
svc_Execute: -- svcCloseHandle (0x23) --
intern:148: svcCloseHandle undefined for handle-type "service".
svc_Execute: -- svcWaitSynchronization1 (0x24) --
mutex_WaitSynchronization: waiting for mutex to unlock..
threads_Switch: Thread switch 0->1
svc_Execute: -- svcWaitSynchronization1 (0x24) --
mutex_WaitSynchronization: waiting for mutex to unlock..
threads_Switch: Thread switch -1->0
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=APT:U, namelen=5, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
apt_u_SyncRequest: apt_u_RegisterApp, app_id=00000300
svc_Execute: -- svcCreateEvent (0x17) --
svcCreateEvent: handleoriginal=fffff88, resettype=0.
svc_Execute: -- svcCloseHandle (0x23) --
intern:148: svcCloseHandle undefined for handle-type "event".
svc_Execute: -- svcCreateEvent (0x17) --
svcCreateEvent: handleoriginal=fffff88, resettype=0.
svc_Execute: -- svcCloseHandle (0x23) --
intern:148: svcCloseHandle undefined for handle-type "event".
svc_Execute: -- svcCreateEvent (0x17) --
svcCreateEvent: handleoriginal=fffff88, resettype=0.
svc_Execute: -- svcCreateThread (0x8) --
svcCreateThread: entrypoint=0013dbf4, r0=00386fe0, sp=00386fe0, prio=2f, cpu=fff
ffffesvc_Execute: -- svcCloseHandle (0x23) --
intern:148: svcCloseHandle undefined for handle-type "service".
svc_Execute: -- svcReleaseMutex (0x14) --
svc_Execute: -- svcGetSystemTick (0x28) --
svc_Execute: -- svcWaitSynchronization1 (0x24) --
mutex_WaitSynchronization: waiting for mutex to unlock..
mutex_WaitSynchronization: waiting for mutex to unlock..
threads_Switch: Thread switch 0->2
svc_Execute: -- svcWaitSynchronizationN (0x25) --
Event_WaitSynchronization: waiting for event to happen..
Event_WaitSynchronization: waiting for event to happen..
threads_Switch: Thread switch -1->0
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=APT:U, namelen=5, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
apt_u_SyncRequest: AppletUtility 00000004 (0FFFFAE0 00000001,0FFFFAE4 00000001)

00 svc_Execute: -- svcCloseHandle (0x23) --
intern:148: svcCloseHandle undefined for handle-type "service".
svc_Execute: -- svcReleaseMutex (0x14) --
svc_Execute: -- svcWaitSynchronization1 (0x24) --
mutex_WaitSynchronization: waiting for mutex to unlock..
mutex_WaitSynchronization: waiting for mutex to unlock..
threads_Switch: Thread switch 0->2
svc_Execute: -- svcClearEvent (0x19) --
svc_Execute: -- svcWaitSynchronization1 (0x24) --
mutex_WaitSynchronization: waiting for mutex to unlock..
threads_Switch: Thread switch -1->0
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=APT:U, namelen=5, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
apt_u_SyncRequest: AppletUtility 00000007 (0FFFFB10 00000004,0FFFFADC 00000001)

01 00 00 00 svc_Execute: -- svcCloseHandle (0x23) --
intern:148: svcCloseHandle undefined for handle-type "service".
svc_Execute: -- svcReleaseMutex (0x14) --
svc_Execute: -- svcWaitSynchronization1 (0x24) --
mutex_WaitSynchronization: waiting for mutex to unlock..
mutex_WaitSynchronization: waiting for mutex to unlock..
threads_Switch: Thread switch 0->2
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=APT:U, namelen=5, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
intern:133: NOT IMPLEMENTED, cid=000e0080
arm11_Dump: Reg dump:
<snip>
svc_Execute: -- svcCloseHandle (0x23) --
intern:148: svcCloseHandle undefined for handle-type "service".
svc_Execute: -- svcReleaseMutex (0x14) --
svc_Execute: -- svcArbitrateAddress (0x22) --
svcArbitrateAddress: ArbitrateAddress DEADBAC1 003A39DC 00000000 FFFFFFFF 000000
00 00000000 svc_Execute: -- svcWaitSynchronizationN (0x25) --
Event_WaitSynchronization: waiting for event to happen..
Event_WaitSynchronization: waiting for event to happen..
Event_WaitSynchronization: waiting for event to happen..
threads_Switch: Thread switch -1->0
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=APT:U, namelen=5, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
apt_u_SyncRequest: AppletUtility 00000004 (0FFFFAE0 00000001,0FFFFAE4 00000001)

00 svc_Execute: -- svcCloseHandle (0x23) --
intern:148: svcCloseHandle undefined for handle-type "service".
svc_Execute: -- svcReleaseMutex (0x14) --
svc_Execute: -- svcWaitSynchronization1 (0x24) --
mutex_WaitSynchronization: waiting for mutex to unlock..
mutex_WaitSynchronization: waiting for mutex to unlock..
Event_WaitSynchronization: waiting for event to happen..
Event_WaitSynchronization: waiting for event to happen..
Event_WaitSynchronization: waiting for event to happen..
threads_Switch: Thread switch -1->0
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=APT:U, namelen=5, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
apt_u_SyncRequest: apt_u_Enable, unk=66630055
svc_Execute: -- svcCloseHandle (0x23) --
intern:148: svcCloseHandle undefined for handle-type "service".
svc_Execute: -- svcReleaseMutex (0x14) --
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=ndm:u, namelen=5, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=cfg:u, namelen=5, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=fs:USER, namelen=7, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcSendSyncRequest (0x32) --
fs_user_SyncRequest: fs:USER:OpenArchive(sex/000000000B0000F000000000/);
svc_Execute: -- svcSendSyncRequest (0x32) --
fs_user_SyncRequest: fs:USER:OpenFile(/ubll.lst);
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcCloseHandle (0x23) --
svc_Execute: -- svcSendSyncRequest (0x32) --
fs_user_SyncRequest: fs:USER:CloseArchive(sex/000000000B0000F000000000/);
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=frd:u, namelen=5, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcSendSyncRequest (0x32) --
frd_u_SyncRequest: GetMyPresence 004B0002,0FFFF9D8
svc_Execute: -- svcSendSyncRequest (0x32) --
fs_user_SyncRequest: fs:USER:OpenFileDirect(romfs/000000000000000000000000);
arm11_Dump: Reg dump:
<snip>
svc_Execute: -- svcSendSyncRequest (0x32) --
file_SyncRequest: read 0FFFFAD0 00000028 0000000000000000

svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcCloseHandle (0x23) --
svc_Execute: -- svcSendSyncRequest (0x32) --
fs_user_SyncRequest: fs:USER:OpenFileDirect(romfs/000000000000000000000000);
arm11_Dump: Reg dump:
<snip>
svc_Execute: -- svcSendSyncRequest (0x32) --
file_SyncRequest: read 0FFFFA18 00000028 0000000000000000

svc_Execute: -- svcSendSyncRequest (0x32) --
file_SyncRequest: read 0FFFFA40 00000028 0000000000000000

svc_Execute: -- svcSendSyncRequest (0x32) --
file_SyncRequest: read 098680B8 0000005C 0000000000000028

svc_Execute: -- svcSendSyncRequest (0x32) --
file_SyncRequest: read 09868114 00000368 0000000000000084

svc_Execute: -- svcSendSyncRequest (0x32) --
file_SyncRequest: read 0986847C 00001274 00000000000003EC

svc_Execute: -- svcSendSyncRequest (0x32) --
file_SyncRequest: read 098696F0 00015778 0000000000001660

svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=hid:USER, namelen=8, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcMapMemoryBlock (0x1f) --
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcSendSyncRequest (0x32) --
intern:65: STUBBED, cid=00160000
arm11_Dump: Reg dump:
<snip>
svc_Execute: -- svcSendSyncRequest (0x32) --
intern:65: STUBBED, cid=00150000
arm11_Dump: Reg dump:
<snip>
svc_Execute: -- svcGetSystemTick (0x28) --
svc_Execute: -- svcCreateThread (0x8) --
svcCreateThread: entrypoint=0013dbf4, r0=00592088, sp=00592088, prio=30, cpu=fff
ffffesvc_Execute: -- svcSendSyncRequest (0x32) --
file_SyncRequest: read 09864700 000001E8 00000000057C2D30

svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=dsp::DSP, namelen=8, unk=0x0
svc_Execute: -- svcSendSyncRequest (0x32) --
dsp_dsp_SyncRequest: LoadComponent 0000C288 003A3AB4 505300FF DEAD00FFmutex_Wait
Synchronization: waiting for mutex to unlock..
Event_WaitSynchronization: waiting for event to happen..
Event_WaitSynchronization: waiting for event to happen..
Event_WaitSynchronization: waiting for event to happen..
threads_Switch: Thread switch 0->3
svc_Execute: -- svcArbitrateAddress (0x22) --
svcArbitrateAddress: ArbitrateAddress DEADBAC1 0038E9A8 00000001 00000000 000000
00 00000000 svc_Execute: -- svcSendSyncRequest (0x32) --
srv_SyncRequest: srv_GetServiceHandle
srv_SyncRequest: name=ir:USER, namelen=7, unk=0x0
svc_Execute: -- svcCreateMemoryBlock (0x1e) --
svc_Execute: -- svcSendSyncRequest (0x32) --
intern:49: NOT IMPLEMENTED, cid=00180182
arm11_Dump: Reg dump
<snip>
svc_Execute: -- svcCreateEvent (0x17) --
svcCreateEvent: handleoriginal=591ea8, resettype=0.
svc_Execute: -- svcSendSyncRequest (0x32) --
svc_Execute: -- svcCloseHandle (0x23) --
intern:148: svcCloseHandle undefined for handle-type "event".
svc_Execute: -- svcWaitSynchronization1 (0x24) --
Event_WaitSynchronization: waiting for event to happen..
threads_Switch: Thread switch -1->0
svc_Execute: -- svcCreateThread (0x8) --
svcCreateThread: entrypoint=0013dbf4, r0=15c29fe0, sp=15c29fe0, prio=23, cpu=fff
ffffesvc_Execute: -- svcCreateThread (0x8) --
svcCreateThread: entrypoint=0013dbf4, r0=15c25fe0, sp=15c25fe0, prio=24, cpu=0sv
c_Execute: -- svcSendSyncRequest (0x32) --
file_SyncRequest: read 0FFFF9E0 00000040 000000000029DA40

svc_Execute: -- svcSendSyncRequest (0x32) --
file_SyncRequest: read 15C2C8C0 000085E0 00000000002A2F20

svc_Execute: -- svcSendSyncRequest (0x32) --
file_SyncRequest: read 15C34EA0 000054A0 000000000029DA80

svc_Execute: -- svcArbitrateAddress (0x22) --
svcArbitrateAddress: ArbitrateAddress DEADBAC1 15C4E240 00000000 FFFFFFFF 000000
00 00000000 svc_Execute: -- svcArbitrateAddress (0x22) --
<endless ArbitrateAddress loop> (ArbitrateAddress is not working currently)
 
  • Like
Reactions: Margen67

YoshiInAVoid

Banned!
OP
Banned
Joined
Jan 10, 2011
Messages
560
Trophies
1
Website
google.com
XP
465
Country
that are no error that is debug output try to wait a little longer (the new Version has a faster display reload timing)
Thanks. Working!

3dmoo.png


Unplayably slow though. Think I'll still use real hardware to debug.
 

KazoWAR

Well-Known Member
Member
Joined
Aug 12, 2008
Messages
1,952
Trophies
1
Age
35
Location
Winter Haven
XP
2,124
Country
United States
so work on sound and try again :D


also, i dont have a real 3ds to test on but is it normal for yeti to have the bottom screen a cutt off version of the top screen?
 

ichichfly

Well-Known Member
Member
Joined
Sep 23, 2009
Messages
619
Trophies
1
XP
1,075
Country
Gambia, The
so work on sound and try again :D


also, i dont have a real 3ds to test on but is it normal for yeti to have the bottom screen a cutt off version of the top screen?
no it is not the bottom screen stuff is not yet supported as I have not added some HW I/O ports

What It would need to run stuff that was compiled with nin sound SDK would be ArbitrateAddress but I have no idea how that works.
 

Snailface

My frothing demand for 3ds homebrew is increasing
Member
Joined
Sep 20, 2010
Messages
4,324
Trophies
2
Age
40
Location
Engine Room with Cyan, watching him learn.
XP
2,255
It'd be interesting to see the progress of both 3Dmoo and Citra. Things are starting to get interesting.
You betcha it is. As of just today, the latest build of 3dmoo has increased speed dramatically. Yeti3D now runs at about 4-5 fps, on both screens, which is faster than Citra (input too!). Homebrew compatibility is still not great, but we can be assured improvement in that regard will occur soon if today is any indication. :)
 
  • Like
Reactions: Margen67 and Celice

gamesquest1

Nabnut
Former Staff
Joined
Sep 23, 2013
Messages
15,153
Trophies
2
XP
12,247
i believe 3dmoo was in development before citra .....but just privately the devs behind 3dmoo are not just some idiot copy cats (ichfly made the gba emulator for the DS and Normmatt is a Former AKAIO Programmer) they have been on the 3ds scene for quite a while, and the DS scene before it, its good to have 2 experienced devs working on it

i say its good if its driving development of either emulator, but as always one will excel...place your bets XD
 

Jayro

MediCat USB Dev
Developer
Joined
Jul 23, 2012
Messages
12,964
Trophies
4
Location
WA State
Website
ko-fi.com
XP
16,974
Country
United States
okay, okay, fair enough... Why don't you developers work together then, sharing your knowledge and contributing your efforts to a single emulator? that would seem more efficient and beneficial than multiple emulators offering features the others don't have, etc...
 

Snailface

My frothing demand for 3ds homebrew is increasing
Member
Joined
Sep 20, 2010
Messages
4,324
Trophies
2
Age
40
Location
Engine Room with Cyan, watching him learn.
XP
2,255
okay, okay, fair enough... Why don't you developers work together then, sharing your knowledge and contributing your efforts to a single emulator? that would seem more efficient and beneficial than multiple emulators offering features the others don't have, etc...
Both projects are open source ...

It's the best of both worlds this way: competition with two teams and cooperation with open source info sharing.
 
  • Like
Reactions: Margen67

RichardLaughter_

Well-Known Member
Member
Joined
Sep 11, 2012
Messages
149
Trophies
0
XP
239
He makes a point. Competition inspires great things. Collaberation does too, but with competition, the competitors want to be the first to do it, while Collaberation doesn't have the need for speed. (That is if the devs look at it that way)
 

Inuuto

Enigmatic
Member
Joined
Feb 2, 2010
Messages
154
Trophies
0
Location
Undernet
XP
300
Country
United States
You betcha it is. As of just today, the latest build of 3dmoo has increased speed dramatically. Yeti3D now runs at about 4-5 fps, on both screens, which is faster than Citra (input too!). Homebrew compatibility is still not great, but we can be assured improvement in that regard will occur soon if today is any indication. :)
You said the latest build increased speed dramatically and then said that tit runs at about 4-5 fps. I'm sorry but that gave me a laugh. We're you'd get the info? I got to stay updated on the 3DS homebrew scene. I might join it in the future.

37690846.jpg
 
  • Like
Reactions: jocopoco
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: yawn