Thanks a lot for the opportunity to play with the beta version of the Army Editor. Unfortunately, I can't start it (32 or 64 bit version) :( I double click on the shortcut and nothing happens. Looking at the Windows event viewer I can see the following two errors (sorry French version of Windows):
Application : GSBPArmyEditor.exe
Version du Framework : v4.0.30319
Description : le processus a été arrêté en raison d'une exception non gérée.
Informations sur l'exception : System.FormatException
à System.Number.ParseDouble(System.String, System.Globalization.NumberStyles, System.Globalization.NumberFormatInfo)
à ArmyEditor.MainWindowViewModel+<>c.<loadAccuracies>b__71_1(System.String)
à System.Linq.Enumerable+WhereSelectListIterator`2[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.Double, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
à System.Linq.Buffer`1[[System.Double, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]..ctor(System.Collections.Generic.IEnumerable`1<Double>)
à System.Linq.Enumerable.ToArray[[System.Double, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Collections.Generic.IEnumerable`1<Double>)
à ArmyEditor.MainWindowViewModel.loadAccuracies()
à ArmyEditor.MainWindowViewModel..ctor()
Informations sur l'exception : System.Windows.Markup.XamlParseException
à System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri)
à System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)
à System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)
à System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)
à ArmyEditor.MainWindow..ctor()
à ArmyEditor.App.Application_Startup(System.Object, System.Windows.StartupEventArgs)
à System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
à System.Windows.Application.<.ctor>b__1_0(System.Object)
à System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
à System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
à System.Windows.Threading.DispatcherOperation.InvokeImpl()
à MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
à System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
à System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
à System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
à MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
à System.Windows.Threading.DispatcherOperation.Invoke()
à System.Windows.Threading.Dispatcher.ProcessQueue()
à System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
à MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
à MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
à System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
à System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
à System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
à MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
à MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
à System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
à System.Windows.Application.RunDispatcher(System.Object)
à System.Windows.Application.RunInternal(System.Windows.Window)
à ArmyEditor.App.Main()
and
Nom de l'application défaillante GSBPArmyEditor.exe, version : 1.0.0.0, horodatage : 0x5b758d00
Nom du module défaillant : KERNELBASE.dll, version : 10.0.17134.165, horodatage : 0xb0bb231d
Code d'exception : 0xe0434352
Décalage d'erreur : 0x000000000003a388
ID du processus défaillant : 0x1e58
Heure de début de l'application défaillante : 0x01d435ac04b085ab
Chemin d'accès de l'application défaillante : D:\Program Files (x86)\GeneralStaff\BlackPowder\GSBPArmyEditor\GSBPArmyEditor.exe
Chemin d'accès du module défaillant: C:\WINDOWS\System32\KERNELBASE.dll
ID de rapport : 6fca0064-451f-413f-b567-de0583dce6cb
Nom complet du package défaillant :
ID de l'application relative au package défaillant :
It looks like you don't have .net framework 4.7 installed. I thought the installer would check for this. Apparently not.
Net 4.7 is required.
Installing net 4.7 is certainly the first thing to look at.
You can download from:
https://www.microsoft.com/net/download/dotnet-framework-runtime/net47
I just uninstalled .net4.7 off my test machine.
Rebuilt the installer.
Tried it.
I got a message saying .net4.7 wasn't installed and did I want to install it.
Not sure what's going on exactly on your machine.
The different versions of net4.x install over one another.
Maybe its not checking what's after that dot and net 4.0 satisfies the dependency check in the installer.
This is an interim method of installation, we'll only be using this just for beta testers.
Because of that, we're using a relatively simplistic installer which is easy to set up for straight forward just-install-stuff but quite fiddly to make it do more sophisticated things.
Sorry if this is a bit frustrating as a result.
I have the same issue. Here's the log (sorry, it's in Norwegian):
Programnavn med feil: GSBPArmyEditor.exe, versjon: 1.0.0.0, tidsangivelse: 0x5b758d00
Modulnavn med feil: KERNELBASE.dll, versjon: 10.0.17134.165, tidsangivelse: 0xb0bb231d
Unntakskode: 0xe0434352
Feilforskyvning: 0x000000000003a388
Feil prosess-ID: 0x23fc
Feil starttid for program: 0x01d436416c5c4f43
Feil programbane: C:\Program Files (x86)\GeneralStaff\BlackPowder\GSBPArmyEditor\GSBPArmyEditor.exe
Feil modulbane: C:\WINDOWS\System32\KERNELBASE.dll
Rapport-ID: bd6ea720-bcbd-4295-b7a2-92ae3cef43d2
Fullstendig navn på feilpakke:
Relativ program-ID for feilpakke:
I tried to install the framework, but I allready have it.
The issue here:
à System.Number.ParseDouble(System.String, System.Globalization.NumberStyles, System.Globalization.NumberFormatInfo)
Is saying it's trying to convert the text it's read out an accuracies file into double.
These will be using a full stop as a decimal place and will work fine on both Ezra's machine and mine.
Because we're american and english.
In other countries, a comma is used as the decimal place symbol and this could cause that specific error.
I'll investigate.
Quote
à System.Number.ParseDouble(System.String, System.Globalization.NumberStyles, System.Globalization.NumberFormatInfo)
Is saying it's trying to convert the text it's read out an accuracies file into double.
These will be using a full stop as a decimal place and will work fine on both Ezra's machine and mine.
Because we're american and english.
In other countries, a comma is used as the decimal place symbol and this could cause that specific error.
Yes, this is it. I have changed the settings on my computer (decimal symbol is "." instead of ",") and the editor starts successfully.
Quote from: Mickey3D on August 17, 2018, 03:44:10 PM
Yes, this is it. I have changed the settings on my computer (decimal symbol is "." instead of ",") and the editor starts successfully.
Thanks for the tip. I changed the language settings and that worked.
Great stuff.
This is, obviously, not an ideal solution.
I've got a version which attempts to cope with different language settings.
This will be rolled out once Ezra has tested it.
( It's almost impossible to thoroughly test something you've written yourself. )
This is what beta testing is all about :)
Works fine in the new version! :)
Great stuff.
Thanks for the feedback.