LaunchBox 13.17 - Beta Thread

[The Papaw]

I can't seem to get a manual scan to work on the PS Vita platform (I have disabled the autoscan for it), I get to this screen and then just hangs. I let it go for over an hour and 1/2 thinking it was going to add more than just the eboot.bin files, but I finally just canceled it. Made 2 attempts with same results

I then tried Atari 7800 just to see what it would do, no new roms, and it took forever to scan and report back there was nothing new. Just reporting

[faeran]

28 minutes ago, The Papaw said:

I can't seem to get a manual scan to work on the PS Vita platform (I have disabled the autoscan for it), I get to this screen and then just hangs. I let it go for over an hour and 1/2 thinking it was going to add more than just the eboot.bin files, but I finally just canceled it. Made 2 attempts with same results

I then tried Atari 7800 just to see what it would do, no new roms, and it took forever to scan and report back there was nothing new. Just reporting

The manual scan does not work with PS Vita, at least not well. The only current method of importing your PS Vita games is through the auto scan option, which does work well.

I just ran a test on Atari 7800, and that seemed fine. If your still running your ROMs across a network, I'm guessing that might be the cause of what you are seeing.

[The Papaw]

1 minute ago, faeran said:

The manual scan does not work with PS Vita, at least not well. The only current method of importing your PS Vita games is through the auto scan option, which does work well.

I just ran a test on Atari 7800, and that seemed fine. If your still running your ROMs across a network, I'm guessing that might be the cause of what you are seeing.

Thx Brian, will give the auto a try

[The Papaw]

14 minutes ago, faeran said:

The manual scan does not work with PS Vita, at least not well. The only current method of importing your PS Vita games is through the auto scan option, which does work well.

I just ran a test on Atari 7800, and that seemed fine. If your still running your ROMs across a network, I'm guessing that might be the cause of what you are seeing.

Is the scan for removed roms working?

[The Papaw]

21 minutes ago, faeran said:

The manual scan does not work with PS Vita, at least not well. The only current method of importing your PS Vita games is through the auto scan option, which does work well.

I just ran a test on Atari 7800, and that seemed fine. If your still running your ROMs across a network, I'm guessing that might be the cause of what you are seeing.

Ok, here is what I have going on. I have 2 PC's still running LB v13.16 and one PC running the current beta. The 2 running v13.16 are finding 971 games. The one running the current beta is only finding 965 games. All 3 PC's are scanning the same folder. Any thoughts why?

[faeran]

1 minute ago, The Papaw said:

Ok, here is what I have going on. I have 2 PC's still running LB v13.16 and one PC running the current beta. The 2 running v13.16 are finding 971 games. The one running the current beta is only finding 965 games. All 3 PC's are scanning the same folder. Any thoughts why?

If you would like to go through some configuration discussion send me a PM and I'll see what I can do for you.

[stensgaard]

if anyone have 5 min could you PLEASE try this using the latest beta:

set theme to "Default"
set game view to "Text List with Details"
turn OFF "show loading game.." Message
 

then try and start a game from a playlist, play for 10 seconds, and close it again!
now does your menus update work when switching between games?

mine stops updating, until I go all the way back out of the playlist and re-enter it again!

the if I enable the "show loading game message" again it starts updating again .. (tried this on 4 different machines so far all with the same result)

[dbalcar]

Getting this error when just click on different games.  Every game I click on pops this error.

Object reference not set to an instance of an object.

