-
Posts
14 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by IronFistZilla
-
-
16 hours ago, Retro808 said:
If you are on Win 7, 8, or 8.1 then LB 13.10 and future versions will not work any longer. Updates required now make 13.9 the last LB/BB versions that will work on any of those older OS.
Thank you for letting me know. Any idea how I might be able to get version 13.8 (which is what I was using) or 13.9 so I can get things working again on my Win 7 Pro rig? I appreciate any info you can provide.
-
I just upgraded LaunchBox to 13.10 via the auto update and now when I launch I get the following:
Error - It is strongle recommended to close and restart LaunchBox in order to prevent any additional issues.
=============================================================================================================
(Inner Exception)
A procedure imported by 'I:\LaunchBox\ThirdParty\Chromium\CefSharp.Core.Runtime.dll' could not be loaded.
App:
Version: 13.10
Theme: NOT SET
Type: System.IO.FileLoadException
Site: Void LoadFromPath(IntPtr, System.String, System.String, System.Runtime.CompilerServices.ObjectHandleOnStack)
Source: System.Private.CoreLibat System.Runtime.Loader.AssemblyLoadContext.LoadFromPath(IntPtr ptrNativeAssemblyLoadContext, String ilPath, String niPath, ObjectHandleOnStack retAssembly)
at System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyPath(String assemblyPath)
at System.Reflection.Assembly.LoadFile(String path)
at Unbroken.LaunchBox.Windows.Desktop.Program.<>c.LoginSessionObject(Object )
at Unbroken.LaunchBox.Windows.Desktop.Program.<>c.ManageInvalidReader(Object sender, ResolveEventArgs e)
at System.Runtime.Loader.AssemblyLoadContext.InvokeResolveEvent(ResolveEventHandler eventHandler, RuntimeAssembly assembly, String name)
at System.Runtime.Loader.AssemblyLoadContext.OnAssemblyResolve(RuntimeAssembly assembly, String assemblyFullName)
(Outer Exception)A procedure imported by 'CefSharp.Core.Runtime, Version=117.2.40.0, Culture=neutral, PublicKeyToken=40c4b6fc221f4138' could not be loaded.
App:
Version: 13.10
Theme: NOT SET
Type: System.IO.FileLoadException
Site: Void .ctor()
Source: CefSharp.Coreat CefSharp.CefSettingsBase..ctor()
at Unbroken.LaunchBox.Windows.Desktop.App..ctor()
at Unbroken.LaunchBox.Windows.Desktop.Program.Main(String[] args)Recent Log:
3:53:21 PM Exception
=============================================================================================================
This happens everytime I close and attempt to relaunch LaunchBox. Any assistance is greatly appreciated.
-
23 hours ago, Retro808 said:
Doesn't this apply only to those who have previously purchased the Android version of Launchbox? I currently only have a Forever license for Windows.
-
On 4/10/2020 at 10:17 AM, Jason Carr said:
We have unfortunately had to increase the price with the new version, but anyone who previously purchased from Google Play will of course receive a forever-updates license and will receive all new versions. The new pricing model closely matches the desktop, but is also much cheaper: $10 for a regular license, or $25 for a forever-updates license. These new prices will help to ensure that Android development continues to be feasible for us long-term.
This has now gone up from $25.00 to $40.00?!? Is this right? I was reluctantly willing to pay the 25, but 40 for another license (as I have Premium on Windows) so I can have LB on the go is too much. Hopefully will be on sale on Black Friday.
-
I just upgraded to LB11 and am unable to figure out how to change the rom file for any game I have in LB. I used to be able to right-click on the game, select Edit, then modify the rom/cue file associated with that game. The new version no longer has a field for this that I can see. Is this still a viable option that I am missing or do I need to delete the game and re-add it to LB? I appreciate any assistance.
UPDATE: NM, just figured it out. My apologies for the trouble. For those wondering how to modify the rom file for a game in LB11 you would do the following:
- Right-click on the game and select Edit.
- Click on Launching on the left-hand column.
- Modify the value of the ROM File (emulation is enabled) field.
- Then click OK.
-
My pleasure.
- 1
-
Did a fresh install and everything seems to be working now without the need for Admin rights. Obviously something on my system somewhere but it seems to be sorted now. Thank you all for the assist, I really appreciate it.
- 1
-
1 minute ago, Jason Carr said:
Typically requiring administrator permissions is caused by file permissions issues. Have you always had to use LaunchBox as administrator?
No, things have always launched just fine from the desktop icons without any additional modification. Im going to do a clean install and see what happens. Ill update as soon as I am done.
-
I:\LaunchBox
-
Sorry, been editing my prior post. Yes I have ended task on the process and I have restarted. The only way I can get Beta 2 LaunchBox or Big Box to launch is to "Run as Administrator".
-
LaunchBox Beta 2 is stuck at initializing and refuses to launch for me unless I "Run as an Administrator". Same goes for Big Box. The controller still works in both, but having to launch this way is a bit inconvenient. Have not had to do this in the past so is a bit odd.
-
Sorry for the delayed response. Windows 7 Professional with a Wireless Xbox 360 Controller. I just tried the Beta release and my controller is now working!
- 1
-
I second this, just updated to LaunchBox/Big Box 10.4 and I'm having the same issue. I cannot navigate in Big Box nor can I control the mouse in Launchbox. Controls in game are fine, however, my normal exit from a game (Select + Start on my xbox controller) does not function. I have already tried resetting the controller in the options and deleting LaunchBox\Data\InputBindings.xml file. however, nothing seems to work. Any information and assistance is greatly appreciated.
Launchbox 13.10 will not launch - Error Received
in Troubleshooting
Posted · Edited by IronFistZilla
Will do. Thank you for your help, I really appreciate it!
Please consider this matter resolved.