For ease of access, would it be possible to include the 'send error report' in the options menu? Or is it a necessity to have TCE closed and use it via the launcher?
Will add it to the Options panel. For error's, you have to close TCE and start the launcher, because TCE is sometimes no longer accessable when the error appears.
Have also reworked the 'Report A Bug' function at the launcher, no longer required to exit ED too, to send a complete report.
Changelog: - Added the "EngineerContribution" event.
- Added a "Report a bug" button to the Options panel.
- Added a version checker at start to prevent running TCE in an outdated enviroment.
- Fixed a counting issue at the Mission Summary (Systems) of the Personal panel.
- Fixed an issue with the classic UI not dehighlighting the Mission button, when the Mission panel was closed.
- Fixed an issue that you can't close the Missions panel by clicking the Mission button again at the UI.
- Fixed an issue with the details of active missions, displaying the location ID instead of the location name, at the Personal panel.
- Fixed an issue with multiple simultaneous events at the journal, only processing the first recognized.
- Fixed an issue with the "RepairAll" event not recognized.
Note:
Copy all files and folders from the update into your TCE installation folder (see version requirements) to update your version.
I like to remind any user, who wants to use TCE in french, spanish and russian to help in translating the
latest interface phrases and commodities at OneSky. Thanks in advance.
Hi Eventure. Please would it be possible to get the mission count next to the mission icon on button view, so it is always on screen and we don't need to go into several menus to see it? This would be a good quality of life improvement.
Hi Eventure. Please would it be possible to get the mission count next to the mission icon on button view, so it is always on screen and we don't need to go into several menus to see it? This would be a good quality of life improvement.
Is the selling of Commodities to the SEARCH AND RESCUE AGENT also not covered yet? I assume so, as I've recently sold a few items and they remained in the CARGO list. Which I deleted manually without issue. But I also noticed that when selling these items my Balance didn't change in the PERSONAL PANEL.
[1] Handing in Rares to Engineer Errors
Handing in FUJIN TEA to BROO TARQUIN and I get this error. When this happens TCE remains in PROCESSING mode and I have to quit TCE and restart. I get one of these two errors. And the Rare is not removed from the Cargo Panel. I tried this twice by handing in 1 Rare each time.
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentException: Argument 'Start' must be greater than zero.
at Microsoft.VisualBasic.Strings.Mid(String str, Int32 Start)
at Trade_Computer_Extension.MD_Journal.Event_EngineerContribution(Int64 a) in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal.vb:line 1459
at Trade_Computer_Extension.MD_Journal.Events_bestimmen() in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal.vb:line 244
at Trade_Computer_Extension.MD_Journal.Check_Journal() in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal.vb:line 74
at Trade_Computer_Extension.Ablauf_Startprozedur._Lambda$__1(Object a0, EventArgs a1) in F:\Trade Computer Extension\Trade Computer Extension\Ablauf_Startprozedur.vb:line 289
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** 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.
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.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentException: Argument 'Start' must be greater than zero.
at Microsoft.VisualBasic.Strings.Mid(String str, Int32 Start)
at Trade_Computer_Extension.MD_Journal.Event_EngineerContribution(Int64 a) in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal.vb:line 1459
at Trade_Computer_Extension.MD_Journal.Events_bestimmen() in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal.vb:line 244
at Trade_Computer_Extension.MD_Journal.Check_Journal() in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal.vb:line 74
at Trade_Computer_Extension.Ablauf_Startprozedur._Lambda$__1(Object a0, EventArgs a1) in F:\Trade Computer Extension\Trade Computer Extension\Ablauf_Startprozedur.vb:line 289
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** 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.
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.
Is the selling of Commodities to the SEARCH AND RESCUE AGENT also not covered yet? I assume so, as I've recently sold a few items and they remained in the CARGO list. Which I deleted manually without issue. But I also noticed that when selling these items my Balance didn't change in the PERSONAL PANEL.
[1] Handing in Rares to Engineer Errors
Handing in FUJIN TEA to BROO TARQUIN and I get this error. When this happens TCE remains in PROCESSING mode and I have to quit TCE and restart. I get one of these two errors. And the Rare is not removed from the Cargo Panel. I tried this twice by handing in 1 Rare each time.
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentException: Argument 'Start' must be greater than zero.
at Microsoft.VisualBasic.Strings.Mid(String str, Int32 Start)
at Trade_Computer_Extension.MD_Journal.Event_EngineerContribution(Int64 a) in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal.vb:line 1459
at Trade_Computer_Extension.MD_Journal.Events_bestimmen() in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal.vb:line 244
at Trade_Computer_Extension.MD_Journal.Check_Journal() in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal.vb:line 74
at Trade_Computer_Extension.Ablauf_Startprozedur._Lambda$__1(Object a0, EventArgs a1) in F:\Trade Computer Extension\Trade Computer Extension\Ablauf_Startprozedur.vb:line 289
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** 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.
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.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentException: Argument 'Start' must be greater than zero.
at Microsoft.VisualBasic.Strings.Mid(String str, Int32 Start)
at Trade_Computer_Extension.MD_Journal.Event_EngineerContribution(Int64 a) in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal.vb:line 1459
at Trade_Computer_Extension.MD_Journal.Events_bestimmen() in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal.vb:line 244
at Trade_Computer_Extension.MD_Journal.Check_Journal() in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal.vb:line 74
at Trade_Computer_Extension.Ablauf_Startprozedur._Lambda$__1(Object a0, EventArgs a1) in F:\Trade Computer Extension\Trade Computer Extension\Ablauf_Startprozedur.vb:line 289
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** 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.
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.
I've been using 1.6.3.3 for the last couple of days and have suddenly come across a problem. When attempting to start TCE I now get the following error: -
TCE WORKSPACE
Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
".", hexadecimal value 0x00, is an invalid character. Line 1, position 1
with the following details: -
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos)
at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XDocument.Load(String uri, LoadOptions options)
at Trade_Computer_Extension.Config_File.Read_TCE_config() in F:\Trade Computer Extension\Trade Computer Extension\MD_TCE.config.vb:line 472
at Trade_Computer_Extension.TCE_Launcher_Login.Form1_Load(Object sender, EventArgs e) in F:\Trade Computer Extension\Trade Computer Extension\TCE_Launcher_Login.vb:line 21
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)
************** 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.
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.
If I click continue I get to the login screen but for a Commander named 'Hellmachine' rather than my own commander name - 'Maedhros'. Also the ability to change commanders is disabled. Obviously it will not log me in as Hellmachine and my only option is to then close TCE. As TCE will not start I am unable to use your error reporting.
Please let me know which files / db entries you will need to check the problem & I'll forward these onto you.
I've been using 1.6.3.3 for the last couple of days and have suddenly come across a problem. When attempting to start TCE I now get the following error: -
TCE WORKSPACE
Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
".", hexadecimal value 0x00, is an invalid character. Line 1, position 1
with the following details: -
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos)
at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XDocument.Load(String uri, LoadOptions options)
at Trade_Computer_Extension.Config_File.Read_TCE_config() in F:\Trade Computer Extension\Trade Computer Extension\MD_TCE.config.vb:line 472
at Trade_Computer_Extension.TCE_Launcher_Login.Form1_Load(Object sender, EventArgs e) in F:\Trade Computer Extension\Trade Computer Extension\TCE_Launcher_Login.vb:line 21
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)
************** 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.
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.
If I click continue I get to the login screen but for a Commander named 'Hellmachine' rather than my own commander name - 'Maedhros'. Also the ability to change commanders is disabled. Obviously it will not log me in as Hellmachine and my only option is to then close TCE. As TCE will not start I am unable to use your error reporting.
Please let me know which files / db entries you will need to check the problem & I'll forward these onto you.
There must be a problem with your TCE.config file at the root folder of TCE, maybe it is damaged? Send it to me, so I can take a look. If you can't fix it on your own, delete it. TCE will create a new on start.
But you have to configure some parts of TCE again. But if you have an outdated archive or installation on your drive, you can take it from there, but you have to edit the TCE_Version row at the file to be
the same as your actual TCE version.
That reminds me to add the TCE.config also to the daily backup file.
There must be a problem with your TCE.config file at the root folder of TCE, maybe it is damaged? Send it to me, so I can take a look. If you can't fix it on your own, delete it. TCE will create a new on start.
But you have to configure some parts of TCE again. But if you have an outdated archive or installation on your drive, you can take it from there, but you have to edit the TCE_Version row at the file to be
the same as your actual TCE version.
That reminds me to add the TCE.config also to the daily backup file.
Changelog: - Added a Donation field to the Expenses category of the Credit Balance at the Personal panel.
- Added a mouse-over tooltip of influence values at the faction chart of the Faction panel.
- Added a mouse-over tooltip of money values at the credit chart of the Personal panel.
- Added the number of active missions to the Missions button at the text- and icon-based UI.
- Added a "Yesterday" node at the Mission Summary treeview of the Personal panel.
- Added the TCE.config file to the backup archive. Better safe than sorry.
- Added a high gravity warning for high-G (>3G) planets, when stored at the cartography database.
- Fixed an issue at the mission destination display for registered markets.
- Fixed the Full Screen Display Mode Warning at start. It was moved to the Settings tab of the launcher.
- Fixed an issue with the "EngineerContribution" event.
Note:
Copy all files and folders from the update into your TCE installation folder (see version requirements) to update your version.
I like to remind any user, who wants to use TCE in french, spanish and russian to help in translating the
latest interface phrases and commodities at OneSky. Thanks in advance.
Hi Eventure, Many thanks for the latest addition to TCE I'm forever grateful for your prompt updates. Might I draw your attention to a "n i g g l e" I have, I say "n i g g l e" as it starting to become a thorn in my side because I'm forever repeating it and it revolves around photographing the object once the initial scan is complete. This works as it should, but when repeats are required thats when the error on my part happens. If I am unhappy with an image placement within the target frame I repeat the picture BUT if I am too hastie the image replaces the default star in the system which you can imagine requires an extra trip back to the default star to correct said error. This is fine if ur close to main star, but not so if ur 200,000ls away (involves jumping out and returning to said system to retake image).
Therefore, is it possible for the action to default to the object targeted rather than the default star? I am currently exploring and to say I've done this same error 2 dozen times is an understatement and feel it could be rectified thus saving many (as I fear I am not the only Cmdr who has experienced this annoyance more than once) Is it possible to retain the repeated image on current target rather than it default to system star?
Appreciate your input on this. Thanks, Delta 2-7
PS Apologies for the spaced out wording "N I G G L E" but apparently this forum does not allow the word to be written.
URGENT!!! Can anyone assist me? I appear to be in a catch 22 position the image window has appeared above my current screen for some reason and no amount of restarting TCE or changing screen modes helps to aide me in getting access to it. Thanks in advance
URGENT!!! Can anyone assist me? I appear to be in a catch 22 position the image window has appeared above my current screen for some reason and no amount of restarting TCE or changing screen modes helps to aide me in getting access to it. Thanks in advance
Enter the Options panel, select Panel Configuration, thereafter under Panel Position, select Camera and enter a Y value greater than 20. Will add a fix, that this can't happen in the future.
Hi Eventure, Many thanks for the latest addition to TCE I'm forever grateful for your prompt updates. Might I draw your attention to a "n i g g l e" I have, I say "n i g g l e" as it starting to become a thorn in my side because I'm forever repeating it and it revolves around photographing the object once the initial scan is complete. This works as it should, but when repeats are required thats when the error on my part happens. If I am unhappy with an image placement within the target frame I repeat the picture BUT if I am too hastie the image replaces the default star in the system which you can imagine requires an extra trip back to the default star to correct said error. This is fine if ur close to main star, but not so if ur 200,000ls away (involves jumping out and returning to said system to retake image).
Therefore, is it possible for the action to default to the object targeted rather than the default star? I am currently exploring and to say I've done this same error 2 dozen times is an understatement and feel it could be rectified thus saving many (as I fear I am not the only Cmdr who has experienced this annoyance more than once) Is it possible to retain the repeated image on current target rather than it default to system star?
I understand your problem. I will change the treeview node selection, if you have scanned a planet or star before, so the proper entry is automatically selected, removing your issue.
The node selection returns to normal (selecting the primary star), if you leave a star system. Additionally the Event reporter will give a message of the selected planet or star, when the Camera panel is opened.
All will come with the next update.
Only your own data, you have entered and the journal data of course. It's the most time consuming methode.
EliteOCR makes commodity updates much easier than manual input. You have to OCR every commodity market page. OCR checks are done by TCE. It's still time consuming, but alot faster than manual input.
EDMC gets the data from the Frontier cAPI directly, so a complete data update of the local market is only a click on a button (could also be automatic on docking).
It's the fastest way to update, plus you get outfitting, shipyard, personal and ship data ontop.
TCE-Relay is only partial useable at the moment. It uses crowdsourced data from EDDB/EDDN to inject them into the TCE databases.
So it can create a starter database (without price data ), but the commodity prices update is currently offline (will be back when fixed).