App:     LaunchBox
Version: 13.17-beta-5
Theme:   Default
Type:    System.NullReferenceException
Site:    Unbroken.LaunchBox.Search.LocalDbSearchResultGame GetGameById(Int32)
Source:  Unbroken.LaunchBox

   at Unbroken.LaunchBox.Search.LocalDb.GetGameById(Int32 id)
   at Unbroken.LaunchBox.Windows.Data.Game.DestroyNotificationStub(Int32 )
   at Unbroken.LaunchBox.Windows.Data.Game.CanScrapeSteam(String& steamAppId)
   at Unbroken.LaunchBox.Windows.Desktop.Controls.SteamStoreLink.CheckStatelessWriter(Object spec, DependencyPropertyChangedEventArgs counter)
   at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
   at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
   at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
   at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
   at System.Windows.DependencyObject.InvalidateProperty(DependencyProperty dp, Boolean preserveCurrentValue)
   at System.Windows.Data.BindingExpression.TransferValue(Object newValue, Boolean isASubPropertyChange)
   at System.Windows.Data.BindingExpression.Activate(Object item)
   at System.Windows.Data.BindingExpression.AttachToContext(AttachAttempt attempt)
   at System.Windows.Data.BindingExpression.MS.Internal.Data.IDataBindEngineClient.AttachToContext(Boolean lastChance)
   at MS.Internal.Data.DataBindEngine.Task.Run(Boolean lastChance)
   at MS.Internal.Data.DataBindEngine.Run(Object arg)
   at MS.Internal.Data.DataBindEngine.OnLayoutUpdated(Object sender, EventArgs e)
   at System.Windows.ContextLayoutManager.fireLayoutUpdateEvent()
   at System.Windows.ContextLayoutManager.UpdateLayout()
   at System.Windows.ContextLayoutManager.UpdateLayoutCallback(Object arg)
   at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
   at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
   at System.Windows.Media.MediaContext.AnimatedRenderMessageHandler(Object resizedCompositionTarget)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Recent Log:

   4:14:03 PM Exception

[JoeViking245]

1 hour ago, dbalcar said:

Getting this error when just click on different games.  Every game I click on pops this error.

Object reference not set to an instance of an object.

App:     LaunchBox
Version: 13.17-beta-5
Theme:   Default
Type:    System.NullReferenceException
Site:    Unbroken.LaunchBox.Search.LocalDbSearchResultGame GetGameById(Int32)
Source:  Unbroken.LaunchBox

Try Tools < Download < Force Update Games Database Metadata and see if doing that clears things up.

[dbalcar]

1 hour ago, JoeViking245 said:

Try Tools < Download < Force Update Games Database Metadata and see if doing that clears things up.

Thanks @JoeViking245 That fixed it.  no errors now.  I tested across like 10 systems and multiple games in each.  Thanks again for the help.

[The Papaw]

Steam videos aren't downloading for me for installed games (not installed by Steam), it just hangs. Anyone else?

[faeran]

21 minutes ago, The Papaw said:

Steam videos aren't downloading for me for installed games (not installed by Steam), it just hangs. Anyone else?

I just tried both a bulk metadata and media wizard download and a per-game download of Steam videos, but they both worked just fine.

[The Papaw]

11 hours ago, faeran said:

I just tried both a bulk metadata and media wizard download and a per-game download of Steam videos, but they both worked just fine.

Do you think it might be related to me using a non default location for my media? (not using ..\Launchbox\Videos\*)

Edited October 22 by The Papaw

[Sbaby]

On 10/9/2024 at 11:15 PM, Sbaby said:

Thank you very much for sharing your experience. The same thing happens to me regardless of whether I click on other programs or not. I am attaching a video where you can see that on the first launch, Launchbox remains stuck for a long time. After 50 seconds, I decided to terminate the process via the Windows Task Manager. As you can see, I then relaunched Launchbox, and this time it started correctly in about 10 seconds, with an additional 5 seconds to finish loading the game data.

 

 

I have identified the reason why LaunchBox does not start properly in the latest beta versions. The problem seems to stem from the loading of startup applications: if I manually start the same applications or use an AutoHotkey script before launching LaunchBox, everything works smoothly, and LaunchBox opens instantly.

I haven't made any changes to the applications I've been using for months, and with the older versions of LaunchBox, everything was functioning correctly. However, with the new beta versions, crashes occur about 4 times out of 5. In my opinion, this is a bug related to the timing between the loading of startup applications and the launch of the frontend.

I suggest considering a modification that allows custom startup applications to be fully loaded before LaunchBox starts.

