Products Support > Honolulu FSX/P3D
Jet Bridges not moving in Honolulu - but working in Lihue
bjratchf:
Umberto, I reinstalled today and double checked that the PHNL-HonoluluIntl.bgl file was marked "off"- and that MegaScenery is below all of my FSDT entries in the scenery library. Something is still conflicting- perhaps it is GSX or a COUATL problem? Would there be a fix to make scenery not pop in and out, and force jetways to be displayed ALL of the time? And, do you have any other ideas about what could be conflicting?
virtuali:
--- Quote ---I reinstalled today and double checked that the PHNL-HonoluluIntl.bgl file was marked "off"- and that MegaScenery is below all of my FSDT entries in the scenery library
--- End quote ---
That simply means your conflict is not caused by Megascenery. Doesn't mean it can't be something else.
--- Quote from: bjratchf on January 04, 2013, 09:53:40 pm ---Something is still conflicting
--- End quote ---
Sure it is.
--- Quote ---perhaps it is GSX or a COUATL problem?
--- End quote ---
Have you read my previous message ? How this could be a "GSX or Couatl problems" when I've clearly said:
--- Quote ---Jetway in a scenery are handled only in the AFCAD, the only thing that can exclude jetways it's another AFCAD
--- End quote ---
--- Quote ---Would there be a fix to make scenery not pop in and out, and force jetways to be displayed ALL of the time?
--- End quote ---
As I've said:
--- Quote --- there's nothing we can do from the scenery side, to prevent another AFCAD to exclude our jetways.
--- End quote ---
This means, the only way to fix this, is to find the offending file and remove it.
--- Quote ---And, do you have any other ideas about what could be conflicting?
--- End quote ---
There are not "other ideas", only ONE thing can cause this, which is another AFCAD of another product. Another common source for conflicting AFCADs are Traffic package products, like My Traffic or Traffic X. They usually come with their own AFCADs, which should be used only with a default scenery, and turned off if you have an addon scenery for the same airport.
bjratchf:
I just rescanned everything with FSX Airport Scanner. This is what it came up with. I'll keep searching for the offending file- maybe it's part of Ultimate Terrain, I'm not sure. But I'm not sure what else to deactivate with the Megascenery, and why PHNL works fine without it activated even when Megascenery sits at a lower priority. Appreciate your continued work on this issue Umberto, I'll keep working on my end.
bjratchf:
Perhaps there could be a conflict with another FSDT scenery?
virtuali:
--- Quote from: bjratchf on January 04, 2013, 10:21:14 pm ---Perhaps there could be a conflict with another FSDT scenery?
--- End quote ---
We surely not release other *AFCAD* ( as I've said already, the ONLY thing that can cause this it's another AFCAD ) in conflict with our own sceneries and, of course, if there was such conflict (there isn't), *everybody* would have seen it already by now.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version