Jump to content
LaunchBox Community Forums

jacob.pederson

Members
  • Posts

    15
  • Joined

  • Last visited

About jacob.pederson

  • Birthday 07/18/1977

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

jacob.pederson's Achievements

8-Bit Processor

8-Bit Processor (3/7)

0

Reputation

  1. I'm looking for a way to truly force a full-screen aspect ratio, without allowing the theme to insert black bars? I'm aware of the "force" settings in themesettings.xml; however, they don't seem to behave that way. Instead they force 4x3 or 16x9 while taking the current resolution aspect ratio into account, then inserting black bars to compensate. The problem with this approach, is that is doesn't allow for me to use the "weird" 4:3 CRT modes that are available to me, such as 632 x 264. Instead I am stuck on VERY LOW RES modes to correct the aspect ratio issues. Thanks! <Force16X9AspectRatio>true</Force16X9AspectRatio> <Force4X3AspectRatio>false</Force4X3AspectRatio>
  2. Yes, but only on the CRT portion of the setup, and that only applies after RetroArch launches certain games so it probably shouldn't effect it? Also it looks normal when you have the 1080p screen set as primary.
  3. Anybody know what could cause the BigBox fonts to shrink? (It's not a DPI issue) I've been messing around with a lot of different methods for swapping monitor primary / secondaries around because I'm trying to incorporate some regular PC games into my arcade cabinet. Suddenly everything looks like this. Any ideas? My setup is a 240p CRT as primary and a 1080p mini monitor normally for menus. It worked fine a second ago? Edit: When the 240p screen is set as secondary, Bigbox looks normal . . . but I need it to be primary for windows games to launch on the correct screen. Arg? Edit2: When the 240p screen is set as primary, the bigbox splash appears on that, but then bigbox respects its settings and moves over to the correct screen (perhaps its pulling a font DPI based on the 240p screen over to the 1080p screen?) Edit3: For now I'm just going to give up on the idea of using the marque screen as the menu and just resign myself to very blurry menus
  4. I managed to just about break my entire cabinet with display fusion so I uninstalled that. Retroarch does this thing where it randomly messes up which monitor is which. Same thing with Big-box. Since I'm running a 240p screen is is VERY difficult to find menu options when the screens get messed up. GRR.
  5. I am trying to figure this out also. Just getting around to adding various native games to launchbox, and sofar, can't get any of them to launch on the proper monitor. All I've found so far is this https://www.autohotkey.com/boards/viewtopic.php?f=19&t=29175&sid=5fbdbe1a91d6ff085cba674cde7389be but seems needlessly complicated to just change the frigging monitor
  6. Arcade Cabinet Custom Attract loop using autohotkey. (Bigbox + Retroarch) I got this great idea this morning that the attract mode would be alot more attractive if it actually launched games, so I made this script. Super easy mode if anybody wants to try it. If any wizards want to make a better version of the script that sleeps when you're playing a game, then turns back on. That would be even better! https://www.youtube.com/watch?v=uAni6umWQtM Custom Attract Loop.ahk
  7. X2 - No Relief (Japan) hangs up at Environ performance level 15 when launched from launchbox when launched from within retroarch it launches normally. core is mednafex_psx_libretro.dll. Xevious 3D/G+ (USA) launches correctly from both Any ideas where I could have screwed up? Is there a bios getting selected somewhere I'm not aware of? Thanks! Solution: launchbox was pointing at the 7zip file instead of the cue file. I'll just leave this post here in case somebody else runs into it.
  8. YES! This is what was causing it. The SNES one had an core association already in there or created automatically. The MAME one didn't even have a platform. Thanks so much for your help!
  9. It's definitely the core causing problems. When I add a manual command line switch path to the core like so (retroarch -L /path/to/libretro/core.so game.rom) in the launchbox properties, the game launches correctly. Is there a spot somewhere to select this, so I'm not doing this for every game?
  10. Yes, launching the SNES games from launchbox, using retroarch as the emulator works correctly. I'm not sure where to tell launchbox to use a specific core. I thought it was grabbing the core preferences from the retroarch playlist. I have around 80 hours in to setting up this retroarch install already, I was adding launchbox because some of my games need specific renderers (d3d vs opengl) and retroarch doesn't support switching renderers. I saw that launchbox had the command line options thing and figured that was my best bet.
  11. I don't think this is the issue because I had no issue launching SNES games through this same retroarch install.
  12. I had a heck of a time grabbing that error cause I couldn't figure out were the retroarch log file is, so its a screenshot of a video running in slow motion. The error is only on the screen for a few milliseconds.
  13. I think so, otherwise I wouldn't be getting a retroarch error popping up when I launch the games (see screenshot). Why would the install folder cause issues? I'm pretty sure that is the default install location for retroarch on windows. There is a whole complaint thread for the install location lol
  14. Anybody know a way to fix libretro_path is not set error when launching mame files? They launch correctly from within the retroarch menu system. Preferably a fix that doesn't involve setting the core path manually on a per shortcut basis. Thanks!
×
×
  • Create New...