MazJohn [Mr Arcade]

Thanks, so far That seems to be working. Whats odd, is that I've previously made the default config file read only without success.... however by making the whole folder read only seems to be blocking the configuration from being wiped. I had to go into advanced permissions and remove write access for all users for it to work. Oddly, using the same ports restricted to read only works regardless to what windows assigns!

Hi all, been having this issue for over 1 year now. Mame isn't holding onto joystick port mappings on re-boot with Xbox one wireless controllers.... since v .170 all the way up to the current release of 0.187, I've tried everything imaginable without success.... Without a reliable Mame, my launch-box build is severely lacking. Windows 10 and the wireless adapter seem to randomly assign different joystick ports everytime the system is powered off and back on. Mame resets the port mappings back to default every single time my machine is turned off and back on. If the wireless controllers are not powered on, mame also wipes the controller mappings... wondering if I Am i the only one with these issues? im using xbox one wireless controllers with Launch-box connected to an HTPC over a 10 ft interface on the couch... wired controllers are not an option here. I cant seem to emulate the older mame32 stuff with mame .187 using retroarch cores otherwise i would dump mame completely. I Appreciate any help , feedback or thoughts ... also are there other types of wireless controllers that i could switch over to to prevent this? anyone have success ? apologies for the rant....lol

SmPetty, thanks for the detail... for the very first time, i,ve gotten my launchbox setup working without needing to leave mode 4 with my 2 xbox360 controllers combined with mayflash bar, retroarch 1.5 and all other emulators including dolphin... all running on the windows 10 creators build update... im thinking to block my build from taking future windows updates at this point so it remains stable.... lol... pleaee keep this thread going... it is one of the most important threads to anyone using a mayflash dolphin bar in combination with retroarch and other emulators.....seriously!

Hey there blackstar1 and mmsiphone, Only feedback i could provide is from my previous post... so this may or may not apply- after i upgraded to the creators build of windows 10, i had a corrupt nvidia driver update (dated 4/5 or 4/6 if i recall) that caused constant crashing when launching any application that utilized direct-x (including Launch-box) The solution for me was to to completely remove and re-install the latest nvidia driver. Once i did that, Launch-box and all other direct-x related applications are working great for me with the creators build update. I've have no further issues since. if you are using an nvidia card, i would give that a try- thats what worked for me. regards, Mazjohn (aka Mr. Arcade)

CKP, SentaiBrad, Thanks, I was totally unaware notpad++ could batch replace multiple files at once like that to open documents. That does make it quite a bit simpler to do for sure. In my case, I am very reluctant to re-import but would do so as last resort. While it does also work provided we " uncheck" and do ROMs only, i've admitantly "botched things up" in past by my own doing simply because I fail to re-import sets exactly the same way and find myself having to clean things up a little. (My bad here nothing to do with Launchbox...Launchbox itself has been simply incredible). Thanks again much for helping to take the time to explain. That was huge. Mazjohn ( aka Mr. Arcade)...

Ahhh... Thanks! I've been using Launchbox a pretty long time and was un-aware of the changes since. (I was still thinking the rom paths were controlled by the Launchbox.xml file!) So drilling down into launchbox\data\platforms then individually editing the paths does work for me... problem solved! however if there are 30 platforms, it seems i will need to edit each and every one (one at a time) that's STILL easier to me than having to re-import again for many platforms (as also mentioned) - so it will have to do. My number one feature request would be to have a simple way from the Launchbox UI to modify the rom-path for each platform. This shouldnt be difficult to implement into Launchbox I would suspect ( just a search and replace algorythm for the XML path?) Thanks for solving this ! Mazjohn (aka Mr. Arcade)

Asking for some help from the community on this one: I cant seem to successfully edit my rom paths in the Launchbox XML file for the life of me. I wish this had a video tutorial but couldn't find one on how to do this. I'm using notepad ++ , and I am substituting all paths beginning with the phrase "E:/launchbox" and using the "change to" command to rename to "/games" my goal is to put all the rom folder paths back into the default launch-box folder location (whereas my rom paths are currently located on a separate E drive for the majority of my platforms}. So all references to the E drive path inside the Launchbox.XML file have been replaced as stated above (had found like 5,700 references to re-name) I confirmed this by checking the XML again afterwards to make sure the new paths did actually save. Then I re-launch launch-box, and all the previously discovered games are still pointing to the "E:/launchbox/" path... so this is not working at all. Does Jason or the launchbox team have any plans to add a simple way to easily change existing Rom paths of an existing installation as of yet? I have a very large library so I need to find the easiest way to do this without losing all of my metadata... this is a sorely needed feature Appreciate some advice guys.... thanks in advance for any help. Mazjohn (aka Mr. Arcade)

