Can someone browse to their directory which contains effects.cfg?

 

C:\Users\All Users\Lockheed Martin\Prepar3D v3

 

And tell me if their file displays anything.  Mine is blank.  I think this is why none of my default cockpit lighting works.

Try deleting it Ryan and then restart the sim and close it again, it should put a new one in there that looks like this:

 

 

[Entry.0]
Title=Default Effects
Path=Effects
Required=True
Active=True

Yep that was missing, thanks!

Ok... you SHOULD NOT BE TOUCHING the files in All Users area. The sim should be taking care of that on it's own. The ProgramData are is where you should be changing files, and then the sim should update the files in All Users on it's own.

Didn't catch that Ed :blush:

Here's what I found on my system:

 

I modified .cfg files that were in the ProgramData area. After doing so, and I believe after running the sim, the entries were transferred to the files in the All Users area. I certainly didn't modify the files in the All Users area and yet they have the same updated entries I put in the other .cfg files.

On 10/26/2015 at 3:45 AM, WarpD said:

Ok... you SHOULD NOT BE TOUCHING the files in All Users area. The sim should be taking care of that on it's own. The ProgramData are is where you should be changing files, and then the sim should update the files in All Users on it's own.

Is it still valid in the current v4 iteration?

Thanks,

With v4 you shouldn't be touching the .cfg files at all.  There are command line options with Prepar3D to install items.

And what if I still need my own "user-created" package to work completely outside of Prepar3D v4 folder? Where, in which of the 2 say gauges or sounds .cfg files do I reference them to have my package working? Even knowing 'command line options' science you should know what goes where to work properly, should you not? Those .cfg files are still txt editable file, so txt-editing them properly shouldn't destroy anything in Prepar3D v4?

Thanks,

PS: Lorbi's AO is extremely helpful in most cases.

Edited December 9, 20178 yr by Dirk98

"Stay away from the config files", you're right. Whereas Lorbi's AO can do almost everything for user and it has its UI (vs. command line options).

Dirk.

The problem with relying on any method that directly modifies the config files is that you are assuming absolutely nothing regarding those files is going to change in the future.  You are assuming that their format will remain unchanged.  You are assuming their location will remain unchanged.  You are taking a risk/gamble that can result in issues in future sim releases.

The command line options are there and should be used before any other method.  If they don't work, then L-M needs to be made aware of it so that it can be addressed.  I know that everyone wants to do it the 'easy way', whatever that happens to be... it's human nature.  I strongly urge you chose to do it the 'right way'... whatever that happens to be.