Release Screen Shot Changer

Glad it's working but not sure how that relates to your problem! Either way that's another thing that I've fixed in 1.2.1 - if the values are negative I will reset them.
1.2.1 is coming soon, just trying to sort out auto running the game from the launcher.

I had an old version that didn't work so I updated to 1.2.0 and then the settings window co=ordinates where off the screen so I couldn't sort my settings out to the right paths. fixed now and appears to be working just fine with a quick test I did.
 
Last edited:
I had an old version that didn't work so I updated to 1.2.0 and then the settings window co=ordinates where off the screen so I couldn't sort my settings out to the right paths. fixed now and appears to be working just fine with a quick test I did.
Ah ha! I understand now :)
 
Will be downloading this tool for my next expedition into the (getting less so) great unknown. Should be heading out on the Friday the 1st. Will be extra nice knowing I'll have nicely organised snapshots of my travels.

Keep it up Cmdr ó7
 
Done it! Version 1.2.0 is available now and it has an option to start up the ED launcher.

Hi, after upgrading to 1.2.0 I found I had a problem with the settings.
I copied the new SSChanger.exe into the directory I was running 1.1.9 from and when I ran it and set the directories. I got an un-handled exception when I clicked the check button for verbose.

SSChangerException.png

I then ran SSChanger as Admin and the error went. Running SSChanger as a user after that everything was fine. I could change things and they were saved. :)
(BTW I am running SSChanger from my F drive.)

One other thing, my network settings are in AppConfigLocal.xml
I am running Elite Horizons and elite-dangerous-64
 
Found an intermittent error with version 1.2.0

I'm running Windows 10 and using Steam screenshots. Sometimes everything works perfectly, and sometimes SSChanger fails to notice when new screenshots show up in the folder. If I start and stop a few times, open and close settings, and then start again... it suddenly starts working. Then it works for the rest of the session.

Is there any data I can give you that would help you figure this out?

Lelna
 
Last edited:
Hi, after upgrading to 1.2.0 I found I had a problem with the settings.
I copied the new SSChanger.exe into the directory I was running 1.1.9 from and when I ran it and set the directories. I got an un-handled exception when I clicked the check button for verbose.

Sorry SMcA - I have no idea why I sometimes don't get notifications of posts on this thread so I didn't see this posting. I'll look into this later. No initial ideas why you had the issue.

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

Found an intermittent error with version 1.2.0

I'm running Windows 10 and using Steam screenshots. Sometimes everything works perfectly, and sometimes SSChanger fails to notice when new screenshots show up in the folder. If I start and stop a few times, open and close settings, and then start again... it suddenly starts working. Then it works for the rest of the session.

Is there any data I can give you that would help you figure this out?

