FSDreamTeam forum
Products Support => Hawaiian Airports support FSX/P3D => Topic started by: 9Y-POS on July 20, 2011, 06:42:25 pm
-
I purchased Hawaii II yesterday and all seems well except for the bleed thru on the runway on approach, haven't noticed the issue on takeoff.....changed the priority in the scenery library but no improvement. PHKO is fine though, so seems a bit puzzling.
Also checked the scenery/ world/ scenery folder and noticed there was a PHOG. ALT.BGL can this have anything to do with the issue?
Many Thanks
-
Also checked the scenery/ world/ scenery folder and noticed there was a PHOG. ALT.BGL can this have anything to do with the issue?
That file is there just to *prevent* the issue to be happening when approaching.
-
Also checked the scenery/ world/ scenery folder and noticed there was a PHOG. ALT.BGL can this have anything to do with the issue?
That file is there just to *prevent* the issue to be happening when approaching.
can it be edited in anyway seeing that i'm not experiencing the desired intent?
-
That file look fine, try with the attached AFCAD, in the fsdreamteam\PHOG\scenery folder
-
That file look fine, try with the attached AFCAD, in the fsdreamteam\PHOG\scenery folder
Unfortunately the bleed persists, this is an image after the modified afcad
http://i255.photobucket.com/albums/hh157/stanmantt/2011-7-20_16-59-40-374Medium.jpg (http://i255.photobucket.com/albums/hh157/stanmantt/2011-7-20_16-59-40-374Medium.jpg)
-
I'm experiencing the bleed also, same as in the image.
Update: I've completed another flight (still PHOG Rwy 2), and this time it didn't bleed at all. I don't know how to explain a problem that occurs only occasionally, but that's what it appears to be.
-
Same problem here, as i had with PHNL when it was released.
@ PHNL => with Mega-scenery Hawaii installed => texture bleeding (when arriving, never at departure, and never when from departing from another Hawaii island, I have to arrive from KSFO or e.g NTAA to trigger it (pls make this a fixed part on any beta-testing)
deactivating Hawaii photoscenery made no difference, got fixed meanwhile
Now @PHOG bleeding again, no installed scenery at this island, but having "The Hawaiian Islands - Kauai" installed, deactivating and deinstalling doesn't make any diffference
@ KSFO from Mir, he fixed the texture bleeding issue (when arraving this airport) a day after release with a bgl, which seemed to be missing in world/scenery folder => had installed Mega-scenery San Francisco before
tested with mesh resolution 10/5/2 meters, without success. My mesh is FS Global08
Umberto, i hope you get this fixed soon, these texture bleeding issues every time with new Hawaiian airports are really annoying, errors like this can't really pass any serious QA, if there is any. :D
btw. the hawaiian Flag pole at the backside of the airport is hovering (of course having photographic proof), pls fix this before nitpicking german flightsim-journalists badmouth your beautiful sceneries based on issues like that, cause they can't find any serious points ;D
will approach PHKO today, any bet if ground-texture will be bleeding, when arriving from US west coast? :)
regards
-
@ KSFO from Mir, he fixed the texture bleeding issue (when arraving this airport) a day after release with a bgl, which seemed to be missing in world/scenery folder => had installed Mega-scenery San Francisco before
This already comes with PHOG, and it's supposed to prevent the bleeding.
Umberto, i hope you get this fixed soon, these texture bleeding issues every time with new Hawaiian airports are really annoying, errors like this can't really pass any serious QA, if there is any.
Don't you think that if we HAD this error, the scenery would be released ? Of course we can't reproduce it, I was never able to see it at PHNL for example, we had to keep fixing things at random, waiting for users report, until we hit the right fix by chance, because you just can't test for an error, if you don't see it on your system first.
-
Unfortunately the bleed persists, this is an image after the modified afcad
Without forgetting to point that I can't see nothing of the sort (both before and after the modified AFCAD), the irregular shape of your bleeding, seems to indicate it's caused by another terrain in the area, what mesh are you using ?
However, this shouldn't simply happen, because the scenery of course comes with a proper flatten command, which should flatten the WHOLE airport area to the correct altitude so, either right or wrong, higher or lower, what you are supposed to see it's a FLAT airport which means, even if you had a bleeding, it should have at least FLAT, not irregular and bumpy as in your screenshot.
Which means, the flatten is not working for a reason.
What is your frame rate there ?
-
Just wanted to add that I don't have any mesh installed for this region, everything is stock. I didn't have any other bleed thru areas in the region except for PHNL, which has seen been fixed. Maybe the same methods can be applied to fix phog, because the problems seems so similar?
Regards
-
Could you please try the files attached here ?
As before, the larger AFCAD should be in the fsdreamteam\PHOG\scenery folder, the smallest one, in the main Scenery\World\Scenery folder
-
Could you please try the files attached here ?
As before, the larger AFCAD should be in the fsdreamteam\PHOG\scenery folder, the smallest one, in the main Scenery\World\Scenery folder
Ok i gave these files a try but unfortunately i think it made it just a tad worse :o
-
Ok i gave these files a try but unfortunately i think it made it just a tad worse
I'm sorry, but it's simply not possible: the same files entirely fixed the issue for another user! There's something really wrong with your system or your settings.
Can you try to move your FSX.CFG file to a different location (like your Desktop) and let FSX create a new one from scratch ?
Also, try to reset your Video card Control Panel to default settings too.
-
I use FS Global 2010 along with GEX and UTX and had this flickering texture bleed through problem at PHNL a year ago. The solution was to set the Mesh Complexity to 100, Mesh Resolution to 10 Meters and 1 Meter for Textures.
-
Just finished a flight and I have the same problem.
I flew from KLAX-PHKO (no problems at PHKO) then decided to hop over to Kahului. Like others have reported, this never happens to me during takeoff.
I am using a freeware mesh but deleted everything that has to do with PHOG. Just to check I flew from PHLI to Kahului with the mesh deactivated and it still bled through (just the runways). On a side note, all the buildings were there but the jetways were not...
I have my mesh resolution and texture set higher then reccomended above but not the mesh complexity. I will give it a try soon.
I had this similar problem with PHNL when it came out but when I reinstalled a year later it was all fixed (using Megascenery btw). So whatever the fix was at PHNL, might work here....
EDIT: Maybe it only happens with the sim isopen for a longer period of time? If I just takeoff, fly around the island then land again there is no problem. I will try the files above now.
-
placed the 2 attached bgl files from the post above in the rigth folders
a) KSFO -PHOG => still bleeding
b) KSFO - PHOG (without the primary given FSDT_PHOG_ALT.BGL from the installer in world scenery folder) => still bleeding, too.
I really don't understand this issue. I have no actice/installed scenery left in this sector beside FSDT PHNL and FSDT Hawaii 1+2.
My FSX has SP1 and SP2 installed, FS Global08 in "standard" mode , Active Sky Evolution, REXv2 and using PMDG Md-11 or 747 on my flights. Why this shouldn't be reproducable when doing a
whole flight from KSFO. This is a common config.
After my first landing with the above given replacing files i used a fsuipc autosave to make a quick test with the config of flight 2 from long final (appr. ~10 min before landing)
=> no surprising, no bleeding, as it is when flying local traffic pattern at any Hawaiian FSDT Airport.
It seems to trigger it always a long haule flight is needed.
I am worried this will happen in KLAX, too!
Umberto, maybe it is easier to share all your beta team configuration with us customers, to investigate any deviation. ???
Personally, i don't think that you and your team wouldn't have experienced this, if you ever took the time for a real long term flight from continent. It happened to often at several of your airports, and i think it isn't uncommon to expect that every payway scenery works with the most common meshes FS Genesis / FS Global perfectly @ release, without trial & error.
Sorry for that irritation, but this approach isn't even professionally from my point of view!
-
Please, stop referring to the PHNL fix!!
The latest file posted ALREADY includes exactly the same methods to fix PHNL, which are:
- a small AFCAD in the Scenery\World\Scenery
- both AFCADs set to the same height, which is also the same as the default one, correctly set to the millimeter, which is the native internal AFCAD format.
- a VTP flatten with a slightly lower altitude than the AFCADs, set to the closest lowest 1/128 of a meter, which is the internal format for VTP/LWM polygons.
By comparing to the PHNL fix, as if we weren't aware of the issues, you are probably confusing two different things:
1) the fix we made in a similar way to PHNL, which it's attached here
2) your settings. There's no way a fix can be settings-independent because, if you don't have enough mesh resolution, the flatten will not work correctly, because it doesn't have enough data to work with.
Just to be clear, I'm still unable to see ANY bleeding, not with the original released files, not with the 1st fix, and not with the 2nd one.
I've tried everything trying to see the bleed, starting a flight a PHOG, nothing. Starting a flight on another airport, like PHLI (which should be far enough away) then fast slewing to PHOG, nothing. Starting a flight at another airport and *manually* flying in realtime to PHOG, nothing as well.
So, it can only be setting dependent in some way. I'm using Mesh Complexity at 100, Mesh Resolution at 10m, Texture resolution at 60cm.
-
Ok i gave these files a try but unfortunately i think it made it just a tad worse
I'm sorry, but it's simply not possible: the same files entirely fixed the issue for another user! There's something really wrong with your system or your settings.
Can you try to move your FSX.CFG file to a different location (like your Desktop) and let FSX create a new one from scratch ?
Also, try to reset your Video card Control Panel to default settings too.
I removed the FSX.cfg as you suggested but no improvement, what i've done is to re-install the scenery now that i have a new FSX. cfg and i did a circuit with the ultralite and landed, no issue but for some strange reason when i fly say phko to phog or any other destination in the region, the bleed occurs. I will now reset the video card and see if that helps.
my frames are also quite good, have never had an issue there.
-
what i've done is to re-install the scenery now that i have a new FSX
Without forgetting to add the 2nd fix I've posted, I hope...
-
Umberto, maybe it is easier to share all your beta team configuration with us customers, to investigate any deviation. ???
That wouldn't have changed anything. If we can't reproduce it, the only thing we can do, is trying fixes blindly, which is exactly the same of what we are doing here, and of course asking about system configuration trying to understand if there's a pattern.
Right now, the only pattern I see, is the same users that used to have the problem at PHNL back then, are seeing it at PHOG so, it's seems to be more related to system settings.
i think it isn't uncommon to expect that every payware scenery works with the most common meshes FS Genesis / FS Global perfectly @ release, without trial & error.
Nowhere I've said the scenery is supposed to work only with default scenery. In fact, a user is saying he sees the bleeding even with a stock installation so, there's no "scenery works with default only" stance at all.
Of course I still HAVE to ASK about other addons otherwise, how you suggest we can eventually find if there's a pattern ? That's the only other option we have, failing to reproduce it first-hand.
-
Another set of files to try, this time both should be put into the fsdreamteam\PHOG\scenery folder.
-
Well I flew from PHLI to PHOG and just to add time I made a quick stop in PHNL. All flown at real time in the TinMouse 737-200.
I flew with the posted small AFCAD in the scenery/world/scenery folder and after dowloading the other posted AFCAD I noticed the only change (I think) was the airport elevation (54.99 to 55.00). So I just opened up the AFCAD already installed and changed the airport elevation to 55.00. I did this because I didn't want to re-do all my gate assignments and other stuff I changed for my preference.
No bleeding! And jetways were present (I think they dissapeared last time because I was slowly running out of memory on approach).
I'm not going to be convinced until I do a flight from the mainland but for now it works fine for island hopping ;)
-
Just to be clear, I'm still unable to see ANY bleeding, not with the original released files, not with the 1st fix, and not with the 2nd one.
I've tried everything trying to see the bleed, starting a flight a PHOG, nothing. Starting a flight on another airport, like PHLI (which should be far enough away) then fast slewing to PHOG, nothing. Starting a flight at another airport and *manually* flying in realtime to PHOG, nothing as well.
Umberto,
pls read carefully what customers write:
Ethan744N763
EDIT: Maybe it only happens with the sim isopen for a longer period of time? If I just takeoff, fly around the island then land again there is no problem. I will try the files above now.
i wrote:
I have to arrive from KSFO or e.g NTAA to trigger it (pls make this a fixed part on any beta-testing)
and once more:
It seems to trigger it, always a long haule flight is needed.
If you search for old feedback respective the PHNL issues in your forums, i wrote at that time, that i can only trigger the bleeding on longer flights, not on a jump e.g. between PHTO and PHNL!
I did flights since release of Hawaii2:
from KLAS to PHOG
from KSFO - PHOG
and from NTAA - PHOG
=> every time bleeding
Now you are writing again, you can't reproduce it, while hanging around at PHLI and PHOG. ;)
I can tell you why you don't experience it, you don't listen to your customers, who are spending their freetime to fix sceneries they have have already paid for.
This isn't a mesh slider problem, as i said i tested several setups and the complexity is always set to 100%.
-
after dowloading the other posted AFCAD I noticed the only change (I think) was the airport elevation (54.99 to 55.00). So I just opened up the AFCAD already installed and changed the airport elevation to 55.00.
Be careful using feets in your editor (ADE ?), because the native altitude format in AFCAD it's not feets, but *millimeters*, stored as 32 bit long integers. MS chose this format in order to stay away from problems due to inherently inaccurate floating point libraries. For example, the default scenery at PHOG is set at 16.459 meters, so it's internally stored as 4 bytes with the value 16459.
We set it at 16.459 in this last set of files, just to be 100% identical to the default scenery but, in general, setting the AFCAD *higher* should *lower* the chance of bleeding because, what is covered by the terrain is the AFCAD runway so, the higher the AFCAD, the less chance the surrounding terrain would cover it.
Of course, there's also an additional flatten in the two small 000/CVX.BGLs, which is set lower than the AFCAD, this should further ensure that any terrain/mesh should stay clear of the runway but, I believe the flatten might not work if there's not enough mesh resolution to work with, which is why it should be set to high values.
It's POSSIBLE (note, I'm only guessing) that after a long flight, due to memory exhaustion, maybe there's an optimization in place that, in order to save memory, doesn't load all the elevation points that are in the mesh, so the flatten can't do its work properly. I noticed there's more delay loading the higher resolution meshes, if the frame rate is lower or the system is overloaded, and this might affect the work of flattens. In fact, it seems the same posted files for FS9, which is generally faster (I have about 120-130 fps at PHOG in FS9...), seems to have eliminated the problem, at least according to first reports.
-
Another set of files to try, this time both should be put into the fsdreamteam\PHOG\scenery folder.
and what about the files which we have tested before?
a) making folder status after installer
b) or after workaround 1 and 2
???
-
I can tell you why you don't experience it, you don't listen to your customers, who are spending their freetime to fix sceneries they have have already paid for.
That you are wrong saying I "don't listen" to customer, can easily been proven by my last message, which was written BEFORE this latest one of yours, were I can try to explain why the problem can be seen on long flights only.
However, it's not clear if the problem is TIME related (long flight = lots of time) or DISTANCE related (long flight=coming from far away)
-
and what about the files which we have tested before?
They have to stay, the 2nd version of course.
If these last two files were supposed to be an alternative fix that should have been used in place of the other one, I would have clearly said to remove the previous fix, reinstall the scenery and apply these files only.
-
However, it's not clear if the problem is TIME related (long flight = lots of time) or DISTANCE related (long flight=coming from far away)
In the "KSFO bleeding investigation" the distance KLAS - KSFO was enough to trigger it. If it helps.
Flights from PHTO to PHNL were to short to trigger it at that days.
-
and what about the files which we have tested before?
They have to stay, the 2nd version of course.
If these last two files were supposed to be an alternative fix that should have been used in place of the other one, I would have clearly said to remove the previous fix, reinstall the scenery and apply these files only.
roger that (i'll better ask before having an 4:30h flight):)
-
Interesting heads-up about ADE - I'm going to overwrite my AFCAD with the new one then and add the new flatten files above.
Going to start an HAL flight from PDX to OGG to see if the new files work. I'm also going to set my mesh to 100% just to be safe. Most of its ocean anyway :D
-
another question?
why is the PHOG airport groundlayout "popup"-radius that small, it's @ ~6 DME?
The buildings popup earlier.
-
:-[
Just completed a 4:40 flight (in 4X speed) from KOAK to PHOG. As soon as the radar altimeter called "10" the bleeding appeared. I am using all the files posted above and every mesh and terrain setting (other then water) is maxed out. I never have this problem with any of the other Hawaiian airports even when flying from the mainland (4+ hours).
I hope a solution can come up.
I also didn't notice any memory issues, all the buildings, jetways etc. displayed normally and my FPS were always 20+
How do you change the airport elevation other then in ADE or another payware airport editor?
-
why is the PHOG airport groundlayout "popup"-radius that small, it's @ ~6 DME?
No, it's not, if you are referring to ground vehicles, their range it's 0.5 NM for each group of objects measured from each center point but, you can control it with the Anti-popup setting in the Addon Manager, which can go up to 30, that's why it default to a small value, so users with low-end system don't experience fps loss, and users with fast systems can just crank the Anti-pop setting and increase all the ranges up to 30x.
However, nothing will be loaded anyway outside the global scenery range, which is 10.0 NM (regardless of high the Anti-popup is), which is the range of the main buildings so, with Anti-popup at 30, everything will be loaded at 10.0NM.
But, as usual, it's not so simple, because some objects like ground vehicles, also have a maximum altitude visibility range, and they also have several complexity levels so, for example, cars in the parking lot appear more and more dense when going close.
-
why is the PHOG airport groundlayout "popup"-radius that small, it's @ ~6 DME?
No, it's not, if you are referring to ground vehicles,
No, i am still referring to airport ground textures which are loading at exactly 6.1 DME (situation at 6.5 DME attached) And this is very uncommon for your Airports, i'd say. Normally this happens at ~9.5 DME.
Btw. the latest BGL fix, makes no difference, had another flight from KSFO to PHOG.
-
No, i am still referring to airport ground textures which are loading at exactly 6.1 DME (situation at 6.5 DME attached) And this is very uncommon for your Airports, i'd say. Normally this happens at ~9.5 DME.
Ok, it wasn't very clear. In that case, then no, they are not dependent by the Addon Manager at all, we might have to tweak the loading ranges, because we usually do larger airports, and that value is related to the overall area.
Btw. the latest BGL fix, makes no difference, had another flight from KSFO to PHOG.
Well, as I've said, I still haven't the pleasure to see it. Yesterday I even tried a flight from KSFO myself (using time acceleration, though) but still can't see it.
However, there might be good news, since Fabrizio "Simbio" (the Hawaii2 scenery developer) CAN reproduce it on his system and no, it doesn't seem to require a very long flight, since he can see it on a short flight too inside the islands so, I hope he should be able to fix it in the end.
-
I don't mean to push it right now but just to let you know I flew an Island Air Dash-8-100 from HNL to OGG (20 min flight) and the bleeding appeared.
Hopefully Simbio will come up with something :)
-
However, there might be good news, since Fabrizio "Simbio" (the Hawaii2 scenery developer) CAN reproduce it on his system and no, it doesn't seem to require a very long flight, since he can see it on a short flight too inside the islands so, I hope he should be able to fix it in the end.
Wow, that's great news, going crazy trying to figure this out ;D
-
been busy over here haven't had a chance to see if on my system if I get the bleed thru but will check it out today. running it in demo mode :'( some unforeseen expense came at the wrong time.
-
The texture bleeding doesn't happen at PHKO (thank flightsim god! :)), so only PHOG seems to be affected.
-
Yah I flew from KLAX-PHKO with no issue the other day and just completed KDEN-PHKO also with no bleeding.
-
That's why fixing this might be tricky: we haven't done anything special or different at PHKO to prevent it! So maybe, there's some interaction with what's in the default scenery in each area.
-
Whe have find a solution after testing all the day, we will post files for the moment later in the weekend due family duty.
A final patch will adress the bleeding problem for FSX and FS9 and other bug on Monday.
Really sorry and thank you for your patience.
Fabrizio
-
Yes, very glad to hear that Simbio! Before the final patch, should we remove the AFCAD and other files posted here and replace them with the originals first?
Thanks!
Ethan
-
Thanks very much. i can wait until tomorrow ;)
got the same issue at PHOG.
(bought the Hawaïan package and waouw...incredible).
Worth to come back in Hawai in a few months or in a year to make a Vol. 3 ! but i know, you already posted something about it. Thanks
Dom
-
There's no need to wait tomorrow, you can start trying the files attached here.
As before, the larger AFCAD should be in the fsdreamteam\PHOG\scenery folder, the smallest one, in the main Scenery\World\Scenery folder
-
Thanks very much.
The last fix works like a charm, here !
Dom
-
Works perfectly now, thank you very much ;D
-
new fix doesn't work on my todays flight: KSFO -PHOG
with my FSX standard settings (cause of some of my ORBX sceneries):
mesh complexity at 100%
mesh resolution at 2m
texture resolution at 7cm
-
So far PHLI-PHOG, no bleeding but I will see if it works tommorow from KSEA.
If I modify the gates and stuff to my liking in ADE will it change the altitude automatically to the nearest centimeter instead of millimeter even if I don't touch the modify airport altitude feature?
Ethan
-
new fix doesn't work on my todays flight: KSFO -PHOG
I'm sorry, but that's just not possible, it's clearly a problem of your system now, since you can see from messages from all the other users that HAD the bleeding, this fixed it for everyone. This has been confirmed on the FS9 forum as well, it fixed the problems for everyone there too.
Be SURE you installed BOTH files in the correct folders, and be sure you downloaded the latest files.
with my FSX standard settings (cause of some of my ORBX sceneries):
Have you tried with OUR suggested settings, which are Mesh Resolution at 10m and Texture resolution at 60cm ? Does it make any difference ?
-
Virtuali, fix works for me as well. I think the people that still having problems are putting the wrong files in the wrong folders. Once files are in the CORRECT folders should work for everyone?
Example of where the 2 files should go.
\FSX\fsdreamteam\PHOG\scenery\AFX_PHOG.bgl
\FSX\Scenery\World\Scenery\FSDT_PHOG_ALT.BGL
-
Just landed with no bleeding ;D
The terminals, jetways, buildings and towers were gone (not the runways signs, windsurfers or trees though...) and this seems to happen sometimes. Might be a memory issue because it was a long flight with no 4X.
But the bleeding is fixed :D
QUESTION: I want to modify the gate assignments and other preferences in ADE. I'm afraid to do that because I don't know if (even if I don't touch the change altitude tool) it will automatically round up the airport altitude to the nearest centimeter instead of millimeter. Anyone know? I don't like seeing all the AI planes at the wrong gates or being assinged runways that are rarely ever used in the real world...
-
I'm afraid to do that because I don't know if (even if I don't touch the change altitude tool) it will automatically round up the airport altitude to the nearest centimeter instead of millimeter.
I'm not sure about ADE, because it shows the altitude correctly with 3 decimal points in the Airport properties, but selecting "Change Airport Altitude" use only 2 decimal points. However, you would notice 1 cm difference regarding AI and, as long it rounds up, there shouldn't be any risk of bleeding coming back.
In any case, be careful with ADE because, I've noticed it always save back the file with the "DeleteAllApproaches="TRUE" parameter set, even if in the original .BGL it was set to False, like in most of our airports. If you don't edit it back to false, you'll lose all the default Approaches when saving back the file.
Unfortunately, it doesn't seem to be possible to edit this parameter with ADE (it's always greyed out) so you'll have to configure ADE to keep the XML code when compiling, then edit the XML manually, and compile it back with the MS BGLCOMP program from the SDK. This will also allow you to check what's happened with the altitudes.
-
Thanks for the response virtuali.
Actually I'm pretty sure no one has to open any XML codes if they don't want to. All I do is go to tools - load stock data - check the approaches box - load. Bam approaches present in FS. Unless any new approaches were added in the scenery the default approaches always display for me.
-
Actually I'm pretty sure no one has to open any XML codes if they don't want to. All I do is go to tools - load stock data - check the approaches box - load. Bam approaches present in FS.
Yes, of course, that would work too. We just don't do it, since it seems a bit inefficient to me to have a command to remove all default approaches, only to have another copy of them in my .BGL...
-
The terminals, jetways, buildings and towers were gone (not the runways signs, windsurfers or trees though...) and this seems to happen sometimes. Might be a memory issue because it was a long flight with no 4X.
Not sure if this is your problem or not but there is a known bug in FSX where over long flights parts of the aircraft will start to disintegrate and/or when arriving at airports certain buildings will be missing or corrupted. The fix is to edit your FSX.CFG and paste in the following line. It should go under the [GRAPHICS] Section.
HIGHMEMFIX=1
-
Wow thanks Paul. Will test it soon :)
-
having finished my actual flight i can also give green lights for the settings:
mesh complexity at 100%
mesh resolution at 2m
texture resolution at 15cm
no bleeding at PHOG again.
And finally what was ist the reason the bleeding didn't appear at BHOG departure but at arrival, Umberto?
-
And finally what was ist the reason the bleeding didn't appear at BHOG departure but at arrival, Umberto?
It's the lack of the small .BGL file correctly put in the Scenery\World\Scenery
-
Hey Umberto
Do I need to get rid of the old bgl before placing the new bgl in the PHOG Scenery folder?
Joel
-
Do I need to get rid of the old bgl before placing the new bgl in the PHOG Scenery folder?
When you do that, Windows will prompt if you want to overwrite, you have to reply Yes, and if you do, the old file will not be there anymore so, it's kind of automatic, just be sure you don't end up with two copies of it.