FSDreamTeam forum
Products Support => Honolulu FSX/P3D => Topic started by: JamesChams on February 04, 2010, 05:25:33 am
-
Virtuali/FSDT Dev.'s,
The issue here is the Flight1's GEX USA & Canada places Hangers/Ground-textures on the field at PHNL that FSDT's PHNL v1.0 scenery DOES NOT EXCLUDE. Thus, it shows up in the scenery over the FSDT scenery even when ONLY the FSX stock (default) field and AFCAD are enabled. I disabled all 3rd Party AFACDs and sceneries entries (e.g. MyTraffic X, UTX USA, etc.) to insure that it was NOT an AFCAD. I, also, made sure that PHNL had a higher priority than all the other 3rd Party products in FSX Scenery library and the problem remains. Please provide a fix for this in the next update. Grazie!
Here are examples:-
-
The issue here is the Flight1's GEX USA & Canada places Hangers/Ground-textures on the field at PHNL that FSDT's PHNL v1.0 scenery DOES NOT EXCLUDE. Thus, it shows up in the scenery over the FSDT scenery even when ONLY the FSX stock (default) field and AFCAD are enabled. I disabled all 3rd Party AFACDs and sceneries entries (e.g. MyTraffic X, UTX USA, etc.) to insure that it was NOT an AFCAD. I, also, made sure that PHNL had a higher priority than all the other 3rd Party products in FSX Scenery library and the problem remains. Please provide a fix for this in the next update.
You need to check again for duplicate AFCADS...When there's two birds piled on top of each other, that generally means you're running duplicate AFCADS.
-
You need to check again for duplicate AFCADS...When there's two birds piled on top of each other, that generally means you're running duplicate AFCADS.
The double airplanes are not really the problem, because in this case there's a conflict between the static airplanes and the AI.
The real issues that shows something else is in conflict, are the misplaced grey hangars, that don't belong to PHNL, and are not coming from the MS Default scenery either.
We should be able to fix it, but is a little bit tricky, because there are bugs in the exclude code in FSX (and FS9), that make quite messy to exclude areas without excluding our own stuff, mainly the custom jetways, which is the main problem.
-
Everyone,
You need to check again for duplicate AFCADS...When there's two birds piled on top of each other, that generally means you're running duplicate AFCADS.
The double airplanes are not really the problem, because in this case there's a conflict between the static airplanes and the AI.
Actually, I started the secession loading the CaptainSim KC-767 at the FSDT's PHNL AFCAD's W Parking spot (only FSX AFCAD Parking spot in the Military Area) and saved the flight for further tests. So, what you are seeing is the FSDT's static C-17 + my choice of aircraft loaded in the same spot. I believe that this problem was mentioned before in another post so, I hope this clears any confusion about it being AFCAD and/or AI related.
The real issues that shows something else is in conflict, are the misplaced grey hangars, that don't belong to PHNL, and are not coming from the MS Default scenery either.
We should be able to fix it, but is a little bit tricky, because there are bugs in the exclude code in FSX (and FS9), that make quite messy to exclude areas without excluding our own stuff, mainly the custom jetways, which is the main problem.
Yes, this is the MAIN ISSUE HERE, and I believed that it is related to Flight1's GEX USA & Canada as that is the ONLY addon AUTOGEN product that affects this area that I have NO way of turning off. I was able to disable Flight'1 UTX USA and some of the texture elements, etc. went away but this basically means that the current FSDT PHNL v1.0 is not able to surpress Flight1's UTX & GEX USA items inplace of its own.
I appreciate whatever can be done to fix this and will wait for it in the next release(s).
Grazie!
-
I have GEX USA/CAN and UTX USA and do not have the extra hangers. Are you using any addon landclass products? GEX does not add additional autogen to the sim, just places textures where the landclass tells it to.
-
I have GEX USA/CAN and UTX USA and do not have the extra hangers. Are you using any addon landclass products? GEX does not add additional autogen to the sim, just places textures where the landclass tells it to.
The ONLY other product is FSGlobal 2010 and I disabled that along with UTX USA before I reported this. I am also showing these on other systems and all my FSX display sliders are MAX.'ed; your's might not be and that is why you do not see these. (I've noticed that before with other addons where even the developers didn't have sliders at max when testing :-X ) Also, GEX + UTX does place extra autogen with landclass, etc. So, for now, unless otherwise proven, its most likely a conflict with GEX/UTX USA-CAN.
-
Just fired up the sim with all scenery sliders maxed, UTX active and GEX installed. No unwanted hangers.
(http://)
-
Just fired up the sim with all scenery sliders maxed, UTX active and GEX installed. No unwanted hangers.
Could you post some pics of your FSX Scenery Library structure (for UTX USA-CAN and FSDT PHNL) and ALL FSX Display settings, please?
I want to make sure I didn't miss anything; Thanks! ;)
-
No problem. Here are some captures of my scenery library showing the UTX-USA layers and PHNL layer and my settings when I took the screen shot earlier. One thing I forgot to mention is that I have Scenery Tech Landclass installed, so I tried with it disabled and the result on the airfield was the same. I also disabled UTX and Scenery Tech both, and had the same result. Your screen shots look very much like another AFCAD above the PHNL scenery, but I see from your AFX shot, you don't have any other AFCADs, so that should rule that out. When I first installed the scenery, I forgot I had the Alpha India Group AFCAD for PHNL in my Addon Scenery directory and had some double objects on the airport. Removing the AFCAD cleared that right up.
-
Hmmmm...
I was considering purchasing this one but I also have UTX Usa & Canada and Scenery Tech USA landclass addons installed.
I've seen similar issues such as this in other addon airports like AIG whre I get occasion trees/bulidings on the airport aprons where they shouldn't be. This is with no duplicate AFCADS either...
It has to be down to the landclass layering.... and therein in some order the fix has to be. Maybe uninstalling or reinstalling UTX and ST after this airport.
Maybe ST shouldn't be sandwiched between the UTX Urban and Vegetation layers...
B.T.W. did you check for any remaining library object .bgl files for AIG's PHNL airport???
Very curious to find the solution.
-
@JamesChams: Are you using Mytraffic? I believe (unfortunately) that they also include certain structures that can cause conflicts. I seem to vaguely remember an issue I had with Mytraffic (and fsdt Las Vegas) that once a Afcad had been used, buildings were sometimes left behind unless you physically marked the specific Traffic X Afcad for that area as passive. (even when MytrafficX had lower priority, maybe because these extra buildings were not excluded by the higher priority scenerys?)
-
I guess I just hadn't explored the airport enough, but I have the same rogue hangers as James.
-
Turns out I have a couple extra hangars too. They kind of hide since they are deep in the military ramps.
EDIT: I should have added a little about my setup. I have FSGenesis mesh (doubt it's causing this), GEX USA (doubt this, but it's a little more possible) and SceneryTech NA Landclass (?...doesn't seem logical but who knows). I've never had any freeware or payware Hawaii specific scenery installed and have no other global add-ons other than REX which I can all but be certain is not causing this. I use WOAI traffic, which does nothing with AFCADs, so I also doubt this as a source.
I have looked for duplicate AFCADs, but only know how to do this by just manually looking through the FSX file structure. Is there a more efficient way (like a program) to check for these?
-
I have the same isseu with the demo, so that is keeping me from buying it, i have tried everything, i even deleted the default afcad :o
Please someone make it go away :'(
Greets,
Randy
-
Please someone make it go away :'(
LOL...I agree, although still a great scenery. The extra hangers are far in the back of the military cargo ramps. They're kind of hidden there and I didn't notice them for some time, even when taxiing around a few of the military ramps. Of course, now that I know they're there, they seem to just stare at me while I'm approaching 08L :(
-
I use WOAI traffic, which does nothing with AFCADs, so I also doubt this as a source.
Some of the WOAI military packages do include AFCADS. I had some bad situations occure at a few airports worldwide in FSX when I first installed all the WOAI packages due to their military packages putting AFCADS in FSX that I was unaware of. Once I deleted all of their AFCADs I was fine, but had to fine modified FSX ADE's to replace the ones WOAI installed. They have some military packages that quite possibly could have installed AFCADS that are causing the problem. Unfortunately I deleted them on my system so long ago that I dont remember where they were placed exactly, but I am thinking they may have been in either addon scenery/scenery folder or the scenery/world/scenery folder. Check these two locations to be sure.
-
I just went to the WOAI site and saw that they have a Hickam C-17 package of which Hickam is at PHNL. That could be the source of the trouble if it has an AFCAD installed in FSX.
-
I just went to the WOAI site and saw that they have a Hickam C-17 package of which Hickam is at PHNL. That could be the source of the trouble if it has an AFCAD installed in FSX.
I just installed the WOAI Hickam C-17 package and it installed an FS9 AFCAD into my FSX/Addon Scenery/Scenery folder called MAIW_AF2_PHNL_DEFAULT_DB.bgl.
Look for that file and remove it if you have it and that should fix the problem.
I dont own the FSDT PHNL scenery so I cant test it on my system, but I wouldn't be surprised if that is the cause of the problems.
If not, sorry for occupying forum space. Might be beneficial to the FS9 users also if they have AFCAD issues and are running the WOAI package.
Edit:
Using the WOAI uninstaller doesn't remove the AFCAD in FSX, it needs to be deleted manually.
-
I can confirm that the MAIW Hickam (sic) - pronounced "Hick-em" - AFB AFCAD does not impact the issue for me. Pretty much knowing the MAIW AFCAD was developed for default PHNL, using FS9, told me to leave it out of FSX.
The source seems to be the GEX install, combined with the FSDT PHNL. When I removed GEX, the extra hangers issue went away. As I prefer both GEX-USA & PHNL, I'll personally deal with the hangers until a formal resolve is completed.
Thanks
Bill
-
Good to know that it's not that file for you. Though it was worth mentioning though since not everyone know that. Strange that GEX is causing it. I haven't seen GEX place a hanger or any type of autogen inside of any airports. Have seen UTX do some funny things, but not GEX. Guess anything is possible though.
Thanks for pointing out that I spelled it wrong. I know how to pronounce it. Guess when I wrote that at 5 am I was a little tired, lol.
-
I also do not have the MAIW package installed. It seems odd that GEX is adding hangers, but at least it's a clear source. Now it's time to figure out how to remove them (...abd the small amount of extra tarmac it seems to add).
-
I also do not have the MAIW package installed. It seems odd that GEX is adding hangers, but at least it's a clear source. Now it's time to figure out how to remove them (...abd the small amount of extra tarmac it seems to add).
GEX is a set of textures, which are annotated with autogen objects. There are no autogen hangers to be placed. When the FSDT scenery is active the photo layer should be excluding any autogen objects not specific to the photo layer. As it does on my system, where I have GEX textures in FSX, but don't have the GEX package installed at the moment. Don't worry, it's just a reinstallation thing for me. And the copy *is* legit, albeit a freebie. ;D
Somewhere, somehow these scenery objects are appearing. At the moment I don't have UTX installed, but anyone seeing extra objects might want to disable the object repositioning layer to see if the buildings are coming from UTX. They might be, but if they were then it would behoove FSDT to make sure their exclusions extend out this far.
It helps a whole lot (Mr. Chams) to have the lat/lon and heading showing in any screen caps.
-
GEX is a set of textures, which are annotated with autogen objects. There are no autogen hangers to be placed....
I understand that in theory (hence the reason it seems odd that GEX is the culprit), but it seems like a pretty compelling argument that people who have these extra hangars are able to get rid of them simply by uninstalling GEX.
At the moment I don't have UTX installed, but anyone seeing extra objects might want to disable the object repositioning layer to see if the buildings are coming from UTX.
Well, I have these extra hangars and have never even looked at purchasing UTX, much less actually had it on my system.
-
Gents,
I know that there was much confusion here but let me assure you'll that the issue is definitely between Flight1's GEX and FSDT's PHNL v1.0 and NOT an AFCAD from MyTraffic X (which I've already removed prior to posting) or any other product (like WOAI or the MAIW package) which I do NOT have installed at all. For those of you that have the same issue, thank you for confirming it for Virtuali and the FSDT team, who usually need that before they attack an issue.
@Mr. LCSim, will try and add the LON/LAT in future pics for you; however, all the objects are in the vacinity or on the field at PHNL so nothing's outside of that area.
Thanks for all the help. ;)
-
These scenery objects are seen by some, but not all. I have two different land class products to toggle between, along with the default land class and none will show these stray structures? As I mentioned before, I have the GEX textures installed, just not the interface, but that should have no effect.
If this is as claimed, a problem with GEX, then the issue should be addressed at the Flight1 forums, where I'm 99% positive of the response you'll get from Mr. Needham... :o
I have only seen one set of circumstances where photo scenery does not exclude the autogen of the underlying default (or add on) textures. I don't see that with the FSDT photo work.
And in more than one occasion have random objects appeared from some scenery work totally unrelated, many thousands of miles away.
And James, with lat/lon of the four(?) objects it would take about 90 seconds to make an exclusion to get rid of them.
-
I'm not sure GEX is the problem here. According to Flight1, it doesn't even cover Hawaii:
http://www.simforums.com/forums/forum_posts.asp?TID=30189
I ask everyone some little bit of patience, we are going to update PHNL soon, probably during this weekend and we hope this issue should be sorted.
-
... According to Flight1, it doesn't even cover Hawaii:...
Virtuali,
Please re-read Mr. Nick's statement: "...GEX does not cover it completely as of yet.. there are some GEX textures used there but the bulk of them are not replaced as of yet.. " So they have done something there and I can visually confirm that based on the difference that DEFAULT FSX Hawaii looks from when the GEX/UTX USA package is installed; the difference is like day and night. I'm NOT looking to pass blame here; its just that us users just have to wait while dev.'s play the "Pass-the-buck" game, again. So, I'm being patient, again. ;)
Also, I'll be patient for the next fixes/updates and hope you will include this -> JUST FYI: Wrong Signs (http://www.fsdreamteam.com/forum/index.php?topic=2781.0) issue as well.
Grazie! :)
-
Well, I've just started really trying to play around with the scenery issues I've been having. Unfortunately, the new patch absolutely did not change things for me. I am on a more thorough search now for duplicate AFCADs or if there is any hope of a difference with scenery library priorites, etc. I will report if I find a solution myself.
I agree with the comments said before about the absolute lack of logic that this was be associated with GEX. However, I also can't ignore the evidence that everyone with this problem has GEX and some have reported that it goes away with an uninstall of GEX.
We'll see...
-
Unchanged in 1.02 update.
-
Well I decided to find the cause of this problem, as I'm not convinced at all it is GEX. And guess what, its NOT!
The problem is in the scenery added by the Aerosoft F-16, or F-16 missions pack. Look in your scenery libray for Falcon X, turn off. hangers gone.
Problem solved. ;D
-
peacedivision is right :) i deleted the mission pack and the hangars are gone now. now its time to buy the scenery
Thanks peacedivision
Greets,
Randy
-
Well I decided to find the cause of this problem, as I'm not convinced at all it is GEX. And guess what, its NOT!
... Problem solved. ;D
Mr. "peacedivision,"
Let me be the first one to say, "Thank you," to you 8) ... and, I'm glad to be wrong about GEX being the issue, if only not to have to uninstall it and get this issue fixed as easily as this. :D
My ONLY suggestion is to NOT have users DELETE the scenery .BGL files but either rename the .BGL to .BGL_OFF or do as I have by UNCHECKING the ACTIVE checkbox for the Falcon X Scenery Folder in FSX's Scenery Library.
(eg. see Pic below "FSDT_PHNL_AI_Building_DISABLE_Aerosoft_FALCON_X.jpg")
PS: Placing the FALCON X Scenery Folder in a lower priority in the FSX Scenery Library does NOT fix this issue, you have to either disable it or rename the files.
Thank you once again.
-
hehe, I think you misunderstood :) I don't recommend they delete the scenery, simply that they uncheck "Falcon X" in the scenery library
But either way, I'm just glad its solved.
-
Well I decided to find the cause of this problem, as I'm not convinced at all it is GEX. And guess what, its NOT!
The problem is in the scenery added by the Aerosoft F-16, or F-16 missions pack. Look in your scenery libray for Falcon X, turn off. hangers gone.
Problem solved. ;D
Excellent job! Somehow that seems so simple, yet no one was able to come up with it.
-
Well sometimes the simple solutions can be the most difficult to figure out. James is also absolutely right that the scenery priority for Falcon X had no effect, mine was far below PHNL.
We can also thank Aerosoft for not using PHNL in their BGL filenames :-\ that alone would have made the fix very quick for most.
In the end it was just trial and error, disabling huge blocks of scenery in my library until the hangers went away.