13.19 update is broken

[xokia]

13.19 hosed my setup. Don't know why its putting the word file in the path.

Also would be nice if we had an option to roll back instead of having to ask for a old release. Can I get 13.18 please?

 

The specified path is invalid. : '\\HOME-SERVER\pool5\games\LaunchBox\file:\Z:\Arcade\SNK Neo Geo Pocket Color\roms'.

App:     LaunchBox
Version: 13.19
Theme:   Default
Type:    System.IO.IOException
Site:    WIN32_FILE_ATTRIBUTE_DATA GetAttributeData(System.String, Boolean)
Source:  System.Private.CoreLib

   at System.IO.FileSystem.GetAttributeData(String fullPath, Boolean returnErrorOnNotFound)
   at System.IO.File.GetAttributes(String path)
   at Unbroken.LaunchBox.Windows.Desktop.ViewModels.RomImportLocationParseViewModel.<>c__DisplayClass10_0.CompareAutowireTag(Object)
   at Unbroken.LaunchBox.Windows.Desktop.ViewModels.RomImportLocationParseViewModel.<>c__DisplayClass10_0.AssetReadableConnection()
   at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.CancelPrincipalIdentifier(Object)
   at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.CalcInvalidPage()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

Recent Log:

   8:18:25 PM Exception

Edited March 2 by xokia

[xokia]

I can confirm this is an issue with 13.19 luckily I still had the 13.18 laying on my server. Re-installed and all works again

Edited March 2 by xokia

[AstroBob]

Hi there,

Thanks for the report here. Right off the bat, that file path definitely seems a bit off. Can you confirm.

- Go to Tools > Manage > Platforms, and then into your Neo Geo Pocket Color platform.

- Under the Folders tab, what is the path listed there for Game

Can you also take a single pocket color game and edit it's metadata, go to Launching and then provide an example of what the ROM File path looks like?

Finally, can you confirm:

- Does this error occur for other platforms, or just Neo Geo Pocket Color
- Can you confirm where these affected games are stored? It looks like it's some sort of network or external drive.

Please let us know and we'll try to get you sorted

[xokia]

On 2/12/2025 at 12:38 AM, AstroBob said:

Hi there,

Thanks for the report here. Right off the bat, that file path definitely seems a bit off. Can you confirm.

- Go to Tools > Manage > Platforms, and then into your Neo Geo Pocket Color platform.

- Under the Folders tab, what is the path listed there for Game

Can you also take a single pocket color game and edit it's metadata, go to Launching and then provide an example of what the ROM File path looks like?

Finally, can you confirm:

- Does this error occur for other platforms, or just Neo Geo Pocket Color
- Can you confirm where these affected games are stored? It looks like it's some sort of network or external drive.

Please let us know and we'll try to get you sorted

I already switched back to 13.18. This happens when I try to add roms. I have a mapped drive called games. Z drive.

When I choose the importer is starts off in \\Home-server\balh\.blah instead of Z:\  even when I installed in Z:\ Then when I browse to Z:\path_to_roms it will insert the file path it has along with file:\ in the name prepended to the actual path

Edited March 2 by xokia

[faeran]

26 minutes ago, xokia said:

I already switched back to 3.18. This happens when I try to add roms. I have a mapped drive called games. Z drive.

When I choose the importer is starts off in \\Home-server\balh\.blah instead of Z:\  even when I installed in Z:\ Then when I browse to Z:\path_to_roms it will insert the file path it has along with file:\ in the name prepended to the actual path

A very specific scenario that we are unable to reproduce on our end. Every attempt at importing either a UNC or mapped network drive is successful.

If you can zip up your Data folder and send it to me in a PM that may help track down what's going on in your build.

[xokia]

Sure I can upgrade again later this afternoon.

[xokia]

Just sent you both working 13.18 and broken 13.19 so you can diff

Only thing I can think of that was done different is 13.18 install file is sitting on  the network drive 13.19 install file is sitting on the local drive.