EDIT: I initially had a corrupt NVIDIA driver install that was causing problems but it wound up having nothing to do with Launch-box or Windows 10 Creators build. re-installing the NVIDIA driver again seems to have resolved the issue. I stand by my below comment, Will update this post if anything changes. Seems like the creators build 1703 works just fine with Launch-box. The framerates actually seems better with this new build _________ Original comment; Im running Launchbox with the final windows 10 creators build 1703. I have not experienced any issues at all running a heavily populated Launchbox. Xbox 1 controllers seem to be working fine so far as well. Windows does prompt that it is adding back Xbox and other input device driver support after updating. Thankfully, all seems to be running well. The system seems a little faster and frame rates are the same if not better in most cases here. I'm running Launchbox on the latest beta which at the time of this writing is v7.9b7. Regards, Mazjohn- aka "Mr . Arcade"

Interesting... In my case it prompts me every time a game is launched to enter date & Time, not just the first time it is run,,, I am using the latest Mednafen core in retroarch 1.41 and also tried the newer retroarch 1.5

Not sure how to advise. I've had a similar problem with MameUI32/64 on and off for the past year where Mame keeps losing the Xbox controller settings intermittently when restarting. I've tried changing write settings in the INI file and even making the files read only but it still randomly loses the controller configurations ....

Does anyone know if there is a fix yet for the Retroarch Mednafen core? It still keeps asking to set date & time everytime a game is launched.

Does the retro-arch Saturn core only support US bios? maybe that's why the Jap games wont launch with Retroarch and Launchbox? There are only 2 bios files used by the mednafen Saturn core... Did anyone here successfully boot a Jap Saturn game with Retro-arch and Launch-box?

kev25b said It breaks ds4windows and xbone controllers. If you don't use them controllers it's ok lol. Thanks for the feedback... I went ahead and updated. after the update, a few things occurred as follows if anyone else is interested: 1- After the update and reboot, I needed to unplug my Xbone wireless adapter and plug it back in to get windows 10 to see the controllers again. I also needed to re-sync both xbone wireless controllers again. 2- Retroarch had to be re-configured from scratch... not sure what changed and caused this but until i reconfigured and set the controllers again nothing would work. 3-MameUI lost its xbone configuration... had to go back in and re-configure. Launchbox would not launch (requires elevation issue)... I think its just a windows permission issue.... need to figure it out 4- emulators outside retroarch seem to work fine. (with the exception of elevation issue) 5- controller automation inside big box mode seems to not work since with many systems to exit games. not sure if its coincidental or not on my part.. (escape key on keyboard still seems to work to exit using scripts at least) Overall a little work but seems ok... I have contemplated the idea of removing this PC from the network moving forward since this is mostly launchbox.... however its probably not practical i do realize. *Edit... elevation required issue resolved by running Launchbox as an admin... the issue only occurred with MameUI. Not sure why. Also now that I am running Launchbox as an admin, I can no longer get Launchbox to launch with windows by using a shortcut inside the startup folder (windows 10 startup folder does not work when a shortcut to an application has admin rights) Launchbox is great, its windows that is a wild west folks... lol

Before updating, I'm Curious if Anyone running Launchbox has installed Microsoft's latest "windows update" for windows 10. Microsoft has just begun Pushing this new build update gradually to Windows 10 users. For those who have updated, curious to know if there were any issues for you after the update with using Launch-box... as you can probably tell, I'm always paranoid with these big OS changes... fearing permissions issues or Xbox controller changes made at the OS level that can cause headaches.... Safe to update? Thanks....

I tried WMP... no difference here ( same audio issue as with VLC)