Lelna
Well, like any good developer my initial response is "please upgrade to the current version" :) Grab 1.2.1 and see if that's the same.
If it is then can you let me know the paths you are using for where the images arrive in? Also it would be good to get the output text from the app when you notice this happening (it might have some messages about trying to access the file and failing etc.
 
....

One other thing, my network settings are in AppConfigLocal.xml
I am running Elite Horizons and elite-dangerous-64
SMcA, it just occured that if you are using AppConfigLocal.xml then don't bother setting the option to update the config. AppConfigLocal is intended to avoid the need to update the AppConfig.xml as it's settings persist across upgrades. So if you have set verbose in there then you don't need my app to look for it.
 
Does not work.

Hi Voz

It is not working for me as well,

X:\Frontier\EDLaunch\Products\elite-dangerous-64\Logs\netLog

, the SSchanger start when windows start but ED launcher does not start
 
Last edited:
Hi Voz

It is not working for me as well,

X:\Frontier\EDLaunch\Products\elite-dangerous-64\Logs\netLog

, the SSchanger start when windows start but ED launcher does not start

Where have you specified that path? Logs path should be X:\Frontier\EDLaunch\Products\elite-dangerous-64\Logs\
 
Sorry SMcA - I have no idea why I sometimes don't get notifications of posts on this thread so I didn't see this posting. I'll look into this later. No initial ideas why you had the issue.

No problems. It only happened once and it's a couple of versions ago.
 
I have specified that path to d:\Frontier\EDLaunch\Products\elite-dangerous-64\Logs\


Here's a few of the relevant lines from the code
Code:
Dim starti As Integer = My.Settings.logpath.IndexOf("Products", 1)
Dim launchPath As String = Left(My.Settings.logpath, starti) & "EDLaunch.exe"
...
Process.Start(launchPath)

So, what I do is to take the path specified for the logs, take away anything from the start of 'Products' and add the EDLaunch.exe on. Then run that full path to the .exe

This bit hasn't changed in the last version and I thought this was working ok for you before John? Can you confirm what the SSC log is saying is happening?
 
Here's a few of the relevant lines from the code
Code:
Dim starti As Integer = My.Settings.logpath.IndexOf("Products", 1)
Dim launchPath As String = Left(My.Settings.logpath, starti) & "EDLaunch.exe"
...
Process.Start(launchPath)

So, what I do is to take the path specified for the logs, take away anything from the start of 'Products' and add the EDLaunch.exe on. Then run that full path to the .exe

This bit hasn't changed in the last version and I thought this was working ok for you before John? Can you confirm what the SSC log is saying is happening?





Hi John,,

the real problem is that SSchanger does not start the ED launcher , and when I go to setting it is a default meaning I have to do the path again and checked the option what I want and then pressed start button,and SSchanger can make a screenshoot and converted to png, not sure If I am the only one who has this issue.



here is the log, after I change the setting.


2/3/2016 3:43:33 PM - Detected that Elite: Dangerous 64bit is running.
2/3/2016 3:43:33 PM - Ready to start
2/3/2016 3:43:33 PM - Auto Enabling.
2/3/2016 3:43:33 PM - Watching for new images at C:\Users\John Prepare3D\Pictures\Frontier Developments\Elite Dangerous
2/3/2016 3:43:33 PM - Logfile: D:\Frontier\EDLaunch\Products\elite-dangerous-64\Logs\netLog.160203152458.01.log
2/3/2016 3:43:33 PM - No system found in logfile. Is Verbose logging enabled? Have a look in Help.
2/3/2016 3:43:33 PM - No system found so not minimizing.
2/3/2016 3:43:33 PM - ED Launcher is already running
 
Last edited:
It only tries to run the launcher when it first starts up. So changing the setting and then enabling the SSC will not make it Launch. You need to test by closing the SSC down and re-running it - then post the log please.
 
Yes I know that. And I did close SSC and re-running it and changing the setting . It works indeed. But when I log off and log in . The SSC start but ED launcher not. I will send you the log file.
 
Hi John

it is surprised, I start my computer and it works, finally, I did not change anything, so here is the log fiel

2/3/2016 5:31:04 PM - Detected that Elite: Dangerous is not running.
2/3/2016 5:31:04 PM - Ready to start
2/3/2016 5:31:04 PM - Auto Enabling.
2/3/2016 5:31:04 PM - Watching for new images at C:\Users\John Prepare3D\Pictures\Frontier Developments\Elite Dangerous
2/3/2016 5:31:04 PM - Logfile: D:\Frontier\EDLaunch\Products\elite-dangerous-64\Logs\netLog.160203172949.01.log
2/3/2016 5:31:04 PM - No system found in logfile. Is Verbose logging enabled? Have a look in Help.
2/3/2016 5:31:04 PM - No system found so not minimizing.
2/3/2016 5:31:05 PM - Starting ED Launcher
2/3/2016 5:31:05 PM - ED Launcher starting



I have another question or request, if it is possible, that the SSC starts minimized at taskbar.
 
BUG REPORT:

Program worked flawlessly until I set (see below)

I experience problems with enabling "Start ED launcher"
Upon setting this checkbox and restarting, all I get is a SSChanger tasktray icon.
I cannot maximise it, it does not start Elite Horizons and it does not rename screenshots.

ENVIRONMENT:

Win7 all up to date
Elite Horizons 2.0.05
SSChanger 1.2.1

The only way to stop SSchanger, in this configuration, is via taskmananger.

No Outputlog.txt file is created at all when this happens.



Temporary solution:

To clear the symptom (and all settings), the data in C:\Users\USERNAME\AppData\Local\SSChanger needs to be deleted.
 
2/3/2016 5:31:04 PM - No system found in logfile. Is Verbose logging enabled? Have a look in Help.
2/3/2016 5:31:04 PM - No system found so not minimizing.
.......

I have another question or request, if it is possible, that the SSC starts minimized at taskbar.
Glad it's working. That bit from the log that I've left is where it looks to minimise. It will if everything looks good. In this case it didn't find a system in the log (which can happen if the last start of the EDLauncher then didn't lead to a full login to game). If it had found a system it should have then minimised.

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

