Nick Cooper Posted June 10, 2019 Share Posted June 10, 2019 Hello, I can confirm that I am seeing the same anomalies. It looks like the black areas are night textures. I have asked the developers. Link to comment Share on other sites More sharing options...
carlosqr Posted June 10, 2019 Share Posted June 10, 2019 20 hours ago, Ridvan Celik said: @Richard Lincoln is it normal for Central to always download some files after clicking verify and scanning is complete? +1 I have the same question as some times you think you have all in place and if by chance you did a verification the Central seems to download something else... Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 10, 2019 Share Posted June 10, 2019 Hello. It is normal for "verify files" to download whenever it is run. Verify files is a trouble shooting function, not intended to be run unless there is a problem. Link to comment Share on other sites More sharing options...
JohnVulcan Posted June 11, 2019 Share Posted June 11, 2019 A Solution? I was suffering the same problems on my first flight, but then found that FTX Central had not uninstall Australia V1 as rightly or wrongly I'd rather assumed that it would. After uninstalling V1 the problem has been resolved on my system anyway. Link to comment Share on other sites More sharing options...
jring2 Posted June 13, 2019 Share Posted June 13, 2019 Same thing here. Not a location problem. . its an Australia Version 2 problem. These appear anywhere I fly to varying degrees. Water - land makes no difference. Nice product though. Hopefully this can be resolved. Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 13, 2019 Share Posted June 13, 2019 2 hours ago, jring2 said: Same thing here Hello, your problem is not the same thing. Despite your screen shot, I have found this airstrip, YCWL and it looks fine. You might try refreshing your terrain.cfg file. Link to comment Share on other sites More sharing options...
Flukey Posted June 13, 2019 Share Posted June 13, 2019 4 hours ago, jring2 said: Same thing here. Not a location problem. . its an Australia Version 2 problem. These appear anywhere I fly to varying degrees. Water - land makes no difference. Nice product though. Hopefully this can be resolved. Did you previously have V1 installed along with Holgermesh for Australia? If so did you uninstal them as instructed? If not please do so. If so please go to your ORBX folder within P3Dv4 and make sure there are no files left over as per this post... For me FTX central did not properly uninstall Holgermesh so had to remove this myself If you haven't done as above please advise if issue persist once completed. Link to comment Share on other sites More sharing options...
Ridvan Celik Posted June 15, 2019 Author Share Posted June 15, 2019 Any news on the black textures ? Link to comment Share on other sites More sharing options...
UA991 Posted June 16, 2019 Share Posted June 16, 2019 Thought I'd add my experience to the mix. The following pictures show what I am getting as viewed directly above YMAV. The same happens if I have Orbx YMAV active. If I turn off folder FTXAU48_CUSTOM the issue is immediately corrected. However, I don't know what is then missing. Also, based on the contents of folders FTXAU18_CUSTOM, FTXAU28_CUSTOM, FTXAU38_CUSTOM and FTXAU48_CUSTOM, I suspect each folder will have an impact on different parts of AUv2. I had just acquired a new PC, so AUv1, Holgermesh or any of the Orbx airports had not been installed prior to installation of AUv2. Terrain.cfg refresh has been done, etc to no avail. Look forward to a solution. Thanks, Darryl Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 16, 2019 Share Posted June 16, 2019 Hello, Australia v2 does not include FTXAU18_CUSTOM, FTXAU28_CUSTOM, FTXAU38_CUSTOM and FTXAU48_CUSTOM which are most likely the Tasmania demo folders. In any event, you need to remove them, both from your PC and from your scenery library. To try to make life easier, all the Australia V2 folders are named FTXAUv2 Link to comment Share on other sites More sharing options...
UA991 Posted June 16, 2019 Share Posted June 16, 2019 Thanks Nick. I wondered the same thing. So I uninstalled AUv2, all Aust Orbx airports and made sure only the Orbx Libaries were in the FTX_AU directory. I then reinstalled AUv2 (re-download) and those four folders returned. When you look at the contents of those folders they contain files for all parts of Australia. I've also never installed the Tasmania demo. Here's the AU48 folder for example. So I guess the question is how these folders managed to be installed? I'm sure it'll be sorted. Regards, Darryl Link to comment Share on other sites More sharing options...
chumley Posted June 16, 2019 Share Posted June 16, 2019 I just downloaded and installed AUv2 this evening. My FTX_AU folder contains 100 folders and 33,049 files. There is no evidence of a FTXAU_Custom folder. I trust you removed v1 beforehand. I have looked at P3Dv3 and there is a FTXAU48_Custom folder in there and it contains many, if not all, of the files shown in your image. Link to comment Share on other sites More sharing options...
The Merowinger Posted June 16, 2019 Share Posted June 16, 2019 I just tried to evaluate the situation YMAV in post #49. No black textures, even the landclass looks different. Maybe there are some leftovers from V1 with you? I only didn't delete the files from V1 but I deinstalled V1 in FTXC. mfg Kai Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 16, 2019 Share Posted June 16, 2019 1 hour ago, UA991 said: Thanks Nick. I wondered the same thing. So I uninstalled AUv2, all Aust Orbx airports and made sure only the Orbx Libaries were in the FTX_AU directory. I then reinstalled AUv2 (re-download) and those four folders returned. Darryl Hello Darryl, I have installed Australia v2 in both FSX and P3D and like the other contributors, have never seen the addition os any folders that are not named v2. I don't think that there is a problem with the installer. In any event, just delete the FTXAU18_CUSTOM, FTXAU28_CUSTOM, FTXAU38_CUSTOM and FTXAU48_CUSTOM folders, remove their scenery library entries and it should work correctly for you too. Link to comment Share on other sites More sharing options...
Holger Sandmann Posted June 16, 2019 Share Posted June 16, 2019 Hi Rydvan, Quote Any news on the black textures ? I believe I've discovered the cause of the issue and am working on a fix. I'll keep you posted. Cheers, Holger Link to comment Share on other sites More sharing options...
UA991 Posted June 17, 2019 Share Posted June 17, 2019 OK Nick. I'll just delete those folders. But per my first post, AUv1 has never been installed on this computer. I do though have a backup of my old computer and used some of that to reduce download size when I was installing multiple Orbx airports. (I gave FTX Central the airport backup location during install. Pretty silly in light of unlimited downloads and high speed internet but I digress! ) I suspect FTX Central now thinks it has to restore those folders and does so at the same time AUv2 is installed. Is there another file somewhere that makes FTX Central think it needs to do this? Just a thought that may help track what the issue might be. I'd have a hunt myself but don't have access to my PC for a few days. Something called work......! Thanks, Darryl. Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 17, 2019 Share Posted June 17, 2019 Hello, yes I remember work. You should delete any of scenerylib_AU_BLUE.cfg scenerylib_AU_RED.cfg scenerylib_AU_GREEN.cfg scenerylib_AU_GOLD.cfg that you might find in the ORBX\scripts folder. Link to comment Share on other sites More sharing options...
corinoco Posted June 17, 2019 Share Posted June 17, 2019 Hi All, I've got the same 'black scenery' issue, also near YSRI. I have done a totally fresh install, in this order: P3D4.5.12 Acedemic, FTX Global, FTX Vector, FTX Trees, FTX Australia V2. My settings in FTX Vector are all options for roads/rail checked, 'I have FTX Australia' also checked (confirmed, Sydney Harbour Bridge looks correct) The black textures flicker quite badly - the common factor is these areas have small dams and might be classed as swamps? There are actually some real areas classed as marshland around Bilpin (the area where the black textures occur around YSRI) so maybe that is the key? Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 17, 2019 Share Posted June 17, 2019 21 hours ago, Holger Sandmann said: Hi Rydvan, I believe I've discovered the cause of the issue and am working on a fix. I'll keep you posted. Cheers, Holger Link to comment Share on other sites More sharing options...
Ridvan Celik Posted June 17, 2019 Author Share Posted June 17, 2019 On 6/17/2019 at 1:45 AM, Holger Sandmann said: Hi Rydvan, I believe I've discovered the cause of the issue and am working on a fix. I'll keep you posted. Cheers, Holger Hi Holger, Thanks for the update, glad you’ve found the problem. I look forward to the fix. Best regards, Ridvan Celik Link to comment Share on other sites More sharing options...
Striker Posted June 17, 2019 Share Posted June 17, 2019 I flew YPAD-YPPH-YBRM-YBAS-YPDN, black squares about 20% of scenery and orange squares at night, will post images when I can. I downloaded and installed AU v2 manually because FTX central was only giving me 124 kb/s D/L. After manual install verified files no issues, disabled freezing water in LC. Can't believe the amount of black squares in AU2, haven't been able to appreciate the added features because of this Steve Link to comment Share on other sites More sharing options...
rf253 Posted June 18, 2019 Share Posted June 18, 2019 15 hours ago, Nick Cooper said: Hello, yes I remember work. You should delete any of scenerylib_AU_BLUE.cfg scenerylib_AU_RED.cfg scenerylib_AU_GREEN.cfg scenerylib_AU_GOLD.cfg that you might find in the ORBX\scripts folder. Hi Nick, being one of those who had the issue where v2 installed without v1 uninstalling first also checked the User Documents folder and had to remove v1 Australia.pdf and also checked the Versions folder to remove any remnants of v1 there also. Just checked Scripts folder as you have indicated for any v1 then saw I still had scenerylib_ AU_HOLGERMESH.cfg still there. So assume that with AU Holgermesh uninstalled this would also need to be deleted from the folder ? Link to comment Share on other sites More sharing options...
Striker Posted June 18, 2019 Share Posted June 18, 2019 Images of previous post YPAD-YPPH-YBRM-YBAS-YPDN looks like other textures bleeding through Link to comment Share on other sites More sharing options...
rf253 Posted June 18, 2019 Share Posted June 18, 2019 Not sure where we report discrepancies or anomalies identified or found re ground textures so please move if this is not the correct post for it but identified a couple along the beaches around Newcastle, North of YPEC. The road depict fairly accurately here as does the shoreline shape but on what are natural rock formations at sea level the platforms show houses on them. These platforms have ocean baths in them which date back almost 100 yrs. here are some comparison shots using Google Earth and Aus v2 captures of the rock platforms Merewether Baths were built into the rock formation Aus v2 Bar Beach / Cooks Hill where the 'Strzelecki Lookout' is located also Newcastle's Memorial Walkway which was built along the ridge down to Bar Beach in recent years and notice that the walkway (highlighted in pic) has been modeled into the scenery. The rock formation below again shows houses there which does not reflect the area. Other rock platforms along the coast look fine with no housing showing on them Aus v2 Newcastle Ocean Baths near Nobbys Aus v2 Link to comment Share on other sites More sharing options...
Striker Posted June 18, 2019 Share Posted June 18, 2019 It looks like several layers are trying to load at once. I have Fly Tampa Sydney but can't fined the LC mentioned to disable, nothing in the Fly Tampa settings. Can someone point me to the correct folder. YPDN-YBAS-YAYE Inland seas in the Desert Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 18, 2019 Share Posted June 18, 2019 Your symptoms are similar to either having a problem with the terrain.cfg file or having both V1 and V2 installed at the same time. Link to comment Share on other sites More sharing options...
Striker Posted June 18, 2019 Share Posted June 18, 2019 14 hours ago, Nick Cooper said: Your symptoms are similar to either having a problem with the terrain.cfg file or having both V1 and V2 installed at the same time. Nick, That thought crossed my mind but I'm not sure how to remove either one, I am confused by all the suggestions in this thread. I would have thought using FTX Central to remove AUv1 before installing AUv2 would have been sufficient, but not so. I don't want to start deleting files or cfg's for fear of deleting the wrong ones. Steve Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 18, 2019 Share Posted June 18, 2019 Here is the way to refresh the terrain.cfg file. Link to comment Share on other sites More sharing options...
Striker Posted June 18, 2019 Share Posted June 18, 2019 Thanks Nick, Tried all fixes in those posts, still getting black squares but not as many, here's an aerial around YAYE, Connellan Airport. I think I'll revert back to AU1 and follow this thread for a definitive fix for AUv2 - AUv1 was working beautifully. Steve Link to comment Share on other sites More sharing options...
Flukey Posted June 19, 2019 Share Posted June 19, 2019 16 hours ago, Striker said: It looks like several layers are trying to load at once. I have Fly Tampa Sydney but can't fined the LC mentioned to disable, nothing in the Fly Tampa settings. Can someone point me to the correct folder. Lockheed Martin\Prepar3D v4\FlyTampa\Sydney_LC folder - file yssy_lc.bgl Link to comment Share on other sites More sharing options...
Striker Posted June 19, 2019 Share Posted June 19, 2019 2 minutes ago, Flukey said: Lockheed Martin\Prepar3D v4\FlyTampa\Sydney_LC folder - file yssy_lc.bgl Thanks Mate Link to comment Share on other sites More sharing options...
corinoco Posted June 19, 2019 Share Posted June 19, 2019 Is the 'delete the terrain.cfg file' the fix for the 'black blotches' issue; or is there still a fix in progress on that issue? Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 19, 2019 Share Posted June 19, 2019 Hello, the terrain.cfg fix is for the extensive misplaced squares, like this: The "black blotches" are quite different and the solution for them is being worked on. Link to comment Share on other sites More sharing options...
Striker Posted June 19, 2019 Share Posted June 19, 2019 Nick, Deleted the terrain.cfg(copied) then I followed your post and as per Close P3D v4, delete that file and then start P3D v4, which will create a new terrain.cfg file. Close P3D v4 and open FTX Central. Wait for FTX Central to display this message at the lower left. "Activating Orbx scenery...". I didn't do any of Holger's fixes for fear of wrecking all my other addon scenery and it was dated 2014 for P3Dv 2.5 and v3. Using FTX Central 3, all I did was delete AU1 as per guide then install AU v2 ...How did it get to this? from being perfectly harmonized to aesthetically awful. Here are more images after this was done Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 19, 2019 Share Posted June 19, 2019 Thanks, can you attach a copy of your scenery.cfg file please? Link to comment Share on other sites More sharing options...
rf253 Posted June 19, 2019 Share Posted June 19, 2019 Striker - did you also remove AU Holgermesh as that is only applicable to AUS v1 not needed with v2 at all. Link to comment Share on other sites More sharing options...
Striker Posted June 20, 2019 Share Posted June 20, 2019 6 hours ago, rf253 said: Striker - did you also remove AU Holgermesh as that is only applicable to AUS v1 not needed with v2 at all. .....missed that one I'll remove and advise, Nick I'm at the office at the moment I'll upload the file first chance, appreciate the help from everyone - Thanks Steve Link to comment Share on other sites More sharing options...
Striker Posted June 20, 2019 Share Posted June 20, 2019 Update. I removed AU Holgermesh, some improvements made but still issues around YAYE and YBAS. I have attached scenery.cfg pre/post Holgermesh removal for comparison. The Jetstar A320 is about 100nm south of Cairns, the aerial is of Connellan and the R22 is at Alice Springs scenery.afterHolger remove.cfg scenery.BeforeHolger remove.cfg Link to comment Share on other sites More sharing options...
Nick Cooper Posted June 20, 2019 Share Posted June 20, 2019 On 6/16/2019 at 10:25 AM, Nick Cooper said: Hello, Australia v2 does not include FTXAU18_CUSTOM, FTXAU28_CUSTOM, FTXAU38_CUSTOM and FTXAU48_CUSTOM In any event, you need to remove them, both from your PC and from your scenery library. To try to make life easier, all the Australia V2 folders are named FTXAUv2 Extract from your scenery.cfg file. Please remove your scenery.cfg file and try the one I have attached instead. I have also disabled the traffic global entry at the bottom of the library. Please don't re-enable it until you have Australia v2 working. scenery.cfg Link to comment Share on other sites More sharing options...
UA991 Posted June 20, 2019 Share Posted June 20, 2019 On 6/17/2019 at 6:28 PM, Nick Cooper said: Hello, yes I remember work. You should delete any of scenerylib_AU_BLUE.cfg scenerylib_AU_RED.cfg scenerylib_AU_GREEN.cfg scenerylib_AU_GOLD.cfg that you might find in the ORBX\scripts folder. Nick, I deleted those files and it has helped keep the AUv1 folders away. Most of the time.... Some did make a reappearance upon installing all my Australian Orbx airports. Anyway, I'm just deleting any AUv1 folders that make a re-appearance. Thanks for the help. No more black squares here. Darryl Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.