Elite: Dangerous PvE - Mobius

Posted: **Sat Aug 01, 2015 8:31 pm**

de Carabas wrote:
BlueDrache wrote:It may be because of the game and logs are in the (x86) folder? IDK, it only happens on startup of the SS utility, but like I said, I can click continue and soldier on.

Ah! So, when exactly does it throw the error? As soon as it starts, when you click enable, or the first screenshot capture?

Enable.

Posted: **Sat Aug 01, 2015 9:17 pm**

With you. Hence your thought about it being the log reading as that's the first thing it does.

Odd, given it does then get the system name when you grab a screenshot, so must be OK to access the file at that point. I'll do some testing in that area in the morning once I recover from this evenings real ales and stinking bishop cheese.....

Posted: **Sat Aug 01, 2015 11:07 pm**

*laughs* ... enjoy your rest ... I'm about to get a serving of each on my own.

Posted: **Sun Aug 02, 2015 6:29 am**

BlueDrache - can you try this one? https://dl.dropboxusercontent.com/u/31232647/SSChanger_test.zip

It should give us a clue as to what's throwing the error. I can then sort that in a 'proper' version.

Posted: **Sun Aug 02, 2015 2:00 pm**

Extracted the zip to the desktop and double clicked the .EXE

On running, first thing was an error with a blue border.

"To run this application you must first install one of the following
versions of the .NET framework:
v4.0.3xxx"

The window disappeared before I could finish typing out the error ... but it was a notice from my Avast AV installation and not a Windows system modal. The window disappeared and the SSChanger main window came up.

In this test version:

Output type .BMP is greyed out until I select the (hr) format. (I understand why, having coded a few things myself)
Clicked "Enable" and it created a temp.log on the desktop and ran just fine.
It also found my leftover log from last night. Whups ... forgot to delete that. (After uploading my netlog for my flight recorder on INARA, I delete them.)

Started the game.

First screenshot with the old log worked fine. It found it, renamed it, and saved it as a .PNG SYNUEFAI CS-H D11-60
Jumped to a new system, since the game creates a new log file for each session (on my system)
Second screenshot was renamed with the old system name. Should have been named SYNUEFAI UM-Z B47-0

Output window:

► Show Spoiler

"An idiot proof program always forgets to take into account the ingenuity of idiots." ~ Paraphrased from Gene Brown

Posted: **Sun Aug 02, 2015 2:16 pm**

BlueDrache wrote:Extracted the zip to the desktop and double clicked the .EXE

On running, first thing was an error with a blue border.

"To run this application you must first install one of the following
versions of the .NET framework:
v4.0.3xxx"

Do you have the latest .NET Framework installed?

If not, download .NET Framework 4.5.2 install it and reboot. It contains all the previous .NET Framework versions as far as 2.0

If installed, there's an .NET Framework Repair Tool for it.

Posted: **Sun Aug 02, 2015 4:05 pm**

Boozeman wrote:Do you have the latest .NET Framework installed?
If installed, there's an .NET Framework Repair Tool for it.

yes, and yes. Installed, and "fixed". Same odd issue occasionally.

Posted: **Sun Aug 02, 2015 4:33 pm**

Wow BlueDrache, you really are individual

So the first bit with the .net framework I'm going to hope isn't me.

The bit with it not finding the new system name. From the output window text it appears it's not picking up that a new log file has been created. Can you confirm one was there?

Overall it does 'feel' like there's some funny permissions thing going on. I'll keep looking.

Posted: **Sun Aug 02, 2015 4:56 pm**

Confirmed ... I reuploaded the old log and the new log from the current session.

Posted: **Sun Aug 02, 2015 7:00 pm**

I'm struggling to find a problem.
In the output below I started the application with an empty log directory - hence the "no log files found". I then started the game up and it detected a new log file was created. Screenshot taken and I confirmed it found the right system and added the correct name to the output file (Pyramio SM-D c15-14).
I then jumped to another system and took another shot and it identified Pyramio OF-F b31-13 fine.
I disabled the screenshot changer with the game still logged in. Then re-enabled again and could see it re-found the current log file and system.
I jumped and again it found the right system (Pyramio TL-D b32-15). Any other scenarios to try?

► Show Spoiler

Elite: Dangerous PvE - Mobius

Screen Shot Changer

Re: Screen Shot Changer

Re: Screen Shot Changer

Re: Screen Shot Changer

Re: Screen Shot Changer

Re: Screen Shot Changer

Re: Screen Shot Changer

Re: Screen Shot Changer

Re: Screen Shot Changer

Re: Screen Shot Changer

Re: Screen Shot Changer