Release Trade Computer Extension Mk.II

I tried different ways to run TCE for several days. Deauthorization / new authorization did not work. TCE reports "Invalid credentials", even if the EDMC GUI is successfully authorized. EDMC CLI debug.log:
Code:
2021-01-25 01:06:14.371 - ERROR - companion.Session.query:500: Frontier CAPI Auth: GET
Traceback (most recent call last):
  File "companion.pyc", line 496, in query
  File "requests\models.pyc", line 943, in raise_for_status
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://companion.orerve.net/profile
2021-01-25 01:06:14.374 - ERROR - companion.Session.dump:583: Frontier CAPI Auth: https://companion.orerve.net/profile 400 Bad Request Please <a class="alert-link" href="https://frontierstore.net/">Visit the store</a> to purchase Elite: Dangerous.
2021-01-25 01:06:15.683 - ERROR - companion.Session.query:500: Frontier CAPI Auth: GET
Traceback (most recent call last):
  File "companion.pyc", line 496, in query
  File "requests\models.pyc", line 943, in raise_for_status
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://companion.orerve.net/profile

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "companion.pyc", line 496, in query
  File "requests\models.pyc", line 943, in raise_for_status
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://companion.orerve.net/profile
2021-01-25 01:06:15.685 - ERROR - companion.Session.dump:583: Frontier CAPI Auth: https://companion.orerve.net/profile 400 Bad Request Please <a class="alert-link" href="https://frontierstore.net/">Visit the store</a> to purchase Elite: Dangerous.
2021-01-25 01:06:15.687 - ERROR - companion.Session.query:505: Frontier CAPI Auth: query failed after refresh
2021-01-25 01:06:15.690 - INFO - companion.invalidate:351: Frontier CAPI Auth: Invalidated token for "Chilace"
2021-01-25 01:06:16.191 - ERROR - companion.Auth.refresh:261: Frontier CAPI Auth: Can't refresh token for "Chilace"
2021-01-25 01:06:16.193 - INFO - companion.Auth.refresh:271: Frontier CAPI Auth: New authorization request
2021-01-25 01:06:16.195 - INFO - companion.Auth.refresh:277: Trying auth from scratch for Commander "Chilace"
2021-01-25 01:06:16.396 - ERROR - EDMC.main:394: Frontier CAPI Server: Invalid Credentials
2021-01-25 01:08:36.844 - ERROR - companion.Auth.refresh:261: Frontier CAPI Auth: Can't refresh token for "Chilace"
2021-01-25 01:08:36.847 - INFO - companion.Auth.refresh:271: Frontier CAPI Auth: New authorization request
2021-01-25 01:08:36.848 - INFO - companion.Auth.refresh:277: Trying auth from scratch for Commander "Chilace"
2021-01-25 01:08:37.057 - ERROR - companion.Session.query:469: cannot make a query when unauthorized
2021-01-25 01:08:37.058 - ERROR - EDMC.main:394: Frontier CAPI Server: Invalid Credentials
I have an EGS version of the game and it looks like this is a clue and I found a way to run TCE without error -
Before starting TCE, you first need to start the game, in this case, TCE reports that the EDMC is ready to use.
Interesting... Did you tried to follow my path posted above?
Otherwise, this log and post is better placed into the thread or issue tracker of EDMC to find a solution.
Thanks
 
Hello,
Just updated to the 1.8.3.0 have an issue with the database again, not much changed since last time, so here's a link to the error report and screenshot. I can't seem to get it to a point where I can create a bug report so this will have to do for now.

Under 1.8.2.5 database verifies ok. see additional SS.

 
Last edited:
And its Back. Doing the same thing. It looks like I will try checking with the EDMC guys.. intersting note. It says invalid credentials.. however if I tell it to update the trade station s databse it seems to be pulling information.
 
