FSDreamTeam forum
Products Support => Vancouver CYVR support FSX/P3D => Topic started by: nevetrek on January 05, 2013, 03:05:02 pm
-
Hi
In my test I have 1 probleme ... the ground textures are flickering !!!
I have a Flatten issues... ???
I look for find an old af2_cyvr file remain on my FSX but not find ...
I activated Orbx and disable it ... without différence on this problem ...
I think have an elévation probleme ! :-\
When the trial time are end, I see on the ground the hole with a little différence altitude with the ground and the runway/taxiway ... :-\ :-\
Some other are the same ????
Do you have an little way for find where is the problem ?
Thank
http://www7.pic-upload.de/05.01.13/zha77n1sx774.jpg (http://www7.pic-upload.de/05.01.13/zha77n1sx774.jpg)
http://www10.pic-upload.de/05.01.13/cypf4cnbkr1h.jpg (http://www10.pic-upload.de/05.01.13/cypf4cnbkr1h.jpg)
-
First, be sure you use the Mesh complexity settings as suggested on the CYVR manual, which is 5m/pixel resolution and 100 Complexity.
If that doesn't fix it, and you are sure you don't have another AFCAD from another product in conflict (use the free FSX Airport Scanner to search for AFCAD duplicates), the problem is likely caused by another 3rd party mesh, in this case you have to disable it, because meshes will always display first depending on their resolution, even if they are on a lower level.
-
Thanks for very speed answer
Yes, the settings mesh are good and conform to your manual, 5 and 100
I use the scan, but not find another afcad ... :-\
Do you have some idea whats the default ellévation file in FSX for see if this file are an original ...
( in the scenery folder with folder name 0000, 0001, 002 etc ... end by the folder World ) Witch folder are the CYVR by default ?
I'm despited ... I look at for find a solution all the days, tried all solution ... disable all my scenery except Cyvr ... patch Orbx ...but not run corectly, I have every time this elévation problem, hole, on some area from the airport :'( :'( :'(
Yes, the symptom are the same with 3rd party or duplicated afcad ... except ...there is not 2X afcad and not 3rd party in this area !
-
I use the scan, but not find another afcad ... :-\
Then the problem is likely caused by a 3rd party mesh instead.
Do you have some idea whats the default ellévation file in FSX for see if this file are an original ...( in the scenery folder with folder name 0000, 0001, 002 etc ... end by the folder World )
It's unlikely some addon has modified the default files, it's most likely you have a separate .bgl somewhere else. Unfortunately, there's no similar utility like the airport scanner, to look for mesh scenery, you'll have to find it manually.
-
Then the problem is likely caused by a 3rd party mesh instead.
It's unlikely some addon has modified the default files, it's most likely you have a separate .bgl somewhere else. Unfortunately, there's no similar utility like the airport scanner, to look for mesh scenery, you'll have to find it manually.
3rd party or mesh ... yes I not doubt ... but where ??? I dissable all my scenery in library ! :-[
I looking the file with ADE, I find the original FSX file, In ( scenery /0101 base/ scenery/APX15140.bgl )the original altitude are 4,267 meter ... With the ADE scan, I not find another BGL file with CYVR référence ... ( except your files )
Yes, one extra Mesh are possible ...but where ...I think the search are very long :'(
But for moment, I just disable the original file APX15140.bgl, Is not again perfect, I have again some flickering but less and it is playable...
Chers.
-
I have a flickering problem too.
Difficult to make a screenshot maybe you could take a look at the video.
www.creppel.de/Bilder/cyvr.mp4 (http://www.creppel.de/Bilder/cyvr.mp4)
What can cause this?
-
I search also ... I see your video, that's in the same style for me :-\
-
What can cause this?
All possible causes are already discussed in this thread.
It's either another AFCAD or a 3rd party mesh, assuming you set your settings as suggested on them manual, which was also already discussed in this thread.
-
This happens only in aircraft view or top down view for me. Cockpit and spot view are fine. Using recommended scenery settings. Found no addtional AFCAD's.
-
In Top Down view, you should expect some flickering. It's important you don't have it in Spot view or in the VC, where it counts...
-
It's important you don't have it in Spot view or in the VC, where it counts...
My thought exactly. Otherwise the scenery looks great. Including the shadows.
-
That's my setting vieux with your add-on manager Do you think some parameter are not good ???
http://www7.pic-upload.de/05.01.13/kmr3i8txpz3d.jpg (http://www7.pic-upload.de/05.01.13/kmr3i8txpz3d.jpg)
-
If you are seeing flickering in VC or Spot view (in Top Down view is to be expected), it's either another AFCAD or a 3rd party mesh. The only settings that could affect this, are those suggested on the manual about the Mesh settings.
-
Also, since installing CYVR, now my GSX not run :-\ when I apply by ctrl shift F12 ... the menu not came ...
-
Also, since installing CYVR, now my GSX not run :-\ when I apply by ctrl shift F12 ... the menu not came ...
Already discussed here:
http://www.fsdreamteam.com/forum/index.php?topic=7872.0
try to run the installer again now.
-
Thank you for the suggest, now, GSX are full out !
I delete CYVR
I delete GSX
I delete Coalty
I delete Addon manager
I réinstal standallone manager and coualty vers 2.9... all are good, ctrl shift F12 are come back for a menu about your other airports but if I trie instal again CYVR or GSX, that's the same ... ctrl shift F12 not run !
-
If GSX is working elsewhere, it should work at CYVR too. Have you installed the Stand-Alone Addon Manager just now ? Because, we had a small fix about an hour ago, that might affect GSX and should be fixed now. No need to re-download anything, just RUN the installer Stand-Alone Addon Manager.
-
O.K., GSX problem after CYVR are solved for me now. :)
For the Flickering ... I put some files about ORBX on "Off" and 1 default FSX file also and it seems to work well.
30 fps, and just very rarely one flickering now in each view .
For the ORBX file, I put on "OFF" some files ( see this discussed, http://www.fsdreamteam.com/forum/index.php?topic=7843.0 (http://www.fsdreamteam.com/forum/index.php?topic=7843.0) )
And also in the Microsoft flight Simulator X/scenery/NAMW/Scenery
If you have one file name vancouv.bgl with a different date creation versus your other default file ... also, rename it on "off" for disable it (vancouv.off) ... and make a test !
For me, that's OK Now !
-
I have the same issue with KDFW with the flickering and CYVR but it seems trivial to me since the scenery runs smoothly.
-
I have a flickering problem too.
Difficult to make a screenshot maybe you could take a look at the video.
www.creppel.de/Bilder/cyvr.mp4 (http://www.creppel.de/Bilder/cyvr.mp4)
What can cause this?
Hi Chris,
I have the same problem as you, I wish to have it in top down only, sadly it happens in virtual cockpit also. I have yet to find a solution.
Manta
-
If you see flickering on ground in top-down view, it's normal and it's the same with all our past sceneries starting from KDFW. If you see flickering on ground in normal flying view, that's more likely another scenery in conflict.
-
I have the same flickering problem, it appears in cockpit and tail view, but not in spot and 2D cockpit view. I made the following test:
tryed different aircraft (standard and payware)
tryed disabling ORBX North America
tryed DX9 (I usually run FSX in DX10)
runned scenery scanner but no conflicts appear in Vancouver airport
cancelled ORBX files as advised in another thread
checked mesh installed, I have many NextMap Pro mesh but only California in USA and nothing in Canada
checked mesh settings in FSX and they are correct (5 and 100)
The only other scenery addon I have beside ORBX are GEX and UTX, plus I use Active Sky airport textures.
I think it's an elevation problem because when I enable the progressive taxi, the arrows are not visible, but they appear sometimes in transparency just under the ground.
Beside that, thank you Umberto for this great airport and I can understand how hard must be for you to help all of us solving these problems which I think are not caused by your addon.
-
I have the exact same problem as described by Epos hence not starting a new thread. The difference is that I do not run Vancouver Plus 3 or GEX or UTX. I only have ORBX PNW but I removed all afcad files associated with YVR as well as the FSX default afcad just in case. The flickering and tearing is only visible in 3D main VC mode, but as soon as I cycle the cockpit view by hitting "A" on my keyboard (I use EZDok) to the next VC mode, the flickering / tearing disappears and the scenery behaves normally. So I can live with this temporary solution. Needless to say in 2D mode, no tearing or flickering as described by other posts. Very strange as I have not encountered this problem with any other FSDT sceneries. Hopefully there will be an answer to resolve this. Apart from that, this scenery is top notch and the FPS is much better than expected and I also Thank You FSDT for this wonderful scenery. ;D
-
The flickering and tearing is only visible in 3D main VC mode, but as soon as I cycle the cockpit view by hitting "A" on my keyboard (I use EZDok) to the next VC mode, the flickering / tearing disappears and the scenery behaves normally.
It's possible the problem is caused by EZDok, I've noticed a similar issue with Opus FSX, which also creates its own camera views. I can see flickering too, but ONLY in the camera view created by Opus, not the standard ones.
I'll check better if it's possible to fix this.
-
I uninstalled OPUS (don't use EZCA anymore) and tryed again but the flickering in cockpit view is still present.
I attached a picture which shows how sometimes the progressive taxi arrows appear under the surface.
I know it seems an elevation conflict, but I can't figure out what can cause it, even because I've just made a fresh FSX reinstall and so I remember what addon I have installed.
Thanks again for your help
-
I attached a picture which shows how sometimes the progressive taxi arrows appear under the surface.
Progressive taxi doesn't really work in any of our latest sceneries. Not always, but in general is not reliable.
-
The flickering and tearing is only visible in 3D main VC mode, but as soon as I cycle the cockpit view by hitting "A" on my keyboard (I use EZDok) to the next VC mode, the flickering / tearing disappears and the scenery behaves normally.
It's possible the problem is caused by EZDok, I've noticed a similar issue with Opus FSX, which also creates its own camera views. I can see flickering too, but ONLY in the camera view created by Opus, not the standard ones.
I'll check better if it's possible to fix this.
I have the flickering, and am also using the EZdok camera. On my descent into the airport, my flickering is constant UNTIL I get to 800 ft. AGL. At that altitude, the flickering stops completely and everything is perfectly fine through the landing and taxi.
-
I have the flickering, and am also using the EZdok camera. On my descent into the airport, my flickering is constant UNTIL I get to 800 ft. AGL. At that altitude, the flickering stops completely and everything is perfectly fine through the landing and taxi.
The same behaviour occurs on my system. I am an EZdok user too. The flickering disappears when switching to a default view using the "A" key. Deleting various files as stated in this topic did not solve or affect the issue in my case.
Mark
-
I'm having the same issue but am not using ezdok. No other Canada files other than UTX and GEX.
-
I'm sorry, but I can only confirm the flickering will appear when using products that creates custom camera views (es. Opus, EZdok) and this *might* be fixed on our side, not 100% sure because it might be a limitation of the FSX camera system, but if there's something that can be fixed, we can only fix it from our side.
AND, there will be flickering if you use Top-down view or other far-away views like tower view.
But if you are having flickering in standard VC or 2D views, and you have the Mesh settings and Complexity as indicated on the manual (note they should be at *that* setting of 5m/pixel not less, but even not more), then it's something caused by another scenery.
-
But if you are having flickering in standard VC or 2D views, and you have the Mesh settings and Complexity as indicated on the manual (note they should be at *that* setting of 5m/pixel not less, but even not more), then it's something caused by another scenery.
Which it was my issue. I have both Opus and Ezca, but once I solved the .bgl file shimmering, these two kind of cameras don't give me any problem, at least so far.
-
Confirming this only happens in VC view from the pilot side only.
-
Confirming this only happens in VC view from the pilot side only.
Do you use Opus or other programme modify your native V.C. FSX camera ? Or an aircraft with specific camera ?
For me, this flickering happend again only when I use the not native camera FSX ... ( Fsrecorder camera, Opus, Ezdok, camera vieuw ...)
I not have this problem with other FSDT scenery exept Bergen from cloud 9.
-
Confirming this only happens in VC view from the pilot side only.
Do you use Opus or other programme modify your native V.C. FSX camera ? Or an aircraft with specific camera ?
For me, this flickering happend again only when I use the not native camera FSX ... ( Fsrecorder camera, Opus, Ezdok, camera vieuw ...)
I not have this problem with other FSDT scenery exept Bergen from cloud 9.
No Opus. No modification to native camera. No EZDOK.
-
I've found a solution that works for me. Since Umberto said that could be a software like OPUS or EZCA the cause of the flashing textures, I took the original camera.cfg from my second pc with a standard FSX + Acceleration installation (no addon) and made a comparison with the one on my main pc.
I've found that the only difference was in two camera views:
[CameraDefinition.999] Title = "OpusFSX External View" and [CameraDefinition.002] Title = Virtual Cockpit
These two views had the following line in my main pc camera.cfg file (the one with flashing textures) which are not present in the original FSX camera.cfg file:
ClipMode=Minimum
I deleted this line in both views and now all the flashing textures are gone with OPUS camera active and working as before.
Hope this can help others solve the problem but remember to make a backup copy of your camera.cfg before making any change to it.
-
Good post. This solution also worked for me as a EZDOK user. After I deleted the Clipmode=minimum line in both the VC and Locked Spot Views, I flew around CYVR, and did a full flight from Kelowna CYWL to CYVR - no more flickering. Solved for my setup!
-
I have no clipmode= minimum in my FSX camera CFG file and I still have the flickering on approach. But goes away as I get near. I use Ezdoc. I have no other scenery on my computer at this time. ???
-
i have purshased your product i have a big problem with Flickering texture when approching the airport,testing all issues in the forum nothing for me ,plz help for this problem.
-
i have purshased your product i have a big problem with Flickering texture when approching the airport,testing all issues in the forum nothing for me ,plz help for this problem.
As already discussed in the forum, the flickering can be caused by any one of these:
- Another scenery in conflict
- An add-on program that creates custom camera views with the ClipMode=Minimum, this should be removed
- Mesh Settings not as in the CYVR manual (5 mt/pixel at 100 Complexity)
And, if you have flickering in Top-down view, that's normal and can't be solved in any way, all our sceneries starting from KDFW are the same.
-
OK
No addon seanery.
mesh at 5m
complexity 100
no clipmode=minimum
In vc not top down view on final app.
Getting tired of being told its on are end when lots of us are having problems.
If I fly to klas KJFK or other FSTD airports that I have I do not get this.
One day you guys will find a solution that really works and all of use will say told you so.
Sorry for being harsh but thats how I feel right now.
-
Getting tired of being told its on are end when lots of us are having problems.
"Lots of us" are exactly 6 different people that posted here, with 3 of them having the problem solved by removing the ClipMode=Minimum and one not really minding the problem.
If I fly to klas KJFK or other FSTD airports that I have I do not get this.
Every area is different and chances for a conflict with something else depend on the area, the settings and what else you have installed.
One day you guys will find a solution that really works and all of use will say told you so.
Since there's no flickering for 99% of users, there's no solution needed on our side. The only solutions that works are those already explained above: finding a conflict caused by something else, fixing the camera cfg file and keep the scenery setting as suggested.
You said you did all of them but, since the mesh/complexity and the ClipMode=Minimum are easy to test, it can only mean you have a conflict caused by something else that you still haven't found yet.
Of course, I can only speak of KNOWN solutions. It's possible someone might find another solution for a problem caused by something else (like the ClipMode=Minimum) that still doesn't require we have to "fix" anything in the scenery. We would never have the time to test a scenery with any possible add-on out there.
THAT'S what the Trial is made for: to allow you to test the scenery on YOUR system, using YOUR combination of add-ons and settings.
-
I just want to get it to work as good as the other FSDT addons.
I have no other addons other then fstd airports as I rather have good FPS then nice grounds as I am 40000ft above it.
I also just added 2 aerosoft airports in Europe and have no problems with them.
When I fly to KLAS or KJFK with no setting changes I do not get the flickering.
Was thinking last night about something. If the old scenery is showing its self buy flickering then can you guys raise the airport height so it does not happen? I am talking about raising it buy 1 ft or so.
Also would it not be better to load the scenery a bit smoother? Instead of loading it all at 10 nm away how about load ground at 30nm then buildings at 25nm then rest of textures at 15nm. Just a thought I had last night. I am in no way a programmer. Just giving my thoughts.
-
Was thinking last night about something. If the old scenery is showing its self buy flickering then can you guys raise the airport height so it does not happen? I am talking about raising it buy 1 ft or so.
As I've said, since we don't see any flickering, and the vast majority of user don't either, there's nothing to fix in the scenery, because the problem is caused by something else. Are you sure it's the default scenery showing up and not something that *looks* like default, but it's an AFCAD for another scenery ?
Also would it not be better to load the scenery a bit smoother? Instead of loading it all at 10 nm away how about load ground at 30nm then buildings at 25nm then rest of textures at 15nm. Just a thought I had last night. I am in no way a programmer.
Surely not, because we don't want to impose the CYVR memory footprint to other airports in the area. As always, smoother flight doesn't go together with memory consumption, to get a more seamless loading, you have to take more memory, but this will result in risking more OOMs.
With our method, you can be *sure* that outside 10NM, not a single bit of memory is being used by CYVR, which is not the case with sceneries made entirely with BGL, where the loading is entirely handled by FSX, which is known for loading BGLs for areas even thousands of miles away from the airplane.
-
So how do I look for other AFCAD files as I know i do not have other scenery but will give it a shot.
If there is a program to do this please give me the link as I can not find one out there that I feel I can trust.
Will try a flight from cyyc to cyvr tomorrow and disable EZDOC to see if that gets rid of it.
-
I saw this today, this ground flickering. Saw it on approach to 26R. About 5 to 10 miles out it started. Saw what appeared to be this bleed through from underneath. Though the flickering was white. I don't have any other scenery for this area other than UTX/GEX. Never had any other scenery for this area. It almost looked like the issue people were having with PHNL and the bleed through issues we were having there.
Sent from my Samsung Galaxy Note 2
-
what was the solution for PHNL? If there was one.
-
I saw this today, this ground flickering. Saw it on approach to 26R. About 5 to 10 miles out it started
You don't say if it *ended* when you went closer. It's a big difference if it did, if it's a conflict, it shouldn't go away in any case.
-
New here, so hello to Umberto and all the users.
According to my "subject" title, like others, i am also affected by this unusual heavy texture flickering. Never experienced that at any FSDT airport before or at any other payware airport. Just took two days of troubleshooting without success. Used all the advices in that forum. I did for testing:
-enabled/disabled UTX areas in scenery lib.
-disable EZDOK within FSX menue (not had any "clip" entry in camera.cfg)
-switched FTX Central to default/North America
-no ENB Mod in use
-using GSX
-removed ORBX bgl´s/used airport scanner. No combination did a solution
-FSDT CYVR is above FTX in scenery lib.
-renewed fsx.cfg
-See nvidia inspector settings attached (using 4xAA + 2x Sparse grid Super Sampling)
-See screenshots (hardly visible) at two test screenshots
-FSX mesh res is 1m
-FSX mesh complex is 100
This massive flickering is only out of aircraft VC view. 2D view i have not checked yet.
-
You wouldn't believe how much this bugged me when filming my little clip for the contest! Soon as i moved the camera up about 1000ft it was already flickering.
-
Maybe another information for Umberto to detect the cause:
Umberto talked about the general issue when in external view (on top view) directly above the field which generally cannot be solved at the moment. That issue i know about at many of the ORBX airports as well. In specific angles and zoom levels there is heavy ground/taxiway/rwy/ flickering.
For example in approach configuration when on GS angle or above or below GS flickering starts when CYVR becomes visible. That flickering is visible all the way on approach and stops short before ground contact (touchdown). The heavy (approach)flickering at FSDT CYVR is the same style and type as when i am on top view as written at the beginning of my post. The known "on top view flickering" is exactly same type, intensity, colors, as type/style of flickering when i am on glide path/above/below from any direction and only out of virual cockpit, not in external view.
Is it possible that the installer has something to do having that issue? Are the resolution settings selected from the installer maybe a cause many customers have that issues?
Kind regards
-
We know exactly what causes the top view flickering and THAT one can't be solved.
The flickering while approaching in normal VC doesn't happen, not as described.
Even if it "looks" similar (all z-fighting looks similar), it's not the same issue but, while we know about the top-down view flickering and can replicate it easily (it's just there and will not go away), I can't see ANY flickering when approaching from normal glide path angles or, in any case, no flicker stays until just before touch down, as described.
Yes, we can tweak the scenery to lessen the problem but, the very fact we ARE seeing different things (and of course, everybody would reported it just the same) should be proof enough the problem is not just the scenery, but might become worse when something else is installed.
It MIGHT be video-card related too, because z-fighting is related to z-buffer precision and bit depth so, for example, some tweaks related to z-buffer setting might improve/worse the situation.
-
Got this also, however, it does indeed go away as I get CLOSER.
I'm almost 99% sure it's caused by the FXAA Injector Tool, (a form of ENB).
My "flickering" isn't in the Virtual Cockpit view, most usually in spot.
It doesn't really bother me that much, but I just thought I would post this.
-
[CameraDefinition.002] Title = Virtual Cockpit
These two views had the following line in my main pc camera.cfg file (the one with flashing textures) which are not present in the original FSX camera.cfg file:
ClipMode=Minimum
I deleted this line in both views and now all the flashing textures are gone with OPUS camera active and working as before.
Hope this can help others solve the problem but remember to make a backup copy of your camera.cfg before making any change to it.
Thanks epos, removing ClipMode=Minimum from "[CameraDefinition.002] Title = Virtual Cockpit" fixed the ground flickering for me. After reading a handful of post's here at this forum the situation is resolved. I had Opus installed quite a while ago and I think that is what edited my camera.cfg file. I couldn't figure out why at one time there wasn't any flashing then all of the sudden CYVR looked really bad from the air.
I am glad that I didn't post anything negative about CYVR in the meantime. Now I can go back to enjoying one of the many fantastic airport sceneries that I have.
Thanks again!
Robert
-
I have the texture flickering problem too - but only the terminal building glass, and the airport signs flicker (and the jetway at stand 96). Its a strange one. Ive tried all of the above, I've loaded 2048 and 4096 textures with no difference, I've tried 5m mesh and higher/lower combinations. I have changed AA/trilinear, reflection/shadow options with no change to the flickers. It does look to me like some sort of default scenery is showing through. The surrounding airport and terrain have no texture issues for me. ORBX PNW is installed. I am using P3D v2 which is not yet approved for PNW, so it may be something to do with that, however I have disabled the problem Vancouver files from ORBX.
Great frame rates on P3D2 with your scenery, which looks superb!!! (Except the flickering which is driving me crazy).
-
It does look to me like some sort of default scenery is showing through
If this was the case, you should also see parts of buildings, not just flickering, since default buildings are quite different from the FSDT ones, if there was some default scenery visible, you should have seen it.
-
The central part of the Vancouver terminal glass does not flicker - just the extensions. Umberto, I will attempt to make a video of the screen to let you see what I get. It must be impossible to find a cure for something you don't have happening to your own test rigs!! The other issue is it's obviously nothing to do with the CYVR scenery, and it doesn't affect the windows of the central part of the terminal, so what is different about the legs? And is there a file somewhere thats causing the flicker on my GTX680? And can I delete it - whatever it is? I will PM you once I get the video made. Thanks for looking at it!!
-
This just gets stranger. I use P3Dv2 and because there are currently issues with the P3D2 menu loading on some nVidia cards, my default flight loads and starts at another airport/region. When moving to and loading CYVR I get the flickering window textures. However when I load a new flight with CYVR saved as the default starting point, there are no flickers....
???
-
Solved the glass flickering problem. :) The ORBX PNW scenery was affecting the glass textures in the Vancouver scenery, even with the scenery disabled in P3D. Removing the PNW files completely from the drive has cured the flickers. I will wait until an official P3D2 installer is produced by ORBX and will reinstall then.
-
I was getting this in a fresh install of P3dV2 with FSDT CYVR. I have no EZCA or OPUS. I have no additional sceneries except FTX Global for P3Dv2
Go to ~(install dir)\scenery\world\scenery and change the suffix of CYVR_AP_alt.bgl to .OFF
Fixed.
-
Just uninstalling CYVR previous version and installing the new version 1.1 with the full installer, not using updater alone:
fixed for me