Release [Explorer's Application] Captain's Log

LeLv30_Superbus · Nov 19, 2015

Ok, I'll try validating everything.

FWIW, this is my AppConfig.xml:

<AppConfig>
<Display>
<ScreenWidth>1280</ScreenWidth>
<ScreenHeight>720</ScreenHeight>
<FullScreen>false</FullScreen>
<VSync>true</VSync>
<PresentInterval>1</PresentInterval>
<Adapter>0</Adapter>
<Monitor>0</Monitor>
<DX11_RefreshRateNumerator>60</DX11_RefreshRateNumerator>
<DX11_RefreshRateDenominator>1</DX11_RefreshRateDenominator>
<LimitFrameRate>false</LimitFrameRate>
<MaxFramesPerSecond>30</MaxFramesPerSecond>

</Display>

<Threads
RenderThreadStackSize="1048576"
WorkerThreadStackSize="1048576"
NumWorkerThreads="6"
RenderJobQueueSize="10240"
KernelJobQueueSize="10240"
MinSpareCores="0"
OptimiseForPerformance="1"
UseThreadPriorities="0"
PerformanceScaling="1"
/>

<Files
MaxLoadRetries="10"
/>


<PlanetNoiseTextures
Enabled="auto"
ShaderWarmingDialogAnimTimeInMs="600">

<AutoDisableOnOsx>ATI Radeon HD 2400</AutoDisableOnOsx>
<AutoDisableOnOsx>ATI Radeon HD 2600 Pro</AutoDisableOnOsx>
<AutoDisableOnOsx>ATI Radeon HD 5770</AutoDisableOnOsx>
<AutoDisableOnOsx>ATI Radeon HD 5870</AutoDisableOnOsx>
<AutoDisableOnOsx>ATI Radeon HD 6800 Series</AutoDisableOnOsx>
<AutoDisableOnOsx>AMD Radeon HD 6970M</AutoDisableOnOsx>
<AutoDisableOnOsx>AMD Radeon HD 6870 Series</AutoDisableOnOsx>
<AutoDisableOnOsx>AMD Radeon HD 6xxx</AutoDisableOnOsx>
<AutoDisableOnOsx>Intel HD Graphics 3000</AutoDisableOnOsx>
<AutoDisableOnOsx>NVIDIA GeForce GT 120</AutoDisableOnOsx>

</PlanetNoiseTextures>

<Network
Port="0"
upnpenabled="1"
LogFile="netLog"
DatestampLog="1"
VerboseLogging="1"
ReportSentLetters="1"
ReportReceivedLetters="1"
VerboseLogging="1"
>
</Network>

<GameObjects />
</AppConfig>

- - - - - Additional Content Posted / Auto Merge - - - - -

Genar-Hofoen said:
The only thing I can suggest is Validate Game Files in the launcher.

This fixed the problem! Thank you very much, Sir!

I think it was the monitor setup, there was one small resolution in the file. Probably my display number two. My primary is 2560 x 1440.

Genar-Hofoen · Nov 19, 2015

LeLv30_Superbus said:
This fixed the problem! Thank you very much, Sir!

Another satisfied customer

Regards o7

LeLv30_Superbus · Nov 19, 2015

You know you should too

Everyone, I made a donation via Paypal to Genar-Hofoen and I'd like to recommend You to do the same.

It's easy. Just open Captain's Log -> About and use the donate-button. Took me less than 60 seconds.

This man is not only making free software for us to enjoy, he also provides free support for it. If you enjoy CL, there really no excuse not to donate.

drkaii · Nov 19, 2015

Genar, will there be a way to tweak this to work with beta installs? Will need it for the Horizon's beta

Genar-Hofoen · Nov 19, 2015

drkaii said:
Genar, will there be a way to tweak this to work with beta installs? Will need it for the Horizon's beta

It should work with beta installs - IF the betas include the same type of "jump event" line in the netlogs that the Live game does.

Like I mentioned earlier, the last time I checked this with a beta release was way back in something like 1.1 beta or 1.2 beta. I remember very clearly panicking at the time because CL wasn't registering the jumps I was making, but after manually checking the netlogs, found that the jump message wasn't logged in that beta.

And since then I always had it in my head that "betas don't include the jump message".

I'll test this with beta 1.5 later and report back.

Regards o7

- - - - - Additional Content Posted / Auto Merge - - - - -

LeLv30_Superbus said:
Everyone, I made a donation via Paypal to Genar-Hofoen and I'd like to recommend You to do the same.

It's easy. Just open Captain's Log -> About and use the donate-button. Took me less than 60 seconds.

This man is not only making free software for us to enjoy, he also provides free support for it. If you enjoy CL, there really no excuse not to donate.

Kind words - thanks

Genar-Hofoen · Nov 19, 2015

drkaii said:
Genar, will there be a way to tweak this to work with beta installs? Will need it for the Horizon's beta

EDIT: Disregard this post - you can now reconfigure CL from within the program!

Right - I just tested this...

To use Captain's Log with Beta 1.5...

0) exit Captain's Log and ED if they're running.

