P51 Posted August 17, 2018 Share Posted August 17, 2018 Dear ORBX, There are square artifacts visible during flights, it seems like it's showing only after about 15 min of flight. see this screenshot https://imgur.com/a/p8Nm535 My config is: Prepar3D v4.3 All instalation with FTX3, no extra scenery accept ORBX scnery Everything in the global range installed and some regions usage of occulus rift in native virtual reality mode, single pass on, but the artifact are also visable with VR off. My brotherwho has the exact same config as me, is experiencing the same artifacts. Please your support on this one thnks in advance Martijn Link to comment Share on other sites More sharing options...
Goose.- Posted August 17, 2018 Share Posted August 17, 2018 Same issue as mine it looks like. Link to comment Share on other sites More sharing options...
bobterri6 Posted August 17, 2018 Share Posted August 17, 2018 I descended down very closely to one of these squares and took a screenshot. Very interesting. As I got close the lower left corner turned into, what looks like, a snow texture and the rest of the square looks like water texture. Link to comment Share on other sites More sharing options...
P51 Posted August 18, 2018 Author Share Posted August 18, 2018 That's exactly what we are experiencing too, water where there should be land, but also squares of land where thare should be water. Your screenshot is showing the problem better than mine. Link to comment Share on other sites More sharing options...
Nick Cooper Posted August 18, 2018 Share Posted August 18, 2018 Hello, the exact location of these would help. You could try deleting or renaming C:\ProgramData\Lockheed Martin\Prepar3D v4\terrain.cfg. Run P3D once and see if the anomalies are still there. If not, close P3D and run FTX Central. Wait until it has "activated Orbx scenery". Then try again. Link to comment Share on other sites More sharing options...
P51 Posted August 19, 2018 Author Share Posted August 19, 2018 Hello Nick, I renamed the terrain.cfg, to terrain.old.cfg starting P3D and the Anomalies are gone Than an other strange thing happened: after running FTX, P3D is not loading anymore, and gets stuck in the splash screen. (P3D was running as adminstrator). I looked at the scenery.cgf in C:\ProgramData\Lockheed Martin\Prepar3D v4 and compared it with an old scenery.cfg file from a backup: first lines from the old backup: [General] Title=Prepar3D Scenery Description=Prepar3D Scenery Areas Data Clean_on_Exit=TRUE [Area.001] Title=Default Terrain Texture_ID=1 Local=Scenery\World Active=TRUE Required=TRUE Layer=1 [Area.002] Title=Default Scenery Local=Scenery\BASE Active=TRUE Required=TRUE Layer=2 First lines from the newly generated scenery.cfg after running FTX3: [Area.000] Title=ORBX!OPENLC_zBASE Local=ORBX\FTX_OLC\OLC_AA Active=TRUE Required=FALSE Layer=0 [Area.001] Title=ORBX!OPENLC_SAMERICA2 Local=ORBX\FTX_OLC\OLC_SA2 Active=TRUE Required=FALSE Layer=1 [Area.002] Title=ORBX!OPENLC_SAMERICA1 Local=ORBX\FTX_OLC\OLC_SA1 Active=TRUE Required=FALSE Layer=2 P3D wasn't running with this new scenery.cfg, so I made some changes "by hand", adding in the [General] part en changing the [Area.000] to [Area.001]. So that it looked like this: [General] Title=Prepar3D Scenery Description=Prepar3D Scenery Areas Data Clean_on_Exit=TRUE [Area.001] Title=ORBX!OPENLC_zBASE Texture_ID=1 Local=ORBX\FTX_OLC\OLC_AA Layer=1 Active=TRUE Required=FALSE [Area.002] Title=ORBX!OPENLC_SAMERICA2 Local=ORBX\FTX_OLC\OLC_SA2 Layer=2 Active=TRUE Required=FALSE After the changes P3D was running again, don't know what is causing this, but it seemed that there can't be a [Area.000] entry in the scenery.cfg file. Also, some parts of the scenery looked a lot better (like asia), and the anomalies are gone. But every time I am running FTX, I'll have to change the scenery.cfg file by hand, because FTX is overwriting it (in the wrong way I suppose). is there a sollution so that FTX is making the scenery.cfg file in the correct way again?? Best regards Martijn Best regards Link to comment Share on other sites More sharing options...
Nick Cooper Posted August 19, 2018 Share Posted August 19, 2018 Hello, you will need to reset the Insertion Point in FTX Central to cure that. Here is a guide. Link to comment Share on other sites More sharing options...
P51 Posted August 19, 2018 Author Share Posted August 19, 2018 That was the sollution, thanks for your support best regards Martijn Link to comment Share on other sites More sharing options...
bobterri6 Posted August 19, 2018 Share Posted August 19, 2018 Sigh!!!! Unfortunately this did not work for me. Any other ideas? Link to comment Share on other sites More sharing options...
P51 Posted August 23, 2018 Author Share Posted August 23, 2018 At first it looked like it was resolved, but unfortunately the squares have returned, or still present. So still no solution, please your help again. best regards, Martijn Link to comment Share on other sites More sharing options...
Vin Posted August 23, 2018 Share Posted August 23, 2018 I experienced the square anomalies as well, so I tried renaming terrain.cfg to terrain.old.cfg. The file was regenerated after running Prepar3d, and after running the vector autocorrection tool all seemed well, but today the same issue unfortunately reappeared. The location is in Norway (OrbX Norway). Link to comment Share on other sites More sharing options...
Nick Cooper Posted August 23, 2018 Share Posted August 23, 2018 Hello, you might try force migration on the FTX Central settings page. Then run the migration troubleshooter and see what it says. ORBX\Troubleshooter\MigrationTroubleshooter.exe Link to comment Share on other sites More sharing options...
P51 Posted August 24, 2018 Author Share Posted August 24, 2018 Orbx Migration Troubleshooter ==================================== REGIONS Australia NOT INSTALLED Central Rocky Mountains NOT INSTALLED England MIGRATED CORRECTLY FTX Global MIGRATED CORRECTLY Ireland NOT INSTALLED Northern California MIGRATED CORRECTLY Northern Ireland NOT INSTALLED Norway MIGRATED CORRECTLY Northern Rocky Mountains NOT INSTALLED New Zealand North Island NOT INSTALLED New Zealand South Island MIGRATED CORRECTLY FTX Global openLC Europe MIGRATED CORRECTLY Pacific Fjords NOT INSTALLED Pacific Northwest MIGRATED CORRECTLY Southern Alaska NOT INSTALLED Southern California MIGRATED CORRECTLY Scotland MIGRATED CORRECTLY Wales MIGRATED CORRECTLY ==================================== All region files exist. All files valid, MD5 hashes checked. Thanks for the response This is the result from the troubleshooter, I just took it for a little spin, and haven't seen any artifact, but it seems like its appearing only during a longer flight time, often in descend. if it's showing again, I'll post another reply best regards Martijn Link to comment Share on other sites More sharing options...
Vin Posted August 25, 2018 Share Posted August 25, 2018 Thanks for the reply Nick, I ran the force migration tool as advised. Results from the migration troubleshooter are below: Orbx Migration Troubleshooter ==================================== REGIONS Australia NOT INSTALLED Central Rocky Mountains NOT INSTALLED England MIGRATED CORRECTLY FTX Global MIGRATED CORRECTLY Ireland NOT INSTALLED Northern California MIGRATED CORRECTLY Northern Ireland NOT INSTALLED Norway MIGRATED CORRECTLY Northern Rocky Mountains NOT INSTALLED New Zealand North Island NOT INSTALLED New Zealand South Island MIGRATED CORRECTLY FTX Global openLC Europe MIGRATED CORRECTLY Pacific Fjords NOT INSTALLED Pacific Northwest MIGRATED CORRECTLY Southern Alaska NOT INSTALLED Southern California MIGRATED CORRECTLY Scotland MIGRATED CORRECTLY Wales MIGRATED CORRECTLY ==================================== All region files exist. All files valid, MD5 hashes checked. I will do the same as P51, on my next longer flight I will keep an eye out and post here if I find more anomalies. Kind regards Vin Link to comment Share on other sites More sharing options...
Nick Cooper Posted August 25, 2018 Share Posted August 25, 2018 Did you try this? Quote You could try deleting or renaming C:\ProgramData\Lockheed Martin\Prepar3D v4\terrain.cfg. Run P3D once and see if the anomalies are still there. If not, close P3D and run FTX Central. Wait until it has "activated Orbx scenery". Then try again. Link to comment Share on other sites More sharing options...
P51 Posted August 26, 2018 Author Share Posted August 26, 2018 Dear Nick, Did all you proposed, unfortunaletly no sollution (yet) Please your help once again. best regards Martijn Link to comment Share on other sites More sharing options...
Vin Posted August 26, 2018 Share Posted August 26, 2018 Hello Nick I have already done this, as you suggested in the beginning of this topic. So unfortunately the anomalies have returned in spite of: - the terrain.cfg renaming and regeneration by Prepar3d - rerun of the migration tool This is really starting to feel like a bug, as they seem to appear at random, and seem to consistently start after a few minutes of flight and persist for the rest of the flight. Also they do not seem to have a fixed location, if you fly the same route, the anomalies appear in a different location. I hope you can help. Thanks, Vin Link to comment Share on other sites More sharing options...
bobterri6 Posted September 7, 2018 Share Posted September 7, 2018 Mine never went away either. Link to comment Share on other sites More sharing options...
pf21414 Posted September 7, 2018 Share Posted September 7, 2018 I am having the same issue and have tried all the posted solutions as well. They are still there. Link to comment Share on other sites More sharing options...
M-Sauce Posted October 16, 2018 Share Posted October 16, 2018 This topic is marked as resolved? Can anyone comment what they did to resolve it? Last posts from all involved seems like Nick's recommendations did not solve the issues. I'm asking as I am experiencing the same or similar issue. Link to comment Share on other sites More sharing options...
Nick Cooper Posted October 16, 2018 Share Posted October 16, 2018 Hello, a quick look at post number 8 would have shown you that the topic was indeed resolved but that you and others chose to add to the resolved topic. If you have an unresolved problem, please open a topic of your own. Link to comment Share on other sites More sharing options...
M-Sauce Posted October 16, 2018 Share Posted October 16, 2018 8 hours ago, Nick Cooper said: Hello, a quick look at post number 8 would have shown you that the topic was indeed resolved but that you and others chose to add to the resolved topic. If you have an unresolved problem, please open a topic of your own. Actually Nick, if you read past post #8, you will see that the author (P-51) continued to experience the same problem. So not really resolved. Since it showed the matter as "solved", I posted here hoping that someone would advise how they solved their problem. I came upon this thread looking for answers since I am suffering from the exact same issue that they where (albeit in a different location). I posted my own topic in the Global LC forums, but have not found a solution to this problem yet. Any ideas? Link to comment Share on other sites More sharing options...
M-Sauce Posted October 23, 2018 Share Posted October 23, 2018 Bump. Can we get this sorted please? Issue not resolved. Any ideas? Kind of annoying to see these black squares. Link to comment Share on other sites More sharing options...
Nick Cooper Posted October 23, 2018 Share Posted October 23, 2018 I have marked the topic as active again but have no further suggestions. Hopefully one of the better qualified staff will find the time to look here and offer a solution. Link to comment Share on other sites More sharing options...
M-Sauce Posted October 24, 2018 Share Posted October 24, 2018 Thanks Nick! I’ve run out of solutions myself as well. Link to comment Share on other sites More sharing options...
Juanjo Posted October 27, 2018 Share Posted October 27, 2018 I experience the same problema but only at North America ….. I have done all the suggestions and I find that the Migration Troubleshooter report includes FTX Global openLC Europe but not includes FTX Global openLC North America, FTX Global openLC South America, Trees HD, Vector …...…. is this normal ? Thanks J J Gómez Prieto IVAO : 142928 Link to comment Share on other sites More sharing options...
Nick Cooper Posted October 27, 2018 Share Posted October 27, 2018 Hello, yes, it is normal. Only older products need to be migrated. Newer ones already are. Link to comment Share on other sites More sharing options...
Juanjo Posted October 27, 2018 Share Posted October 27, 2018 Ok Nick …. thanks But I experience the same problema of the black polygons ….. but only at North America Nowadays I fly a VFR IVAO Tour in the west coast of USA and another one, also of IVAO, along all South America, and I have the problema with the first one but not with the second. I have done all the suggestions ( …. terrain.cfg, Migration, …. ) but the problema remains here How can I solve the problema ? Thanks again and regards J J Gómez Prieto IVAO : 142928 Link to comment Share on other sites More sharing options...
Nick Cooper Posted October 28, 2018 Share Posted October 28, 2018 Hello, perhaps reinstall Open LC NA? Link to comment Share on other sites More sharing options...
Juanjo Posted October 28, 2018 Share Posted October 28, 2018 Thanks Nick …. done and solved …. I hope …. I'm sure …. Thanks again and regards J J Gómez Prieto IVAO 142928 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.