Jump to content
LaunchBox Community Forums

Lordmonkus

Members
  • Posts

    11,556
  • Joined

  • Last visited

  • Days Won

    76

Everything posted by Lordmonkus

  1. Thanks for your efforts, it's too bad that more people aren't helping with it.
  2. and now DariusBurst is on sale on Steam, 60% off, they must have been paying attention to this thread lol
  3. lol it's a common problem, I have been on Jason to improve the associated platforms window bay having pre filled drop down menus to try and help reduce the user error in this regard.
  4. What core are you loading in the command line parameters of the associated platforms window ? Are your SNES games using Retroarch to load ? What core are you wanting to load in Retroarch and is that core .dll file in the \cores folder of your Retroarch install folder ?
  5. One of the main differences I have seen between the stand alone Mednafen and RA versions is the RA version does require a little more CPU to drive it. My system (AMD 8350 @4Ghz) is just on the bubble of being just barely fast enough to run the RA core. I can run it perfectly fine for the most part but I do get the occasional audio crackle. There are 3rd party GUIs for Mednafen but I haven't found one that I like, This one here is the newest and more fancy one though if you wanna take a look at it https://medlaunch.info/ I just set my Mednafen up manually editing the config file which does suck but that's more to do with the fact they put every single emulator core setting in a single config so navigating through it gets to be cumbersome at times. It would be nice if they broke up the different sections of the config by system. They do have very detail documentation on their site though and you really don't need to configure too many settings at all to get the most out of it. One downside to the stand alone when compared to the RA core is the lack of CHD support and the devs have stated on their forums that have no plans to ever put that support in.
  6. I use the mednafen_supergrafx_libretro core just because it does the SuperGrafx games as well as the regular PC Engine / CD games but the mednafen_pce_fast_libretro is perfectly fine as well. There is an accuracy core in the stand alone version of Mednafen though if you really want the extra accuracy.
  7. It'll go on sale again for a good price. I'm good waiting, I got plenty of great shooters to keep me going til then.
  8. Yeah it's a great game, I have played it at a buddies and I have it on my Steam wishlist waiting for it to go on sale for a reasonable price, 55$ just feels a bit high for a shmup to me when I got Darius Gaiden which I love so much.
  9. Yeah sometimes the other game executable can be located in a sub folder like \bin\ as an example. I guess sometimes they just force you to go through the launcher which is lame.
  10. That's very strange to have 2 exes and both be for the launcher, every time I have seen games with launchers you can bypass the launcher by loading the other exe in the install folder.
  11. Hmm, interesting I couldn't get it to work with my controller with the Nestopia core but yeah your solution is the best way to load a different core. And just FYI you don't need to upload images to a 3rd party site to post them here, you can directly upload them when posting.
  12. Did you look in the install folder for another executable ? If there isn't one you can probably setup an AHK script to press the Enter key on your keyboard since it looks like that would press the "Launch" button
  13. I had a look and in the core controller options there is an option for the Arkanoid controller but I couldn't get it to work. I tried setting up 2 controllers, one as a normal controller and the 2nd as Arkanoid and the other way around as well but no luck in either configuration. I even tried the stand alone version of Mesen along with the Nestopia and Fceumm cores and neither of them worked either, maybe i'm missing something. The actual game was packaged with its own rotary controller so maybe that has something to do with the emulation of it not working the way it should.
  14. I would love to be able to make a tutorial on this but to be perfectly honest I don't feel even remotely qualified enough to explain it in a way that is correct so instead what I will do is this. Here is a direct copy paste from http://emulation.gametechwiki.com/index.php/Input_lag "Some emulator frontends like RetroArch or GroovyMAME have the option to delay processing of emulation for a few milliseconds until right before a vsync occurs, which causes inputs to be polled quickly before your display refreshes instead at the beginning of the 16.7ms (for 60 fps) vsync period. The amount of time you can use frame delay without dropping frames is dependent on the performance of the emulator on your machine. Predictive waiting may also be forced with any DirectX based program through GeDoSaTo. Realistically, this is the last thing to configure, after all other sync and buffer settings have been configured for your system's performance. It is only useful with significantly more power than is required to run at full speed." Essentially the way I understand it is this (keep in mind this is my interpretation of the information and I could be wrong). If you have a display that runs at 60hz and v-sync enabled this means the game is running at 60 fps which equates to 1 frame every 16.7 milliseconds. The emulator polls for input at the beginning of every frame and then it has 16.7 milliseconds (ms) to do all of its "emulation work" before it displays the next frame. This is an automatic 16.7 ms of input latency on top of what ever latency your display has (more info below). What frame delay is doing is holding off that input poll until the last possible millisecond based on the frame delay setting. If you have a frame delay of 10 it is delaying that input poll by 10 milliseconds this means you then have 6.7 ms between when it polls for input and when it renders the next frame on screen. This also means that your computer only has 6.7 ms to do all of its "emulation work" before it outputs the next frame on screen this is why pushing your frame delay setting too high causes performance issues and audio crackling. The higher you push frame delay the faster and more powerful a CPU is required, this is also why heavy CPU requirement cores such as Higan and Beetle Saturn cannot achieve the same levels of frame delay as other cores that do not have the same CPU power requirements. High end gaming monitors have approx somewhere between 1-5 ms delay, average PC monitors have slightly more but not a drastic amount, maybe 10-30 range, it really depends and varies from monitor to monitor. TVs however have quite a bit more input latency because it has extra video processing hardware in them to make the image better for watching video. You can reduce it somewhat by turning on gaming mode but this does not remove the input latency completely. I good TV with gaming mode enabled will still have 50-80 ms and without gaming 120+ ms of latency. ***Disclaimer: The numbers provided above are not 100% accurate because it varies greatly by maker and model of display. Also all numbers provided are for illustration purposes to explain what is happening, they are fairly close though as to not totally skew the information. So please if you are reading this and anything I have provided is way off base please let me know instead of tearing me a new asshole***
  15. Unfortunately very few people use Raine anymore and it's been many years since I have even looked at it. I did a Google search and I did find there 2 posts over on the GameEX forums: https://www.gameex.info/forums/topic/13534-resolved-raine-neo-geo-cd-command-line/ https://www.gameex.info/forums/topic/13617-raine-neo-geo-cd-command-line/ You also may wanna look in your Raine folder for any documentation that might be able to help you out with loading via command line.
  16. Just copy / paste that script into the Autohotkey Script tab of the Edit Emulator window of your PinballFX emulator window, it's in the screenshot you posted above.
  17. Try setting your ini files to read only. I have not run into this issue myself ever but I have heard of instances where people with wireless controllers lose their controller settings when Mame gets started up without the controller turned on.
  18. If it's just gonna be your NUC or whatever you use to take to your friends and then take it home with you again when you leave you can leave the license file on it. The only thing you can't do is give your friends the license.xml file.
  19. Not sure what to tell you, if they all work in Retroarch outside of Launchbox and some games work in Launchbox they all should work in Launchbox.
  20. Yeah, that's perfectly fine. I have done this myself for friends, loaded up a USB stick with everything setup and removed the license.xml file and they were good to go.
  21. It's a very technical discussion but the simple thing to know is the higher the frame delay the lower the input latency. Frame delay is a setting in the video settings of Retroarch and if it's something you are going to use you should be doing it on a per core basis because not all cores use the same amount of CPU power to push it. Cores that require a lot of CPU power like the Beetle Saturn or the BSnes and Higan SNES cores require far more CPU power to run them than compared to something like the Nestopia core for the NES and the Mesen core requires more CPU power than the Nestopia core. You should play around with the different cores and the frame delay setting to find the right setting for each core. What you wanna do is push the frame delay up until you start hearing audio glitches and crackling. Once you start hearing these crackles drop the frame delay back down 1 or 2 settings and save out the Core Override.
  22. Try setting an AHK script to to close it $Esc:: { Process, Close, {{{StartupEXE}}} } This will close it when you press the Escape key which is what Launchbox uses with its controller automation.
  23. I think if you just set video to "auto" # OSD VIDEO OPTIONS # video auto and then enable HLSL # DIRECT3D POST-PROCESSING OPTIONS # hlslpath hlsl hlsl_enable 1 Setting the video to Auto instead of BGFX should tell Mame to ignore the BGFX settings. Yeah, should work just fine.
×
×
  • Create New...