Dear All;

Im having some issues with the Diagnostic function. It keeps giving me warning about NUM LIGHTS is set less than 8 in the config. In my cfg they are set to 8. I am using FSX SE, WIn7 64bit.

Anyone here had any issues with this before? Any known solutions?

Many Thanks,

PS. Just noticed: It also tells me that my Texture Max load is 1024 or less; even though, its set to 2048.

Have you had a dual uninstall and removed the DVD version and reinstalled steam?  Or installed the steam beta at some point? 

 

It sounds like the fixer is looking at the wrong fsx.cfg file.

 

Provided the path is set correctly to FSX-SE then the fixer should deduce that its Steam that you are using.  

 

It then has two possibilities

 

a) its a dual install 

there will be a fsx directory under <your user>\appdata\roaming\microsoft\fsx  with the DVD edition fsx.cfg  in it

and  another directory <your user>\appdata\roaming\Microsoft\fsx-se with the FSX-SE  fsx.cfg.  called fsx_se.cfg

 

b) its FSX-SE only then there will be a directory

<your user>\appdata\roaming\Microsoft\fsx  with the fsx-se fsx.cfg in it. called fsx.cfg

 

As you can see the directory changes based on other things outside the fsx-se system itself.

 

So the algorithm it uses is prefer the fsx-se directory if it exists but if it does not exist then use the fsx directory.

 

I would guess that you have fsx-se using  the fsx config directory but also have an old fsx-se config directory

 

I understand that installing the beta alongside the standard steam version also created a confusement of fsx config directories.

Hello Steve;

No, I have completely removed the FSX legacy and then installed the steam version. In the beginning all worked good. I guess that the issues started after DTG pulled the new update. Perhaps? Or could have been after the DX10 update to the 2.9V. Sorry, not 100% sure.

The FSX Path is pointing to the correct location.

So what do I need to do now? Sorry, not that computer savvy as some might be.

In my APP Data/Roaming/.... I have two files one is FSX and the other one is FSX-SE.

Thanks for your help,

 

Best.  

 

Edit:

So I have two FSX files.

1. FSX

In it I have all of the usual FSX related options i.e. Controls, SimObjects..............

2. FSX SE

In that folder I have only 4 files.

DLL

DLL_xml.....

FSX_se (Like a config that consists out of 5 Entry's. Texture Max load is set to 1024....) Most likelz that's the config that the fixer is looking at.

Tidy

 

So what do I have to do to change, so that the fixer will look in the direct config file?

 

Many thank once again.

Ok which config directory are you editing to set NUM LIGHTS ?  I assume the fsx one - if so rename the fsx-se directory to OLDfsx-se  and see if the fixer is then using the correct directory.

 

NOTE: to anyone reading this thread - this is not general advice.

Renaming it fixed it.

I have renamed the FSX SE directory to Old FSX SE.

Thank you so much Steve.

ok, now we need to double check that FSX-SE is in fact using the fsx directory for its config. 

 

The best way is to edit the fsx.cfg and change something that is obvious in there  e.g

 

AIRCRAFT_SHADOWS in [GRAPHICS]

 

so assuming it is set to 1 (on) change it to zero (off)  - then check that it has changed fsx-se and when you run it that there is no aircraft shadow on the ground.

 

If this has no effect then fsx is probably wanting to use the FSX-SE directory - if this is the case check back here for instructions

Hello Steve;

Seems to work good.

 

Many many thanks for all your help.

that's great!

Hello Steve;

After renaming the config all still is working and looking good

I do; however, have another problem. Today I was trying to launch the Aerosoft Dublin configurator. Unfortunately, it doesn't open any longer. It gives me an error message that says it can not find the  FSX_SE config. Its looking for the config that we have renamed in order for the fixer to find the correct one. Is that something you could by any possibility assist with? Or is it better that I contact Aerosoft about this issue now?

Many Thanks as Always.

I think you need to contact them!   

 

You have one installation of FSX (SE) that is using the config in the FSX directory. 

 

Due to the history  of the dual installation in the past there are some traces left in your  system.  One of these was the FSX-SE directory which we have removed and so now the fixer is finding the correct directory.

 

Aerosoft are still trying to go to that (wrong) location - you need to find out what algorithm they use and what needs to be cleaned up. Restoring the FSX-SE directory wont really help as it isn't the config that your FSX is actually using

 

Uninstalling the airport and reinstalling might solve it but I cannot promise that - it depends how they decide which directory to use.

Thank you very much. I will contact them.

Best,