February 4, 201214 yr I have been trying to by the process of elemenation to find out what scenery caused this to show up at Fly Tampa's Seattle scenery (FS9). Already check with Fly Tampa and George advised not there's but it is a test spot used by Microsoft SDK for developers to learn how to export models, thinks someone forgot to remove it.By bruceu at 2012-02-03thanksBruceU
February 4, 201214 yr There was a problem like that with FSDreamteam Zurich v2:http://www.fsdreamteam.com/forum/index.php?topic=5227.0If you have that scenery, then get the latest updates. Graeme Butler
February 4, 201214 yr That was it Graeme, there fix worked like a charm, much appreciate your help !!BruceU
February 4, 201214 yr Thats a little funny......"ground crew to tower, we have a jetway gone rogue, please call in all available resources to advance with caution, and secure the area"Sorry, im a little bored. Edited February 4, 201214 yr by flyinpilot212121 Intel I7 12700KF / 32 GB Ram-3600mhz / Windows 11 - 64 bit / NVIDIA GeForce RTX 3060TI / 32" Acer Monitor, Honeycomb alpha/bravo, CH rudder pedals, Tobii 5, Buttkicker, Logitech radio panel.
February 4, 201214 yr I know ;) Intel I7 12700KF / 32 GB Ram-3600mhz / Windows 11 - 64 bit / NVIDIA GeForce RTX 3060TI / 32" Acer Monitor, Honeycomb alpha/bravo, CH rudder pedals, Tobii 5, Buttkicker, Logitech radio panel.
February 4, 201214 yr Commercial Member Yep, every time you export a model from gmax an example placement .xml is created that places your new object at precisely that location at KSEA. You can then compile that to a temporary .bgl and fire up the sim for a quick look at your model. There have been numerous threads about odd objects showing up at rwy 34 at KSEA as a result, when scenery designers compile this temporary .bgl and then forget to remove it when packaging up the download. I've done it myself a couple times :smile:Jim
Create an account or sign in to comment