by toprob » Sun Jul 19, 2015 10:42 pm
Hi Mat
Woodbourne is tricky, as the normal way of getting a non-FSX-compatible airport working is to just disable all the FTX elements for that airport, but the problem with Woodbourne is that the FTX elevation is just so different from the default. So I've just had a look at it, and tried going the other way, turning off all the Godzone elevation files, leaving the FTX elevation files, and turning off the FTX objects and fences.
This kind of works, but there is far too much flickering of the ground polys, simply because I've had to disable the Godzone flatten. So I can't get it to work properly just by disabling files, it would need a new flatten as well.
HOWEVER this is kinda academic, as it doesn't explain why you wouldn't have all the Godzone scenery showing. Normally I'd put this down to scenery priority -- a FTX exclusion with higher priority -- but if you have checked the priority and set it properly using FTX Central Insertion Point then this shouldn't happen. It would be worth noting, though, that you should check the priority of Real NZ Marlborough, if it has been activated for a while it might be lower in the library than it should be, so it might be worthwhile bringing it up to the top of the list.
I really don't have any immediate plans to make Woodbourne compatible, as it just isn't worthwhile -- there is almost no interest in these older airports amongst FTX users in general, so I wouldn't recoup the cost of the time it would take to fix it.
However -- another however, not the same however -- Doug Cunliffe has been working on a new photoscenery for Marlborough, and I've promised to tweak these old airports for that, which would be a good time to tweak the compatibility. I don't know how long this will take, I am not really in a position to work on it at the moment.
If you can get the Godzone buildings etc to show, then I can run through some steps to make the airport 85% workable.