Joseph29 wrote:Question, I have Ørland and Bodø airports as part of a Noway airpots scenery package. Are your airports improvment on those? Or just new AFCADs?
Orland (or Andoya?) is totally missing from the Norwegian Airport scenery...
Orland and Bodo are both in the Norwegian Airports package, but the military parts of these fields are not very detailed. That's why I started this little project. Andoya isn't covered by Norwegian Airports.
Orland is indeed a good place for spotting. The German F-4s are regular visitors and on friday you will find the NATO E-3 on the ramp.
Now Andoya and Orland are finished, I will get to Bodo. Hope I will not encounter the mentioned problems. We'll see
Pemor2 wrote:I Have problem with the installation of the Ørland.
When i have removed the Ørland from the Norwigian package i can't get the, runway to show or the taxiway to show in the Enol package.
The only thing is the buildings, and the grass.
Help?
First check out if you have removed all the mentioned files from the Norwegian Airports package. Don't delete them, you might want to save them in case you want to restore ENOL from their package.
Otherwise it might be the order of your Addon scenery folders?
To rule this out try this:
Create a folder \Addon scenery\ENOL\Scenery and copy the file ENOL_Objects.bgl to this location.
Create a folder \Addon scenery\ENOL_Flatten\Scenery and copy the files ENOL_Flatten.bgl to this location.
Then copy the file AFX_ENOL_DJB.bgl to \Addon scenery\Scenery
Now make sure that you add the ENOL folder to you scenery library with a higher priority than Addon Scenery.
The ENOL_Flatten folder goes right below the ENOL folder, also with a higher priority than Addon scenery.
I just have to say many thanks for the Orland and Andoya sceneries. I set both up over the weekend and programmed in some P-3 and F-16 AI, excellent stuff as Norway has always been my favourite location outside the UK to visit and fly from. Although I've got the Norwegian Airports installed I'm really pleased that you're doing a Bodo as that airfield has been one of the most frustrating places to set up in the past and none of the versions of Norwegian Airports have worked properly at that location. As said previously, although the civil airport is well detailed, the military side is very basic to say the least. Also, it suffers from a frustrating case of either floating or sunken AI, depending what version you're using and whereabouts on the airfield you are (currently, on my set up the civil terminal is fine, but the F-16's in the shelter area are sunken upto the intake!). I tried to correct it a while ago, without much luck by mixing files from various versions and using a AI fix that was released - it doesn't! So, I'm really looking forward to Bodo. Just a quick query, will it just be the military side or will the civil terminal area also be covered (if it could somehow fit onto the existing adequate civil version from Norwegian Airports and fix the annoying AI problem then that would be superb).
Two things that you also need to check.
One is that you have no other scenery for the area that is stamping over this one. To give you an example of this my UK2000 scenery for Warton disappeared and after a weeks worth of messing around and found that an MAIW exclude for Warton was in a higher priority folder and effectively wiped it out.
The second thing is that you say that you have the MAIW scenery libs necessary for this scenery but they must be loaded before the scenery that calls them. This means that the MAIW Scenery folder must be activated and be below the ENOL and ENOL_Flatten folders.
Steve _______________________________________________________ Quid Si Coelum Ruat _______________________________________________________
From what you have said I gather that the listing that you are talking about is the list as it appears inside FS9 once it has loaded up. In which case the MAIW Scenery Libs folder must be as low as possible but above the default scenery, Just above Addon Scenery.
UNLESS, you have placed anything that uses the libs in the Addon Scenery folder, in which case it has to be below it.
As I understand it FS9 scenery is loaded from the bottom up. If you get to a scenery folder that calls for a lib that is not yet loaded by FS9, then it gets ignored. This is why you find some sceneries that say that its Landclass folder needs to be activated and below the associated Scenery folder. I hope this makes sense.
Steve _______________________________________________________ Quid Si Coelum Ruat _______________________________________________________
Two things that you also need to check.
One is that you have no other scenery for the area that is stamping over this one. To give you an example of this my UK2000 scenery for Warton disappeared and after a weeks worth of messing around and found that an MAIW exclude for Warton was in a higher priority folder and effectively wiped it out.
The second thing is that you say that you have the MAIW scenery libs necessary for this scenery but they must be loaded before the scenery that calls them. This means that the MAIW Scenery folder must be activated and be below the ENOL and ENOL_Flatten folders.
Tried that way to.
The only things i have installed to Norway, is the scandinavien airports and the Norwigians airports and landclass.
Small status update of the Bodo project. Getting along fine. Because of the short distance of the shelters to the detailed coastline, I'm sorry to say that this one will only work with Ultimate terrain Europe. With the default coastlines, these shelters are flooded...
Maybe there's someone out here who wants to do a LWM/coastline modification to the default scenery when I'm done? I'm not an expert with these things I'm affraid.
No problems with AI floating, take-off and landing though. Looks pretty good.
I had a similar problem yesterday with the ENVA (Vaernes) scenery from Norwegian Airports. I was running some circuits from Orland and noticed that the commerical stuff was turning left straight across the grass when they should be turning right towards the terminal. I figured it was a simple AFCAD problem so had a look, found several on the system but the Norwegian airports one was the only one active and was marked out correctly, with no links of any sort where the aircraft were actually taxiing. Infact the only AFCAD with links at that position was the original stock FS9 AFCAD right at the bottom that certainly wasn't activated. I pulled all the other AFCADS (including the stock one labeled AP9***** something or other) and went back and they were still doing it! It was beyond me why aircraft were taxiing where there was definitely no links on the only AFCAD in the system. I was just about to ask here when I did a couple of minor alterations on the AFCAD which seemed to make the aircraft obey it for some reason even though it was already active. Not sure if it would work in this case but it seems worth a try. This Norwegian Airports pack seems to have a few interesting problems associated with it!
The problem with Orland and Andoya is that the buildings is also standing on the taxwai and the aircrafts is standing outside the parkingsports and there is no, parking spots.
Have tried to remove all of the norwigian airport package and the mesh scenery.
The only thing that there is, are the buildings now again, nothing is there, the runway or taxiway is not there what is the problem help.
Pemor2 wrote:The problem with Orland and Andoya is that the buildings is also standing on the taxwai and the aircrafts is standing outside the parkingsports and there is no, parking spots.
Have tried to remove all of the norwigian airport package and the mesh scenery.
The only thing that there is, are the buildings now again, nothing is there, the runway or taxiway is not there what is the problem help.
Can you show some screenshots to clarify what you mean?
This may muddy the problem even more or be similar to what the other guy is having problems with but I did also have a similar issue when first setting Andoya and Orland up.
Everything was fine on both installs but I wanted to tinker with the AFCADs a bit (change the parking codes, move some parking, cosmetic stuff... etc) so made the changes in AFCAD and saved without thinking any further and then noticed the stock trees, buildings...etc... were back covering the scenery, which they were not before editing the AFCAD. The other files in your download were not touched. As soon as I replaced the original, untouched AFCAD back into the folders the stock scenery was gone again. I don't know much about this sort of thing, but was under the impression that the bgl files attached to the new scenery altered the stock scenery, not the AFCAD itself? I also noticed that both the ENAN and ENOL AFCADs, as supplied start with 'AFX' rather than the 'AF2' I'm familiar with, yet after I edited them, AFCAD renamed them 'AF2' following my attempted edits. Even after I renamed them the same as the original supplied files (AFX...etc...) and overwrote your originals the stock scenery was back in the way again. I've got around it by not editing the AFCADs in anyway and editing my parking codes to your AFCADs. As I say, I don't really know why the above happened or if it is connected to the other guys problem but thought it might be of interest.
The AFX_* afcads are made with the AFX program (payware), not with Lee Swordy's AFCAD (which uses the AF2_ prefix in file names). There are excludes in this AFCAD, which are not supported in Lee's AFCAD tool. So if you save the AFX made airport in AFCAD, you are removing these excludes.