BUG REPORT:

Program worked flawlessly until I set (see below)

I experience problems with enabling "Start ED launcher"
Upon setting this checkbox and restarting, all I get is a SSChanger tasktray icon.
I cannot maximise it, it does not start Elite Horizons and it does not rename screenshots.

ENVIRONMENT:

Win7 all up to date
Elite Horizons 2.0.05
SSChanger 1.2.1

The only way to stop SSchanger, in this configuration, is via taskmananger.

No Outputlog.txt file is created at all when this happens.



Temporary solution:

To clear the symptom (and all settings), the data in C:\Users\USERNAME\AppData\Local\SSChanger needs to be deleted.

That's very odd :(
Can you confirm the path that you have the game installed into? Anything interesting in where you installed it?
What might really help is - can you force this to happen again and then send me the xml file in that 'local' folder? Something is clearly getting set that is wrong somehow.
 
Game is in default directory:
C:\Users\USERNAME\AppData\Local\Frontier_Developments\Products\elite-dangerous-64

If the checkbox for "Start ED launcher" is ticked this behaviour is consistent.

"Run default game" is NOT checked. (Have tried both options)


user.config
Code:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <configSections>
        <sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
            <section name="SSChanger.My.MySettings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
        </sectionGroup>
    </configSections>
    <userSettings>
        <SSChanger.My.MySettings>
            <setting name="Usedate" serializeAs="String">
                <value>current</value>
            </setting>
            <setting name="VideoDelimiter" serializeAs="String">
                <value />
            </setting>
            <setting name="logpath" serializeAs="String">
                <value>C:\Users\USERNAME\AppData\Local\Frontier_Developments\Products\elite-dangerous-64\Logs</value>
            </setting>
            <setting name="configpath" serializeAs="String">
                <value>C:\Users\USERNAME\AppData\Local\Frontier_Developments\Products\elite-dangerous-64</value>
            </setting>
            <setting name="sourcetype" serializeAs="String">
                <value>bmp</value>
            </setting>
            <setting name="videosavepath" serializeAs="String">
                <value>C:\Users\USERNAME\Pictures</value>
            </setting>
            <setting name="delete" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="ScreenShotDelimiter" serializeAs="String">
                <value />
            </setting>
            <setting name="savepath" serializeAs="String">
                <value>C:\Users\USERNAME\Pictures\Frontier Developments\Screenshots</value>
            </setting>
            <setting name="VideoString" serializeAs="String">
                <value>%s %M_%d_%Y_%H_%k</value>
            </setting>
            <setting name="ShouldUpgrade" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="launchElite" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="deletevideo" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="imagepath" serializeAs="String">
                <value>C:\Users\USERNAME\Pictures\Frontier Developments\Elite Dangerous</value>
            </setting>
            <setting name="ScreenShotString" serializeAs="String">
                <value>%s %M_%d_%Y_%H_%k</value>
            </setting>
            <setting name="sourcetypeV" serializeAs="String">
                <value>avi</value>
            </setting>
            <setting name="videopath" serializeAs="String">
                <value>C:\Users\USERNAME\Pictures</value>
            </setting>
            <setting name="savetype" serializeAs="String">
                <value>jpg</value>
            </setting>
            <setting name="UsedateV" serializeAs="String">
                <value>current</value>
            </setting>
            <setting name="verbose" serializeAs="String">
                <value>True</value>
            </setting>
        </SSChanger.My.MySettings>
    </userSettings>
</configuration>


Removing the code below from user.config allows the program to function again.
Code:
            <setting name="launchElite" serializeAs="String">
                <value>True</value>
            </setting>
 
BUG:

If you set the verbose log directory and immediately click the "check" button the application still thinks that the default C:\Windows is focused, causing an application crash.


WORKAROUND:

Select verbose folder, then exit application and restart. Then click "check"
 
Last edited:
Back
Top Bottom