OZx “Complete” install location in FSX
You’re on the right track. The short version is: don’t drop any of these into the core FSX folder tree if you can avoid it. Treat them like normal add-on sceneries and keep them together in one dedicated folder, then add them via the FSX Scenery Library.
Recommended folder layout (keeps things clean)
Pick a location outside the FSX install (helps avoid permission/UAC weirdness). Example:
C:\FSX_Addons\OZx\
Inside that, keep each package as its own scenery “area” folder, like:
...\OZx_AUS_v3.0\scenery\ and ...\OZx_AUS_v3.0\texture\
...\OZx_AUS_v3.1\scenery\ / texture\
- ...and so on
...\OZx_NA_v1.01\scenery\ / texture\
...\OZx_LIB_v1.2\scenery\ / texture\
If the download already contains the scenery/texture subfolders, you’re basically just placing the whole folder(s) somewhere sensible.
Where to “install” them
Install them by adding them in FSX:
- Start FSX
- Settings -> Scenery Library -> Add Area
- Browse to the folder for the package you’re adding (example:
...\OZx_AUS_v3.0)
- Click OK, let FSX rebuild the scenery index
Do that for each OZx package you’re using.
About the “install between v3.4 and v3.5” note
That’s just telling you the order to apply the updates / additions. It doesn’t mean they go in a special location.
So you’d do it like this:
- Add/enable OZx_AUS up through v3.4 (however the package is structured on your end)
- Add/enable OZx_NA_v1.01 (as its own scenery area folder, same method)
- Add/enable OZx_LIB_v1.2 (same)
- Then add/enable OZx_AUS_v3.5
Scenery Library layering (important)
Typically you want libraries below the sceneries that use them. So in Scenery Library priority terms:
- OZx_AUS entries (higher priority)
- OZx_NA (if it’s actual scenery coverage, it can sit with the other OZx sceneries)
- OZx_LIB (lower than the OZx sceneries so it feeds objects/textures to them)
FSX’s UI can be a little confusing because “higher up” in the list = higher priority. If things are missing (objects, buildings, etc.), the first thing I check is that the library layer is present and not sitting above everything else in a way that causes confusion.
Two quick checks before you commit
- Each area you add should contain a
scenery folder (and usually texture). If you’re accidentally adding one level too high/low, FSX will accept it but nothing shows up.
- Make sure you didn’t end up with double-nested folders like:
...\OZx_AUS_v3.5\OZx_AUS_v3.5\scenery
If you did, move the inner folder contents up one level.
A couple questions so I don’t steer you wrong
- Which FSX are you on: boxed (SP2/Acceleration) or Steam Edition?
- When you extracted OZx_Complete, do the AUS packages come as full “standalone” scenery folders, or are they intended to overwrite/merge into a single existing
OZx_AUS folder? (A quick look at the folder names you see after extraction will tell us.)
- Any readme/install notes included in the download (especially about whether v3.x are cumulative or incremental)?
Answer those and (if needed) I can tell you the cleanest exact order and how many Scenery Library entries you should end up with.