Community Event / Creation TradeDangerous GUI front end

v1.0.6.5
Getting .net error msg
Unhandled exception
Index was out of range.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at TDHelper.Form1.readNetLog()
at TDHelper.Form1.buildOutput()
at TDHelper.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
TDHelper
Assembly Version: 1.0.6.5
Win32 Version: 1.0.6.5
CodeBase: file:///C:/Program%20Files%20Games/Frontier/TradeDangerous/TDHelper/TDHelper.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34251 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data.SQLite
Assembly Version: 1.0.96.0
Win32 Version: 1.0.96.0
CodeBase: file:///C:/Program%20Files%20Games/Frontier/TradeDangerous/TDHelper/System.Data.SQLite.DLL
----------------------------------------
System.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.Runtime.Serialization
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
Last edited:
This exception is thrown from TDHelper on startup after the trade script update.
TradeDangerous script itself still works great :)

************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at TDHelper.Form1.readNetLog()
at TDHelper.Form1.buildOutput()
at TDHelper.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at
 
Last edited:
Similar here. I updated TD scripts last night, then this - Initially TDHelper started normally and requested to set VerboseLogging then immediately crashed on exception error. Now it throws this on startup but apparently continues ok after 'continue' pressed :

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at TDHelper.Form1.readNetLog()
at TDHelper.Form1.buildOutput()
at TDHelper.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
TDHelper
Assembly Version: 1.0.6.5
Win32 Version: 1.0.6.5
CodeBase: file:///C:/Temp/TradeDangerous/TDHelper.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data.SQLite
Assembly Version: 1.0.96.0
Win32 Version: 1.0.96.0
CodeBase: file:///C:/Temp/TradeDangerous/System.Data.SQLite.DLL
----------------------------------------
System.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.Runtime.Serialization
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.6.76.2 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Checking manually VerboseLogging="1" is set correctly in the AppConfig.xml and my batch scripts work fine for TD main on the command line.
 
Last edited:
Hmm.. I'll take a closer look in a bit. I'm not experiencing the issue at the moment, but I think I know what might be causing it.

