Jump to content
LaunchBox Community Forums

Headrush69

Members
  • Posts

    1,347
  • Joined

  • Last visited

Everything posted by Headrush69

  1. Just to be clear, you are using MAME standalone emulator and not MAME Retroarch core?
  2. Expect to get some varied answers, but both are great emulators. They have different goals and if your use case is just playing games than either will work. A few points: MAME supports more games MAME supports outputs (if that is important to you.) FBNeo supports Retroachievements in some games FBNeo supports Retroarch's shaders If you have lots of input devices, MAME is probably easier to deal with them. FBNeo supports end user improvements while MAME maintains absolute accuracy, (including faults and problems) FBNeo supports some hacked roms FBNEO supports alternate control devices, sound output, colors for various games Some will suggest that MAME is more accurate but that can be debated and likely not that important to the average gamer. Why not use both IF needed, Easy enough to set roms to use either emulator. No need to use one for all roms.
  3. I haven't had time to really investigate but since a couple versions ago I have the same consistent issues. It seems the GUI stalls yet everything is functioning otherwise. If I click around the screen, I can hear LB playing the preview video for whatever game I may be clicking on. The GUI elements don't highlight. The only way to fix is to close LB and restart. Edit: Ypu should ask a mod to move this to the troubleshooting forum where it will likely get more attention. This one is for website/forum problems.
  4. Me either. FYI If it's availiable and playable and you're looking to add it to your kid friendly setup, be aware the ending has some not too subtle nudity. sucramjd, would that be part of the artwork? 😆 Thanks again for all your work on these.
  5. Did you install Retroarch manually or through LB or both? It could be they are starting different Retraorch installations.
  6. No Launchbox doesn't have anything to do with emulator settings changing unless you have passed some command line options to the emulator. Teknoparrot is a constantly changing emulator. Have you recently updated it and have you checked that the custom resolution option is still set in the Teknoparrot UI? Just tested with MKDX1.18 and custom reolution @ 1920x1080 and still working OK.
  7. That's interesting. I still use RL mostly just for Teknoparrot for it's loading screens. Some Teknoparrot games take so long to start (Mario, Buck Hunter, etc) , so the having support for actively waiting for the game window over just timed start up screens is perfect. Of course if LB added startup screen longer than 30 seconds and it wouldn't be needed.
  8. There is no way to use CHD unless Rich the developer adds support for that format in a future update.
  9. Same here. I wasn’t suggesting changing.😃
  10. For the most part yes, but some people will suggest standalone emus over the RA cores of the same emulation engines. Some notable changes are: BigP emu for Atari Jaguar Ryujinx and Yuzu are both excellent for Nintendo Switch Retroarch has a separate a5200 core now that works well for many games (based on same atari800 core)
  11. I'm pretty sure this issue is inherent to the emulator and no solution exists at this time. I installed a clean copy of m2emulator to verify and when in windowed mode the emulator's internal resolution is 640x480. Larger windows, whether displayed or borderless, just stretch the image to fit. When in fullscreen mode the emulator's internal resolution is higher. For some games this may be perfectly acceptable but where it is especially noticable is if you use crosshairs. (Yes real men don't use crosshairs but these old eyes need them 😀 ) Crosshairs will get stretched as well which will make them larger. Of course you can account for that and resample your crosshair images smaller to account for the stretching. Just something to be aware of.
  12. I have a Logitech MOMO steering wheel and pedals working fine with both Retroarch flycast core and standalone Flycast. Your wheel will be mapped to a virtual XBOX layout and you will most likely need to go into the game service menu and calibrate the controls.
  13. You can but it might ackward and have the same issues you might be looking to avoid using the builtin Retroarch override system. I don't use them anymore, but you can pass Retroarch the location of the Retroarch config file and at the very least have that config put the to a different location for the options file. Retroarch doc is here. Not that I know of. You could also use a prelaunch command to copy/modify the options file manually which wouldn't tie it to the name. I have use this in the past but it's cumbersome to maintain (easier using Joe's bulk editors), but I find it was easier just to use the built in options for my sanity rather than trying to remember what hacks/routines I used for specific games.
  14. If you are using the a800 Retroarch core for atari computer systems and the a5200 Retroarch core for atari consoles, you should be able to bring up the Retroarch menu (F1 by default), go to core options and change the computer system emulated. Then just save a game override and that game should load as that system.
  15. I'm not sure where the error is. The first code is the old deprecated format, and the second one is the new format. Other than that they look functionally the same. (I haven't had my morning coffee though ) The default bezel will apply to all games. If you want seperate ones for vertical and horizontal you need a vertical.zip and a horizont.zip
  16. I don’t think so, but I could be wrong. I was sure it was hard coded into the emulator that it scaled when in full screen and stretched in window mode. That is why RL’s bezel system does and you don’t get the nicer scaled resolution. my guess is reshade and such intercept the frame buffer, rescale and do what ever they need than send the new frame buffer to get displayed. The emulator thinks it’s full screen still and uses the better scaled resolution. my setup is working so don’t really want to touch it, but I remember that was the issue when I set it up.
  17. If I remember from correctly, if you used windowed mode it stretched the image, no higher resolution internally like fullscreen mode
  18. You might be out of luck if you have to run the app fullscreen exclusive mode
  19. JoeViking245, am I right in assumming that since you are using window mode and hiddening window decorations that with the m2emulator that using window mode you run into the low resolution issue? Shaby, I use ReshadeManager for the m2emulator which uses a version of Reshade to work in full screen mode and add bezels.
  20. You can use MAME stable controller IDs to help with the issue: MAME stable controller IDs One problem is the IDs between the same Xbox controllers aren't unique (unless the situation has improved), so you could set up 2 xbox controller to specific IDs, but you can't make sure a specific xbox controller is the first or second xbox controller . For example you can map 2 xbox controller to MAME joystick 7 and one to MAME joystick 8. Which ever one is scanned or attached first will be assigned to MAME joystick 7 and the next one as MAME joystick 8. So within MAME you can map controls to joystick 7 and 8 for player 1 and player 2, but you don't know for sure which Xbox controller will be which.
  21. Just to clarify, I was referring to a fixed Pitfall rom. Starts and plays perfectly for me with the a5200 core.
  22. Are you using an actual trackball? What values did you end up with for sensitivity? I have a Hi-Rez encoder wheels on my trackball, so my values are different than most people, but I never played Marble Madness on a real cabinet, so I don't know exactly how it should feel.
  23. WOW those are some tight controls in that video. Have you adjusted the analog controls within MAME? Every once in a while MAME devs makes corrections and adjustments to control values if better information becomes avaliable. Whenever I have a random issue with MAME for a game that previously worked perfectly, I extract a clean MAME folder and run the game there as well. Helps narrow down whether it was a MAME change or possibly a faulty or corrupt older cfg, ini, etc.
  24. Still working fine for both. (I used ReshadeManager) I switched to using better lua scripts for widescreen support so don't use bezels for most m2 games now. I did have per game bezels, but if I remember correctly, finding the model 2 games bezels was tough. It wasn't a complete pack and I got them individually all over. I take a look and see if I still have them.
×
×
  • Create New...