I found a bug. When I try to config Citra, it searches for file name 3dmoo.exe, and when i try to cinfigure 3dmoo, it searches for citra.exe. Their mixed up.
I've read the posts in this thread - yet I have to ask: What's the point of this?
1. Both 3dmoo and Citra support 3dsx loading.
2. Citra has a GUI already, you don't need to use the command line.
3. Both the CLI and the GUI version of Citra support booting applications by dragging the .3dsx files onto the citra executable file. 3dmoo probably supports that, too.
Am I missing some purpose of this tool? If indeed not, I'd prefer not having the emulator project I'm working on associated with this.
1. Both 3dmoo and Citra support 3dsx loading.
2. Citra has a GUI already, you don't need to use the command line.
3. Both the CLI and the GUI version of Citra support booting applications by dragging the .3dsx files onto the citra executable file. 3dmoo probably supports that, too.
Am I missing some purpose of this tool? If indeed not, I'd prefer not having the emulator project I'm working on associated with this.
If you don't like dragging and moving files, this boots them without drag and dropping, you just browser for a file.
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
I removed the version number from the thread's title.
edit:
and moved it to 3DS utilities section.
(that's hard to choose where to put emulators... they are launched from computer, they are not homebrew)
But I consider your application a front end, not an emulator.
edit:
and moved it to 3DS utilities section.
(that's hard to choose where to put emulators... they are launched from computer, they are not homebrew)
But I consider your application a front end, not an emulator.
I don't like having software that I worked on being shadowed by literally pointless software. You're advertising features where there are none, and either intentionally misleading users to make your software more popular or you just literally didn't even spend a single minute using Citra, yet use it for your software.
Actually, given that you distribute a binary of our software, why is no source code distributed along with it? The GPL (the license Citra uses) requires you to do so, so not only is the use case of your software dubious, but it's also violating our license.
Okay. Yeah, this program doesn't do much, but it's still easier to use and sexier.
New Update: Version 0.6
3DMoo will now not longer start as an extra opened Windows it will now start Directly in 3DSXLoader
And an Overall update of the Config menu with some fixes.
3DMoo will now not longer start as an extra opened Windows it will now start Directly in 3DSXLoader
And an Overall update of the Config menu with some fixes.
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
please comply with GPL and provide the sources (or don't provide emulators, that would be even better instead of including quickly outdated builds, and let the end user find the latest release himself).
Your application is not really a ROM loader, it's a front end right?
You select a .3dsx file and it sends it to the selected emulator with the selected user defined emulator's control mapping?
It's not a "ROM" loader. it doesn't load ROM, and only load the emulator with the file as argument (game or homebrew).
ROM is only used for chipset dumps, it's not an acronym for game files.
Your program description is confusing and user can think that it's actually Your program which loads the ROM thanks to citra and 3dmoo engine running in the background, but it actually runs the emulator.
I also don't understand the need of a program to send a file to another program which has the exact same features.
A front end for a command line program, I understand.
A front end to keep different settings for different games, I understand.
But creating a program to always "select a file" where the other program can already do it is (currently?) useless.
maybe if you plan to add more features later, it will be useful, for example different control mapping for each homebrew, etc.
but currently, emulators don't have lot of options and features to justify a front end.
Your application is not really a ROM loader, it's a front end right?
You select a .3dsx file and it sends it to the selected emulator with the selected user defined emulator's control mapping?
It's not a "ROM" loader. it doesn't load ROM, and only load the emulator with the file as argument (game or homebrew).
ROM is only used for chipset dumps, it's not an acronym for game files.
Your program description is confusing and user can think that it's actually Your program which loads the ROM thanks to citra and 3dmoo engine running in the background, but it actually runs the emulator.
I also don't understand the need of a program to send a file to another program which has the exact same features.
A front end for a command line program, I understand.
A front end to keep different settings for different games, I understand.
But creating a program to always "select a file" where the other program can already do it is (currently?) useless.
maybe if you plan to add more features later, it will be useful, for example different control mapping for each homebrew, etc.
but currently, emulators don't have lot of options and features to justify a front end.
Its an frontend Yes
Okey on next release of it i will remove the emulators
On thing I do is handle both emulators with on file on v0.7 I add option to 3dmoo for browse an directory for sdmc and other stuff will follow the key map can already edit by Citra in config menu
I aso will add an list to select roms in coming version
Okey on next release of it i will remove the emulators
On thing I do is handle both emulators with on file on v0.7 I add option to 3dmoo for browse an directory for sdmc and other stuff will follow the key map can already edit by Citra in config menu
I aso will add an list to select roms in coming version
- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
Thank you !
the Descrption and the main window now looks better
having a list of homebrew in a single window is good idea. no need to browse the file every time anymore
it checks only one folder, or also subfolders?
the Descrption and the main window now looks better
having a list of homebrew in a single window is good idea. no need to browse the file every time anymore
it checks only one folder, or also subfolders?
Similar threads