1) browse to %LOCALAPPDATA%

2) Make a backup copy of the existing CaptainsLog directory - this will have all the settings for the Live game! - including all your data (if you haven't specified a different data directory)

3) remove or rename the CaptainsLog directory

4) run Captain's Log

5) Point Captain's Log to the PUBLIC TEST SERVER/Logs directory for the Logs Directory setting.

Captain's Log will examine the beta AppConfig.xml file and produce a LocalAppConfig.xml file with the verboselogs set to "1" as per usual.

6) Choose your data directory and click the apply/proceed button

7) Captain's Log will start up

You will be using a default database with the name default. Use the DB Manager to create a new database with a more appropriate name and switch to that database.

8) Start the Beta

Jumps in the Beta will now be logged just as in the Live game.

To get back to using Captain's Log with the Live game:

0) exit Captain's Log and ED if they're running.

1) browse to %LOCALAPPDATA%

2) rename the CaptainsLog directory to something like "CaptainsLog - beta"

3) rename the copy of the CaptainsLog directory (as seen in the first procedure step (2) at the top of this post) back to CaptainsLog

4) start Captain's Log

5) start the game.

If you subsequently wish to view your Beta database, simply cut/paste, or copy it from the renamed CaptainsLog - Beta directory to the now Live CaptainsLog directory, and use CL's Database Manager to load it.

Regards o7

drkaii · Nov 19, 2015

Excellent, thank you very much!

Genar-Hofoen · Dec 1, 2015

New Version Released : 1.2.1 "Over the Horizon"

1.2.1 "Over the Horizon"

– POSSIBLE BUGFIX: Made getting the latest version from the site a bit more robust. Maybe.

– ENHANCEMENT: Make sure Configuration window is on top of everything else when activated.

– ENHANCEMENT: Can now reconfigure by calling up the configuration window whilst running CL.

– ENHANCEMENT: Captain’s Log can restart itself if there’s been a configuration change.

– ENHANCEMENT: Detection of whether ED is running made more generic, which should catch all versions of the game.

– ENHANCEMENT: Don’t include systems from CQC if user is playing it.

– ENHANCEMENT: Tweaked the Configuration Window’s look and feel to be the same as the other windows.

– MISC: Version bumped to 1.2.1

To bring up the Configuration Window, bring up the Database Manager window and click the green Reconfigure button.

Regards o7

SnugglySocks · Dec 1, 2015

Thanks for another great version of the tool

looks like verbose logging is now required to use CL with the 'new' 32bit version of elite I had to install today!

I have also noticed that you have to configure both the logs location and the db location before the finish icon comes up. This is when reconfiguring them.

'In game' achievements gained:
- manually entered missed jump into CL DB
- manually cleaned up DB after accidentally clicking import all logs :S
- backed up clean db file so I could maybe mess with it some more at a later date

SnugglySocks · Dec 2, 2015

Mungler said:
looks like verbose logging is now required to use CL with the 'new' 32bit version of elite I had to install today!

I have also noticed that you have to configure both the logs location and the db location before the finish icon comes up. This is when reconfiguring them.

Ok, so I did a bit more testing. Firstly verbose logging is always required (silly me), but I didn't notice because CL did it for me. So here is more detail on the issue I faced which may crop up when the next release hits.

i had ED installed in a 1001 folder in products, with the 'new' 32bit version of ED, it installed another copy of the game in the (previously unused) 1000 folder.

this meant I had to reconfigure CL (new feature came just in time) and where I had trouble just updating the log location on its own. I manually added verbose logging to the app config before realising that you had to register a change in both config fields before you could save it, so I don't know if CL would have updated the new app config on its own once I figured that out.

so mostly my own problem but something to consider when you come to install the full release of 1.5/2.0 in 64 bit.

Genar-Hofoen · Dec 2, 2015

Mungler said:
Ok, so I did a bit more testing. Firstly verbose logging is always required (silly me), but I didn't notice because CL did it for me. So here is more detail on the issue I faced which may crop up when the next release hits.

i had ED installed in a 1001 folder in products, with the 'new' 32bit version of ED, it installed another copy of the game in the (previously unused) 1000 folder.

