-
There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.
If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.
Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.
The Staff of SOH
Marianas 1945 Uploaded
- Thread starter stovall
- Start date
robert41, I will make new airfields with different exclusions to see if that helps. We can start with Isley, Kobler and Rota. I will attach when done.
Robert, I have attached a possible fix for the three airfields mentioned. If this works for you I can do any others you have problems with. Place these two files into your Northern Marianas Large/scenery folder. Let me know.
Robert, I have attached a possible fix for the three airfields mentioned. If this works for you I can do any others you have problems with. Place these two files into your Northern Marianas Large/scenery folder. Let me know.
Last edited:
jojohnson9
Charter Member 2016
I tried the exclusion files, but still have all the trees, etc.
Thanks Tom.
This is incredible generous.
I will install the files as soon as I can.
And yes, I did find some other fields with the trees.
I will let you know.
Butcherbird17
Charter Member 2012
I just went through all the airfields in this scenery and added excludes to all. Here is a new zip with all
airfields. Hope this helps.
Joe
airfields. Hope this helps.
Joe
It would be helpful if users who report anomalies would give a few further informations, like
- version of simulator (FSX, p2d1.4, p3d2.0, p3dv2.1)
- location of Mariana1945 in scenery database (the order / priorities of the 4 Mariana folders is important)
- if a global addon scenery is installed (e.g. ftx global) and where it resides in the scenery database (above or below Marainas)
- if a modified terrain.cfg is present (the use of ftx global or orbx products imply that, but there is the modified version that activiates the FS9 vector elements, for example)
What is confusing right now is that we have many diffierent reports and we need to sort out what effect applies to which scenario.
The Marianas aren't the only scenery that has problems, by the way. On P3Dv2.0 and v2.1 many "old" sceneries, including the Solomons, show anomalies in areas where ADEX was used for scenery / airifeld construction.
Cheers,
Mark
- version of simulator (FSX, p2d1.4, p3d2.0, p3dv2.1)
- location of Mariana1945 in scenery database (the order / priorities of the 4 Mariana folders is important)
- if a global addon scenery is installed (e.g. ftx global) and where it resides in the scenery database (above or below Marainas)
- if a modified terrain.cfg is present (the use of ftx global or orbx products imply that, but there is the modified version that activiates the FS9 vector elements, for example)
What is confusing right now is that we have many diffierent reports and we need to sort out what effect applies to which scenario.
The Marianas aren't the only scenery that has problems, by the way. On P3Dv2.0 and v2.1 many "old" sceneries, including the Solomons, show anomalies in areas where ADEX was used for scenery / airifeld construction.
Cheers,
Mark
Butcherbird17
Charter Member 2012
Mark,
I have this scenery installed into FSXA. I also have FTX Global and PNW installed. I have your Solomon43v2 plus Tom's Chi-chi, Iwo and Truk sceneries. These packages sit below my FTX entries in the scenery library. My Terrain cfg file is a modified one, as it was done when you released your Solomons v1 package. (I also have backups of the terrain cfg)
As in one of my post above, I did a test and moved the Marianas above my FTX entries in the scenery library. I also removed my excludes from the scenery and then went to Tinian North Field. It was covered in jungle growth, so I moved it below the FTX entries, and went back to same base and only the tree's that I did excludes were left. Put my excludes back in and all tree's are gone. I also checked the above mentioned scenery to see if there were any anomalies, and there were none.
One other thing I should say, is I do read the read-me files before I install any scenery packages into my sim. I also always extract them to a temp folder before I install into sim. (except for the FTX products) I like to make sure that if the scenery needs another d/l (object library) or an edit of some sort, that I do that to make it work.
As of now I have the tree anomalies fixed, and would like to know if my excludes helped the other 2 with same problem. If you or Tom come up with another fix, I would like to test it for you.
Joe
P.S. I'm wondering if its ADE 1.60 excludes that are the problem? In my post above I did remove the original excludes in ADE and replaced them with new ones and I still had the problem. That's when I used IS3 to place the excludes. (which are the ones in my attached files)
I have this scenery installed into FSXA. I also have FTX Global and PNW installed. I have your Solomon43v2 plus Tom's Chi-chi, Iwo and Truk sceneries. These packages sit below my FTX entries in the scenery library. My Terrain cfg file is a modified one, as it was done when you released your Solomons v1 package. (I also have backups of the terrain cfg)
As in one of my post above, I did a test and moved the Marianas above my FTX entries in the scenery library. I also removed my excludes from the scenery and then went to Tinian North Field. It was covered in jungle growth, so I moved it below the FTX entries, and went back to same base and only the tree's that I did excludes were left. Put my excludes back in and all tree's are gone. I also checked the above mentioned scenery to see if there were any anomalies, and there were none.
One other thing I should say, is I do read the read-me files before I install any scenery packages into my sim. I also always extract them to a temp folder before I install into sim. (except for the FTX products) I like to make sure that if the scenery needs another d/l (object library) or an edit of some sort, that I do that to make it work.
As of now I have the tree anomalies fixed, and would like to know if my excludes helped the other 2 with same problem. If you or Tom come up with another fix, I would like to test it for you.
Joe
P.S. I'm wondering if its ADE 1.60 excludes that are the problem? In my post above I did remove the original excludes in ADE and replaced them with new ones and I still had the problem. That's when I used IS3 to place the excludes. (which are the ones in my attached files)
Thanks to Mark and Joe for your comments. It is essential when reporting any anomalies to mention the points Mark listed. With all the different systems and installations out there problems are bound to happen. With the help of people like Mark and Joe, surely we can solve the issues.
Thanks for the offer Joe, you are commissioned as a tester. Having someone as a tester that has experienced the problem is essential to finding the answers. Joe my installation is essentially the same as yours. FTX Global cause the tree issue on Iwo Jima. I published a fix for that that seemed to work. I simply installed a landclass under the runways that had no trees. It definitely seems that part of the problem is with the excludes in Airport Design Editor. Why they work for some and not others is still a mystery.
A small update, I have finished Saipan and most of Tinian in my attempt to make Marianas 1945 compatible with Prepar3D v2.1 and 2.0. Those with questions and wishing communication on this matter don't forget my email listed in the Readme file.
Thanks for the offer Joe, you are commissioned as a tester. Having someone as a tester that has experienced the problem is essential to finding the answers. Joe my installation is essentially the same as yours. FTX Global cause the tree issue on Iwo Jima. I published a fix for that that seemed to work. I simply installed a landclass under the runways that had no trees. It definitely seems that part of the problem is with the excludes in Airport Design Editor. Why they work for some and not others is still a mystery.
A small update, I have finished Saipan and most of Tinian in my attempt to make Marianas 1945 compatible with Prepar3D v2.1 and 2.0. Those with questions and wishing communication on this matter don't forget my email listed in the Readme file.
jojohnson9
Charter Member 2016
As one final effort, I deleted all Marianas 1945 files. I downloaded again and reinstalled. Ran without excludes, same tree problems. Installed the exclusions and have identical tree problems. But it seems that I am the only one having this trouble, so I wouldn't spend more time trying to fix.
Thanks for the efforts...I'll fly to the Solomons now.
Thanks for the efforts...I'll fly to the Solomons now.
After quite a bit of flying this morning around the islands, I have found that Joe's exclusions do not help in my system.
I have FSXA. Mostly default. No FTX stuff installed. GEX North America installed. Lumberjack, turned off, made no difference.
I installed Tom's exclusions for Saipan and Rota. This cleared most of the trees, but still have small trees dotting the airfields.
At the moment, I have this Marianas scenery installed at the top of the list, in this order,
small
large
objects
mesh
I have not installed the shoreline mods yet.
I also have the Solomons, Truk, Iwo sceneries installed with the shoreline cfg mods.
I will post some screen shots shortly.
Harmon
Kobler
Rota
Tinian fighter
I have FSXA. Mostly default. No FTX stuff installed. GEX North America installed. Lumberjack, turned off, made no difference.
I installed Tom's exclusions for Saipan and Rota. This cleared most of the trees, but still have small trees dotting the airfields.
At the moment, I have this Marianas scenery installed at the top of the list, in this order,
small
large
objects
mesh
I have not installed the shoreline mods yet.
I also have the Solomons, Truk, Iwo sceneries installed with the shoreline cfg mods.
I will post some screen shots shortly.
Harmon
Kobler
Rota
Tinian fighter
Really appreciate the input Robert. I have just had a major break through in the making Marianas 1945 compatible with P3D v2.1. I am thinking this could have an effect on both P3D v2.1 and FSX. I will get back to you soon. Check for a private message soon. Thanks!!
It occurs to me that I have seen this problem with trees and bushes appearing when Orbx NA scenery is being used. I think I had to turn it off because I was getting trees and bushes on the runways at add-on Danang and at some Canadian add-on around Vancouver. For those experiencing this issue try turning off your Orbx scenery and see if that cures the problem.
I have
Mariana Islands Objects
Marianas 1945 Mesh
Northern Marianas Large
Northern Marianas Small
Objects is is the lowest number 103
Small is the highes number 106 and
Marianas Boat Traffic is 107
Mine works fine.
It is also the highest priority of the Pacific stuff (everything else is 108 or higher), but everything else (Solomons, Truk, Iwo and Chichi) are all disabled.
Dave
Mariana Islands Objects
Marianas 1945 Mesh
Northern Marianas Large
Northern Marianas Small
Objects is is the lowest number 103
Small is the highes number 106 and
Marianas Boat Traffic is 107
Mine works fine.
It is also the highest priority of the Pacific stuff (everything else is 108 or higher), but everything else (Solomons, Truk, Iwo and Chichi) are all disabled.
Dave
As mal998 mentioned, Orbx and FTX scenery definitely has an effect on many a scenery, mine included. But it is not the entire issue. Still testing and working on the problem.
One bright note, I have Marianas 1945 working almost perfectly in Prepar3D v2.1. There are still some minor issues with some objects (older probably FS9 converted) and a few effects that simply don't work in v2.1. We are getting there.
Robert41 is helping with a couple tests since the fix by Joe didn't help his setup. Thanks to all for your patience. Those with no issues, enjoy.
One bright note, I have Marianas 1945 working almost perfectly in Prepar3D v2.1. There are still some minor issues with some objects (older probably FS9 converted) and a few effects that simply don't work in v2.1. We are getting there.
Robert41 is helping with a couple tests since the fix by Joe didn't help his setup. Thanks to all for your patience. Those with no issues, enjoy.
In the scenery database list, FTX global vector scenery (or any other of that type) must be __below__ any other scenery addons, because it will overwrite anything that sits below it.
The best place for it would be just above the last default scenery entry. The scenery db is a layered system that has to be read from the bottum up - any entry overwrites all lower ones of the same class (e.g. vector / mesh).
But regarding FTX or other global vector changes, even deactivating it won't entirely disable it, because there are still the changes it makes in the terrain.cfg as well as potential texture replacements.
I think we're slowly getting a picture here. Thanks for your input, guys!
Best,
Mark
The best place for it would be just above the last default scenery entry. The scenery db is a layered system that has to be read from the bottum up - any entry overwrites all lower ones of the same class (e.g. vector / mesh).
But regarding FTX or other global vector changes, even deactivating it won't entirely disable it, because there are still the changes it makes in the terrain.cfg as well as potential texture replacements.
I think we're slowly getting a picture here. Thanks for your input, guys!
Best,
Mark