(Edit: I think I found the problem. I overlooked a potential null reference when the Logs directory is empty. I'll re-release v1.0.6.5 after I test this a bit more to catch any other edge cases.)
 
Last edited:
My logs dir was not empty, unless something about switching back to live from beta test affected the logs.

Let me know if you still experience the exception. I think I caught both potential causes.

(Edit: If the path was different from the one listed in the Default.xml, or the Logs directory is empty the path to the log files would be invalid or null. Referencing a null list of paths was causing the exception.)
 
Last edited:
No new version to d/l yet, and checking default xml no issues. the only deviation is capitalisation of the td dir which is ignored under M$ anyway

<TDPath>C:\Temp\tradedangerous</TDPath>
<NetLogPath>C:\Users\hitch\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1002\Logs</NetLogPath>
<PythonPath>C:\Python34\python.exe</PythonPath>
<LastUsedConfig>C:\Temp\TradeDangerous\Default.xml</LastUsedConfig>
 
No new version to d/l yet, and checking default xml no issues. the only deviation is capitalisation of the td dir which is ignored under M$ anyway

TDHelper only checks for new versions when it starts to avoid hammering BitBucket unnecessarily. Also, double check your config to make sure the <DoNotUpdate> tag is set to "false", when set to "true" it prevents auto-updating.

(Edit: I'll be putting out 1.0.6.6 in a day or two, as I have a feature ready that should improve CPU usage when doing database updates that dump a lot of text to the output log. I'll take the opportunity to fix some more potential index/null bugs.)
 
Last edited:
Assuming you put out a bug fix to 1.0.6.5, no d/l from the program itself, or going to bitbucket as far as i can tell. Confirming <DoNotUpdate> is false.
 
Same error as my previous post #241

re-release v1.0.6.5
I will be waiting a few days/weeks for FD to fix a few bugs before I play again but will test any TDHelper updates I see

Note: logs directory is not empty and EDDiscovery is picking up systems as normal.
my default TDHelper config

<TDSettings>
<LocationParent>0,0</LocationParent>
<LocationChild>0,0</LocationChild>
<SizeParent>904,1040</SizeParent>
<SizeChild>492,226</SizeChild>
<TDPath>C:\Program Files Games\Frontier\TradeDangerous\repository</TDPath>
<NetLogPath>C:\Program Files Games\Frontier\EDLaunch\Products\FORC-FDEV-D-1001\Logs</NetLogPath>
<PythonPath>C:\Python34\python.exe</PythonPath>
<ImportPath>C:\Program Files Games\Frontier\MyLogs\OCRSystemData\import.prices</ImportPath>
<UploadPath>C:\Program Files Games\Frontier\MyLogs\OCRSystemData\import.prices</UploadPath>
<LastUsedConfig>C:\Program Files Games\Frontier\TradeDangerous\TDHelper\Default.xml</LastUsedConfig>
<Padsizes />
<Avoid>Imperial Slaves,Slaves</Avoid>
<Via />
<ExtraRunParams />
<Hops>2</Hops>
<Jumps>0</Jumps>
<Credits>3374353</Credits>
<Insurance>374353</Insurance>
<Capacity>40</Capacity>
<PruneHops>0</PruneHops>
<PruneScore>0</PruneScore>
<LSPenalty>0</LSPenalty>
<MaxLSDistance>0</MaxLSDistance>
<LoopInt>0</LoopInt>
<Limit>0</Limit>
<AbovePrice>0</AbovePrice>
<BelowPrice>0</BelowPrice>
<Age>0</Age>
<GPT>0</GPT>
<MaxGPT>0</MaxGPT>
<Stock>40</Stock>
<Demand>0</Demand>
<Verbosity>3</Verbosity>
<CSVSelect>1</CSVSelect>
<UnladenLY>30</UnladenLY>
<LadenLY>1</LadenLY>
<Margin>0</Margin>
<Towards>false</Towards>
<Loop>true</Loop>
<Unique>false</Unique>
<ShowJumps>false</ShowJumps>
<TestSystems>false</TestSystems>
<Corrections>false</Corrections>
<MiniModeOnTop>true</MiniModeOnTop>
<DisableNetLogs>false</DisableNetLogs>
<DoNotUpdate>false</DoNotUpdate>
<HasUpdated>true</HasUpdated>
</TDSettings>

[EDIT] just noticed its not showing the change log could it be connected to that?

also after clicking Continue and then clicking [C] i get this
InvalidArgument=Value of "1" is not valid for SelectedIndex

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of '1' is not valid for 'SelectedIndex'.
Parameter name: SelectedIndex
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at TDHelper.Form1.backgroundWorker1_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
TDHelper
Assembly Version: 1.0.6.5
Win32 Version: 1.0.6.5
CodeBase: file:///C:/Program%20Files%20Games/Frontier/TradeDangerous/TDHelper/TDHelper.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34251 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data.SQLite
Assembly Version: 1.0.96.0
Win32 Version: 1.0.96.0
CodeBase: file:///C:/Program%20Files%20Games/Frontier/TradeDangerous/TDHelper/System.Data.SQLite.DLL
----------------------------------------
System.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.Runtime.Serialization
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[EDIT 2] Typing into source doesn't bring up any systems, switching back to v1.0.6.4 does
 
Last edited:
Doesn't bring up any systems as in no recent systems, or any systems at all? If it's the latter, that's totally unexpected behavior.

Either way, I think I've figured out the root cause of this. The regex that checks for the system name and timestamp is using a set of non-optional matches, if either happens to fail it returns null instead of blank. I'll have another version out shortly that should fix this and some other issues. I'm in the process of testing to make sure there aren't any significant differences between open play and the other modes.
 
V1.0.6.6 is rolling out now, hopefully this will resolve the recent systems errors. If not, my only recommendation left is to clear your Logs directory of any logs from before the Powerplay update.

This release also introduces a culling buffer for the output log to help prevent severe performance issues when dumping huge amounts of text to the output log such as during database updates from Maddavo. I was seeing 3 minute updates take over 15 minutes before this version just from the text box being flooded with data. The downside of this feature is that very large buffers get their viewable output trimmed to something reasonable. This approach may be overly aggressive, but I'll tweak it a bit if it ends up being necessary.
 
V1.0.6.6 is rolling out now, hopefully this will resolve the recent systems errors. If not, my only recommendation left is to clear your Logs directory of any logs from before the Powerplay update.

This release also introduces a culling buffer for the output log to help prevent severe performance issues when dumping huge amounts of text to the output log such as during database updates from Maddavo. I was seeing 3 minute updates take over 15 minutes before this version just from the text box being flooded with data. The downside of this feature is that very large buffers get their viewable output trimmed to something reasonable. This approach may be overly aggressive, but I'll tweak it a bit if it ends up being necessary.

I was getting the long updates until I download the updated files from maddavo see post #1829 in TD thread

I tracked down the error with the logs, seems some of my files may be written to disk incorrectly, (Refresing the files fixed the error)

I have zipped the erronous ones up if you would like me to email them so you can investigate further?

For anyone else with this issue Dont delete your logs load each file into a txt editor and resave them over the original (may take a while depending on logfolder size)

[EDIT] Small bug - v1.0.6.6 keeps suggesting there is an update available after it has been updated and then reloaded
 
Last edited:
Still the same issue :(

Thanks to NoTones sending me his netLogs I believe I finally have a working fix on my local repo. The bug is caused when TDHelper tries to process a netLog that contains no System names (for instance, when logging in then immediately logging out without going in-game).

If no one else decides to post their netLogs on BitBucket I'll re-upload 1.0.6.6 with the fix in a few hours.

- - - Updated - - -

[EDIT] Small bug - v1.0.6.6 keeps suggesting there is an update available after it has been updated and then reloaded

This happens when the MD5 of your existing TDHelper.exe is not the same as the MD5 listed in the manifest on BitBucket. You may want to try unpacking a freshly downloaded binary archive over your existing install if you encounter issues like that after an update. Normally it wouldn't be necessary, but I can't guarantee with absolute certainty the hot-swap updater is 100% bug free.
 
If anyone would like to help me test to make sure this patch fixes the error, grab the binary in THIS issue ticket and let me know if it works or not.

(Edit: Make sure to run it with the command line option "/noupdate" so it isn't immediately overwritten by the auto-updater.)
 
Last edited:
Think I accidentally hit the Run button twice before the first command had finished. Totaled my .prices file beyond systems starting with the letter 'C'. :(

Still running v1.0.6.4
 
Version 1.0.6.7 is up, and this time with a proper fix for the recent systems bug (seriously). This version also includes a few other bug fixes as well, see the changelog for details.

I should have the flight log ready to go in about a week or so, maybe sooner based on spare time. I'm eager to finish it as the features in Powerplay kind of necessitate having a flexible pilot's log.
 
Back
Top Bottom