Last edited:
Hello,
Just updated to the 1.8.3.0 have an issue with the database again, not much changed since last time, so here's a link to the error report and screenshot. I can't seem to get it to a point where I can create a bug report so this will have to do for now.

Under 1.8.2.5 database verifies ok. see additional SS.

Please send me a bug report from the v1.8.2.5 incl. your files.
Thanks.
And its Back. Doing the same thing. It looks like I will try checking with the EDMC guys.. intersting note. It says invalid credentials.. however if I tell it to update the trade station s databse it seems to be pulling information.
These data coming from my server containing files provides by EDDB, so they have nothing to do with EDMC.
 
When trying to update (actually recreate) a market database it gets stuck on "Deleting obsolete unregistered stations" step
with this exception text...

System.IndexOutOfRangeException: Индекс находился вне границ массива.
в System.Array.InternalGetReference(Void* elemRef, Int32 rank, Int32* pIndices)
в System.Array.GetValue(Int32 index1, Int32 index2, Int32 index3)
в Microsoft.VisualBasic.CompilerServices.Symbols.Container.GetArrayValue(Object[] Indices)
в Microsoft.VisualBasic.CompilerServices.NewLateBinding.InternalLateIndexGet(Object Instance, Object[] Arguments, String[] ArgumentNames, Boolean ReportErrors, ResolutionFailure& Failure, Boolean[] CopyBack)
в Microsoft.VisualBasic.CompilerServices.NewLateBinding.ObjectLateInvokeDefault(Object Instance, Object[] Arguments, String[] ArgumentNames, Boolean ReportErrors, Boolean[] CopyBack)
в Trade_Computer_Extension.MD_SQLite_Database_Access.DB_URegMarkets_EDDBDelEntries() в F:\Trade Computer Extension\Trade Computer Extension\MD_SQLite_Database_Access.vb:строка 0
в Trade_Computer_Extension.TCE_Launcher_UI.Create_initial_Database() в F:\Trade Computer Extension\Trade Computer Extension\TCE_Launcher_UI.vb:строка 37336
в Trade_Computer_Extension.TCE_Launcher_UI.BTN_CreateDB_Click(Object sender, EventArgs e) в F:\Trade Computer Extension\Trade Computer Extension\TCE_Launcher_UI.vb:строка 2026
в System.Windows.Forms.Control.OnClick(EventArgs e)
в System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
в System.Windows.Forms.Control.WndProc(Message& m)
в System.Windows.Forms.Label.WndProc(Message& m)
в System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Can't make a report via TCE itself because i can't interact with the window. Only close/mimimize it. When i relaunch it and try to verify my databases it gives me an error in registered markets DB which i can't repair. Only replace with a default one.
 
When trying to update (actually recreate) a market database it gets stuck on "Deleting obsolete unregistered stations" step
with this exception text...

Can't make a report via TCE itself because i can't interact with the window. Only close/mimimize it. When i relaunch it and try to verify my databases it gives me an error in registered markets DB which i can't repair. Only replace with a default one.
If you can verify your databases, you can send me a report, so I can check your files and see what happens and why TCE can't repair it.
Thanks in advance.
 
Hello everybody,

I have received reports of problems, updating the databases with EDDB-Relay and using CPUs with more than 4 physical cores.
Please return to the V1.8.2.5, until I can fix the issue with a patch.
Thanks.

@Found the problem, it will be fixed with the next patch aimed for this beginning weekend. RL is catching me today and tomorrow.
 
Last edited:
Version [1.8.3.1] released
Changelog:
  • Fixed a rare error when transferring outdated version databases to the actual version.
  • Fixed an error when deleting unregistered markets through the EDDB Market database creation for users with less than 4 physical core CPUs at the EDDB-Relay.
  • Fixed a critical issue with an endless loop of the EDDB-Relay update for users with more than 4 physical core CPUs.
  • Fixed an issue with the Cartography database repair routine, skipping entries with special characters.
  • Fixed an issue with the Star System database repair routine, not considering in-game duplicate star systems in finding duplicate entries in database.
  • Fixed an error in case of an empty cartography picture folder while transferring databases to a new version.
  • Fixed an issue when updating the star class for the next star system on a route.
