Start doesn't start, A and B don't do anything, D-pad and analog sticks do nothing (but give visual feedback). That said, while the buttons are clearly being pressed and give feedback as such, it does not trigger anything in the games. In that windowed view (which basically takes up most of the screen on my 8-inch tablet), it is now visually evident that my touch is registering appropriately on the overlayed buttons. The sweet spot on resolution on my device seems to be 1280x960. Taking all of that into account as well as your ideas about resolution and such, I feel like we are making progress. Yes, the plugins that you mentioned are exactly what I am using, and are what the author of the virtual controller for this program recommended. Yes, the controller was appearing after starting the ROM but not responding (or giving any type of visual feedback that I was pressing the buttons on screen).
Thanks so much for the suggestions, Dyno2thefinish. Have you tried all the resolutions, in both windowed and/or fullscreen? I'd suggest going down the resolution list and seeing if you have any luck. All systems and devices are different so it may take a bit of experimentation to find something that works. This one worked right off the bat, while other resolutions did not. My native resolution is 1920x1080, and the windowed resolution when I run Project64 is 1152x864. The fact that the controller is appearing, but is non-responsive suggests a resolution issue. You may need to experiment with different resolutions. It is possible that you may need to experiment with the plugins for the emulator. We're glad you're enjoying GestureWorks Gameplay so far! Emulators are tricky and are often finicky in regards to their setup.įor Project 64, the controller appears after you start the ROM, but then doesn't respond? Which plugins are you using? Are they "Glide 64 for PJ64: 2.0.0.1" for the video, "Jabo's Direct Sound 1.7.0.7," for the audio, and "Nrage Input Plugin V2 2.3c" for the controller plugin?
0 kommentar(er)
