DOOLITTLE RAID - TASK FORCE 16 SCENERY

[gillesdubois 0]

I installed the Task Force 16 scenery and when I go to CV8 Airport which is the Hornet, my B25 is sit on top of a 'JETWAY' in the middle of the ocean. And the other carrier VN25 is the same, a "JETWAY". There is a battleship in the area and another carrier which I can see.Anyone has a solution for this problem ?RegardsGilles Duboishttp://forums.avsim.net/user_files/107254.jpg

[rambow 0]

Yeah, but can you take off from it? ;-)TF 16 Scenery is not a MAAM-SIM product, of course, but my guess is you have a conflict between it and some other installed scenery or utility. Try contacting the Virtual Navy developers to see if they have an answer to your peculiar dillema;- James Smith crashaz@hotmail.com- Bruce Baker bbtbmb@direcway.com And keep your eye open for Japanese catering trucks! :-)Bill Rambow MAAM-SIM - Rambow, Visser, Banting, Young, Womack, Sodja & Beaumonthttp://www.fssupport.com/maam_sim/maamsim_logo2.gif

[Guest SWA2873]

My installation did not do this and I think that Bill is correct in assuming there is aconflict with another texture. Remove the BGL files for the scenery from the folder in which you placed them and install them in a dedicated subdirectory in your flightsimulator9 directory. Then activate the scenery as you would normally for an add on package.Here is an example: C:Flightsim9(alt' 2002)AddonSceneryScenery*.bgl C:Flightsim9(alt' 2002AddonSceneryTexture*.* (For your texture files)Start flight sim open "SETTINGS" then "SCENERY LIBRARY". A dialogue box will appear. Select "ADD AREA" Use the browser that pops up to select the Scenery directory that the bgl file is installed in and then click on "OK". If there is a conflict this may resolve teh problem by designating which directory the scenery and textures are being read from.Hope this works for you.Sam

[gillesdubois 0]

THANK YOU SAMI usually make a separate folder for each of my Addon sceneries.I find this easier to maintain. In this case, by placing the *.bgl files directly into the 'scenery' folder and the textures directly into the 'texture' folder, it fixed the problemk.I don't understand why, but what the hech, it works.Thanks againRegardsGilles Dubois

[gillesdubois 0]

Thanks SamAs you can see on the nest reply, your suggestion did fix my problem.But now when I go to KSTL, St Lambert Intl at St Louis, for which I have an Addon scenery for that airport, I find the USS Hornet parked at one of the gates. I guess I found the culprit. KSTL scenery is the culprit. I have a choice to make. Either Task Force 16 or KSTL airport.ThanksRegardsGilles Dubois

[Guest SWA2873]

Your welcome Giles;I would try moving the KSTL scenery to a set of dedicated files like you did with the carrier task force and see if it fixes the problem before I made a decision about one or the other scenery having to go.Just a suggestion.Sam

[Guest IanP]

It sounds like someone has, remarkably amusingly, managed to assign the two items exactly the same object ID in FS. Amusingly, because that's one heck of a lot of numbers to get the same ones both times!!!If you check out the battle of Lago's FS Enhancer (sorry to plug another product in your forum, Bill, but it sounds like exactly the same issue), they assign each user their own individual range of object IDs to use when creating objects, to avoid exactly what appears to have happened here.Whoops? ;-)Ian P.

[Guest SWA2873]

I was thinking the same thing.I thought that perhaps by placing the scenery adn texture files in dedicated subdirecties perhaps the sim might read the textures for each scenery from their respective directories.Kind of a long shot but worth a try.Sam

[mirageiiiea 0]

I experienced this very same issue.  I was able to track down the problem to a conflict with Runway 12 library objects. As it turns out, the objects for 4 of the 6 ships in the task force have the same name (GUID) as assigned to several jetway objects from the Runway 12 library, and your simulator is drawing the jetway objects from the Runway 12 library instead.

I was able to fix this by decompiling the bgl files and assigning new IDs to the 4 conflicting ships.  I checked my new IDs versus the entire Runway 12 object library and the default FS2004 objects, and thankfully I have no conflicts now.

I recompiled the new bgl files and voila!  All 6 ships in the task force now appear properly.  The issue with the St Louis scenery would also be resolved since your scenery will not try to accidentally call upon the USS Hornet or some of the escorts in place of the jetways :-)

If there is anybody with this problem that is still using this scenery with FS2004, feel free to reach out to me for the corrected files.  If there is enough interest I can contact the authors to try to obtain authorization to release a patch to repair this issue.