Notes:
Either download the version above, install and transfer your old database, or use the auto-update function of the launcher.
Click the 'new version' notice at the bottom of the launcher.

If you find an error, please report and use the Report a Bug button at the launcher and don't forget to copy the error details and ErrorReportFile.7z archive.

I like to remind any user, who want's to use TCE in french, spanish or russian to help in translating the
latest interface phrases, common commodities and rare commoditiesat OneSky. Thanks in advance.
 
I don't know If you have seen the Elite G19s companion plugin [it does not actually require a gs19 keyboard] but one of the neat things he has done is integrate the Logitech ARX protocol - allowing the use of a tablet as a second input / display. Thanks for all your hard work!
 
Hello everyone and welcome to the preview of the v1.8.4.

I have invested some time in adding performance to the EDDB-Relay web service. The integration of the Outfitting database into the Trade Market database was big step in reducing the required processing times of the service. But there is more to come.

I have managed to integrate the Prices database into the Trade Market database too, decreasing further the time of processing considerably (-90%).
Also the Star System database update process has gained a performance upgrade, cutting times by 90% too.

So the overall performance is looking really good actually, for example an update of a Max. sphere radius selection (which means, all available stations (about 66,8K) from EDDB) is down to less than 5 mins incl. creating the database, updating prices, outfittings, stations, star systems and factions.

Also I want to show you today the rework of the EDDB-Relay interface at the Launcher below. The old was too complicated or confusing, so my try was to make it as simple as it could. But see yourself...


EDDB_Relay_rework.JPG



The ON/OFF switch has to be added, because of the automatic updates in the future.

Now with the management switch, you can choose, if your Trade Market database stays private or online.

Private meaning, that no additional stations are added in your vicinity to your database, only updates of current available station in database are processed.
Therefore the 'Sphere Radius' become deactivated.

An Online management will add new markets and remove not visited markets outside the 'Sphere Radius' automatically. Also a message will appear while moving through space in game, if your selected Trade Range no longer entirely covering the 'Sphere Radius', if you have selected the 'Manual' database update option.
Online not meaning, that your databases resides online somewhere, all stays local on your PC.

With the Database Update switch, you can select, if you want to make an update manually at the Launcher or TCE doing it automatically in game. This feature has to be developed in the future and is not selectable yet.

The Sphere Raduis selection is only available for 'Online' management to choose, how big your information database will be.

With the 'Start Service' button you can start all processing with one click.

That's all for today. If you have questions or suggestions, feel free to add a post.
 
Last edited:
Hello everyone and welcome to the preview of the v1.8.4.

I have invested some time in adding performance to the EDDB-Relay web service. The integration of the Outfitting database into the Trade Market database was big step in reducing the required processing times of the service. But there is more to come.

I have managed to integrate the Prices database into the Trade Market database too, decreasing further the time of processing considerably (-90%).
Also the Star System database update process has gained a performance upgrade, cutting times by 90% too.

So the overall performance is looking really good actually, for example an update of a Max. sphere radius selection (which means, all available stations (about 66,8K) from EDDB) is down to less than 5 mins incl. creating the database, updating prices, outfittings, stations, star systems and factions.

Also I want to show you today the rework of the EDDB-Relay interface at the Launcher below. The old was too complicated or confusing, so my try was to make it as simple as it could. But see yourself...


View attachment 206459


The ON/OFF switch has to be added, because of the automatic updates in the future.

Now with the management switch, you can choose, if your Trade Market database stays private or online.

Private meaning, that no additional stations are added in your vicinity to your database, only updates of current available station in database are processed.
Therefore the 'Sphere Radius' become deactivated.