Thank you for your attention and support.

[Sbaby]

and then :

 

now I get a never-before-seen warning that I am using too much memory and that LaunchBox cannot continue. I just restarted my computer and played Zelda for half an hour, upon exiting the game so I find it really absurd that this problem is occurring. I have been playing without any problems for a month and had never had any such warning.

Also, I noticed that the memory alert message seems to be fake see here the screenshot made with alt-tab

The latest betas are a disaster and I really don't know how to continue, and don't tell me I have to buy 256 gb of ram to get these things going because I've been using them forever 

 

 

[Wally]

The Launchbox team is great. They urge to satisfy the community adding tons of stuff.

BUT as a result, Launchbox has become a hog. 

It is SLOW. I have revisited version 7 and back and things were so snappy back then!

In my case, I have errors in my Log (I am expecting an aswer sometime soon) and at least since version 17, Launchox is taking 2 minutes to boot completely. BTW I do not mind the 2.5GB RAM. I guess storing things in RAM makes things quicker...

Launchox boots up and in the background launchbox.exe is taking something like 40% of the CPU for no obvious reasons for around 2 minutes until is settling to idle percentages.

Please make Launchbox, snappy again and thanx for all your hard work.

[zugswang]

49 minutes ago, Wally said:

The Launchbox team is great. They urge to satisfy the community adding tons of stuff.

BUT as a result, Launchbox has become a hog. 

It is SLOW. I have revisited version 7 and back and things were so snappy back then!

In my case, I have errors in my Log (I am expecting an aswer sometime soon) and at least since version 17, Launchox is taking 2 minutes to boot completely. BTW I do not mind the 2.5GB RAM. I guess storing things in RAM makes things quicker...

Launchox boots up and in the background launchbox.exe is taking something like 40% of the CPU for no obvious reasons for around 2 minutes until is settling to idle percentages.

Please make Launchbox, snappy again and thanx for all your hard work.

Agree.

It tries to do too many things and as a result is is so laggy it borders on being unusable.

In comparison Hyperspin + RocketLauncher is lightning fast no matter how much you shove onto it (I have 650+ systems and 250,000+ games) and all still working as good as ever.

Seeing as both haven't been updated in years, it's unbelievable that Launchbox team do not focus more on speeding it all up,  rather than continuing to add more and more stuff that makes it even slower (if that's possible)

[eonder87]

On 10/23/2024 at 11:58 AM, zugswang said:

Agree.

It tries to do too many things and as a result is is so laggy it borders on being unusable.

In comparison Hyperspin + RocketLauncher is lightning fast no matter how much you shove onto it (I have 650+ systems and 250,000+ games) and all still working as good as ever.

Seeing as both haven't been updated in years, it's unbelievable that Launchbox team do not focus more on speeding it all up,  rather than continuing to add more and more stuff that makes it even slower (if that's possible)

I'm tested 12.12 version of launchbox and 13.17 version.
Both Empty and new install only boot time. Nothing added. 

13,17 18 second
12.12 3 second

[faeran]

Locking this thread, as this specific release is out of beta and responses have been getting further off-topic to the testing of beta features and those talking points don't deserve to be lost in an outdated beta thread.

In saying that, there are a few things I'll mention here. For things like user issues (like Sbaby), that might deserve a dedicated thread.

For others with general performance type of comments. Thanks for those, although in order for them to actually be constructive, we'll need a lot more specifics.

What we are going to try and do is create a thread dedicated to collecting specific performance related issues that a user may have. That thread will try and list out specifics to what users may be experiencing, then will categorize them into a few categories. Some might just boil down to education (like why boot times differ between versions), while others could be categorized into internal factors (things we can actually solve) vs. external factors (things the user can solve themselves... ie. a third party plugin causing slowdowns or crashes). If all goes well, we can work together to identify root issues and provide solutions, whether it be changes to the client itself or changes to a user's configuration.

Look out for that, however, do know that there's only a couple of us on here, and we are splitting out time amongst many projects, so we thank you for your patience.