-
Posts
11,556 -
Joined
-
Last visited
-
Days Won
76
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Everything posted by Lordmonkus
-
Ok with the Retrolink brand USB N64 controller it pretty much just worked right out the box. Though I did have to select that controller in the Controls menu because I had 2 other controllers plugged in as well and I had to adjust the A and B buttons but the C-buttons just worked as they should. Ill see what happens when I tell the emu to use my Hori FC even though it has no analog stick it has the 6 face buttons like your controller.
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
Yeah I understand completely since that controller looks like a great option for N64 controls.
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
Hmm, I could have sworn I saw something in there to do what you wanted. I got a USB N64 controller, i'll plug that in and see what I can see with that controller. Maybe the fact I am using an XBox controller is making it annoying.
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
One is a c and the other is a k Just kidding, i'm sure it was just a typo.
-
Awesome, good to know And let me welcome you to the forums here. Rogue Squadron looks and plays great, just some minor sound distortion during the Star Wars story crawl. Perfect Dark looks, runs and plays great. Very nice work.
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
If you use the new nightly build you wont need to mess with the -c command, you can simply save out the control scheme in the core controller settings and it will just load automatically. Plus the nightly build seems to have better controller controls so you can set your c-buttons to actual buttons instead of the analog stick.
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
Well lets just say that Cen64 is not in usable state at all and a cycle accurate emulator is going to need a lot of processing power. Think about this, for 100% cycle accurate SNES requires a 3 GHz CPU to emulate a 3.5 MHz system. That means you need a hell of a lot more CPU power to do the N64 properly. This gets into why the Vulkan Mupen64 core was made. It was done to see if it was possible to emulate using the power of a GPU because CPUs are not getting that much faster anymore. If you can harness the GPU for emulation that means you can get more accurate emulation without having to scale the CPU requirements.
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
Not that I am aware of. The Vulkan one is just a hack of Mupen for Retroarch to use the Vulkan api, more of a proof of concept than anything. Here's the Cen64 page: https://github.com/tj90241/cen64
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
Hopefully Cen64 progresses and gets released sometime. It is aiming to be a more cycle accurate emulator rather than a hack job that Mupen and PJ64 are.
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
At the end of the day it is still N64 emulation using the same old code base and without a total rewrite from the ground up there are going to be issues. Examples of problems using GLupeN64 is Perfect Dark loads to the initial info screen and freezes and Rogue Squadron loads to a black screen. No N64 emulation is perfect, it's just a fact of life for now and getting small progress but GLupeN64 is small progress over current N64 options.
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
I have not tried Conker yet but DK64 and Banjo-Tooie look and play amazing running at 1920x1440 internal resolution. No obvious graphical glitches, sound is perfect.
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
Yeah I started tinkering with the new Glupen64 core and I am very impressed with it. It's by no means perfect, no N64 emulation option is yet but Glupen so far is the best overall.
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
Ahh I get what you are saying now. I loaded up my stable 1.3.6 install and I see exactly the issue you are having. But if you are feeling a bit adventurous try getting the latest nightly build and the GLupeN64 core. I had a quick look in there and it lets you have far more control over the controller.
- 59 replies
-
- 1
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
The best way to do it is in the core controller settings. With an N64 games running, open the Quick Menu go to Controls and remap it to the way you want and use the Save Core Remap File or if it is a game specific remap use the Save Game Remap File option. You may have to turn on Load Override or Load Remaps in the Configuration section of the Settings menu.
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
Are you remapping in the main controller settings menu or in the core remaps section in the Quick menu > Controls ?
- 59 replies
-
- controller
- retroarch
-
(and 1 more)
Tagged with:
-
Part 4 done and nothing more planned.
-
Yeah certain emulators make it more difficult than others, Retroarch though gives the ability to swap disks using the Quick Menu.
-
It should, Jason added in the feature that when you import multiple disks of the same game it automatically adds the other disks as an additional app. This used to have to be done manually.
-
Im not sure how ePSXe handles disk swaps it but I know it doesn't like m3u files. But if you import both disks Launchbox should detect that it's 2 disks of the same game and it will import as a single entry and then when you right click the game you will have to option of which disk to load. I think you will also get that option in BigBox mode but I have not tried it out.
-
Depends on which emulator, Playstation and Saturn through Mednafen and the Retroarch cores you can use an ms3 playlist. Make a text file and for each disk put the name of each disk image on its own line in the file and rename the file extension to .m3u Here is how my FF VIII is: Final Fantasy VIII (USA) (Disc 1).cue Final Fantasy VIII (USA) (Disc 2).cue Final Fantasy VIII (USA) (Disc 3).cue Final Fantasy VIII (USA) (Disc 4).cue Then you just import the m3u file into Launchbox.
-
Hehe yeah I got the notification of you liking my post and realized that this thread was that old and needed to updated lol.
-
This thread should be updated since we now have a Discord server, here is the link for it. https://discord.gg/X3Cwsyw
-
Part 4 - Quick Menu, Core Options and Cores This will be the last part of the guide barring some unforeseen circumstances and if something comes up I will either edit previous parts of the guide or I will make some notes here of if I need to I will make a part 5. The Quick Menu is a wonderful feature of Retroarch. This menu is accessed by pressing the F1 key on your keyboard, the XBox button on and XBox controller or if you are using a Playstation controller the PS button. This is also the same place you loaded shaders above in the last part of this guide. In the Quick Menu you can manage save states, take screenshots, manage disks for multi disk games and modify your controller settings. Most cores have their own "Core Options" or "Settings". These will be very specific settings to that system and not apply to other cores. To access these "Core Options" when you have a game loaded for a specific system access the Retroarch Quick Menu and go to the "Options" entry. This menu will look different for every system and some may not have anything in here and since we have been using the Genesis GX core all this time here is the Core Options for the Genesis GX core. There are a lot of cores to choose from in Retroarch and which ones you use are up to you and your needs and what your system is capable of. Different cores for the same system can have different system requirements, the SNES is an example of this. While BSnes-Accuracy is hands down the best core in terms of quality and compatibility it requires a 3 GHz CPU to fully take advantage of while the Snes9x core on the other hand has much lower system requirements but you won't be able to play 100% of all the games. The BSnes-Balanced core is a good middle ground. Then of course there is the issue of bios files, BSnes-Balanced and Accuracy both require special chip dumps from certain games to play them the BSnes-Mercury series of cores does not need these extra chip dumps. You can use them if you want to but you do not need them since the core is able to emulate them on a high level. Obviously I cannot tell you what cores you should use, you will have to decide that based on your needs and system but I will give you my recommended cores. Arcade - FB Alpha (without the year)though if you have an older rom set the older ones may be better for you. This core is very good for Capcom and NeoGeo games and I wouldn't try and dissuade anyone from using it but I prefer the stand alone version of Mame. Arcade - Mame same as above, use the core with no year unless you have an older rom set that need it. I also prefer stand alone Mame over Retroarch. Atari 2600 (Stella) and Atari 7800 (ProSystem) - Both are excellent and I use these over stand alone options. Dreamcast (Reicast) - Just don't use it, it is in very early stages and very buggy, use a stand alone option such as NullDC or Demul preferably. Gameboy Advance - mGBA is the best core hands down. NES - Both FCEUmm and Nestopia are excellent and pretty much equal though Nestopia may have a very slight edge in compatibility it also requires an .xml database file for full compatibility. Nintendo DS - DeSmuME the core isn't bad but overall quality goes to the stand alone, the RA core does however have the ability to use the right analog stick on a controller for the stylus. Nintendo64 - Use the GLupeN64 core, recent testing has shown this core is really good and a huge improvement over the standard Mupen64 core. It may even be better than the stand alone version of Mupen64 and Project64. Certain games may require some "core settings" tweaks such has Rogue Squadron needing RSP set to LLE and Perfect Dark you need to disable memory packs for all but player 1 controller. N64 emulation has a whole is bit messy but GLupeN64 seems to be in the lead for now. PC Engine / TurboGrafx 16 / CD - I use the Mednafen SGX core, this one core handles all of it. North American and Japanese hucard and cd games along with the 6 SuperGrafx games. The Mednafen PCE Fast core is perfectly fine as well though it will not do the SuperGrafx games. Playstation - Mednafen PSX core is the one I use but you can try the Mednafen PSX HW one if you like. It isn't quite as well developed but is getting better all the time and handles internal resolution scaling on a hardware level so it's faster. PSP - The PPSSPP core isn't bad but there is no reason at all to use it over the stand alone version of PPSSPP. Sega Genesis / CD / Master System / Game Gear - Easily the best core is the Genesis Plus GX core, it handles all but the 32X and does it with 100% compatibility and practically flawless. Sega 32X - PicoDrive is your only option if you want to use Retroarch but Fusion is the the better emulator if you want to emulate this system. Sega Saturn - Mednafen Saturn is your only choice here if you choose to do it through Retroarch. The Yabause core isn't even worth looking at, it is no where close in quality. The one downside with the Mednafen core is it still lacks analog controller support and for that the stand alone version of Mednafen is better for games that use the analog stick. However for games that don't use it the RA core is very good, though you may have to turn on Threaded Video to get 100% speed. This is pretty CPU intensive core. Super Nintendo - Basically you have 3 viable options here and I even talked about it above. Basically I recommend for most people to use the BSnes-Mercury Balanced, this gives you 99% compatibilty and decent system requirements. Use BSnes-Accuracy if you got the CPU to drive it and want 100% game support. If neither of these cores works for you then Snes9x is your best bet and just like the FBA and Mame cores use the one that has no year in the name, those are older cores and serve specific purpose. Any core I didn't talk about I simply do not use and I am not even remotely qualified to even give an opinion on. Well I hope this guide can be of some use to people that are new to Retroarch. There is a lot more stuff in Retroarch but to get through all of that stuff would require a whole other "Advanced" guide and probably be about as along as this one was or longer. If someone reading this guide finds any mistakes or wrong information please either leave a message below or message me directly and I will make the necessary edits to correct the errors. Part 5 - Controllers This part is a late addition by request and I apologize in advance for this part not being as in depth as the previous sections but because so many people use such a wide variety of controllers and have personal preference it would be impossible for me to cover it all. When setting up your controller if using something that Retroarch detects out of the box such as an XBox 360 controller it should just work automatically and be all setup. However if you need to change settings it may be a little confusing (depending on which version of Retroarch you are using). The main thing to remember when rebinding controls the left hand side of the screen represents the controller of the system being emulated and its button naming while the right hand side is the controller you have physically plugged into your PC. With an older version of Retroarch like 1.3.6 this will be somewhat confusing until you wrap your head around it. With a newer 1.4.1 build the devs have made some effort to label the buttons on the right hand side to match up with the controller you are physically using, for example if you are using a Playstation controller the right hand side buttons should be labeled like a PS controller with Square, Triangle, Circle and X. Here is the controller configuration page along with pictures to help you out to understand. https://github.com/retropie/retropie-setup/wiki/retroarch-configuration