this meant I had to reconfigure CL (new feature came just in time) and where I had trouble just updating the log location on its own. I manually added verbose logging to the app config before realising that you had to register a change in both config fields before you could save it, so I don't know if CL would have updated the new app config on its own once I figured that out.

so mostly my own problem but something to consider when you come to install the full release of 1.5/2.0 in 64 bit.

Aye - the reason I made this release was purely down to the fact that game locations or new directories are now being created - and rather than have everyone have to dig into their filesystems and manually remove a CL configuration file in order to trigger the Configuration window to pop up, it's far better to be able to just PRES BUTAN and the Conf window appears.

Also - with the advent of 64-bit versions, I've had to change how CL detects the game process. The original process name in Windows was EliteDangerous32.exe , and as you've probably guessed by now the 64 bit versions are EliteDangerous64.exe. Captain's Log was hard coded to look for the former. This version caters for all - even in the upcoming OSX version (which I will release Soon[tm] - honest!).

Lastly - all you needed to do was point CL towards the new ED Logs folder and it would have activated verbose logging for you

Regards o7

SnugglySocks · Dec 2, 2015

Yeah, so when you sift through all the parts where it is simply me not doing it right, you are left with one thing.

The config screen requires you to 'touch' both log and db fields in order to display the save button.

Genar-Hofoen · Dec 2, 2015

Mungler said:
Yeah, so when you sift through all the parts where it is simply me not doing it right, you are left with one thing.

The config screen requires you to 'touch' both log and db fields in order to display the save button.

Yes that's correct - It's basically the Initial Configuration Window being called back into action, including the code/logic behind it. It's just two things you need to do - set the Logs directory and set the data directory (even if it's the same location) - so I didn't think it would be so onerous to the end user.

If it's really that onerous, perhaps I should reconsider

Regards

SnugglySocks · Dec 2, 2015

Genar-Hofoen said:
Yes that's correct - It's basically the Initial Configuration Window being called back into action, including the code/logic behind it. It's just two things you need to do - set the Logs directory and set the data directory (even if it's the same location) - so I didn't think it would be so onerous to the end user.

If it's really that onerous, perhaps I should reconsider

Regards

I think you have, perhaps mercifully, forgotten that I am the guy who wanted sloth mode

Genar-Hofoen · Dec 15, 2015

Reminder for Updated E and ED:H ...

After updating ED and/or ED: H , ensure you run Captain's Log before running the game - that way, verbose netlogs will be activated.

Also make sure you have CL configured to use the correct logs directory for whichever version of the game you are running

The latest v1.2.1 released a week or so ago included a way of bringing the Configuration Window back up - via a button on the Database Manager - no more need to remove the captainslog.cfg file manually

Regards o7

Ziljan · Dec 15, 2015

This might sound like an odd request and feel free to say "oh hell no," but is there any way you can create an option for the GUI and text to have a red/black color scheme instead of the blue/black? I am a melatonin challenged insomniac and looking at blue light is like a caffeine buzz.

Genar-Hofoen · Dec 15, 2015

Ziljan said:
This might sound like an odd request and feel free to say "oh hell no," but is there any way you can create an option for the GUI and text to have a red/black color scheme instead of the blue/black? I am a melatonin challenged insomniac and looking at blue light is like a caffeine buzz.

Such a feature is on The List[tm]

Doodull · Dec 16, 2015

I'm having some trouble with this new version, please can someone help as I'm lost and cant play without it

I've included a screen shot of the error below:

seanjo · Dec 16, 2015

Doodull said:
I'm having some trouble with this new version, please can someone help as I'm lost and cant play without it
I've included a screen shot of the error below:
View attachment 86649

Same here, not showing systems I visit since I updated to version 2 and the Horizon update.

Genar-Hofoen · Dec 16, 2015

Doodull said:
I'm having some trouble with this new version, please can someone help as I'm lost and cant play without it
I've included a screen shot of the error below:
View attachment 86649

seanjo said:
Same here, not showing systems I visit since I updated to version 2 and the Horizon update.

I think I cricked my neck reading that error screen snapshot

Anyway...

If you're running Horizons, the directory has changed. For me it's C:\Users\Kev\AppData\Local\Frontier_Developments\Products\elite-dangerous-64\Logs

Try the following...

0) Exit the game and CL

1) In Windows Explorer (not Internet Explorer) go to %LOCALAPPDATA%\CaptainsLog and remove the file captainslog.cfg

2) Run Captain's Log - the Configuration Window will appear.

3) Configure Captain's Log as normal - set the Logs directory of the version of ED you are running, then set your CL DB directory.

4) Then start the game.

This should work - it does for me.

Hope that helps!

Regards o7

P.S. I'll try to make detection of the directories more of an automatic thing for the next release of CL, to try to alleviate this type of problem.