crash Launchbox, BigBox, Launchbox.Next crashes with latest version

[anickname]

I could not find an unblock button, but I did something else: I added the nas to the local intranet zone in windows (see screenshot):

Now all three executables are running fine.

Thanks for the help and for the application.

[Jason Carr]

Just now, anickname said:

I could not find an unblock button, but I did something else: I added the nas to the local intranet zone in windows (see screenshot):

Now all three executables are running fine.

Thanks for the help and for the application.

Good to hear.

[ForsakenZaroc]

Whatever version was live April 1, no im not running anything over a network path.

[Jason Carr]

3 minutes ago, ForsakenZaroc said:

Whatever version was live April 1, no im not running anything over a network path.

Did you run the update/setup on that particular machine, or did the files just get copied or sync to it?

[ForsakenZaroc]

It updated automatically

Edited April 13, 2018 by ForsakenZaroc
spelling

[ForsakenZaroc]

The install on April 1 was downloaded and installed on this machine.

[Jason Carr]

@ForsakenZaroc Can you check to see if you have the "unblock" option listed above on the "LaunchBox\CefSharp\x64\CefSharp.Core.dll" file?

[anickname]

I think that the problem that arise when running from network shares should be documented.

Others should know how to fix it.

[ForsakenZaroc]

30 minutes ago, Jason Carr said:

@ForsakenZaroc Can you check to see if you have the "unblock" option listed above on the "LaunchBox\CefSharp\x64\CefSharp.Core.dll" file?

Ill check when I wake up (night shift)

[Jason Carr]

1 hour ago, anickname said:

I think that the problem that arise when running from network shares should be documented.

Others should know how to fix it.

That's the beauty of the forums; it will forever be documented here. I'll also note it so that I should be able to recognize it for next time. That said, in all honesty we don't recommend running the EXE from a NAS or network storage at all anyways due to potential performance issues. We find that ROMs do perfectly fine over network storage, but media and the application itself are much better stored locally.

[anickname]

Yes, you're right, there is a speed difference between a local hard drive and NAS, but on NAS I have storage space, redundancy (RAID), filesystem snapshots.

For me the speed is not so important as those NAS advantages; once the game is loaded the drive is rarely accessed.

Anyway, thanks for the help.

[Jason Carr]

11 minutes ago, anickname said:

Yes, you're right, there is a speed difference between a local hard drive and NAS, but on NAS I have storage space, redundancy (RAID), filesystem snapshots.

For me the speed is not so important as those NAS advantages; once the game is loaded the drive is rarely accessed.

Anyway, thanks for the help.

Yeah, I use Dropbox for the redundancy, backups, snapshots, etc., but it's generally not the cheapest solution.

[ForsakenZaroc]

7 hours ago, Jason Carr said:

@ForsakenZaroc Can you check to see if you have the "unblock" option listed above on the "LaunchBox\CefSharp\x64\CefSharp.Core.dll" file?

I do not, I read the links on how to get the button to appear. A lot of it went over my head but I think I could get through it.

[Jason Carr]

2 hours ago, ForsakenZaroc said:

I do not, I read the links on how to get the button to appear. A lot of it went over my head but I think I could get through it.

We're still not certain if you have the same issue, but it probably wouldn't hurt. Then again if the button isn't showing up I'm guessing that's not the issue, but that's just a guess.

[Jason Carr]

1 minute ago, Jason Carr said:

We're still not certain if you have the same issue, but it probably wouldn't hurt. Then again if the button isn't showing up I'm guessing that's not the issue, but that's just a guess.

Come to think of it, if regular LaunchBox is working but not LaunchBox.Next or Big Box, then it must be something specific to LaunchBox.Next and Big Box. It could be related to game controllers, DirectX, even a driver issue with .NET WPF. Check to make sure your drivers are all up to date, including video drivers. We've heard about weird conflicts with some poorly-written keyboard software from Corsair as well, and nVidia's recording software.

[ForsakenZaroc]

Thanks I’ll look at my drivers in the morning. Have a good night. 

[ForsakenZaroc]

21 hours ago, Jason Carr said:

Come to think of it, if regular LaunchBox is working but not LaunchBox.Next or Big Box, then it must be something specific to LaunchBox.Next and Big Box. It could be related to game controllers, DirectX, even a driver issue with .NET WPF. Check to make sure your drivers are all up to date, including video drivers. We've heard about weird conflicts with some poorly-written keyboard software from Corsair as well, and nVidia's recording software.

The problem was bluetooth passthrough for dolphin. Im hopping I can get them both to play well together.

[Jason Carr]

1 hour ago, ForsakenZaroc said:

The problem was bluetooth passthrough for dolphin. Im hopping I can get them both to play well together.

Ah, wow. I believe I have heard of that but not for a while. Try playing with the controller settings in LaunchBox.

[ForsakenZaroc]

39 minutes ago, Jason Carr said:

Ah, wow. I believe I have heard of that but not for a while. Try playing with the controller settings in LaunchBox.

Will do, thanks for your time.