Jump to content
LaunchBox Community Forums

wockawocka

Members
  • Posts

    12
  • Joined

  • Last visited

wockawocka's Achievements

8-Bit Processor

8-Bit Processor (3/7)

0

Reputation

  1. Window 10, RTX 4070ti, i7 8700 - Licensed Launchbox I'm having issues importing PSX games using the importer on LB. Everything otherwise works. I'm using BB / LB with Duckstation. The emulator works, the games load via LB / BB fine, everything is ok on the surface. But, when importing the games using the importer, be that using the whole rom folder or individual cue or CHD files out of 14 games only 10 go over. I've gone through the forum posts that I could see addressing things but there's no apparrent answer I can see and I'm surprised it's an issue with an older established format like this (so I'm assuming I'm at fault and it's a user error on my part). I've been using Launchbox for almost 3 years now but I'm finally going to try and deal with the issue but I'm stuck. I've used PSX Cue / Bin files and CHD's - The error is the same. I've made some progress but tbh I've got as far as I can with them, two examples are as follows: 'Einhander' is not detected in the importer but change the file names incorrectly to Einhaender and they import, (this works on a couple of others too). In The Hunt (Both one and two) don't import regardless what I do to the wording. I don't know the inner workings of the Launchbox importer. Perhaps it matches the files up against an existing list to import them or not. But either way it's frustrating. I haven't got 500 games in there, just 14 I want to play. If I use Bigbox then leave the frontend to Duckstation they're all there and working / playable. I'm at a lost to understand why the can't be loaded into Launchbox for selection. I'm happy to manually do it but I don't know how to do that.
  2. FIXED Ok so I got the new hardware and tbh I'll keep it anyway... but it didn't fix the issue. What fixed the issue was installing retroarch, which then installed directX 9. I never even ran Retroarch, I just started mame64 as normal. Turns out that installation fixed things and I've full scanlines. It has been an extremely painful process, in that I didn't consider other versions of Direct X as Windows 10 comes with the latest version as standard.
  3. So here's an interesting update. I did a fresh format and re-install, I didn't update windows on install like before, only installed mame64 and one rom. Still no scanlines. So it's hard to believe but I thing it must be something with the motherboard / chip combo but everything tells me that shouldn't be the case. Edit - I just ordered a new motherboard , Asus A320M and a Ryzen 5 2600X and I'll update accordingly. I am starting to think it's the hardware, two other more modern setups are running scanlines fine except this build. I'm taking comfort in the fact that on paper, it'll be twice as fast.
  4. I think it could be some freaking WIndows 10 thing getting in the way. But that's beyond my experience level tbh. It was much easier investigating this stuff on a Win7 machine.
  5. I'm starting to think that, I mean, what else could it be? Hardware: Intel 2600k 16gb ram GTX 750ti (also tried onboard at GTX 1660ti) Mobo is an Asus P8277V-LX * Shrugs *
  6. Update: Still no joy. I didn't get any graphics options in D3D when I hit the tilde key. D3d, OpenGL, GDI and BFX all have the same options!
  7. Ok cool, I'll give that a go. Currently only running Mame outside of Launchbox to nail things down.
  8. I currently appear to have two, one in a presets folder, another one in the parent directory. Is this right?
  9. Oddly my main rig stopped doing scanlines in one way for no obvious reason just now until (when it was before) I went back to D3D and yep I had noticed different settings gave different results. Are there any places that mame could be hiding settings that I'm not checking. I've cleared the ini folder out and also removed the main mame in in there a couple of times.
  10. Yes, no joy. I've copied working ini files and full, known working directories over to see if it helps, but it didn't.
  11. Help. Basically. I purchased and installed Launchbox with a Mame standalone (0209b 64bit) on my main rig and I get scanlines AOK. In fact, it's all good in that respect. I then built another computer for my bartop, bought a 750ti to betterthe onboard gpu yet I cannot seem to get the scanlines to work, none of the online ini file tweaks I've seen work. I've tried 4 now without success. I've tried this with not only the 750ti, but the motherboards onboard gpu as well as a 1660ti. What I will say I've noticed is when I hit the tiele key ( ` ) to get the pop up menu in game , there is a massive amount of options open to me on the working machines than when I pressed it on the machine I have an issue with. This problematic build is comprised of parts a few years old ( 5-6 years ) , but I'd be surprised if it was the hardware. I tentatively don't think it's mame as I've tried new installs, copied my working builds over and tried everything that I can think of to rule out things. I'm now genuinely at a loss at to where to look next. I don't think it's a simple mame.ini fix now :s
  12. Hi, I've installed Launchbox premium, I love it but I'm having trouble creating carousel sub menus (like CPS1, CPS2, Shmups...etc) and also I seem to be unable to correctly get videos to display on the main Bigbox carousel screen. I have them, they just don't run so I'm likely putting them in the wrong place. I have had a look on the forums but before I go through hours of video looking for the answer it would be awesome if some has been there before me and where I should be looking! TIA! P.S. To the creators.... GREAT SOFTWARE!
×
×
  • Create New...