Stewart Hobson

...as will many of us!

Thanks for the clarification, wolfko. I don't own any TE products, so I can't comment about autogen vegetation changing or not.

Truthfully, that's not how I understand how the TE scenery works. It's a once only snapshot of the area in question, dependent on when the photo was taken. That seems to be the feedback that I have read, anyway.

Robert, TE uses photoreal scenery, the regions use landclass scenery--two different display methods. TE scenery doesn't change with the seasons, the landclass regions do.

Hey, Rodger. I believe you have to go out and find those airstrips. There was at one time a google map or kmz file of their locations, but off hand I don't know where that is located on the Orbx site. Perhaps someone knows where to find it. Stew

Thanks, Nick. I had forgotten about the two extra parking spots--it's been awhile.

It appears to be for v5 only, per the product page information.

I take it you are not keen to trying my suggestion I posted above ^^^? If so, there doesn't appear to be any other solution.

There was a recent update to the Orbx Libraries. Perhaps that's the one you are referring to?

Thanks, Nick. Wasn't really sure of the proper place to post this. It's an unusual problem which I haven't encountered before when using SimStarter.

The file in question is this: FTX_VECTOR\FTX_VECTOR_APT\scenery\APT_LPPT.bgl. If this file is not turned "off", then when using SimStarterNG to start a flight at Lisbon, SimStarter does not list the correct starting positions, even though P3Dv4.5's starting positions are listed correctly, and I have "refreshed" the airports using SimStarter's airport refresh tool. Any comments from SimStarter users or perhaps an Orbx Central expert are welcome. Thanks. Stew

Thank you for the added information. It's a beautiful area up there in Idaho and your area of Boise. I enjoy flight simming to all those small airports in Idaho once in awhile. Cheers! Stew

My version was for FSX originally (in 2014), and I just ported it over to P3D. Running v4.5hf2 and it looks ok. The only difference I've noticed is that the areas between the taxiways and the runways, those areas where you saw the depressions, are not green in my version. That may be because P3D has assigned different textures to those areas. Anyway, the scenery works for me as is, so I'm going to leave it alone. There may be differences in the city of Boise itself, but I haven't checked those.

Interesting! I'm curious why my version of KBOI works as is, without a corrected AFCAD. How new or old is your version?

Is your KBOI installed above all Orbx products? It is the case with my installation and I don't see the "canyons" you are seeing. The fact that you do not have Vector installed is not an issue, since CRM uses its own data.

Thanks for the update, Chris. I know that's the case with many of us old farts!

Exactly so, Chris. Crash detection has never been accurately represented in either FSX or P3D, as far as I know. It has made no sense to me that some folks insist on keeping crash detection enabled because "it contributes to the reality of the sim", when, in fact, it does not.

There's this one:

What I and several other users of this airport have done is spawn on the runway and then use "slew" to move the airplane to where you want to spawn next time, then save the scenario. Any fixes that have been attempted in the past have been defeated by P3D in not recognizing the "old" parking spaces which were available in FSX.

Thanks for this valuable information, Louis. Cheers!

Ahh...never mind. This issue is mentioned in Ben's announcement regarding Orbx Central 4.0.10. Any and all changes will not be lost. Thanks!

I have previously run the auto configuration tool and subsequently have run the tool manually to correct those airports added after the auto config tool was run, and saved all the corrections to a profile. Will that profile be saved when the new Vector is installed, or will I have to run the auto AEC again, thus losing that profile which was saved previously?

There is a FreeMesh available--don't know the details, but several folks here use it and haven't had any issues. At any rate, NorCal has its own mesh, so I can't say what might be the problem. Also, it's not reasonable to suppose the four Orbx products you have mentioned are somehow in conflict with each other, so there is a conflict elsewhere, I would guess.

Thanks for the tip, Sherm. You are correct--these two spreadsheets are easily saved as pdf files. Cheers! Stew

FYI, the airport designation is correct in the release announcement, however. Stew