Bedwyr

What changes would I need to make to adapt this script for GoG and the Epic Game Store?

Coming back to this admittedly late. I don't have any Epic games, but I could see that changing if current events are any indication (it'll depend on the ratios of full exclusives vs. timed exclusives vs. the rate of improvement of Epic's services as I'm a pretty dedicated Steam Big Picture services). There's usually a way to run Steam games with Steam offline as well as independently if it doesn't use Steamworks. Is that something that Epic has done/is doing/will do? It seems kind of important for those interested in offline gameplay.

Test2 works like a charm. Very nice to have that functionality back. I've been using Advanced Emulator Launcher and it works, but it's better to shut Kodi down while running another frontend.

I'll see if I can get to it tomorrow. Thanks very much for doing this. Out of curiosity, what was the primary change? I asked about the Steam launcher which I know this cribs from, but didn't go as far as a line-by-line Kdiff in notepad++. (I do a little bit of XML and only enough Python to load libraries; everything else is C/C++/Matlab scientific computing, so I'm not up on the intricacies of how Kodi does things.)

Oh ok. Yeah, that fixed it.

So, umm, I kind of need more time. I'll try to use a stopwatch next time, but it's taking upwards of 8-10 seconds to load Retroarch. I've got the slider pegged to 5 seconds, but it's still not long enough off a fresh reboot. So, feature request? <prettypleasewithacherryontop?>

Hi all. I've dropped out of the beta group for a bit (I'm starting to use LB simply as a daily game driver and didn't want as many interruptions). Given that, I'd like to make a small request. If I missed any changes, apologies. The loading and closing screens are a great feature. However, I've noticed that sometimes, especially when the system has just freshly booted, Retroarch will take longer to load and the loading screen will return the player momentarily to the game selection menu before going finally to Retroarch. Could the loading screen last a teensy bit longer, like 0.5 to 1 seconds? It's a small thing, but it does detract from a very nice feature.

Hi all. I've got issues making the BB script run within a new install of Kodi 18. The dialogue for changing the Launchbox directory does *not* show any files, including exe. So my installation: "d:\games\emulators\LaunchBox\" I can navigate to, but I cannot select BigBox.exe. In fact I cannot see *any* files from folder selection. This is odd because the Steam Launcher script can see files just fine. Perhaps something has changed between Kodi 17.6 and 18 that broke the launcher? Where in the script is the install folder saved? I'd like to see if I can manually edit it.

I replicated the behavior before updating to the new beta. Installed the beta and it went away. That's about as locked down and reliable a behavior as I can think of.

<whispering> (until I found his channel, I thought ETA Prime was you.)

Probably going both ways. I recall seeing the whole no-intro set before Jason started the database. Either way, I'm chit-chatting OT. Back to patch talk.

I think the slanty ones are Hyperspin in origin. I have subs to both.

BTW, what image source are you guys using for 3D boxes? Mine are much more angled; this might be a decent in-between appearance.

Thanks!

The upscaling is very nice on this libretro core. How do I reduce or minimize the polygon jitter though? It's far more noticeable when rendering at 8x than 1x native.

Ok, under 8.9 the behavior did not repeat. I could probably confirm that by running the tests once more with an update pending.

Thx.

Jason: continuing the testing plan from the 8.8 thread. I am now on 8.9 full release. This is the latest from you, correct?

There's the oddball remote possibility that if I did that and the issue is more embedded in the update process itself, you'd get a false positive from me. But yeah, while not universe-heat-death impossible, highly unlikely. Ok. I'll try to get everything updated and try again tonight, both controllers, 15 minutes each.

I could coordinate with you so that I do tests with a fully updated copy (like hold off on a beta for a single evening to see if it replicates or not). I could, for example, spare 15 minutes later tonight if you're going to launch a full release before that (I'm CDT).

Well that works ok once. I've had this behavior through multiple beta and release versions. Anyhow, I replicated the same behavior with the XB1 controller under the same conditions as the SN30 controller. To be crystal clear about how the system responds, I can do three things: navigate with D-pad, press the exit button and get the exit sound effect (but not actually exit the game's page), and on the top button maximize the 2D box art which looks like this (I normally use 3D box art btw):

I'm 99% sure it is the prompt for the beta just after your emergency release. No plugins, just regular setup and media.

Correct, only the SN30 modkit (SNES Bluetooth PCB). I could try and replicate using the XB1 controller. Possibly the N30 one as I recall FFII used only one or two of the four face buttons. Another random thought is that it's still because of the popup, but the popup doesn't display at all. Like not even the yes/no. Somehow I still clear the query condition but BB stops responding correctly after I do. Also, FWIW, I'm running a GTX 1060 on 411.70. The CPU is a new Core i7 8700K. Windows 10's status is just before the October update (which MS pulled I hear). I can't really think of disabling anything else except for core system functions like Bluetooth or Windows Defender (not even gonna think about that one).

So this happened on my first test on exiting. To be clear I stopped these and then rebooted: Kodi, Java, Logitech updater, OneDrive, Dropbox, Controller Companion, AnyDVD, and OneNote. Basically anything I could think of that might cause an untoward effect. After I selected "no" the error happened again. I wonder if the popup dialogue is not displaying correctly and interrupting or screwing up the interface somehow. Like maybe it actually is a focus problem and focus isn't being properly returned from the (invisible???) prompt dialogue. Today's log attached, just in case. Debug 2018-10-08 10-25-37 PM.log