An Online management will add new markets and remove not visited markets outside the 'Sphere Radius' automatically. Also a message will appear while moving through space in game, if your selected Trade Range no longer entirely covering the 'Sphere Radius', if you have selected the 'Manual' database update option.
Online not meaning, that your databases resides online somewhere, all stays local on your PC.

With the Database Update switch, you can select, if you want to make an update manually at the Launcher or TCE doing it automatically in game. This feature has to be developed in the future and is not selectable yet.

The Sphere Raduis selection is only available for 'Online' management to choose, how big your information database will be.

With the 'Start Service' button you can start all processing with one click.

That's all for today. If you have questions or suggestions, feel free to add a post.

Looks good and the performance improvement sounds great. I am about 2500 LY from the bubble, so including those remote stations out in the black would be really helpful for explorers. Got a bit bruised on a 4.5g planet and could do with some hull repairs!

If I can make some suggestions:
1. Move DATABASE UPDATE as 2nd line, under SERVICE. Is the START SERVICE button, purely for the MANUAL option? If so it is not obvious. I had assumed it was an actual Windows Service that you were adding to update the DB regardless of user. Maybe mistaken. Maybe change to START MANUAL UPDATE.
2. I was confused with PRIVATE and ONLINE, and I think others will be. If you change DATABASE MANAGEMENT to INCLUDE SYSTEMS: and change PRIVATE to VISITED and ONLINE to VISITED AND IN RANGE, I think that matches your description.
3. Maybe change SPHERE RADIUS to INCLUDE SYSTEMS WITHIN: to match the description above, as it only relates to when "IN RANGE" option is selected.
4. Instead of the MAX LY, use ALL or infinity symbol ∞. I thought "what is the max", but I think you mean all systems, correct?
 
I am about 2500 LY from the bubble, so including those remote stations out in the black would be really helpful for explorers. Got a bit bruised on a 4.5g planet and could do with some hull repairs!
As long as they are included into the EDDB nightly dump, but there is another problem. TCE includes only those stations actually, which star system is already available at the star system database. Because it isn't far from complete, should TCE add the corresponding star systems for those stations automatically?
@ Checked the number of stations, which star systems are not included in TCE, which are 1,5k from 62,5k.
1. Move DATABASE UPDATE as 2nd line, under SERVICE. Is the START SERVICE button, purely for the MANUAL option? If so it is not obvious. I had assumed it was an actual Windows Service that you were adding to update the DB regardless of user. Maybe mistaken. Maybe change to START MANUAL UPDATE.
The button is for starting the update process, manually or once for the automatic option. You can see, if the service is already running (for the automatic option) when entering the Extension tab or has to be used again for the manual option. You can also stop the service there. Maybe I will add a status field for the service. And right, it is not a windows service. The naming of the button could be adaptive, depending on the Manual or Automatic selection.
2. I was confused with PRIVATE and ONLINE, and I think others will be. If you change DATABASE MANAGEMENT to INCLUDE SYSTEMS: and change PRIVATE to VISITED and ONLINE to VISITED AND IN RANGE, I think that matches your description.
Good suggestion, will do so. Visited is standard by default, also it should be named then like INCLUDE TRADE STATIONS. Options are VISITED ONLY and ALL IN RANGE.
3. Maybe change SPHERE RADIUS to INCLUDE SYSTEMS WITHIN: to match the description above, as it only relates to when "IN RANGE" option is selected.
Same as above, only changes to INCLUDE STATIONS WITHIN.
4. Instead of the MAX LY, use ALL or infinity symbol ∞. I thought "what is the max", but I think you mean all systems, correct?
I mean all stations available from EDDB or at least all available from the nightly dump, which of course isn't the complete list of stations.
This have to be coupled with adding then previously unknown star systems to the database.
And btw, TCE won't add any Fleet Carrier positions to database in the update process.

Nice input, thank you. Anyone else having suggestions too?
 
Last edited:
Back
Top Bottom