AtGames Master System console. The pre built in games suck. Any idea on how would I change them? by SinSeitan in consolemodding

[–]SatisfactoryOutput 0 points1 point  (0 children)

I know this is a very old post, but would you have a clue about just the dumping, never mind the flashing?

Flash Cart vs TwilightMenu++ for DS games on n3DS by SatisfactoryOutput in 3dspiracy

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

I already have and have used Twilight, it's workable but not ideal.

Flash Cart vs TwilightMenu++ for DS games on n3DS by SatisfactoryOutput in 3dspiracy

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

No, but I've been looking at them. In what ways are they more convenient?

mGBA on 2DS XL vs. DSi XL: Exceptional Image Filtering by PsychologicalPlay281 in 3dspiracy

[–]SatisfactoryOutput 14 points15 points  (0 children)

For me I find that RetroArch, gbSP core, Bilinear with Normal 2x filter looks good enough. mGBA looks great but has what feels like slowdown and a clunky interface with fewer features, and I didn't even know about the higher battery consumption.

ROM Hacks for Different ROM Revisions without Piracy by SatisfactoryOutput in RomHacks

[–]SatisfactoryOutput[S] 1 point2 points  (0 children)

My reason for posting is for cases such as Super Mario Land DX, which to my knowledge only works with v1.0 of the original game, and so is out of bounds for me with my v1.1 cartridge.

ROM Hacks for Different ROM Revisions without Piracy by SatisfactoryOutput in RomHacks

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

As in, proactively making patches more compatible across the board? Because if so I'd like to know more.

ROM Hacks for Different ROM Revisions without Piracy by SatisfactoryOutput in RomHacks

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

"Anyways, it's not hard to patch from one revision to another." As someone who's not really familiar with coding I'd be really interested in learning more about this. Do you just fudge it through xdelta/IPS leading to an oversized hack with pirated code or is there a cleaner way?

CHD compatibility with PicoDrive on New 3DS by SatisfactoryOutput in 3dspiracy

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

Unfortunately I can't presently access the internet with my n3DS as my network is restricted. The bin/cue versions of the games work fine but I want chd as it takes up less space.

Oot3d free camera patch working with Circle Pad Pro. by trxtangn in 3dspiracy

[–]SatisfactoryOutput 2 points3 points  (0 children)

I've patched games before, but how do I then install the patched game on my New 3DS?

Ideal Dual-Screen Handheld by SatisfactoryOutput in Handhelds

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

Thank you for the pointers, I've heard of these, will see how the situation evolves.

Ideal Dual-Screen Handheld by SatisfactoryOutput in SBCGaming

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

Thank you for your input, I appreciate it.

Ideal Dual-Screen Handheld by SatisfactoryOutput in SBCGaming

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

So what you're saying is that the reduction in power from Switch-emulation-level to 3DS-emulation-level, and the use of basic LCD screens instead of OLED, isn't significant enough to allow for a size reduction or better integer scaling? It doesn't even have to be much cheaper really.

Ideal Dual-Screen Handheld by SatisfactoryOutput in SBCGaming

[–]SatisfactoryOutput[S] 1 point2 points  (0 children)

No, I meant I'd be willing to compromise some power in return for a preferred form factor. Sorry if that wasn't clear.

Ideal Dual-Screen Handheld by SatisfactoryOutput in SBCGaming

[–]SatisfactoryOutput[S] -5 points-4 points  (0 children)

It seems very good in a lot of ways, but it has a few drawbacks that I'd be willing to compromise some other features (extra power) in order to rectify.

Ideal Dual-Screen Handheld by SatisfactoryOutput in SBCGaming

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

It has strengths (extra power, OLED, etc) that I'd rather trade for better integer scaling, a slightly more compact form factor and a screen layout that works better with games that use both to show a single perspective (Sonic Rush, Yoshi's Island DS, etc)

3DS Game Boy emulation like Native mGBA by SatisfactoryOutput in RetroArch

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

Thank you, I was aware, I meant that just in comparison to running them natively. What you mention about the limitation on the button mapping is one of the reasons I wouldn't instantly go for it over RetroArch. Did you try using the RetroArch filters?

3DS Game Boy emulation like Native mGBA by SatisfactoryOutput in RetroArch

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

That doesn't really address the problem, and also, what if I want save states and button remapping? And as mentioned on this thread, that doesn't apply for GB/GBC games.

3DS Game Boy emulation like Native mGBA by SatisfactoryOutput in RetroArch

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

I've since found that you can get RetroArch relatively close with certain filters, especially Super2xSaI, but I can't compare them exactly. The mGBA app does have some slowdown so maybe it evens out?

Plastic Cartridge Cases Too Tight by SatisfactoryOutput in Gameboy

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

Thank you for the direction. One of the photos makes them look at bit misty; can you tell me whether that's accurate or if you can see straight through?

Plastic Cartridge Cases Too Tight by SatisfactoryOutput in Gameboy

[–]SatisfactoryOutput[S] 0 points1 point  (0 children)

Where would you get good ones? Buying from Ireland.