N3DS touchscreen doesn't work with DSTwo when playing DS roms.

Discussion in '3DS - Flashcards & Custom Firmwares' started by linkenski, Nov 9, 2015.

  1. linkenski
    OP

    linkenski GBAtemp Regular

    Member
    280
    31
    Aug 6, 2008
    Denmark
    I've got a white regular New 3DS on 9.0E and as opposed to my o3DS the touchscreen stops being calibrated as soon as I launch a DS game with DSTwo. Touchscreen works right up until I boot a game and then every point on the screen touches [X,Y] = [1,1]

    What gives and how do I fix it? I wanna play on the n3DS because it has better contrast and saturation (or something. DS games look prettier on it IMO)
     
  2. CheatFreak47

    CheatFreak47 Complex Donut

    Member
    1,340
    902
    Oct 11, 2011
    United States
    Michigan, USA
    Go do the touch screen calibration in the 3DS settings.
     
  3. linkenski
    OP

    linkenski GBAtemp Regular

    Member
    280
    31
    Aug 6, 2008
    Denmark
    No dice. Same problem persists when booting DS games with the DSTWO
     
  4. CheatFreak47

    CheatFreak47 Complex Donut

    Member
    1,340
    902
    Oct 11, 2011
    United States
    Michigan, USA
    Does this happen on other 3DS consoles or just your n3DS?
    Are any of your DS roms patched?
    Does the Real Time Menu have this issue?

    I had a similar issue myself once on my o3DS, but running the touch calibration a few times fixed it.

    Try exiting to the 3DS menu via home button while in the DS game, and running the touch calibrate again. Sometimes it takes a few tries to get it to stick, I think.
     
    Last edited by CheatFreak47, Nov 9, 2015
  5. linkenski
    OP

    linkenski GBAtemp Regular

    Member
    280
    31
    Aug 6, 2008
    Denmark
    Everything works on the o3DS. Real Time Menu works on N3DS but as soon as I launch any game it fucks up the calibration to X,Y 1,1 and doesn't stop until I L+R+Start out to the game-select and then press L to go to Real Time Menu. Then it works again, so it seems like it's something to do with when DSTwo boots the actual games and not DS mode not working, because it certainly does, just not once I boot DS games from the flashcart.
     
  6. linkenski
    OP

    linkenski GBAtemp Regular

    Member
    280
    31
    Aug 6, 2008
    Denmark
    I think I've discovered the problem! I tried installing the MSET_REGION.CIA when I started hacking the 3DS but it always returned with an error, but if I go to DS profile settings my name was changed to something YsCAKES.DAT or whatever it was and then later appeared as "????U?.??T". going to the NDS Wifi settings also screw touchscreen up but if I take my Metroid Prime Hunters Demo catridge and play, the touchscreen works.

    My guess is, whenever my 3DS has to read from the stored NDS settings, it screws up. The problem is that after trying both recalibrating the 3DS touch screen, changing the name, the date, everything, it still doesn't fix the touchscreen issue, so I think my DS firmware is partially bricked or something.

    Hypothetically would there be a way to uninstall the failed install of MSET?
     
  7. Dean_

    Dean_ GBAtemp Advanced Fan

    Member
    651
    374
    Sep 11, 2014
    Simple system format will fix the problem.
     
  8. linkenski
    OP

    linkenski GBAtemp Regular

    Member
    280
    31
    Aug 6, 2008
    Denmark
    ...and remove my EmuNand or fuck it up.

    Anyway, i fixed it. The cause was a half-installed MSET_REGION.CIA that returned with an error and the solution was to find the matching title_ID in FBI under the "delete title" section and then install the MSET_REGION.CIA and it returned "successfully installed" and then once the MSET Exploit was in there, boot a DS game and voila! Now touchscreen works again.