Search the Community
Showing results for tags 'project64'.
Found 4 results
Question: Can I completely disable Steam remapping my controller buttons when Steam Big Picture is running? Context for question: I've added BigBox as a non-steam game so that I can play my emulated games on my TV using my steam link. In steam big picture I disabled steam remapping my controller buttons with BigBox by using the settings pictured here. I didn't quite understand each of the settings, but I kind of guessed at what to disable and it worked. Two of my emulators and games work perfect when I open them by going: Steam Big Picture > BigBox > both Dolphin and SNES9x However I'm getting an issue with my controllers when I try to use a frontend for mupen64plus called m64p (https://m64p.github.io/). I have the controllers working on PJ64, but there are some issues. If I could solve either of my issues for my N64 emulators then that would be great. m64p The controller configuration works when I open the emulator through BigBox from my desktop, but not when I start out by going through Steam Big Picture. Is there someway to completely disable the Steam remapping of my controller buttons? PJ64 I opted to work with m64p instead for two reasons: 1. I want to run BigBox and all my emulators on my 3rd monitor. My primary monitor is 16:10, but both my 3rd monitor and my TV (connected to the steam link) are 16:9. PJ64 will only go fullscreen on the primary monitor (16:10) though, so I get black bars on the sides of my 16:9 TV when I use this emulator. I did a lot of looking around the internet and I don't think there is a way to play PJ64 in fullscreen on a monitor other than the primary one. 2. PJ64 gives this error when I try to open it with Steam Big Picture running if I don't remember to first turn off my Steam Controller. When I forget then its not just simply try again, the error persists until I stop streaming my desktop then start all over again. Retroarch: I put a couple hours into working with this emulator, but I can't get the controllers to work properly either. Not sure if this is my best bet, but I didn't want to keep sinking time into it.
Hi, I'm trying to get Project64 working in 16:9 ratio, but when I use the default Glide64 video driver in the latest Project64 I'm missing the "Emulation Settings" tab in the "Configure Graphics Plugin..." menu (which is where the drop down selector is for aspect ratio). I downloaded the Glide64 Final driver, and that allows me to see and use 16:9, but with that I'm having huge problems running HIRES texture packs. Are there any configuration file options that I can set to force the emulation settings tab to appear in the default Glide64 driver? Many thanks
I have been working around the clock night/day trying to tweak lb/bb like it is on my alienware laptop vs my console. and then i noticed on my console my user/windows folders were missing preventing me from being able to set bigbox up through my kodi build. days i tried to figure it out until some of you said it was absolutely fine to relocate my entire launchbox folder to where-ever. Great! now kodi was able to locate lb/bb exe and once again run. NEW ISSUES AND HEADACHES! Now keep in mind I only relocated kodi my emus/roms never ever moved from their location. Even though I never add them to lb I always copy roms from original location... I have 5 not 1 or 2... but 5! emus that won't run at all since relocating launchbox but before they were running perfectly! I tried deleting them and reimporting them but Launchbox is a smart girl... they still had same error... I was then told by 2 powerhouses of Launchbox dev team to get notepad++ and edit my xml files to fix the issues! I was already writing code at the time for new trainers/emus on my original xbox console... so me Having OCD/ADD/ and ADULT ADHD makes it difficult to focus all at once... Anyways I started editing the xml [wrong xml file] in launchbox and after i realized i was messing up I just stopped and put everything like it was... My the screenshots will show several things The way my brain is programmed you can tell me something all day and i'll either get it or miss it.. but if you show me i'll perfect it instantly... I've looked at all the tuts and none of them showed any issues with emus breaking and how to correct the paths once broken to fix. Can someone anyone please make a short tut on how to properly edit the correct xml file to fix my broken emus... I have a huge day this weekend to demo my work for lots of friends/family and I don't want it to be half done and...I will also be promoting Launchbox/Bigbox and it's amazing dev team like I constantly do on social media but in person. lastly project64 doesn't have same error as other emus but it does have one as shown in ss... it does work just fine manually loading roms as shown in ss. 1. BROKEN EMUS ON LB 2. ERROR I GET WHEN TRYING TO LAUNCH A GAME FROM ONE OF THE BROKEN EMUS 3.SCREENSHOT OF NOTEPAD++ 4. A NEW FOUND ERROR WITH PROJECT64 WHEN ATTEMPTING TO PLAY A GAME THROUGH LB 5. PROOF THAT THE EMU WORKS FINE ON IT'S OWN OUTSIDE OF LB?!