The download hangar is currently disabled. We're doing our best to bring it back as soon as possible.
General MAIW Package Issues
Re: General MAIW Package Issues
Steve, and Martin, I already did it for them all. 8 bit I left as is, 32 bit I changed to DXT1, and unmipped DXT1 and DXT3 were mipped. I have since then uploaded all of them (including the ones that did not need an update) to dropbox if anyone wants to download them. One person already did so. Since then I have found others that needed a fix; GGSE, JGSE, and MAIW_ABO.
Re: General MAIW Package Issues
OK so altering the 32bit textures solved your issues. Good. We will take this into account when we next update the package. I guessed that not all the 32 bit textures caused an issue as some were very small in size.
My guess is the ones that were 4097KB in size were the issue.
My guess is the ones that were 4097KB in size were the issue.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
Re: General MAIW Package Issues
Not a issue but a question about the export Hawks. Can I take the Hawk 103, 120, 127, and 129 folder and combine them to one folder? And do the same thing with the Hawk 64 and 66 folders?
-
- Captain
- Posts: 358
- Joined: 12 Aug 2006, 07:49
- Version: FSX
- Location: Abertillery,South Wales. UK
Re: General MAIW Package Issues
Hi Joseph,
The models for Hawk 103, 120, 127, and 129 are all NBAI_Hawk_100.mdl and for Hawk 64 and 66 are NBAI_Hawk_60.mdl so the cfg should also be the same for the 100 and 60 series so I do not see a problem in combining them but personally I prefer to keep the various type folders separate.
Steve
The models for Hawk 103, 120, 127, and 129 are all NBAI_Hawk_100.mdl and for Hawk 64 and 66 are NBAI_Hawk_60.mdl so the cfg should also be the same for the 100 and 60 series so I do not see a problem in combining them but personally I prefer to keep the various type folders separate.
Steve
Past Beta Tester
- clickclickdoh
- MAIW Developer
- Posts: 1568
- Joined: 03 Mar 2009, 03:04
Re: General MAIW Package Issues
Before combining them, take a look at the lights entries in the .cfg files. I don't know if it was done with the Hawks, but several other models, particularly C-130s, had changes in their lights to represent various nations configurations.
Re: General MAIW Package Issues
Thanks for the tip. I was just about to combine them. Good thing I saw your post first.clickclickdoh wrote: ↑14 Jul 2017, 15:05 Before combining them, take a look at the lights entries in the .cfg files. I don't know if it was done with the Hawks, but several other models, particularly C-130s, had changes in their lights to represent various nations configurations.
Re: General MAIW Package Issues
Just wanted to let you know that the lights sections is the same.Joseph29 wrote: ↑14 Jul 2017, 23:34Thanks for the tip. I was just about to combine them. Good thing I saw your post first.clickclickdoh wrote: ↑14 Jul 2017, 15:05 Before combining them, take a look at the lights entries in the .cfg files. I don't know if it was done with the Hawks, but several other models, particularly C-130s, had changes in their lights to represent various nations configurations.
Re: General MAIW Package Issues
The simple rule with combining is to get a compare proggy.
IF you compare two similar aircraft.cfg files and the only difference is the fltsim numbers then you are good to combine.
IF there are small insignificant differences, extra spaces. comments etc then you are good to combine.
IF any parms are different you can't combine.
IF you compare two similar aircraft.cfg files and the only difference is the fltsim numbers then you are good to combine.
IF there are small insignificant differences, extra spaces. comments etc then you are good to combine.
IF any parms are different you can't combine.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
Re: General MAIW Package Issues
folks,
new at this with MAIW.....great site....I can download a package such as Hurlburt.....run the executable.....exactly where do I direct to installation to go, FS9 root or add on scenery....try to add on after each installation and the package doe not show up in add on scenery.....had no problem with Pope and RAF Mildenhall.....
new at this with MAIW.....great site....I can download a package such as Hurlburt.....run the executable.....exactly where do I direct to installation to go, FS9 root or add on scenery....try to add on after each installation and the package doe not show up in add on scenery.....had no problem with Pope and RAF Mildenhall.....
Re: General MAIW Package Issues
When you run the installer what path does it default to install ?
I just ran the installer and on my PC the path came up as 'F:\Flight Simulator 9' which is my FS9 installation folder.
Are you saying that it doesn't install at at all or is there something else wrong?
I just ran the installer and on my PC the path came up as 'F:\Flight Simulator 9' which is my FS9 installation folder.
Are you saying that it doesn't install at at all or is there something else wrong?
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
Re: General MAIW Package Issues
As I replied to your e-mail: Pope and Mildenhall contain extra scenery. That is why you have extra folders in your Addon Scenery folder which you need to add to the Scenery Library.
Hulburt doesn't have extra scenery. It just installs an AFCAD file in the "Addon Scenery\Scenery" folder. You don't need to do anything extra to activate it since that folder is active by default.
Just follow the readme instructions. If it doesn't say you need to activate anything, there's nothing to activate.
Hulburt doesn't have extra scenery. It just installs an AFCAD file in the "Addon Scenery\Scenery" folder. You don't need to do anything extra to activate it since that folder is active by default.
Just follow the readme instructions. If it doesn't say you need to activate anything, there's nothing to activate.
Re: General MAIW Package Issues
I am looking for flight plans for the C-141B, but I cannot seem to find them. Would a kind soul please point me in the right direction?
Thanks in advance -
Jorgen
Thanks in advance -
Jorgen
Re: General MAIW Package Issues
Hi Jorgen,
I had the two attached files on my machine. Not sure where I found them. Hopefully they are of some help.
Paul
I had the two attached files on my machine. Not sure where I found them. Hopefully they are of some help.
Paul
- Attachments
-
- Traffic_C141B.bgl
- (10.46 KiB) Downloaded 72 times
-
- Traffic_C141.bgl
- (6.46 KiB) Downloaded 70 times
Re: General MAIW Package Issues
Forget to mention, both are FS9 format.
Paul
Paul
Re: General MAIW Package Issues
Thanks a lot. Format is no problem, AIFP is your friend!
Jorgen
Jorgen
Re: General MAIW Package Issues
Can not find traffic files for the AH-1S Cobra, They are not in the RJTK, RJAK and the RJOE scenery's as stated in the read-me file?
Re: General MAIW Package Issues
Please see this thread in the JYAI forum.
Re: General MAIW Package Issues
Is it generally a good rule to keep all scenery folders such as object libraries and collective sceneries such as the folders that contain all scenery for a country, i.e., "UK Airfields", near the bottom of the priorities but before the FS2004 default entries? Thanks!
Re: General MAIW Package Issues
It depends on what you mean by at the bottom a there is two ways of looking at it , at least in FS9.
If you look in the Scenery Library in game at the top you will have something with priority 1, and down at the bottom are the default MS folders with the highest priority number.
This would seem to show that the MS default folders have the highest priority, when in fact the opposite is true.
If you look at the scenery.cfg there are a couple of numbered parms.
Ignore the Area ones. They are just the order in the list, a bit like the fltsim number in an aircraft.cfg file.
The important one is the layer. This is the order that the different layers are loaded into the sim. You will see that the MS folders have the lowest numbers and are therefore loaded first. This means that they are in fact the lowest priority as they can be superceded by something loaded later.
It is very important to get this clear in your mind.
So what you want is the default MS stuff loaded first to set up the world.
Next you want to load any mesh that amend your world.
Then you want to load anything that alters the terrain, i.e. Coastline and Waterway changes
Next you want to add any landclass files that alter your landscape.
Now you want to add all those object libs than add to scenery files
Finally, you add the scenery folders themselves.
In simple terms whatever is loaded first can be stamped over by something loaded later on.
So as I read the question you posed then the answer is no.
Also for clarification any libs that are being used by a scenery MUST be loaded before the scenery that uses it.
If not what happens is that the scenery is loaded and asks for this object to be placed here.
FS9 says I don't know about that object and ignores it. It does not remember that it is needed and places it later on, it just moves on.
So in truth addon scenery folders should be at the top of the list/have the highest layer number.
It does not matter what order you have the actual scenery folders. I have mine in Alphabetic Continent/Country/Airport Name order purely to make it easier to find in SceneryConfigEditor, which I use to keep everything in order.
I think I have covered everything.
If you look in the Scenery Library in game at the top you will have something with priority 1, and down at the bottom are the default MS folders with the highest priority number.
This would seem to show that the MS default folders have the highest priority, when in fact the opposite is true.
If you look at the scenery.cfg there are a couple of numbered parms.
Ignore the Area ones. They are just the order in the list, a bit like the fltsim number in an aircraft.cfg file.
The important one is the layer. This is the order that the different layers are loaded into the sim. You will see that the MS folders have the lowest numbers and are therefore loaded first. This means that they are in fact the lowest priority as they can be superceded by something loaded later.
It is very important to get this clear in your mind.
So what you want is the default MS stuff loaded first to set up the world.
Next you want to load any mesh that amend your world.
Then you want to load anything that alters the terrain, i.e. Coastline and Waterway changes
Next you want to add any landclass files that alter your landscape.
Now you want to add all those object libs than add to scenery files
Finally, you add the scenery folders themselves.
In simple terms whatever is loaded first can be stamped over by something loaded later on.
So as I read the question you posed then the answer is no.
Also for clarification any libs that are being used by a scenery MUST be loaded before the scenery that uses it.
If not what happens is that the scenery is loaded and asks for this object to be placed here.
FS9 says I don't know about that object and ignores it. It does not remember that it is needed and places it later on, it just moves on.
So in truth addon scenery folders should be at the top of the list/have the highest layer number.
It does not matter what order you have the actual scenery folders. I have mine in Alphabetic Continent/Country/Airport Name order purely to make it easier to find in SceneryConfigEditor, which I use to keep everything in order.
I think I have covered everything.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________