iNDS
iNDS copied to clipboard
WilliamLCobb
3D Sections
I know that this has been brought up on NDS4IOS but since this a different app this time around I wanted to mention that 3D sections on games such as Ace Attourney Apollo Justice don't work. Ex. While on the first case the first piece of evidence you have to examine is a hand of cards. Whats supose to happen is when you look at the blue card an examine button will appear but it doesn't. I've tried it on PC and it works on Desmume but not on NDS4IOS or INDS, any possible chance of fixing this or nah?
The same issue has been reported here: https://github.com/WilliamLCobb/iNDS/issues/56 Though it was about a different ace attorney game. It probably is because iNDS works on the previous version of Desmume instead of the most recent version. Why I suggest this is because if you search for these problems on the desmume forums you will find a lot of people did experiencing the same problem. They were probably on the previous version of desmume because the current desmume works fine as you suggested.
People say not to use DeSmuME 0.9.10 for many reasons. I'm assuming this is one of them. Don't worry. iNDS will use DeSmuME 0.9.11 soon, but that's at the bottom of the to-do list.
Alright, funny enough in the first game featuring the mission Rise from the Ashes the 1 3D part involving a phone does work. Weird. Also in the mean time is there any other ds emu that would work for this? I don't mind till they update to the newest Desmume but I'd also love to continue the PW series.
Updating iNDS to the latest version of DeSmuME would take days. There aren't any other ds emulators that will work.
@TuckingFypoTsu There is no other ds emu to my knowledge for iOS devices. Also ace attorney uses different ways to investigate evidence, I can only assume that those parts did not use the DS 3D rendering.
@DarknesGaming This is not an error caused by 0.9.10, as it is something that was not available at previous versions either. Also why say soon, if it is at the bottom of the to-do list. Do not expect it to be implemented soon.
Could you send an ingame bug report with the save state so I can work on this? And please mention the the 3d error and this issue number.
I don't think this is related to the DeSmuME version but because of some things I disabled to prevent crashes.
@WilliamLCobb Ive tried twice but i keep getting an error saying it couldnt be sent. What should I do.
If the reports don't go through you can quickly see the issue by playing Ace Attourney Apollo Justice. The problem only happens within the first 5 minutes of the first stage as it is the first piece of evidence you examine. Heres what it looks like, there should be an examine button on the bottom right.
This bug is definitely a problem. We need a detective for this! xD @essiw I only said the whole DeSmuME 0.9.11 thing will happen "soon." That was it. When "soon" will actually happen depends on lots of factors. One of them would be how long it takes to complete the To-do list.
@TuckingFypoTsu We can either tweak the 3D rendering to fix this problem or update to DeSmuME 0.9.11. The updating part may involve more tweaking so that it doesn't crash on iOS.
After waiting a while for Delta and its new NDS core in the hopes that would fix the bug, I decided to look into this myself. After some forum digging and GitHub searching, it looks like the original bug was fixed in the DeSmuME SVN in 2009, somewhere between 0.9.5 and 0.9.6. The code for the relevant function (gfx3d_glVecTest), looks identical, ignoring an unused ifdef, between the DeSmuME core in the iNDS source and the latest commit to the DeSmuME SVN (which doesn’t have the issue). This leads me to believe that the bug is something on the iNDS end of things.
My first theory was that it was something to do with touch coordinates not getting converted to game coordinates properly (maybe a float/int issue), but seeing how the issue still seems to occur when just using the virtual d-pad and buttons alone that’s probably not the case.
@WilliamLCobb, was there anything you remember changing that would have affected how that function worked? If you have any ideas as to the source of the bug I can try fixing it myself.
