New layout looks really good, can't wait.
Remind me what that Override button is for again?
Remind me what that Override button is for again?
Release [Explorer's Application] Captain's Log
- Thread starter Genar-Hofoen
- Start date
The Override button was for the people who wanted to run Captain's Log 1.x on a different machine from where the game is running. They would install the game on PC1, Captain's Log on PC2, then share the netlog directory from PC1--->PC2, which was then mounted on PC2.
Captain's Log would then be configured to read from that shared netlog directory, and parse the logs.
Because the game wasn't running on PC2, Captain's Log couldn't detect when the game was started on PC1, and therefore it wouldn't start the background process which sucked in the netlogs and parsed them for that juicy jump event. Hence, the Override button was born, which when clicked, starts the log parser thread.
Now, I think - and I haven't tested this - that it should be possible to share the Elite Dangerous folder residing in the Saved Games folder on PC1, mount it on the Saved Games folder on PC2, and have Captain's Log 2.x parse the logs as before.
That's the theory. For now though, I have removed being able to select a netlogs directory from CL2's configuration - it's currently hard coded to the Saved Games folder on whatever PC CL2 is running on. According to this link, it should be possible to do this.
Regards o7
Don't know if this is a bug or I'm using it wrong, but for some reason Beta 2 was only able to read my last 97 jumps. Captains log 1.4.1 didn't have this issue, and I suspect it's because I could tell it where my Elite logs were stored and beta 2 is getting the logs from somewhere that doesn't have it all stored, or it's just accessing 1 log file. It is saving my jumps since, but it not noticing all my jumps in my logs (Which i can confirm still exist) is troubling. Also, verbose logging is on.
On a second note, any way to import a database from 1.4.1 to beta 2?
Edit: I'm dumb. Just realized that Beta 2 is getting information from the journal files... But something I did run into is that my most recent jump was not registered, even though it shows up in the journal. I guess now all we need is a way to transfer old netlog files into the journal, or for beta 2 to allow a database transfer from captains log 1.4.1, and/or be able to read the old netlog files.
On a second note, any way to import a database from 1.4.1 to beta 2?
Edit: I'm dumb. Just realized that Beta 2 is getting information from the journal files... But something I did run into is that my most recent jump was not registered, even though it shows up in the journal. I guess now all we need is a way to transfer old netlog files into the journal, or for beta 2 to allow a database transfer from captains log 1.4.1, and/or be able to read the old netlog files.
Last edited:
The DB format between CL 1.x and CL 2.x is completely different.
CL2.x I consider to be a clean break from CL1.x, which is why CL2 installs separately from CL1 and has a different %localappdir% directory.
There are so many differences between the two, that attempting to write an importer would be quite a difficult task - I'd rather concentrate on adding features to CL2 and just moving on.
As you spotted, CL has been re-written to take the new Player Journal files. All CL1 did was to take advantage of 1 single line that was available in the old netlog files, to detect when you had FSD'ed to a different system. No other information was available - hence users having to manually click planet and star types and enter designations and such.
The difference between the old CL db's and the new CL db's is like chalk and cheese. My head already hurts just thinking about how one would convert between the two
Updated Beta 2 Available For Download With New Layout
As above, I have altered the layout for Beta 2 - I didn't want to up the Beta version number just for this change.
You can just re-download this Beta 2 and install over the last version of Beta 2.
Download : https://www.dropbox.com/s/x2zs6h2u8o91h4o/Captain's Log 2_2.0.0 Beta 2_setup.exe?dl=1
Regards o7
As above, I have altered the layout for Beta 2 - I didn't want to up the Beta version number just for this change.
You can just re-download this Beta 2 and install over the last version of Beta 2.
Download : https://www.dropbox.com/s/x2zs6h2u8o91h4o/Captain's Log 2_2.0.0 Beta 2_setup.exe?dl=1
Regards o7
Lovely, thank you so much!
Captain's Log 2 Beta 3 Available For download And Testing
As per post title.
Download Link : https://www.dropbox.com/s/g7bs3swr20mngh0/Captain's Log 3_2.0.0 Beta 3_setup.exe?dl=1
Changelog
Screenshot
Regards o7
As per post title.
Download Link : https://www.dropbox.com/s/g7bs3swr20mngh0/Captain's Log 3_2.0.0 Beta 3_setup.exe?dl=1
Changelog
Screenshot
Regards o7
I'll download a bit later.
Very quick question: J1 J2 indicate premium, and standard, I presume? Not sure how you use the numbers. In this case what about basic jumponium? For example Germanium is used for both basic and standard FSD injections. I'm running beta 2 and so far I had systems where the jumponium widget did not appear at all despite almost all mats being available at the system.
I also have a suggestion about synthesis but I need to put down some screenshots, so I'll do that later.
Finally, is there a way to define the starting point of a trip? Also a way of counting the number of unique systems visited during that trip?
I return, after a power cut not 10 minutes after I made my last post. (Fuse blew at the local substation).
J1 = basic
J2 = Standard
J3 = Premium
That's what this release fixes - see changelog
If it's to do with being able to search for synthesis mats - that's going to happen.
I also plan on putting in some more Explorer-relevant synth mat indicators if there are some - but do put forward suggestions - I might not have thought about them yet
Intention is each DB represents a Trip - start a new DB for each trip. There is a central GALAXY database which each Trip DB refers to to get the actual star system info, planets, etc.
Unique systems are in the DB summary in the Databases tab in the configuration manager window.
Regards o7
In that case shouldn't the above screenshot have J3 as Niobium (Nb) is also a premium FSD injection material (as is Arsenic)?
Thinking aloud: it's always felt a bit odd to me that I go into the config dialog to see my uploaded screenshots and copy their Imgur URLs to the clipboard. Especially as that dialog is modal, so I can't leave it open in the background.
Thoughts?
Thoughts?
The logic is "If J1 or J2 or J3 mats all exist in this system, then display the appropriate icon and flash the alert"
Basic (J1) requires : Vanadium and Germanium, which this system has got.
Standard (J2) requires : Vanadium, Germanium, Cadmium, and Niobum, again which are present in this system.
Premium (J3) requires : Arsenic, Niobium, Yttrium, and Polonium. That system has Arsenic, Niobium, and Yttrium, but I did not scan a planet which had Polonium.
Ergo, as far as CL2 is concerned, only J1 and J2 are available in this particular system. If there were other landable planets and if they were scanned and if they contained Polonium, then CL2 would duly flag J3 up as being available.
Regards o7
- - - - - Additional Content Posted / Auto Merge - - - - -
Indeed.
I did have a primitive version of that in the main window for an early version of CL2, but honestly it looked out of place seeing picture thumbnails on the main window - it looked really distracting, in fact. I'm having a rethink on that and will probably have the screenshots/urls in a slide-in widget like the Notes widgets do.
Yeah that might be the answer.
Last edited:
Your logic is flawless but unfortunately as an explorer I find this feature pointless. You are telling me if the system has every necessary injection material for an injection of a specific type. Given that I am working with jumponium around 80% of the time and prospect heavily for it, I can tell you that when I look for materials I'm happy to find one or two in one system, especially the ones for premium injection. I usually look for materials over a number of systems as I travel and my next post will tie this with the suggestion regarding synthesis.
When I am in the look for mats I need to know that the system has at least some of J3 mats. The number of systems with some of the mats are plenty. The number of systems with all of the mats are few (and when it comes to all J3 mats extremely rare). Therefore, I suggest you display two indicators, one for all the mats in the system and another for partial mats. Looking at the partial indicator means I can potentially find some of the mats I'm hunting for.
Deleted.
Last edited:
In beta 3 I'm seeing some inconsistency in click response in the planets table. Clicks in the designation column always select the relevant row. Clicks in the other columns are very hit and miss and I can't discern a pattern.
Personally, I like the J1/2/3 and now the A1/2/3 designators. Like how the rock rats identified 'green' systems for the DWE. It's still useful to have a green base system in the vicinity of where you want to work so you can stock up.
I like Rhea's idea too, but that needs manual entry to at least identify the recipes you want to search for - so it would have to be an 'advanced option' rather than a default I think.
I like Rhea's idea too, but that needs manual entry to at least identify the recipes you want to search for - so it would have to be an 'advanced option' rather than a default I think.
Oh don't get me wrong, I love the designators. But when I am looking for materials it's over several systems. Not every system has Polonium but if I find one with Arsenic and Niobium I want to know. Hence, why I'm asking for partial indicators. Knowing that some mats are available on the system is useful.
If I am not mistaken a 'green' system is a system that holds J1, J2 and J3 materials? I am just asking because the J3 button in CL is green in itself and may or may not cause confusion.
This is where the system notes come in. The search entry box at the bottom of the app window searches on system name, system notes and jump notes.
One of my mantras is KISS - Keep It Simple, Stupid! And that's what drives the CL design - has done since its inception. Sure, I could probably program up some sort of thing as you've demonstrated above, but y'know what? It's too complicated, in my opinion.
So you've jumped into a system, scanned many planets, found a bunch of materials. You make a note of 'em in the system notes. You're nearby, so you want to know which system has the materials, you just plug in your search term, say, 'partial J3' , and the results will come up for any system note for 'partial J3'.
Just make up a note taking system and that should suffice. All the information you need is already presented in the planet table and info widget.
The last thing I want to do is get bogged down for weeks trying to come up with some equivalent of a spreadsheet - honestly I understand where you're coming from, but something like that spreadsheet above is IMO not keeping to the KISS principle
I mean don't get me wrong here - I'll try to come up with some way of searching for closest materials - but I've got a ton of stuff I still need to do. One of the things is perhaps uploading planet/material data to EDDB - which does have a search facility for materials now. Again, I have the EDSM module I was intending to start work on today but that got sidelined with Real Life Stuff. We'll see. I'll keep what you're doing in my mind, and I have been finding your feedback awesome
Regards o7
- - - - - Additional Content Posted / Auto Merge - - - - -
Ah, I just came up with my own colour coding for CL - Red, amber, green for J1, J2, and J3, (and A1, A2, and A3) just to distinguish them - no account has been taken of any kind of other group's established colour coding protocols. I'd have thought that the fact that either J1, J1/J2, and J1, J2, J3 showing or not showing within a scanned system was a clear and simple indication, to be honest.
Regards
Last edited:
The pattern is that in cells with icons, you'll find that clicking on the icon won't trigger as a cell click - because that's how the GUI toolkit rolls. Just learn to click on the text-only columns and you should be golden.