I have a three monitor system and for some reason i can not get the main overlay to move to my middle monitor. I have looked in all the option but can't seem to find the right option.
I ask this because I am noticing TCE having issues sometimes it seems recognizing planetary bases. I had asselus primus baker prospect not show up after ED sent me there for some reason on death. I had to call my DBX in to the station and weirdly when I switched to the DBX it then recognized the station again.
I then flew out to another previously known station, forget the name. And the whole time leading up to landing the station was listed right, I saw how many previous visits. But idk if it was shortly after landing or going into hanger, but then it just said add market. It didn't show the market name in location window, just I think the system and planet. Idk what exactly it said since it's a long system name and it was late. Going to to a bit more investigating on this and see if I can find more info. And then make an error report.
I've only noticed it having issues on planetary bases so far. And when you click add market there is no info filled in at all. I also noticed very briefly between either messing with station menus or going switching ships, sometimes it will briefly flicker the known market, then go back to add market with just sysytem name.
I have a three monitor system and for some reason i can not get the main overlay to move to my middle monitor. I have looked in all the option but can't seem to find the right option.
I gave the planetary nav/mini-map a try. Tracking seemed to work, but when I tried to add a location to the map, I popped an error. I copied the error text, but somehow lost it before I could paste it here. 7z sent, Video link sent.
I gave the planetary nav/mini-map a try. Tracking seemed to work, but when I tried to add a location to the map, I popped an error. I copied the error text, but somehow lost it before I could paste it here. 7z sent, Video link sent.
Ok, I repeated the attempt to add a location to the planetary mini map, and got, I belive the same error.
Error:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.InvalidCastException: Conversion from string "" to type 'Long' is not valid. ---> System.FormatException: Input string was not in a correct format.
at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDecimal(String Value, NumberFormatInfo NumberFormat)
at Microsoft.VisualBasic.CompilerServices.Conversions.ToLong(String Value)
--- End of inner exception stack trace ---
at Microsoft.VisualBasic.CompilerServices.Conversions.ToLong(String Value)
at Trade_Computer_Extension.MD_Journal_Sub.Update_Object_Distance() in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal_Sub.vb:line 1406
at Trade_Computer_Extension.Panel_Map.BTN_Save_Click(Object sender, EventArgs e) in F:\Trade Computer Extension\Trade Computer Extension\Panel_Map.vb:line 866
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Label.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.
Also, I think the reason I lost it before was because TCE put something on the clipboard between the time I did "copy" and then "paste" into word to capture the error text.
Anyway, there may also be a problem with TCE showing where an outpost shows on the minimap/radar. I captured some vid and will send you the link. It may just be that I was not far enough away from the outpost for TCE to show it properly, although the location was way off on the map. This is a ED plantary outpost, not something I added.
Ok, I repeated the attempt to add a location to the planetary mini map, and got, I belive the same error.
Error:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.InvalidCastException: Conversion from string "" to type 'Long' is not valid. ---> System.FormatException: Input string was not in a correct format.
at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDecimal(String Value, NumberFormatInfo NumberFormat)
at Microsoft.VisualBasic.CompilerServices.Conversions.ToLong(String Value)
--- End of inner exception stack trace ---
at Microsoft.VisualBasic.CompilerServices.Conversions.ToLong(String Value)
at Trade_Computer_Extension.MD_Journal_Sub.Update_Object_Distance() in F:\Trade Computer Extension\Trade Computer Extension\MD_Journal_Sub.vb:line 1406
at Trade_Computer_Extension.Panel_Map.BTN_Save_Click(Object sender, EventArgs e) in F:\Trade Computer Extension\Trade Computer Extension\Panel_Map.vb:line 866
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Label.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.
Also, I think the reason I lost it before was because TCE put something on the clipboard between the time I did "copy" and then "paste" into word to capture the error text.
Anyway, there may also be a problem with TCE showing where an outpost shows on the minimap/radar. I captured some vid and will send you the link. It may just be that I was not far enough away from the outpost for TCE to show it properly, although the location was way off on the map. This is a ED plantary outpost, not something I added.
Hey Eventure been doing what I can to figure out my issues with 1.6.7.3 Both mine and my wife's machine seem to be experiencing the same problem it not reading the starting location correctly. Also EDDB Relay won't download data it gets stuck at around 98-99% and just hangs there and I need to end task and restart DB verify's ok no errors. I know each new ED Update causes issues and I usually just sit patiently and wait as they usually get iron out soon enough but most folks seem to be saying 1.6.7.3 is working ok now.
Hey Eventure been doing what I can to figure out my issues with 1.6.7.3 Both mine and my wife's machine seem to be experiencing the same problem it not reading the starting location correctly. Also EDDB Relay won't download data it gets stuck at around 98-99% and just hangs there and I need to end task and restart DB verify's ok no errors. I know each new ED Update causes issues and I usually just sit patiently and wait as they usually get iron out soon enough but most folks seem to be saying 1.6.7.3 is working ok now.
as I see, the last netlog and the last journal file are not from the same day (netlog from 04.03.2018, journal from 05.03.2018).
Please do the Auto-Detection process for Elite Dangerous, thereafter it should normally work.
Another minor thing I noticed was: after I scan an unexplored planet, everything runs fine, but I see the "hide the gui by pressing ctr..." flyout twice for some reason.
Another minor thing I noticed was: after I scan an unexplored planet, everything runs fine, but I see the "hide the gui by pressing ctr..." flyout twice for some reason.
No problem, found the issue, it only affect the Landmark type.
What i can't recreate is the doubled message! Badbud reported it also.
Please check the Event Reporter Log, which is only accessable by selecting a keybind for it, if the message is also shown twice.
Thanks.
************** Ausnahmetext **************
System.Data.SQLite.SQLiteException (0x80004005): bad parameter or other API misuse
null connection or database handle
bei System.Data.SQLite.SQLite3.Prepare(SQLiteConnection cnn, String strSql, SQLiteStatement previous, UInt32 timeoutMS, String& strRemain)
bei System.Data.SQLite.SQLiteCommand.BuildNextCommand()
bei System.Data.SQLite.SQLiteDataReader.NextResult()
bei System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
bei System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
bei System.Data.SQLite.SQLiteCommand.ExecuteNonQuery(CommandBehavior behavior)
bei Trade_Computer_Extension.MD_SQLite_Database_Access.DB_Outfitting_DelEntry() in F:\Trade Computer Extension\Trade Computer Extension\MD_SQLite_Database_Access.vb:Zeile 1507.
bei Trade_Computer_Extension.Panel_Classic.Chk_EDMC_Outfit() in F:\Trade Computer Extension\Trade Computer Extension\Panel_Classic.vb:Zeile 1587.
bei Trade_Computer_Extension.Panel_Classic.Call_Classic_EDMC_Data() in F:\Trade Computer Extension\Trade Computer Extension\Panel_Classic.vb:Zeile 1360.
bei Trade_Computer_Extension.Panel_Classic.EDMC_cooldowntimer_Tick(Object sender, EventArgs e) in F:\Trade Computer Extension\Trade Computer Extension\Panel_Classic.vb:Zeile 1323.
bei System.Windows.Forms.Timer.OnTick(EventArgs e)
bei System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
No problem, found the issue, it only affect the Landmark type.
What i can't recreate is the doubled message! Badbud reported it also.
Please check the Event Reporter Log, which is only accessable by selecting a keybind for it, if the message is also shown twice.
Thanks.
************** Ausnahmetext **************
System.Data.SQLite.SQLiteException (0x80004005): bad parameter or other API misuse
null connection or database handle
bei System.Data.SQLite.SQLite3.Prepare(SQLiteConnection cnn, String strSql, SQLiteStatement previous, UInt32 timeoutMS, String& strRemain)
bei System.Data.SQLite.SQLiteCommand.BuildNextCommand()
bei System.Data.SQLite.SQLiteDataReader.NextResult()
bei System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
bei System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
bei System.Data.SQLite.SQLiteCommand.ExecuteNonQuery(CommandBehavior behavior)
bei Trade_Computer_Extension.MD_SQLite_Database_Access.DB_Outfitting_DelEntry() in F:\Trade Computer Extension\Trade Computer Extension\MD_SQLite_Database_Access.vb:Zeile 1507.
bei Trade_Computer_Extension.Panel_Classic.Chk_EDMC_Outfit() in F:\Trade Computer Extension\Trade Computer Extension\Panel_Classic.vb:Zeile 1587.
bei Trade_Computer_Extension.Panel_Classic.Call_Classic_EDMC_Data() in F:\Trade Computer Extension\Trade Computer Extension\Panel_Classic.vb:Zeile 1360.
bei Trade_Computer_Extension.Panel_Classic.EDMC_cooldowntimer_Tick(Object sender, EventArgs e) in F:\Trade Computer Extension\Trade Computer Extension\Panel_Classic.vb:Zeile 1323.
bei System.Windows.Forms.Timer.OnTick(EventArgs e)
bei System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Please sent me a complete bug report, otherwise I can't do much. Could be something with the file (\DB\TCE_Outfitting.db).
You could reset the database and fill it again with the EDDB-Relay.
Please sent me a complete bug report, otherwise I can't do much. Could be something with the file (\DB\TCE_Outfitting.db).
You could reset the database and fill it again with the EDDB-Relay.
Badbud reported it also.
Please check the Event Reporter Log, which is only accessable by selecting a keybind for it, if the message is also shown twice.