The Papaw Posted October 2, 2019 Posted October 2, 2019 I am running LB 10.5 with beta updates turn on, I get nothing about any betas to download. Also, has anyone gotten ds4windows to work with PS4 controller yet???
Jason Carr Posted October 2, 2019 Author Posted October 2, 2019 On 10/2/2019 at 1:25 AM, Wanderer189 said: I am running LB 10.5 with beta updates turn on, I get nothing about any betas to download. Also, has anyone gotten ds4windows to work with PS4 controller yet??? Expand DS4Windows is working well, yes. There aren't currently any betas out. The 10.5 release is the latest release.
dov_EL Posted October 2, 2019 Posted October 2, 2019 (edited) On 10/1/2019 at 6:27 PM, Retro808 said: Not quite sure what you mean. Expand In 10.5 same problem @Jason Carr Edited October 2, 2019 by dov_EL
dov_EL Posted October 2, 2019 Posted October 2, 2019 The volume of retroarch in game, is not the volume of Windows, so it is useless to waste time. I see no other solution and return to the old volume model only in bigbox, or you can try this https://www.nirsoft.net/utils/nircmd.html @Jason Carr
The Papaw Posted October 2, 2019 Posted October 2, 2019 On 10/2/2019 at 4:49 AM, Jason Carr said: DS4Windows is working well, yes. There aren't currently any betas out. The 10.5 release is the latest release. Expand @Jason Carr: I know you are being swamped with the controller issues, can you tell me what version of ds4w you are testing with?
Retro808 Posted October 2, 2019 Posted October 2, 2019 On 10/2/2019 at 6:01 AM, dov_EL said: In 10.5 same problem @Jason Carr Expand I dont believe there was a fix in 10.5 beta 2 for the Retroarch issue. The fix was for a Win7 Xinput concern. On 10/1/2019 at 10:37 PM, Jason Carr said: So it's been a pretty crazy past couple of days. I just put out 10.5-beta-2, which appears to fix an issue where controllers weren't working for Windows 7 users, because Windows 7 apparently does not support XInput 1.4 at all. So I'm now reverting to XInput 1.3 in that case. Any testing you all can do with 10.5-beta-2 would be appreciated. Expand
dragon57 Posted October 2, 2019 Posted October 2, 2019 Anyone have any idea why my default images aren't showing correctly? I just noticed this issue, so not sure when it started happening. The images with the yellow squares around them should show the default 3D box like the image with the pointer.
Chris Kant Posted October 2, 2019 Posted October 2, 2019 On 10/1/2019 at 10:37 PM, Jason Carr said: So it's been a pretty crazy past couple of days. I just put out 10.5-beta-2, which appears to fix an issue where controllers weren't working for Windows 7 users, because Windows 7 apparently does not support XInput 1.4 at all. So I'm now reverting to XInput 1.3 in that case. Any testing you all can do with 10.5-beta-2 would be appreciated. Expand not even realised anything between 10.1 to 10.4
Retro808 Posted October 2, 2019 Posted October 2, 2019 On 10/2/2019 at 11:26 AM, dragon57 said: Anyone have any idea why my default images aren't showing correctly? I just noticed this issue, so not sure when it started happening. The images with the yellow squares around them should show the default 3D box like the image with the pointer. Expand Refreshing the image cache for those games did not help? Just tested on a couple platforms as I have not really added default images and everything worked fine.
dragon57 Posted October 2, 2019 Posted October 2, 2019 On 10/2/2019 at 12:06 PM, Retro808 said: Refreshing the image cache for those games did not help? Just tested on a couple platforms as I have not really added default images and everything worked fine. Expand Nope, I tried refreshing the image cache, existing LB, then nuking the entire cache directory so it would be rebuilt. I have discovered it isn't just my Vectrex platform that shows the issue. A few others do too. I have checked the settings under Tools/Manage Platforms, and all the default images are identified and set correctly. I'm stumped.
Mr. RetroLust Posted October 2, 2019 Posted October 2, 2019 On 10/2/2019 at 1:21 PM, dragon57 said: Nope, I tried refreshing the image cache, existing LB, then nuking the entire cache directory so it would be rebuilt. I have discovered it isn't just my Vectrex platform that shows the issue. A few others do too. I have checked the settings under Tools/Manage Platforms, and all the default images are identified and set correctly. I'm stumped. Expand Could it be an image priority setting? Perhaps youve set box front as an option under priorities for 3d box.
dragon57 Posted October 2, 2019 Posted October 2, 2019 On 10/2/2019 at 1:54 PM, Mr. RetroLust said: Could it be an image priority setting? Perhaps youve set box front as an option under priorities for 3d box. Expand Well, I seem to have found a work-around. For the platforms that show the wrong images, if I uncheck every option for Box Front, or Box 3D, etc., then tell LB to refresh all images, my defaults show up correctly. I can then go back and re-check all the multiple image types under options that I had before and the correct images continue to show, even after another refresh all. Very strange.
Stovies Posted October 2, 2019 Posted October 2, 2019 I'm using a wired xbox controller in Windows 10 and I have switched off the controller game bar setting linked to the central silver button on the controller (to avoid conflicts). I was hoping to bind it to the pause screen. But it doesn't appear to be recognised by Launchbox or BigBox. Any thoughts on how to fix this would be appreciated.
The Papaw Posted October 2, 2019 Posted October 2, 2019 (edited) This controller thing has been a nightmare for many of us, but I know especially for Jason and any one working on it. I have tried to get a genuine PS4 controller to work for 2 days now using DS4W. I can't get LB or BB to recognize it period!!! I was originally running DS4W v1.4.94 (only version I can get the gyro would work in cemu and RPCS3, every time I tried to update it, I couldn't get the gyro to work). Things I have tried: Trying different version of DS4W from v1.4.52 all the way up to v1.5.8 deleting the InputBindings.xml in the LB data folder deleting and reinstalling the 360ce drivers Set up a blank copy of LB 10.1 I have a generic wireless chinese 360 controller with its own dongle, it works, I have a couple barely working official 360 controllers using the MS dongle, they work. I am about to give up on the PS4 controller. I had just ordered 4 Switch Pro controllers to try and replace everything I am using so they would have the gyro using BetterJoyForCemu...I am scared, scared, scared. Did I say I was scared? Of course every controller I have works as expected everywhere except in LB or BB....they work in the emulators, RA, everything. Did I mentioned I was scared? And added to that, I can take the exact same PS4 controller, pair it to my shield, run moonlight (course it uses it own controller stuff), it runs BB fines, now check this out, I take the same PS4 controller and pair it back to my PC, run DS4W v1.4.94, take my shield REMOTE or shield controller, navigate to moonlight, launch it, start BB (I have a shortcut to BB in moonlight) and as soon as I do, the PS4 controller PAIRED to the PC, will run BB, emulators, even the GYRO in Cemu works like I was playing on the PC. Of course it has the moonlight lag and all.... The Switch Pro controllers are suppose to be here tomorrow, maybe they will be okay, right guys???? Did I tell you I was scared?????? hahaha Edited October 2, 2019 by Wanderer189
mcfilmmakers Posted October 2, 2019 Posted October 2, 2019 Why are we discussing Launchbox 10.5 in a thread specifically meant for 10.2? Can we please start a new thread so the discussions are easier to find? Thank you!
neil9000 Posted October 2, 2019 Posted October 2, 2019 On 10/2/2019 at 11:54 PM, mcfilmmakers said: Why are we discussing Launchbox 10.5 in a thread specifically meant for 10.2? Can we please start a new thread so the discussions are easier to find? Thank you! Expand Because these versions followed very quickly and were put out to address issues people were having in this thread. 10.5 contains fixes for the exact things mentioned in here so is very relevant to the discussion.
mcfilmmakers Posted October 3, 2019 Posted October 3, 2019 On 10/2/2019 at 11:57 PM, neil9000 said: Because these versions followed very quickly and were put out to address issues people were having in this thread. 10.5 contains fixes for the exact things mentioned in here so is very relevant to the discussion. Expand But it’s not the same version regardless. When I’m looking for discussions about 10.5, the last place I would look is here.
neil9000 Posted October 3, 2019 Posted October 3, 2019 On 10/3/2019 at 12:04 AM, mcfilmmakers said: But it’s not the same version regardless. When I’m looking for discussions about 10.5, the last place I would look is here. Expand We don't have testing threads for official releases as they have supposedly been tested by that point, hence the release. Clearly though it seems a lot of people who download the betas dont actually test them, as some issues got through that were not reported in the beta phase, so tacking it onto the most recent beta thread is probably the best place for it.
mcfilmmakers Posted October 3, 2019 Posted October 3, 2019 On 10/3/2019 at 12:10 AM, neil9000 said: We don't have testing threads for official releases as they have supposedly been tested by that point, hence the release. Clearly though it seems a lot of people who download the betas dont actually test them, as some issues got through that were not reported in the beta phase, so tacking it onto the most recent beta thread is probably the best place for it. Expand Then we agree. It is illogical to keep posting in a thread about 10.2 when we are now three versions beyond that.
Retro808 Posted October 3, 2019 Posted October 3, 2019 Yeah, its really not that important. I think we should get back to discussing beta testing like the thread is supposed to be about. 1
Recommended Posts