Hello Steve -

 

I just when through the process of upgrading the DX10fixer to 2.1. I backed up my previously edited version of dx10.ini in the same directory. When I uninstalled and re installed the fixer, my directory was empty and and I had to re-add all my fx exclusions. (shockwave and smoke stack effects).

 

Even with the exclusions in place in the file, my effects were still updated ( file date changed) when I ran the fixer. I had to replace them with a backup copy.

 

Did I put the entries in properly in the exclude list?  Is there a way to maintain the list when upgrading between version?

 

Thank you for such a great product!

 

Daniel

 

Here is what my DX10.ini file looks like.

[DX10SceneryFixer]

 

// Lights that we convert as part of the light package and which arenot then converted as effects

[Navlights]

fx_navred.fx=1

fx_navredh.fx=1

fx_navredm.fx=1

fx_navgre.fx=1

fx_navgreh.fx=1

fx_navgrem.fx=1

// These have no shine

fx_navwhi.fx=1

fx_navwhih.fx=1

// these have no shine

fx_strobe.fx=1

fx_strobeh.fx=1

// these have shines.

fx_beacon.fx=1

fx_beaconb.fx=1

fx_beaconh.fx=1

fx_vclight.fx=1

fx_vclighth.fx=1

 

 

// lights we leave alone

[Landing]

fx_landing.fx=1

 

[ExcludeEffects]

ballast.fx=1

fx_dx10shieldtest.fx=1

fx_dx10shield.fx=1

fx_dx10fieldtest.fx=1

fx_dx10field.fx=1

fx_shockwave_beacon.fx=1

fx_shockwave_beacon_fa18.fx=1

fx_shockwave_beacon_rotating_red.fx=1

fx_shockwave_beaconb.fx=1

fx_shockwave_beaconb_l.fx=1

fx_shockwave_beaconb_lowl.fx=1

fx_shockwave_beaconb_nl.fx=1

fx_shockwave_beaconh.fx=1

fx_shockwave_beaconh_l.fx=1

fx_shockwave_beaconh_lowl.fx=1

fx_shockwave_landing_light.fx=1

fx_shockwave_landing_light_747_lw.fx=1

fx_shockwave_landing_light_747_nose.fx=1

fx_shockwave_landing_light_747_rw.fx=1

fx_shockwave_landing_light_a321_nose.fx=1

fx_shockwave_landing_light_double.fx=1

fx_shockwave_landing_light_double_small.fx=1

fx_shockwave_landing_light_double_vsmall.fx=1

fx_shockwave_landing_light_light.fx=1

fx_shockwave_landing_light_light_l.fx=1

fx_shockwave_landing_light_light_sm.fx=1

fx_shockwave_landing_light_narrow.fx=1

fx_shockwave_landing_light_narrow_no_flare.fx=1

fx_shockwave_landing_light_no_flare.fx=1

fx_shockwave_landing_light_short.fx=1

fx_shockwave_landing_light_small.fx=1

fx_shockwave_landing_light_small_xenon.fx=1

fx_shockwave_landing_light_tail.fx=1

fx_shockwave_landing_light_tail_old.fx=1

fx_shockwave_navgre.fx=1

fx_shockwave_navgre_nl.fx=1

fx_shockwave_navred.fx=1

Cool_Tower_CtrlSteamLrg.fx=1

Cool_Tower_CtrlSteamMed.fx=1

Cool_Tower_CtrlSteamSml.fx=1

Cool_Tower_CtrlSteamXL.fx=1

Cool_Tower_CtrlSteamXXL.fx=1

Cool_Tower_SteamLrg.fx=1

Cool_Tower_SteamMed.fx=1

Cool_Tower_SteamSml.fx=1

Cool_Tower_SteamXL.fx=1

Cool_Tower_SteamXXL.fx=1

fsxpp_monardam_spray.fx=1

fsxpp_redlight.fx=1

PowerSmoke.fx=1

PowerSmokeFX.fx=1

PowerSmokeFXL.fx=1

PowerSmokeL.fx=1

 

Hi Daniel,

 

Sorry you have a good point there, I should provide a way or at least mention it in the manual. As to it not working I will need to check

 

 

I had to re-add all my fx exclusions. (shockwave and smoke stack effects).

 

Hey Daniel,

 

I'm curious:  Why do you have the Shockwave lights in your exclude list?

 

 

I'm curious:  Why do you have the Shockwave lights in your exclude list?

 

I use the Shockwave AI navigation lights on my Ultimate Traffic II airplanes. If I don't exclude them in the DX10 Fixer effects conversion process then the AI navigation lights at night are not visible at all.

 

I guess I don't need to convert all of them, but it's just easier that way. Not exactly sure why they disappear when ran through the converter but it's just one more small step in making DX10 and FSX better. 

 

-Daniel

Got it! Makes sense.

Hi Steve- will you please add a line on your pop up info box for the effects conversion for the number of user.excluded effects. I have ran the utility several times and it appears to ignore the exclude list.

 

Thanks again

Hi Steve- will you please add a line on your pop up info box for the effects conversion for the number of user.excluded effects. I have ran the utility several times and it appears to ignore the exclude list.

Which location are you editing the file in? I ask because there are (perhaps confusingly) two DX10.ini files.

 

AppData is for user specific settings involving shaders

 

ProgramData is for shared settings across all users.

 

Effects have to be shared as there is only one effects directory per system, and so its the c:\ProgramData\DX10SeneryFixer\DX10.ini file that you need to edit. You need to launch notepad as administrator to edit this DX10.ini.

 

Assuming that you are indeed editing the wrong one then I will add in some notes on this into the manual.

Hello Steve -

 

You are correct, I was editing the Appdata - dx10.ini, not the ProgramData - dx10.ini. I will apply my setting to the correct file and retest.

Thanks again!

Thanks, I will try and make it clearer in the manual!

Hi Steve -

 

I just uninstalled the DX10 fixer to update it to the new version 2.2. Unfortunately in doing so, it also deleted my updated dx10.ini for my exclusions along with the folder  in the ProgramData File. 

 

Any suggestions on how to maintain the custom exclude list between versions?

Thanks.

Daniel

It now excludes all shockwave lights by default so you just need to paste the 10 lines from the post above in this time I will try and remember to add them to saved profiles in 2.3