soundrats Posted December 21, 2013 Share Posted December 21, 2013 Hello, after installing FTX Global I run into a problem with my beloved destination ENBR. Please see the pic. If I delete the FTX entries out of my terrain.cfg I do not have this problem. As soon as I put them back the problem is back. Please tell me what to do. Kind Regards Tom Weber Link to comment Share on other sites More sharing options...
JohnR Posted December 21, 2013 Share Posted December 21, 2013 Check your insertion Point within FTX Central and ensure your Scenery Addons are above FTX Link to comment Share on other sites More sharing options...
soundrats Posted December 21, 2013 Author Share Posted December 21, 2013 Check your insertion Point within FTX Central and ensure your Scenery Addons are above FTX Thnx for your answer. But this I tried at first with no result. All FTX / ORB files are below the addon sceneries I have. As soon as I have the ORBX entries in my terrain.cfg this problem occurs. Kind Regards Tom ps. my FTX order below all my Addon sceneries FTXAA_ORBXLIBS ORBX!OPENLC_EUROPE1 ORBX!OPENLC_NAMERICA1 ORBX!OPENLC_BASE FTX_NA_PNW05_SCENERY FTX_NA_PNW06_CVX FTX_NA_PNW07_MESH FTX_NA_PNW08_CUSTOM Link to comment Share on other sites More sharing options...
soundrats Posted December 21, 2013 Author Share Posted December 21, 2013 I need a specialist for solving this issue. Does nobody else have this problem? Maybe it is only one entry in the terrain.cfg or a wrong xxx.bgl. Maybe it is causing other problems somewhere else. To solve this is my little christmas wish to ORBX.Thnx and Kind Regards Tom : Link to comment Share on other sites More sharing options...
soundrats Posted December 22, 2013 Author Share Posted December 22, 2013 I did more investigation. I deinstalled everything for FTX, I deinstalled Ultimate Terrain all Regions and took a brandnew terrain.cfg. Then I installed FTX global 1.10 and 1.20. After install the FTX Central opened with the green arrow on FTX Global. I closed it without pressing apply. I opend FSX ENBR and evrything looks fine. Ok so far. I installed Ultimate Terrain 1.5 opened FSX and evrything was fine. After closing FSX I opened FTX Central and pressed Apply for FTX Global. The Problem was back and I could do nothing to get rid of it. Maybe this helps the FTX support getting an idea whats wrong. Kind Regards Tom Weber Link to comment Share on other sites More sharing options...
soundrats Posted December 23, 2013 Author Share Posted December 23, 2013 I have to add the info that I did install the Island Demo. But I deinstalled it after I read about to much problems caused by this scenery. Especially Norway was mentioned in one forum topic. Kind Regards Tom Link to comment Share on other sites More sharing options...
soundrats Posted December 26, 2013 Author Share Posted December 26, 2013 Hello FTX admins, developer, It becomes a bit more light in the ENBR problem. I did a complete reinstall of the default scenery folder and used a brand-new terrain.cfg. After installing FTX Global 1.10 and 1.20 the FTX Central opened and cause it was set to FTX Global and active I did not hit Apply. I opened FSX looked at the scenery order, fine. So I started FSX looked for ENBR and every was fine. I closed FTX and opened FTX Central to choose Vectore Lights. I hit Apply closed Central and started FSX - same problem back at ENBR. Now I ask you FTX members for help - cause it seems there is a problem in FTX GLOBAL or FTX CENTRAL. Kind Regards Tom Link to comment Share on other sites More sharing options...
soundrats Posted December 27, 2013 Author Share Posted December 27, 2013 Hm, I see there are FTX developers around. May I kindly ask you for an answer or help with this issue. Kind Regards Tom Link to comment Share on other sites More sharing options...
Holger Sandmann Posted December 27, 2013 Share Posted December 27, 2013 Hi Tom, it doesn't seem that there are other people using Bergen in combination with FTX Global so it's difficult to tell whether the issue is with your specific setup. Either way there's no guarantee that FTXG is compatible with all other add-ons. I don't own Bergen either but from your screenshot it looks to me as if it excludes the default water locally and then replaces it with its own water polygon. For some reason that water poly isn't displayed as water with FTX Global, which is odd because the only thing Global alters about the default waterbody definitions in terrain.cfg is to get rid of the automatic switching to rock textures of steeper sections of rivers. Specifically, in the Texture blocks 194-199 it changes "Textures=OCEAN_SEA_LARGE_LAKE" to "Textures=OCEAN_SEA_LARGE_LAKE_0". You could try to manually remove those "_0" suffixes but I don't see how that could be the cause unless that entire replacement water poly has a slope. Alternatively you could try to find the exclude .bgl file in the Bergen \scenery folder that removes the default water and deactivate it. Hopefully its name is obvious and it doesn't exclude any other components. Cheers, Holger Link to comment Share on other sites More sharing options...
soundrats Posted December 27, 2013 Author Share Posted December 27, 2013 Thnx Holger tomorrow I will try your suggestions. Kind Regards Tom Link to comment Share on other sites More sharing options...
soundrats Posted December 27, 2013 Author Share Posted December 27, 2013 Hi Tom, it doesn't seem that there are other people using Bergen in combination with FTX Global so it's difficult to tell whether the issue is with your specific setup. Either way there's no guarantee that FTXG is compatible with all other add-ons. I don't own Bergen either but from your screenshot it looks to me as if it excludes the default water locally and then replaces it with its own water polygon. For some reason that water poly isn't displayed as water with FTX Global, which is odd because the only thing Global alters about the default waterbody definitions in terrain.cfg is to get rid of the automatic switching to rock textures of steeper sections of rivers. Specifically, in the Texture blocks 194-199 it changes "Textures=OCEAN_SEA_LARGE_LAKE" to "Textures=OCEAN_SEA_LARGE_LAKE_0". You could try to manually remove those "_0" suffixes but I don't see how that could be the cause unless that entire replacement water poly has a slope. Alternatively you could try to find the exclude .bgl file in the Bergen \scenery folder that removes the default water and deactivate it. Hopefully its name is obvious and it doesn't exclude any other components. Cheers, Holger Hello Holger, again thnx for your answer. After a reinstall of FTX Global the FTX CENTRAL switched automatically to GLOBAL ACTIV. I looked in the terrain.cfg and the entries you mentioned looked like this: Textures=OCEAN_SEA_LARGE_LAKE_0. I started my testflight and everythnig was ok. I saved this terrain.cfg and hit the apply button in the FTX CENTRAL. Notepad informed me that the terrain.cfg was changed by another application (FTX CENTRAL) of course. Still the entries are with the xxxx_0. nothing changed here. But starting the testflight the problem was back. I put the saved terrain.cfg (from before pressing apply) and the problem was gone. So definetely the problem is in the terrain.cfg and occurs when pressing the apply button in the FTX CENTRAL. Now I wonder what entry makes it all. Maybe you know how to check this. I will attach my terrain.cfg before and after pressing apply (remember FTX Global was already active after installation - but without the problem) As I do not see a button for uploading files I attach a link to my server: https://www.hidrive.strato.com/lnk/u4svHfMs Thnx for helping Kind Ragrds Tom Link to comment Share on other sites More sharing options...
soundrats Posted December 28, 2013 Author Share Posted December 28, 2013 Hello Holger, I found the terrain.cfg entries which are causing my ENBR problems. It is located in Texture 164. Before pressing APPLY // Airport Backgrounds (FSX) - Flatten + MaskClassMap + ExcludeAutoGen[Texture.164]Name=Airport_Backgrounds_Flatten_MaskClassMap_ExcludeAutoGenColor=FFFFFF00guid={46BFB3BD-CE68-418E-8112-FEBA17428ACE}FlattenMode=flatFlattenPriority=51000LandClassRemapType=airportExcludeAutogen=YesRenderToTexture=NoRenderPriority=200000Water=No After pressing APPLY // Airport Backgrounds (FSX) - Flatten + MaskClassMap + ExcludeAutoGen[Texture.164]Name=Airport_Backgrounds_Flatten_MaskClassMap_ExcludeAutoGenColor=FFFFFF00guid={46BFB3BD-CE68-418E-8112-FEBA17428ACE}FlattenMode=flatFlattenPriority=51000LandClassRemapType=noneExcludeAutogen=YesRenderToTexture=NoRenderPriority=200000Water=NoTextures=GRASS_SKIRTING_1 Now the question is what to do with this. Of course I want to have FTX GLOBAL working properly. I have no idea what this enreis are really doing. But maybe you as a scenery prof knwo already the solution. Thnx and Kind Regards Tom Link to comment Share on other sites More sharing options...
soundrats Posted December 31, 2013 Author Share Posted December 31, 2013 Hello ORBX - any further suggestions concerning the ENBR problem after I found the FTX CENTRAL terrain.cfg entry which causes the problem? Kind Regards Tom Link to comment Share on other sites More sharing options...
Holger Sandmann Posted December 31, 2013 Share Posted December 31, 2013 Hi Tom, I'm not sure how that particular change can cause the issue with Bergen. All that entry does is change the texture of the airport grass skirting polygons from a flexible type (that switches with the underlying landclass) to a fixed grass type. Doing so should not change water to land let alone outside an airport boundary. And I don't understand why the Bergen team would have used that kind of polygon over a body of water, if that is really the issue here. In any case and as stated above it's very unlikely that the FTX Global team would change their custom terrain.cfg entries for a single airport. Thus, my suggestion still is to dig through the Bergen bgl files and try to find and deactivate their polygon and/or excludes. Cheers, Holger Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.