Jump to content
LaunchBox Community Forums

turbofeet

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

5 Neutral

About turbofeet

  • Rank
    8-Bit Processor

Recent Profile Visitors

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

  1. What are you using as controllers? I would also try removing all USB Bluetooth based devices and try with the controllers connected by USB rather than Wireless. I have a new issue now with Micro Stuttering in modern games (not in Launchbox) so there may well be a windows update that is causing odd behaviour too. A fresh install of Windows may resolve that.
  2. Using a USB 3.1 Hub and have everything plugged into that. Everything is perfect now. 3.1 has more power available which I think helps.
  3. You got it man. I slowly plugged items back in and tested for a few days. I have had zero delay until...Corsair Dongle plugged into USB 2.0 Extension (for range) is the cause. What a b*stard! I'll plug it into it's own USB 3.0 Port and see how we get on.
  4. Thanks Neil I will test it a bit more when I get some more time and then perhaps start plugging stuff back in to confirm. The Corsair dongle was plugged into the USB 2.0 backplate in a Logitech dongle extension cable so perhaps I had complicated matters a bit lol...
  5. Ok so at work all seemed fine. It was when I brought it home it starting freezing up again. It's funny as it will load fine aside from the delays. The games would load too eventually. The only difference between work and home (same PC) was the amount of USB devices plugged in. At work I had my windows Xbox controller adapter and a Logitech wireless keyboard/mouse combo only. At home I have a Corsair K63 wireless dongle, Logitech gaming mouse dongle, aimtrak wide light sensor, infra red remote sensor and some other usb extensions as well as the other devices I had plugged in at work. I also have an older 4 port USB 2.0 header attached to the motherboard and some devices were plugged into that. Some of the dongles were even on extensions to give more range I unplugged everything except the Xbox wireless adapter, Logitech dongle and infra red remote sensor (media center). These 3 are all plugged into the motherboard USB ports only. It all seems to work so I think it's one of those other USB devices or the USB 2.0 header. Launchbox loads in about 20 seconds now. I will reboot a few times and keep testing in case it was a fluke.
  6. Yeah I was tempted to go back to windows 7 but support ends last year and I won't be able to play store games. I will find out what the issue is. Is there a logfile that can be populated in startup so I can see at which point it pauses?
  7. I have the same problem and I think it's definitely windows related (possibly Direct X). I say this because I also had the same issue loading the big box video, then launchbox (total 4-8 minutes) but I also had the same issue in Steam. I used this command to fix Steam "steam://flushconfig" which does work (and also seems to help LB as well) but then the problem comes back after some time (perhaps even after a reboot). Sometimes after a reboot it is fine for a while then starts freezing up (long delay) when launching games. Launchbox takes about 15 seconds to load (after the startup video) which is normal. I think Microsoft have truly screwed up Windows 10 in some recent updates. I installed Windows 10 Fresh today and I still have the same issue. My specs are: Windows 10 64Bit 32GB RAM ASUS Z270-A i7 7700K 1TB 970Pro NAND SSD for Operating System Samsung SSD for Emulated Game drive (G:) Nvidia 1080ti I think it should be able to handle Bubble Bobble. My LB installation is completely portable and when I run it on another machine (work - lol) it works fine so it's definitely nothing to do with Launchbox. My setup is a little different at home; in that my Launchbox and Emulators folders are local but I have a Symbolic Link to the Roms i.e. mklink /d "g:\Emulators\Roms" "\\<MyServer>\Emulators\Roms" I don't think that's the issue though. Windows defender is disabled. Weirdly it seemed OK initially after the Windows 10 re-install but the delay came back as soon as I plugged in all of my USB devices. I think it's a specific USB Device - most likely the controller or some other Human Interface Device. I have a lot of devices plugged in at home. Microsoft must have recently screwed with X-Input as my Turtle Beach Wireless headset no longer has sound for Division 2 and Gears 5 Audio has been screwed from the start with any Wireless headset. Before the re-install I removed GeForce Shadowplay which seemed to help but then (again) the delay came back. I'm still analysing and I'll let you know if I find the solution.
  8. Hi The only way I found to avoid the crap appearing is to use the Default LB options when importing the files. This means all textboxes checked. All I do is prioritise "World" (I think. It was a while ago) as the Default region as I am in the UK. Also ensure that games of the same name are combined (an option a little later on I think) to avoid all the different sets for the same game. You can always set a specific version (e.g. World or 4-player Version) of a game to be the default as well for individual games. LB also gives you the option in Big Box to launch a specific version. You could also try the "Consolidate Roms" option. That should clear out the multiple double dragons into one.
  9. I was also facing this problem. In the end I had changed so many settings in the emulator I was confused. I downloaded an older version (just a few weeks) and started from scratch. I have found that it happens when you set the emulator to "Start in Fullscreen". When I start it up windowed and then ALT+TAB it's fine. So; therefore I now run this AHK Script on start-up and it seems fine now: Sleep, 5000 Send, {ALT DOWN}{ENTER}{ALT UP} You may have to change the Sleep duration according to your setup. The above setting is 5 seconds before it sets it to fullscreen. In my case the Launching box starting window is still in the foreground so you actually don't see it. When you first set it up it creates a "yabause.ini" file and a "bkram.bin" file in your local appdata folder under your user profile. If you're like me and you want this portable then you can cut and paste these files into the same folder as the emulator and it becomes portable. I want everything to be portable so I ensure that the sat bios etc is all in a sub folder of the emulator as well so these can be referenced simply as "General\Bios=bios/Bios Saturn 1.01a (U) [!].bin" in the ini file. I attach my ini file for your reference. I am using version "yabasanshiro-2.8.1-e2696c.zip 2019/09/25" I think controller 2 still needs configuring and you may want to create a .bin fil for an action replay device. I just copied and pasted the bkram.bin and renamed it as areplay.bin and it will overwrite it when you set this up. Hope this helps as it was driving me nuts as well! 2rs wasted yabause.ini
  10. I found out that the ROMs I thought were "missing" were under different names. In previous launchers I showed all ROMs bit Launchbox tidies this up quite well. If it helps ensure that the version of MAME and the Romset you have "acquired" are the same version. You can also use a tool called clrmamepro to check the validity of the romset. Just YouTube if you need instructions. Good luck
  11. Thanks. I got there in the end!
  12. Thanks. I used MESS as I got it working nicely. I did try Stella but got some aspect ratio problems so went back to MESS. I retrospect it was probably more because of Windows Desktop Resizing due to my 4K TV. That causes a real headache and I have had to disable via compatibility settings for a few EMUs. I figured it out from another post on here. I set the emulator as right-thumbstick to quit (UI Cancel) rather than ESC and all is gravy. If you are used to pressing both thumb sticks you won't know the difference. Thanks for the reply. Appreciated
  13. Hi All Got everything working nicely in BigBox; all exiting when I press both Thumb sticks in on my Xbox one controllers. All except MESS which I use for Atari 2600. Pressing the ESC key quits it so nothing odd set up there. Tried an AHK script on exit of the following: ; No custom exit script is necessary for Retroarch ; since it already uses the Escape key by default send {Esc} Even though I do not use RetroArch... Anyone have any ideas? Gracias
×
×
  • Create New...