Jason Carr said Thanks guys, was the audio crackling new for 6.4-beta-3? That's really strange because we've done nothing to change anything related to sound in Big Box for a long time. What video playback engine are you guys using? VLC or Windows Media Player? For me, the issue began after upgrading to 6.4 beta 3 ..seems to have something to do with the game movies playback specifically when inside bigbox mode. When you have a rom selected then switch to another rom, you randomly hear pops, clicks and short 1 second bursts of audio clips from previously watched videos from other games. You also continue to hear the audio glitches while playing games. To test this, I first re-installed 6.4 beta 3 on top of itself... result was the same issue. Then, I proceed to install and revert back to beta 2- ...and the issue was gone. By the way, I am using the VLC engine for playback

With version 6.4 beta 3, in bigbox mode audio is crackling and seems to get stuck in loops and random glitching sounds when switching between videos and game titles within the menus. continues throughout gameplay sessions until bigbox is shutdown. Anyone else experiencing this with this new beta or have any thoughts? Is there a link where I can download the current or previous beta and downgrade the version without loosing my settings and platforms? Issue only began after updating from previous beta 2. Launch box has been amazing. I'm sure I will be able to get this sorted out otherwise. Thanks!

rmilyard said How you get 3DO: Retroarch 4do working? When I run it I just get the CD Screen after system starts up. With retroarch, when adding titles, you need to point to the "ISO" files and not the cue files... If you were using the standalone 4do emulator, it was the opposite (with the standalone emulator, you point it to the cue files)

I just updated to the latest beta, and it seems launchBox now allows you to create your own platform successfully and then assign a scraper type. Worked beautifully! I now have easily separated mame from FBA into 2 separate platforms, while at the same time scraping against "arcade".... Great development work here to say the least!

Getting retroarch and the dolphin bar to co-exist drove me nuts for the longest time... I've been manually switching from mode 4 to mode 1 until now for a lack of a better solution. What is weird in my case, is that retroarch 1.34 seems to properly prioritize my wireless Xbox one controllers better now than previous version. In older versions of retroarch I couldn't get the dolphin bar to use the same priority.. Every time I rebooted, it would assign the wireless controllers to different ports (breaking the emulators) ... 1.34 is the first version of retroarch that I seem to be able to use with the dolphin bar... Of course I still need to change the modes, but at least the priority issue has gotten better. What I am wondering, is if something has changed with the way Launchbox handles microsoft x-input control that has helped? I just may try playing around with the above suggestion in using mode 3... This thread has been the most useful thread I have seen for dealing with retroarch and the dolphinbar. I hope someone from the retroarch forums takes notice. ... I desperately hope to see this situation improve.

Thanks Jason, Brad and all for feedback. This is great info.

This is the exact issue I am looking to find the best solution for. In my case, I installed the FBA core in retroarch and added to the arcade platform.... Problem is that now I want to add mame. Seems I must add them to the same arcade platform?? If I understand, can I use multiple emulators per platform?? What is the best way to have mame and FBA co-exist? I seem to be concerned that it would be tedious to merge them both into a single platform... Maybe there will be a way to separate these platforms in the future? Or is there a way to do this now? Appreciate feedback... A tutorial on how to setup multiple systems on a single platform might be helpful for the challenged! (Me) lol....

After spending countless weeks and months getting all my Launchbox systems working perfectly with all metadata and images included, I wanted to ask an important question here that I haven't seen discussed much. I am wondering what is the best way to preserve all of my work.. What is the best method to use to do a compete backup of my launchbox imstallation in order to restore to current state in the event of dreaded hard drive failure? The games and ROMs can always be copied back, so primarily I am mainly concerned on how to preserve all of the configuration settings for easy restore.... Is there a global way to accomplish? What method do you guys reccomend works best? Thanks,

Changing from 0 to 1 unfortunately did not help for me, but thanks for the tip. Seems windows 10 behavior again creating headaches with Xbox wireless controllers. The port assignments keep changing on my wireless gamepads each time windows starts. In addition, Ever time I restart my PC, mameui64 continues to loose all saved gamepad settings. Unfortunate that I can't seem to get an all in 1 solution working for all platforms in a windows environment. Not a launch box issue at all.... Its just a windows thing I guess. We are able to get sooo close to an all in 1 solution with launchbox, but windows keeps making this a challenge. If I switched to wired controllers, it might work better but its not an option since I am trying to use this in a living room like a console and 14 feet away from the screen.