Both were pointed to the Launchbox directory on the network drive to install into.

Edited March 2 by xokia

[xokia]

Doing all that switching and rolling back now broke my MAME set importation. Hoping this can be resolved.

 

Object reference not set to an instance of an object.

App:     LaunchBox
Version: 13.18
Theme:   Default
Type:    System.NullReferenceException
Site:    Void PrintInvalidIterator()
Source:  LaunchBox

   at Unbroken.LaunchBox.Windows.Desktop.ViewModels.MameFullSetWizardRomLocationViewModel.PrintInvalidIterator()
   at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.ChangeAwareVisitor(Object )
   at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.PopSessionProcessor()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

Recent Log:

   8:23:08 PM Exception

[C-Beats]

Try going to Tools > Download > Force Update Games Database (last option) and letting that run before doing any importing or scraping

[xokia]

10 hours ago, C-Beats said:

Try going to Tools > Download > Force Update Games Database (last option) and letting that run before doing any importing or scraping

Tried that did not fix anything

 

Edited February 14 by xokia

[xokia]

upgrading to 13.19 fix the MAME set importer but import Rom is still broke. I Can not import ANY roms.
It inserts that "file:" into my path and everything breaks.

Also themes dont work under BigBox

Edited March 2 by xokia

[xokia]

Any progress?

13.18 is less broke then 13.19.  Themes work fine under 13.18.

Maybe its not correct to say 13.18 is broke. 13.18 worked 100% until upgrading to 13.19. After upgrading then reverting back to 13.18 MAME import is broke.

Let me know if there is anything I can do to assist in debug.

Edited March 2 by xokia

[xokia]

Here is what it looks like when I try and import a rom with 13.19. 

Same exact import with 13.18

Edited March 2 by xokia

[Zarach]

I'm having the exact same behavior with 3.19. I upgraded to 3.20 today and the issue persists. I can confirm rolling back to 3.18 fixes the ability to import ROMs.

When 3.19 / 3.20 are installed all my platform game folders are displayed as a UNC path rather than the relative path that was shown in 3.18 and before when choosing Tools --> Manage --> Platforms. 

Importing ROMs whether it be a folder or file always prepends file:\\\ as described above. It's worth mentioning also that every time the import process starts, it defaults to "network" in file explorer and immediately shows a UNC path as the current directory before allowing me to browse to the network drive that inevitably results in a crash with again the same error described above (The specified path is invalid).

I store all my ROMs on a file server accessible by a mapped network drive (R:\). My Windows PC is domain joined to a home lab / network

[xokia]

On 2/28/2025 at 9:38 PM, Zarach said:

I'm having the exact same behavior with 3.19. I upgraded to 3.20 today and the issue persists. I can confirm rolling back to 3.18 fixes the ability to import ROMs.

When 3.19 / 3.20 are installed all my platform game folders are displayed as a UNC path rather than the relative path that was shown in 3.18 and before when choosing Tools --> Manage --> Platforms. 

Importing ROMs whether it be a folder or file always prepends file:\\\ as described above. It's worth mentioning also that every time the import process starts, it defaults to "network" in file explorer and immediately shows a UNC path as the current directory before allowing me to browse to the network drive that inevitably results in a crash with again the same error described above (The specified path is invalid).

I store all my ROMs on a file server accessible by a mapped network drive (R:\). My Windows PC is domain joined to a home lab / network

Glad to know I'm not the only one with this issue. I guess I'll hold off upgrading to 13.20. Not sure how they were not able to duplicate. Its fairly simple to replicate. Just use a mapped drive. I can set up a brand new VM with a single platform and hit the issue. Heck if the admin folks need a machine this is replicated on. I could set a VM just for this debug they could RDP into and poke around and change whatever they want. Ping me via IM if this something you might be interested in.

[xokia]

Any update on when this might get fixed or if its on the radar? Not being pushy was just curious how bugs get consumed and then fixed. I assume you folks have a release process and schedule you follow?