Flying Trees at LOWS!

STEPS TAKEN TO IDENTIFY AND RESOLVE THIS ISSUE

Some were unnecessary (4b, 4c and 7) but were included as part of my usual routine after running FTX Central 3 which ensures Black Marble operates optimally and without conflicts.

1. Migration Troubleshooter - All Regions Migrated Correctly. All Region Files Exist. All Files Valid.

2. Check Scenery.cfg (Layer numbers and Area.xxx MATCH - Last Area/Layer=268)

3. FTX_EU\FTX_EU_GES_05_scenery\ADE_FTX_GES_LOWS.bgl.OFF (Still present)

4. Run Lorby-SI Addon Organizer for Prepar3D v1.22

a) FTX_NA_!OLC_LIGHTS  (Disabled for Black Marble Lights - usually remains disabled)

b) ORBX!OPENLC_!EUROPE_LIGHTS    (Disabled for Black Marble Lights)
c) ORBX!OPENLC_!SAMERICA_LIGHTS    (Disabled for Black Marble Lights)

SAVED and Closed.

5. Check Scenery.cfg (Layer and Area.xxx MISMATCH)

MISMATCH starts at Area.114:

[Area.113]
Title=Africa
Local=Scenery\AFRI
Layer=113
Active=TRUE
Required=FALSE

[Area.114]
Title=Asia
Local=Scenery\ASIA
Layer=115
Active=TRUE
Required=FALSE

6. Migration Troubleshooter - All Regions Migrated Correctly. All Region Files Exist. All Files Valid.

7. Installed my Black Marble modded terrain.cfg overwriting the original.

8. Migration Troubleshooter - All Regions Migrated Correctly. All Region Files Exist. All Files Valid.

9. Run P3D v4.1

10. Check content file listing in SceneryIndexes_x64

Filelist00256.dat
Filelist00257.dat
Filelist00258.dat
           <---- 259 (?)
Filelist00260.dat
Filelist00261.dat
Filelist00262.dat
Filelist00263.dat
Filelist00264.dat
Filelist00265.dat
FilelistIndex.dat

11. Load Default Scenario at KVPS - Loads correctly (all scenery elements).

12. Check Scenery Library - 269 Entries

Asia = 155

MyTrafficScenery = 156 (tick greyed out because installed as an Add-on (MyTraffic6). N.B. No entry in Scenery.cfg for MyTrafficScenery)

Africa = 157

13. Confirm LIGHTS entries Disabled (see 4. above).

14. Exit P3D v4.1

15. Re-enable FTX_EU\FTX_EU_GES_05_scenery\ADE_FTX_GES_LOWS.bgl

16. Run P3D v4.1

15. Check Scenery.cfg (Same as 5.)

[Area.128]
Title=MyTraffic
Local=D:\MyTraffic Professional\MyTraffic
Layer=129
Active=TRUE
Required=FALSE

Last Entry:

[Area.268]
Title=CDSBMV
Local=D:\Lockheed Martin\Prepar3D v4\CDS\CDSBMV
Layer=269
Active=TRUE
Required=FALSE

16. Check content file listing in SceneryIndexes_x64 (Unchanged - Same as 10.)

17. Migration Troubleshooter - All Regions Migrated Correctly. All Region Files Exist. All Files Valid.

18. Run P3D v4.1 and Load Default Scenario at KVPS - Loads correctly (all scenery elements).

19. Load Digital Design's Saltzburg (LOWS) - No 'floating trees'

20. Exit P3D v4.1

21. Migration Troubleshooter - All Regions Migrated Correctly. All Region Files Exist. All Files Valid.

22. Run P3d v4.1 and Load Default Scenario at KVPS - Loads correctly (all scenery elements).

23. Load Digital Design's Saltzburg (LOWS) - NO 'floating trees'!

24. Exit P3D v4.1

25. Migration Troubleshooter - All Regions Migrated Correctly. All Region Files Exist. All Files Valid.

26. Re-enable My Traffic Professional\My Traffic\scenery\BR2_LOWS.BGL

27. Run P3d v4.1 and Load Default Scenario at KVPS - Loads correctly (all scenery elements).

28. Load Digital Design's Saltzburg (LOWS) - 'Prepar3D has stopped working...etc'

29. System Restart

30. Migration Troubleshooter - All Regions Migrated Correctly. All Region Files Exist. All Files Valid.

31. Run P3d v4.1 and Load Default Scenario at KVPS - Loads correctly (all scenery elements).

32. Load Digital Design's Saltzburg (LOWS) - NO 'floating trees'!

33. Exit P3D v4.1

34. Migration Troubleshooter - All Regions Migrated Correctly. All Region Files Exist. All Files Valid.

So, it would appear that the failed migration of my unified lclookup was indeed the culprit. 16 Regions had missing files and those regions all had to be reinstalled. On the plus side I found that it became unnecessary to disable ADE_FTX_GES_LOWS.bgl and BR2_LOWS.BGL and explains why others who were good enough to contribute to this thread did not have the problem. Somewhat frustratingly, I am left with the mystery as to why this happened in the first place. Looks like I/we may need to run the ORBX Migration Troubleshooter tool periodically to confirm all is well with our ORBX Regional installations.

Mike