Let me explane to you what i found out last night. I installed on my Win-7 system a Orbiter 031217 build. I tested it with the Dragonfly ship that was included with it. Test Ok. I then added the BoP (the Bop that I first had working before the no see ship problem). I launched it and the BoP was sitting there on the runway or launchpad. The BoP wings move up and down just fine. Test ok.
I then tried a Orbiter 06xxxx build and after a good test launch with an included ship, I added that same BoP. that test failed. I could not see the BoP.
I then went back to the Orbiter-031217 build and added this addon:
-----------------------------------------------------------------------
Star Wars Universe
A star wars universe for orbiter. Includes :
Tatooine, Mustafar, Endor, Coruscant, Yavin, Geonosis, Hoth, Naboo, Dagobah, some moons (including yavin4). 3 spaceships: Kyle Wiegers's Xwing, a naboo royal ship and a very detailed Millennium Falcon (By Alexey Meerow and Chris Johnston)
-----------------------------------------------------------------------
I tried a test launch with the BoP and no see BoP. This SWU addon I supect is the culpret that crashed the BoP when I had it working on my Orbiter- 2010 system. I'm glad I made a back up of the O-031217 that had the BoP working fine. I only wish that I had made a bk-up of the O- 2010 that had a working BoP.
I will test out the new Bop that You have posted and reply back.
Thank's again for all the help from everyone here. DC...
---------- Post added at 07:57 PM ---------- Previous post was at 06:44 PM ----------
Just tried the repaired BoP file from above on my Win-7 Orbiter 2010 (an orbiter 2010 without any other addons other than all 3 of Vinka's Spacecraft dlls and OrbiterSound 4.0. Results = CTD both scenarios.
P.S. I use to have this CTD problem with some of Battlefields. The problem were allway's a screen resolution selection issue.