OMGEDSON Posted January 22, 2016 Share Posted January 22, 2016 Lots of flickering in the parking area, near the rocks, and at the end of the runways. Looks like the textures are battling FTX Global textures underneath. No US Cities Chicago installed and I've run the vector config tool... FSS0455035 Link to comment Share on other sites More sharing options...
Tim Harris Posted January 22, 2016 Share Posted January 22, 2016 Hi, Great shot showing the issue, looks like an elevation clash, which simulator are you using? As Alex is probably sleeping right now (about 3am there) I'll get the ball rolling on this: - Is it possible you have another APX active (from a 3rd party airport or AI traffic program), try running a file search of the main simulator folder for KCGX and note anything outside of the Orbx folder - Check terrain mesh slider is set at 5m - Also as a side-note, if you have FTX-Vector and use the frozen lake option, there is another frozen version of the photoreal which will match the frozen water seen in the top-right of your shot Link to comment Share on other sites More sharing options...
OMGEDSON Posted January 22, 2016 Author Share Posted January 22, 2016 - P3D 3.1 - All signs of KCGX are ORBX (even tried to disable the FTX AA mention of kcgx as seen below - Check, was at 5, staying at 5 - Thanks, this frozen texture is absolutely stunning! Link to comment Share on other sites More sharing options...
Orbx Flyer Posted January 22, 2016 Share Posted January 22, 2016 Not only am I getting this too...flickering at the runway thresholds, but the total downtown buildings of Chicago...blank out, upon their base textures..and then wink back in. I am correctly in ORBX Global. This got past both Alpha and Beta Teams?!?!? Jeez... Link to comment Share on other sites More sharing options...
Tim Harris Posted January 22, 2016 Share Posted January 22, 2016 Hi PNW User, you already posted your issue here Please continue there in your own thread, thanks! Link to comment Share on other sites More sharing options...
Orbx Flyer Posted January 22, 2016 Share Posted January 22, 2016 1 hour ago, Tim Harris said: Hi PNW User, you already posted your issue here Please continue there in your own thread, thanks! Tim, I was also responding here, that I also have runway and airport flickering textures. I did not target that glitch, on my whole downtown core winking in and out. Yes, I'll keep my responses, and hopefully, a fix for the building vanishing, on my own started thread. No problems. Thanks, Link to comment Share on other sites More sharing options...
Fischkopp Posted January 22, 2016 Share Posted January 22, 2016 For me, the texture flickering occurs also. It looks as if the textured objects lie exactly on the same level as the bottom photo. This leads to flickering.To better understand what I mean, here's a video. Link to comment Share on other sites More sharing options...
Nick Cooper Posted January 22, 2016 Share Posted January 22, 2016 P3D? Link to comment Share on other sites More sharing options...
Pegaso Posted January 22, 2016 Share Posted January 22, 2016 No texture anomalies for me in P3D3.1 and mesh 1 m, tried mesh 5 m, too. However I have NOT run Vector Configuration Tool. Did you? Link to comment Share on other sites More sharing options...
Fischkopp Posted January 22, 2016 Share Posted January 22, 2016 50 minutes ago, Nick Cooper said: P3D? Yep, P3D V3.1, no run of Vector Config-Tool and mesh on 5m. I have tested all mesh settings from 20m down to 1m and the texture settings from 1m down to 15 cm but the problem persists in all settings (on my system). Link to comment Share on other sites More sharing options...
Alex Goff Posted January 22, 2016 Share Posted January 22, 2016 This is a known issue with P3D native ground polygons. The FSX version uses FS2002-style ground polygons which are officially deprecated as of P3Dv3. As such I chose to go the native route for Meigs. I noticed the ground polygon tends to flicker upon first load for a second and then if any scenery settings are changed or the scenery library reloaded it will also flicker. As of yet I am not sure if there is a workaround to this. If I can find one, I will patch it in, otherwise this may be a quirk of native P3D ground polygons that can't be fixed. The best solution I can offer until then is to endure the initial flickers and after it "settles in" avoid changing scenery library sliders or reloading. Link to comment Share on other sites More sharing options...
DesertPilot Posted January 22, 2016 Share Posted January 22, 2016 Question--would deleting the scenery index and facilities files (under ProgramData\Lockheed Martin\Prepar3D\SceneryIndexes and Facilities) and the shader files (under AppData\Local\Lockheed Martin\Prepar3Dv3\Shaders) make any difference with those flickers (which I have not yet experienced myself yet at Meigs)? I myself routinely clear those files whenever updating scenery.cfg and so on. To help ensure P3D loads fresh. Link to comment Share on other sites More sharing options...
OMGEDSON Posted January 22, 2016 Author Share Posted January 22, 2016 FYI ORBX Team, it never settles. I can sit there for an hour or fly into downtown and return. Same flickering. No other orbx products have this issue in my sim. @Tim Harris @Alex Goff Link to comment Share on other sites More sharing options...
Bruce Hamilton Posted January 22, 2016 Share Posted January 22, 2016 I've had issues in the past that I've been able to correct by simply adjusting my insertion point up or down a couple slots, where do you have yours? Link to comment Share on other sites More sharing options...
Alex Goff Posted January 22, 2016 Share Posted January 22, 2016 This is one of the first native P3D ground polygons in an Orbx product, the only other I am aware of is KSQL. With the older FS2002 style ones flickering never really occurs, but because they have been deprecated switching to the newer format was chosen, there were some issues with trying to use an FS2002 polygon in P3D. I am actively looking for a solution, one other area I forgot to ask earlier though, are you using any camera tweaks in P3D? They can sometimes have issues with z-bias settings and cause flickers. That may be why testers didn't find flickers. Link to comment Share on other sites More sharing options...
OMGEDSON Posted January 22, 2016 Author Share Posted January 22, 2016 Absolutely yes I can confirm that I am using EZDOK. I will be home shortly and can test the location without it and report back. Link to comment Share on other sites More sharing options...
Alex Goff Posted January 22, 2016 Share Posted January 22, 2016 Try with EZDOK disabled and if any other users have the same issue with EZDOK only that will greatly help in targeting a potential fix Cameras in P3D can be very fickle Link to comment Share on other sites More sharing options...
OMGEDSON Posted January 22, 2016 Author Share Posted January 22, 2016 @Alex Goff I can confirm that without EZDOK launched and using default p3d camera views, there is no flickering issue. I beg you to please not ignore the importance of add-ons like EZDOK for virtual pilots...and hope we can get a fix soon. If there is anything I can assist with, please don't hesitate, we already work closely with ORBX. *You mentioned KSQL being based on the same, i work literally across the st from there and eat lunch there weekly so I'm always flying out of San Carlos. Thankfully I've never seen this issue there using EZDOK. Link to comment Share on other sites More sharing options...
Kilstorm Posted January 22, 2016 Share Posted January 22, 2016 Nice work Alex on narrowing down the cause. I have noticed a far amount of flickering using Avatar walking around scenery and will try and see if that fixes it having Ezdok disabled. I can live without EzDok in Avatar mode and now knowing what might cause flickering will know what my options are in the future. I leased and plan on installing Meigs tonight and if I see that issue will know what is going on...hope not to see it as I dont at KSQL. Link to comment Share on other sites More sharing options...
Alex Goff Posted January 22, 2016 Share Posted January 22, 2016 I'll keep looking for solutions for EZDOK users, it may be a simple matter of just adjusting the z-bias offsets to work with a broader range of camera settings. When it can be fixed a hotfix will be released via FTX Central. These are the teething issues of new systems, but once those are worked out the fun bits like bump-mapped snow on the ground polygon can shine through Link to comment Share on other sites More sharing options...
Alex Goff Posted January 23, 2016 Share Posted January 23, 2016 For folks having issues with EZDOK enabled, could you check your camera.cfg (with EZDOK enabled) and search for "clipmode" and paste out the result? Also be sure you are using the latest EZDOK that was released for P3Dv3. Doing some research it appears EZDOK's clipmode setting has been a source of flickers going back quite far. Link to comment Share on other sites More sharing options...
edpatino Posted January 23, 2016 Share Posted January 23, 2016 Hi, I don't have EZDOK and I'm too having abnormal flickering in Avatar mode. Something is wrong here. Cheers, Edward Link to comment Share on other sites More sharing options...
Alex Goff Posted January 23, 2016 Share Posted January 23, 2016 If your flickering is limited to the ground polygon and persists for more than a few seconds after loading, could you paste out the contents of your camera.cfg file? The file should be in AppData\Roaming\Lockheed Martin\Prepar3D v2\cameras.cfg Link to comment Share on other sites More sharing options...
robtomlinson Posted January 23, 2016 Share Posted January 23, 2016 I had the same flickering threshold and GA parking areas. I looked at my cameras.cfg and changed the ClipMode for each of the EZDOK cameras to =Normal. They were set to =Minimum. I've done a bunch of circuits and viewed the airfield from varying heights and the flickering has gone. Link to comment Share on other sites More sharing options...
Alex Goff Posted January 23, 2016 Share Posted January 23, 2016 Clipmode=minimum is a setting known for causing flickers, Clipmode=normal is the desired setting for minimal flickering. I believe it is also the default in Prepar3d and EZDOK changes the setting to "minimum" Link to comment Share on other sites More sharing options...
edpatino Posted January 23, 2016 Share Posted January 23, 2016 12 hours ago, Alex Goff said: If your flickering is limited to the ground polygon and persists for more than a few seconds after loading, could you paste out the contents of your camera.cfg file? The file should be in AppData\Roaming\Lockheed Martin\Prepar3D v2\cameras.cfg Hi, here you go (see attached file). Yes, it is, flickering is limited to the ground polygon and persists after loading. Cheers, Edward cameras.cfg Link to comment Share on other sites More sharing options...
OMGEDSON Posted January 23, 2016 Author Share Posted January 23, 2016 Did edited cameras.cfg to clipmode=normal and whoa, heck no.... its unusable for gopro style videography! No issues exist at the other airports using this tech, please lets not give up and keep working on a fix. Link to comment Share on other sites More sharing options...
Alex Goff Posted January 23, 2016 Share Posted January 23, 2016 Fixes are being worked on, I am traveling for family matters and cannot produce anything for testing until at least Tuesday. I would continue to recommend not using clipmode=minimum as it is well documented to have the worst z-fighting of all camera views. Comparing to other airports is honestly, useless, because 99% use FS2002 style ground polygons that are not rendered in the same way. Link to comment Share on other sites More sharing options...
Alex Goff Posted January 28, 2016 Share Posted January 28, 2016 Some tweaking has been done on the ground polygon, conforming it to the same standards as KSQL. Navigate to /ORBX/FTX_NA/FTX_AA_KCGX/Scenery, back up "Orbx_KCGX_GP_P3D.bgl", and drop the included BGL in its place. In my testing I've found that the P3D Avatar will create flickers almost everywhere, unless it uses an FS2002 style ground polygon. This holds true for KSQL and KCGX in the Orbx world at least. That's something I'll note with Lockheed Martin for further assistance or patching. That aside, I am interested to hear how it works in regular aircraft but with EZDOK users or others affected. Download: Orbx_KCGX_GP_P3D.zip Link to comment Share on other sites More sharing options...
OMGEDSON Posted January 28, 2016 Author Share Posted January 28, 2016 Oddly enough I found it titled: Orbx_KCGX_GP_P3D.bgl.off thoughts? Link to comment Share on other sites More sharing options...
OMGEDSON Posted January 28, 2016 Author Share Posted January 28, 2016 Returning to CONFIRM FIXED ! Thank you again @Alex Goff! If you like I can have a few more folks in our community having the issue... Link to comment Share on other sites More sharing options...
Alex Goff Posted January 28, 2016 Share Posted January 28, 2016 If it was set to .off that's OK, its just that the HW variant was enabled. Make sure only one is enabled at a time, I'll post up a fixed version of the HW one as well. The more tests the merrier! Link to comment Share on other sites More sharing options...
Kilstorm Posted January 28, 2016 Share Posted January 28, 2016 I'll test it when I get home today and thanks for the explanation of what is happening in Avatar mode, it would be great if LM can create a fix to that in future updates for sure. Link to comment Share on other sites More sharing options...
edpatino Posted January 28, 2016 Share Posted January 28, 2016 Fixed the issues for me, except for the Avatar mode. Hopefully LM will help on this. Regards, Edward Link to comment Share on other sites More sharing options...
OMGEDSON Posted January 29, 2016 Author Share Posted January 29, 2016 On 1/28/2016 at 4:19 AM, Alex Goff said: If it was set to .off that's OK, its just that the HW variant was enabled. Make sure only one is enabled at a time, I'll post up a fixed version of the HW one as well. The more tests the merrier! Haha that explains my return today to say hey with HW it was broken again ;P Excellent thank you! Link to comment Share on other sites More sharing options...
Alex Goff Posted January 30, 2016 Share Posted January 30, 2016 Great, I'll apply the fixes to the HW version as well and issue them in a patch via FTX Central with a couple other small fixes. Thanks for testing the fix! Link to comment Share on other sites More sharing options...
zazaboeing Posted February 26, 2016 Share Posted February 26, 2016 Hi! Just to confirm I had the displaced threshold on Rwy18 completely messed up (almost only the photoreal background showing) and after the fix it is ok, but the overall flickering continues (much less now). Especially at the borders (near the water) and sometimes on the apron. Hoping for a fix! Thanks! Link to comment Share on other sites More sharing options...
OMGEDSON Posted March 11, 2016 Author Share Posted March 11, 2016 Also waiting patiently, we are close but I can't fly it live in stream as it would not give a great impression. Link to comment Share on other sites More sharing options...
edpatino Posted April 9, 2016 Share Posted April 9, 2016 I had to uncheck the Hard Winter GP option, otherwise I get flickering in parking spot #2 with tarmac turning white and grey. With the HW option unchecked, it is OK. Edward Link to comment Share on other sites More sharing options...
daladna Posted April 9, 2016 Share Posted April 9, 2016 same at blue canyon clipmod no fix it, but it's ok, i live with it from 2.5 version till now, so this is f12 heght from no problems btw, i never had any problems with meigs field, and ksql work perfect till couple a day ago i load it, and taxi parking marking gone by certain angle of view Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.