14 minutes ago, Alvega said:

And the screenshot V1ROTA7E posted seems to have the gamma increased with other filters (Reshade or Nvidia) because the values you say this is using looked better than that  here when I tested them before (not that colorful). 

I’m using the above values, just using an HDR monitor, so the contrast is way up in the screenshot. Just the way game bar interprets the shot and outputs it into a png. 

4 minutes ago, turbomax said:

sure. the Drunq approach has the extra advantage " it prevents the patch from being overwritten or the game breaking with updates and offers a simpler installation and removal process.". but perhaps Asobo has this already in their next update anyway.

Yep, but we don't know for sure if there will be any problem with updates because we didn't have one yet. probably the update will just overwrite the exe and we have to edit it again.

1 hour ago, Alvega said:

probably the update will just overwrite the exe and we have to edit it again.

absolutely not, that is the whole purpose of Drunq's approach via an .asi script. he doesn't modify the Flightsimulator.exe file hence doesn't care if/when/how it may get updated. his .asi script searches for the original (over saturated orange) Asobo sky color values in memory (instead of in the Flightsimulator.exe file) once MSFS has been loaded and then changes them on the proverbial "fly".

Edited October 8, 20232 yr by turbomax

Just now, turbomax said:

absolutely not, that is the whole purpose of Drunq's approach. he doesn't modify the Flightsimulator.exe file hence doesn't care if/when/how it may get updated. his code searches for the original (over saturated orange) Asobo sky color values in memory (instead of in the Flightsimulator.exe file) once MSFS has been loaded and then changes them on the proverbial "fly". at least this is how I interpret his short description.

Yeah, I understand how it works. I was talking about what an update could cause if using the manual method, not Drunq's.

2 hours ago, kiwikat said:

As edited above, I do not have the default installation path.

then you must have chosen a different path, perhaps this might help:

https://parallel42.com/blogs/wiki/converting-my-sim-install-from-legacy-to-modern

Edited October 8, 20232 yr by turbomax

1 minute ago, turbomax said:

then you must have chosen a different path, which I have no idea. perhaps this might help:

https://parallel42.com/blogs/wiki/converting-my-sim-install-from-legacy-to-modern

I put it in the folder where the exe is like you said- I wasn't being sarcastic, thank you, if that is indeed where it is supposed to go.

1 hour ago, kiwikat said:

I put it in the folder where the exe is

open the xbox app, select at the left side MSFS and then at the right pane the (third option after the green play button ....)

Choose manage and at the popup window choose files then browse to the folder Microsoft Flight Simulator\Content

let us know if that worked, otherwise you could go the manual route like we all did before, provided your Flightsim.exe is already un-encrypted. otherwise follow the steps earlier in this thread to remove encryption:

https://github.com/jet2code/arpc-injector/issues/1

the beauty of Drunq's approach: because it doesn't touch the .EXE file, any potential encryption is no longer an issue since he modifies the 3 sky color variables in unprotected memory instead.

Edited October 8, 20232 yr by turbomax

4 hours ago, turbomax said:

they are in his source code. but as "we agreed" before, "we" preferred these values with less green tint: (0,00508 , 0,00318 , 0,0) copyright MortThe2nd, 😊,

best if the Drunk could provide a 2nd version for those who prefer the slightly blu-er sky.

I'll add an optional configuration file where the values can be changed. 

4 hours ago, Alvega said:

Yep, but we don't know for sure if there will be any problem with updates because we didn't have one yet. probably the update will just overwrite the exe and we have to edit it again.

I don't know, some games might have weird integrity checks which could cause issues. But it will most likely just overwrite the .exe.

Also I'll improve the instructions a bit so there is no confusion where to drop these files.

I found this easy to do.  I was confused at first because I downloaded the wrong zip (source files without the .dll ), but once I sorted myself out it took seconds and it works great!

Sincere thanks @Drunq.  Best sky colours ever.  I will test the other set of colours when the optional config file is ready.

Edited October 8, 20232 yr by bobcat999

1 hour ago, Drunq said:

I'll add an optional configuration file where the values can be changed. 

great and thanks for your contribution! this is a much easier procedure and would help all those with encrypted .EXE versions.

I wonder what would happen if someone had applied the hack already before, using some other color values and wants to run your method again. I assume it wouldn't work because you are parsing the .EXE for the 3 original values?

your approach is also very popular with other UWP games, like GTA V.

"some games might have weird integrity checks which could cause issues."

the current version of MSFS obviously doesn't, otherwise these hacks wouldn't work.

 perhaps you could briefly describe your method, so people don't have to worry about "overwriting" some original memory. 😊

Edited October 8, 20232 yr by turbomax

I just did a dusk flight, and a dawn flight with light clouds.  Amazing!  Looks real now without the overdone orange and purple.  Looks absolutely beautiful.  I am hoping it will look even better when we can modify to the other parameters.

I don't actually see much green on this original setting, but I think it is probably due to my monitor settings.

Anyway, this saves messing with the files, as I am still on the older 'encrypted' installation, so it is a very clever and useful solution.

Edited October 8, 20232 yr by bobcat999

I'm excited by this as it seems like a simple drag & drop, something a complete dinosaur like me can handle. Thanks to Drunq for doing this.

Just to confirm - my exe is not in this spot (C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe), it's on my D drive. Do I drop these files onto the exe or is there a folder in the G drive I need to specifically drop them to? 

Thanks in advance to anyone who knows what I'm talking about!

 

edit: my G drive path looks like this - D:/XboxGames/MicrosoftFlightSimulator/Content

do I just drop in the content folder?

Edited October 8, 20232 yr by El Diablito

somehow I think as soon as clouds come into play, sorry .... into simulation 😊, they get still too colorful with these new ARPC modifications? that would be something for Asobo I guess.

Edited October 8, 20232 yr by turbomax

2 minutes ago, El Diablito said:

I'm excited by this as it seems like a simple drag & drop, something a complete dinosaur like me can handle.

Same here... Now I should only get the ownership of my WindowsApps folder where the exe file lives... One question though, if one wants to revert back, is it only needed to delete those two files? 

6 minutes ago, Virtpilot said:

Now I should only get the ownership of my WindowsApps folder where the exe file lives

Yeah I got stuck there before when looking at doing the older fix but I found the exe was in the XboxGames folder below it. Unless I'm totally wrong??

edit: sorry, you meant in your C drive, as you were. It's locked for me in both drives anyway.

Edited October 8, 20232 yr by El Diablito