Jump to content

Lithius

Member
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Lithius

  1. The version linked in both topics (open stress test and troubleshooting) is 0.4, which may or may not be worth updating (it auto-upgrades to 0.7 anyway). I appreciate you taking the time to respond this issue. Today, it mysteriously began working again, which I'm going to chalk up to some sort of transient network issue. I do, however, think it would be a good idea to eliminate the possibility of an unhandled exception, either by checking the length of the relevant array/collection before attempting to index into it - and giving an appropriate error message if it doesn't have the expected length, or by wrapping the Application.Run call in a try catch. I typically use the internal GridErrorDlg for this: public static DialogResult ShowErrorDialog(string text, string caption, Exception ex) { Type errorDialogType = typeof(Form).Assembly.GetType("System.Windows.Forms.PropertyGridInternal.GridErrorDlg"); Form errorDialog = (Form)Activator.CreateInstance(errorDialogType, new PropertyGrid()); errorDialog.Text = caption; errorDialogType.GetProperty("Message").SetValue(errorDialog, text, null); errorDialogType.GetProperty("Details").SetValue(errorDialog, ex.Message + Environment.NewLine + ex.StackTrace, null); errorDialog.StartPosition = FormStartPosition.CenterParent; return errorDialog.ShowDialog(); } used as: static void Main() { Application.EnableVisualStyles(); Application.SetCompatibleTextRenderingDefault(false); try { Application.Run(new MainWindow()); } catch(Exception ex) { ShowErrorDialog("Uncaught exception, see details for more information.", "Error", ex); } }
  2. Yes, I have attempted to temporarily disable real-time protection, and have also added the application directory to the exclusion list. By relevant, I meant suggestions relevant to the updater not starting, rather than the issues with the game itself. Installed are 4.5 and 4.6, only. 4.0 appears to be the target framework (as selected in the project application settings in Visual Studio).
  3. Same issue again today. The updater window opens, the "checking" icon spins briefly, and the window crashes. The following entry appears in the Windows Application log: Application: SkylordsRebornUpdater.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IndexOutOfRangeException at SkylordsRebornUpdater.MainWindow.GetUpdateFile() at SkylordsRebornUpdater.MainWindow.CheckForUpdates() at System.Threading.ThreadHelper.ThreadStart_Context(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart() As the game was working fine for many months, I'm sure my system has the necessary prerequisites. I did, however, follow all of the relevant suggestions in this thread, including disabling firewall/anti-virus, deleting Documents\BattleForge, deleting the entire application folder and downloading and extracting both the client and updater again, restarting several times, etc.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use