FSDreamTeam forum
Products Support => Vancouver CYVR support FSX/P3D => Topic started by: davidal on June 10, 2013, 10:43:11 pm
-
Hello,
First of all I would like to congratulare FSDT for this excellent rendition of CYVR.
I am encountering some issues when starting a flight at CYVR, mainly some buildings (those which are far away from the plane) do not load. I need to manually restart Couatl engine to force them to appear. And sometimes the problem still persists. Then, the only way I can force these buildings to appear is either to slew the plane to this area or take off and flight very close over the area. This fixes the issue, but the immersion is over if I need to do this every time.
Any suggestions?
Dan
-
I am attaching a screenshot of the problem.
-
Be sure you don't run FSX or ANY of its add-on modules in any of the "Compatibility" modes.
-
Thanks Umberto,
Unfortunately, I checked and FSX is not running in compatibility mode. I have a pretty clean FSX installation. I am just running REX and UT2 with FSX and none of them is running in compatibility mode. I forced all of them to run as administrator but this does not seem to change anything. I need to keep restarting Cuatl engine to get the problem solved and most of the times the central part of the airport does not load.
I assume I would need to live with that. It is really a pity cause apart from that this is an excellent product.
Rgds,
Dan
-
I need to keep restarting Cuatl engine to get the problem solved and most of the times the central part of the airport does not load.
That's strange because, if you had a problem with Couatl not running, every building should disappear. If only some of them disappear, it's surely something entirely else.
Try to temporarily disable all your other add-ons, maybe another add-on is using Simconnect too and is sending too many commands, that our modules don't have a chance to talk with FSX. We saw this happen a couple of times.
-
Sorry to bring up an old thread but neither one of these solutions are working for me. (And as posted in another thread) The only solution was to run right through the building which is very annoying. This problem has been going on for awhile now and I just want some suggestions.
-
Sorry to bring up an old thread but neither one of these solutions are working for me. (And as posted in another thread) The only solution was to run right through the building which is very annoying. This problem has been going on for awhile now and I just want some suggestions.
As I've said in this thread, the only known possible cause for buildings that appear only if you get close, is if you run FSX or some other add-on that runs together with FSX into Compatibility mode, which causes video drivers to behave differently.
Another possibly issue is having Transparency Antialiasing ( or AAA on some cards ) enabled, this is explained in the scenery manual too, it must be disabled.
-
I don't have any other addon that can make FSX run in compatibility but I will check the AAA
-
Correct me if I'm wrong but I can't seem to find it in the manual the closest is adaptive AA. ???
-
Correct me if I'm wrong but I can't seem to find it in the manual the closest is adaptive AA. ???
That's what I've said. It's either called Transparency Antialiasing, or AAA ( AAA = Adaptive AA )
-
Hmmn... I checked it says it is using the application settings for AA and since I have an AMD there is no "AAA" .
(Is this right?If it isn't, sorry :-[ and how could I correct this?)
-
Hmmn... I checked it says it is using the application settings for AA and since I have an AMD there is no "AAA" .
As I've said, Adaptive Antialiasing, on AMD, it's the same as AAA. You seems to have it set to Multisampling, so it's not set. Try other settings too. Also, try to reset all your video card settings to default.
I'm sorry, but I can only repeat and confirm that, the only known causes for objects appearing ONLY when getting close, is the "Compatibility" mode enabled ( by FSX or another add-on that runs together with it ), or the AAA.
-
As I've said, Adaptive Antialiasing, on AMD, it's the same as AAA. You seems to have it set to Multisampling, so it's not set. Try other settings too. Also, try to reset all your video card settings to default.
I'm sorry, but I can only repeat and confirm that, the only known causes for objects appearing ONLY when getting close, is the "Compatibility" mode enabled ( by FSX or another add-on that runs together with it ), or the AAA.
Oh well at least you tried..
I've tried putting the AA settings to super-sampling and didn't work I've also tried resetting to default settings and double checked all of my addons (and FSX) for compatibility settings but still no change. Could it be my graphics card (specs are in my signature) ??? ???
-
I have found a fix! I think...
I had the coatl in non compatibility mode. I put it to compatibility mode ran FSX opened up CYVR and (of course no buildings) I turned compatibility mode off and ran FSX again it then had all the buildings. :) :)
UPDATE: False alarm thins are still disappearing and I still don't know why. I did everything- reinstalled every FSDT scenery over 4 times tweaked my video card till every setting was tested, checked anything possible with compatibility issues, and updated video cards and drivers. I even did the opposite of what you're supposed to do (turned AAA and compatibility on). ::)???
This also happened on my older computer which I replaced a few months ago (Windows 7 intel)
Any other suggestions Virtuali? I'd be happy to give you as much info on my computer you need.
-
Any other suggestions Virtuali? I'd be happy to give you as much info on my computer you need.
As I've said the only KNOWN causes for objects appearing ONLY when getting close, is the "Compatibility" mode enabled ( by FSX or another add-on that runs together with it ), or the AAA.
If you will eventually find what was causing this on YOUR system, we'll might add it to the known causes too. It surely doesn't happen here or can be replicated in any way.
Have you tried lowering the texture resolution in the CYVR installer ? Perhaps you are just using too much memory with your other installed add-ons, so there's not enough memory left to run CYVR safely. Which is why, CYVR give you some options to save memory. And, you can try using DX10.
-
Any other suggestions Virtuali? I'd be happy to give you as much info on my computer you need.
As I've said the only KNOWN causes for objects appearing ONLY when getting close, is the "Compatibility" mode enabled ( by FSX or another add-on that runs together with it ), or the AAA.
If you will eventually find what was causing this on YOUR system, we'll might add it to the known causes too. It surely doesn't happen here or can be replicated in any way.
Have you tried lowering the texture resolution in the CYVR installer ? Perhaps you are just using too much memory with your other installed add-ons, so there's not enough memory left to run CYVR safely. Which is why, CYVR give you some options to save memory. And, you can try using DX10.
I reinstalled CYVR using the lowest settings possible and ran it in DX10 mode. It still has the missing buildings all taxiways and other buildings are there but just a random group of buildings that are not showing. Its usually the YVR commercial ops building (where the cargojet aircraft parks).
I will try to disable FSUIPC (my only other addon).
-
I'm not to sure if these will help but here are my dll.xml, exe.xml, and FSX.cfg.
*tried disabling FSUIPC didn't work.
-
Sorry but, I can only repeat and confirm that, the only KNOWN causes for objects appearing ONLY when getting close or the reason why SOME objects are missing, is the "Compatibility" mode enabled ( by FSX or another add-on that runs together with it ), or the AAA.
If there was a problem with the software, you wouldn't see ANYTHING. No scenery at all, no buildings at all, just jetways. If you see parts of the scenery and some missing, and especially in a seemingly random pattern, it means everything is running correctly, and the problem is something else in your settings.
OR, another add-on which is interfering, maybe the Simconnect communication pipe is abused by this other add-on, so our software is running, but doesn't have a chance to communicate with FSX.
We had a couple of reports of these issues, they can only be found by disabling all your add-on modules in the DLL and EXE XML files ( except the Addon Manager and Couatl, of course ), then re-enabling them one by one, until you find the culprit.
-
Sorry but, I can only repeat and confirm that, the only KNOWN causes for objects appearing ONLY when getting close or the reason why SOME objects are missing, is the "Compatibility" mode enabled ( by FSX or another add-on that runs together with it ), or the AAA.
If there was a problem with the software, you wouldn't see ANYTHING. No scenery at all, no buildings at all, just jetways. If you see parts of the scenery and some missing, and especially in a seemingly random pattern, it means everything is running correctly, and the problem is something else in your settings.
OR, another add-on which is interfering, maybe the Simconnect communication pipe is abused by this other add-on, so our software is running, but doesn't have a chance to communicate with FSX.
We had a couple of reports of these issues, they can only be found by disabling all your add-on modules in the DLL and EXE XML files ( except the Addon Manager and Couatl, of course ), then re-enabling them one by one, until you find the culprit.
Sadly the only addon I have in the exe/dll.xml files are coatl and addon manager.
-
It happens to me too, same simptoms, I see it mostly on cyvr, bu again it happens on all other airports by fsdt and flightbeam that I have, not always but it does, where a part of the terminal or a complete building won't appear. They reappear if I move closer to them. So you are clearly not the only one. I just learned to live with it :-)
Sent from my Lumia 900 using Tapatalk
-
It happens to me too, same simptoms, I see it mostly on cyvr, bu again it happens on all other airports by fsdt and flightbeam that I have, not always but it does, where a part of the terminal or a complete building won't appear. They reappear if I move closer to them. So you are clearly not the only one. I just learned to live with it :-)
Sent from my Lumia 900 using Tapatalk
Sadly CYVR is one of my top FSX destinations so it's really hard to just live with it.
I also found a few of people who have similar problems which didn't work.
And a couatl err log appeared today I thought it might help.
couatl v2.0 (build 2358)
panic log started on Mon Feb 17 17:07:48 2014
problem raised by addon <unknown>Traceback (most recent call last):
File "couatl\common\sceneryAddOnMulti.py", line 120, in onEnter
File "couatl\common\rwsl.py", line 236, in onEnter
AssertionError
-
And a couatl err log appeared today I thought it might help.
couatl v2.0 (build 2358)
panic log started on Mon Feb 17 17:07:48 2014
problem raised by addon <unknown>Traceback (most recent call last):
File "couatl\common\sceneryAddOnMulti.py", line 120, in onEnter
File "couatl\common\rwsl.py", line 236, in onEnter
AssertionError
Yes, that's useful to know but, it only appeared today ? Or, you simply had error logging turned off until today ?
-
I remember I was in full screen and all buildings loaded, then I restarted coatl and sone buildings dissapeared so I exited to main menu and coatl had some sort of cash. I think this caused this and I think o turned on the err log on yesterday.
-
I remember I was in full screen and all buildings loaded, then I restarted coatl and sone buildings dissapeared so I exited to main menu and coatl had some sort of cash. I think this caused this and I think o turned on the err log on yesterday.
Restarting Couatl should FIX this, not cause this...does it crash now, if you restart it after you see a building disappearing ? Do you still see that error in the log, under a new line, after restarting Couatl ?
-
I remember I was in full screen and all buildings loaded, then I restarted coatl and sone buildings dissapeared so I exited to main menu and coatl had some sort of cash. I think this caused this and I think o turned on the err log on yesterday.
Restarting Couatl should FIX this, not cause this...does it crash now, if you restart it after you see a building disappearing ? Do you still see that error in the log, under a new line, after restarting Couatl ?
Restarting couatl sometimes made it worse (more buildings dissapeared) and no, no new lines in the log, I'm guessing it had something to do with another thing I did.
*And for some reason static cars disappear from afar just like the buildings but again reappear when coming close.
I'm going to try using the simconnect.ini method and see if there are any warnings or errors.
-
Here's what in simmconect.INI when I go close to a building and it reappears.
-
Here's what in simmconect.INI when I go close to a building and it reappears.
What do you mean with "close" ? Buildings are SUPPOSED to appear/disappear when you go close!! But as I've said, if this distance is clearly wrong, like a big, important building appearing only when you are in front of it, that's a problem of the Compatibility mode enabled. Again, that's the only KNOWN cause of it...
But, instead, if you are seeing smaller stuff appearing/disappearing, that's how the scenery has been made and, as explained many times o the forum too, can be controlled by the "Anti pop-up" setting in the Addon Manager. The default of 1, means those smaller objects will appear/disappear on a distance we programmed. Any other larger value, means the threshold distance will be multiplied by that value.
-
What do you mean with "close" ? Buildings are SUPPOSED to appear/disappear when you go close!! But as I've said, if this distance is clearly wrong, like a big, important building appearing only when you are in front of it, that's a problem of the Compatibility mode enabled. Again, that's the only KNOWN cause of it...
But, instead, if you are seeing smaller stuff appearing/disappearing, that's how the scenery has been made and, as explained many times o the forum too, can be controlled by the "Anti pop-up" setting in the Addon Manager. The default of 1, means those smaller objects will appear/disappear on a distance we programmed. Any other larger value, means the threshold distance will be multiplied by that value.
Yes it when I go in front or near the objecy when it reappears , but I can confirm all programs that run with fsx are not in compatibility mode. And reject particle radius is at1.
-
Yes it when I go in front or near the objecy when it reappears
What "object" ? A small, detail-like object, or a main, big building ? As I've said in my previous message, smaller objects are SUPPOSED to appear only when getting close and, not only that, they also appear/disappear depending on your altitude from ground.
Even the switch by altitude can be turned on/off, using the appropriate option in the Addon Manager, named "Altitude Cull"
And reject particle radius is at1.
Haven't said anything about that parameter, if you are referring to the "SmallPartsRejectRadius" FSX tweak. What controls the loading range of the entire object, for objects belonging to sceneries managed by the Addon Manager, is the "Anti pop-up" slider, in the FSDT tweaks section. That slider will only affect smaller objects, because larger one (main buildings) have their loading range fixed at the whole airport radius, which is about 10 NM.
-
Missing big buildings ex. Concourse D is not showing just the gates but all other buildings are there.
Yes and sorry I meant anti-popup=1
-
Missing big buildings ex. Concourse D is not showing just the gates but all other buildings are there.
But it's just ONE missing building ? And, it's always the same, or it's random ? I fairly sure you won't like the reply: if it's random, it means it doesn't depend on anything related to our software, which is running correctly according to your description.
The only possible explanation left (since you said it's not the Compatibility) for random disappearance of single buildings, and especially if they change when you select "Restart Couatl", it's that another add-on is stealing the Simconnect communication pipeline by sending so many commands in so short time, that our modules don't have the chance to talk with it.
Or, possibly, you are low on resources/memory, that the same happens. How's your frame rate, for example ? Are you able to check you free RAM while CYVR is running ?
About the "Compatibility" mode: even if you don't have FSX itself in Compatibility mode, it's possible that if you have another add-on launched together with it that IS running in Compatibility mode, it will make the whole sim session running in Compatibility mode anyway, which results in video drivers underperforming, and creating visual problems like disappearing buildings until you get very close.
-
Yeah the buildings dissappear randomly.
Couatl and addon manager are the only two addos in both the dll and exe.xml files.
I have never checked my free ram but I will when I get back on my computer .Here are my fps:
On a default aircraft ie 747 it runs at 15-20 fps and on an addon aircraft like the posky 747-400 I get frames from 10-12 and from payware aircraft like the sms 777 it runs at about 10-12 fps
My settings are in the fsx.cfg a few post before, and if I turn down the settings completely I run CYVR at 20-30 fps depending on the aircraft.
UPDATE: No programs that use or run with FSX are in compatibility mode. Even programs that have nothing to do with FSX.
As for the RAM I'm using 88%.
-
I tested this problem out with other airports and the same result-random missing buildings. :'(
So it isn't a Vancouver issue.
-
Yeah the buildings dissappear randomly.
They don't here.
I tested this problem out with other airports and the same result-random missing buildings. So it isn't a Vancouver issue.
I was quite sure of that...
-
I tested this problem out with other airports and the same result-random missing buildings. So it isn't a Vancouver issue.
I was quite sure of that...
Ok just wanted to let you know.
-
This might be completely irrelevant but did you install FSX in "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X" or a different path?
-
This might be completely irrelevant but did you install FSX in "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X" or a different path?
Not relevant to any of our products, because they are all 100% UAC compliant, and are not affected by the FSX folder permissions, since they won't ever try to write in the FSX root folder, but only in the proper places such as the local appdata folder.
-
Ok thanks.
-
I tested this problem out with other airports and the same result-random missing buildings. So it isn't a Vancouver issue.
I was quite sure of that...
Oh and just to clarify it was an FSDT airport. I tried installing the Flightbeam KSFO demo and it showed perfectly with no disappearing buildings.
This is really confusing, they both use the couatl engine/simconnect right? If so why doesn't s KSFO have disappearing buildings and CYVR and PHNL (another test airport) have disappearing buildings.
-
This is really confusing, they both use the couatl engine/simconnect right? If so why doesn't s KSFO have disappearing buildings and CYVR and PHNL (another test airport) have disappearing buildings.
That's not confusing at all, it simply further proves that, whatever disappearing problems you have, are not caused by the Addon Manager/Couatl programs, otherwise it would have happened to Flightbeam airports too.
Do you have other Flightbeam airports too ? There's a difference between KSFO and the other two.
-
I actually don't, but I will try more of them (FB and FSDT products), I also tried it with Geneva same result as FB's KSFO (It worked).
-
I actually don't, but I will try more of them (FB and FSDT products), I also tried it with Geneva same result as FB's KSFO (It worked).
That even more clearly indicates there's a problem with video driver settings. Both KSFO and LSGG use less advanced materials like shaders, etc, while both CYVR and KJFK use shaders everywhere, so they could suffer from a problem with video settings.
I asked about other Flightbeam sceneries, because KSFO is the only one that doesn't require Couatl so, perhaps if there was a problem with it, you would not see it there. But LSGG does require Couatl too, like CYVR, the only difference is a simpler scenery in usage of the GPU.
P.S.
Could you please resize the image on your signature ? Is really far too big, it doesn't seem a signature, more like a posted screenshot.
-
I've tested ALL FSDT/Flightbeam airports here's the ones that did work.(meaning no disappearing buildings)
Geneva FSDT
Dallas Forth Worth FSDT
Flightbeam's KSFOX
ZhurichX FSDT
And here again are my video card settings (Both system and FSX). Is there a problem in the settings? If so what should I do to fix it?
My graphics card is a Radeon 8400HD (integrated)
(http://i.imgur.com/0LYAcXw.jpg)
(http://i.imgur.com/SDTS45U.jpg)
-
And here again are my video card settings (Both system and FSX). Is there a problem in the settings? If so what should I do to fix it? My graphics card is a Radeon 8400HD (integrated)
I can't guaranteed that the most advanced shaders will ever run on an integrated graphic card, and even if they did, they would probably have very unsatisfactory performances, see here how it compares to dedicated GPUs:
http://www.videocardbenchmark.net/gpu.php?gpu=Radeon+HD+8400
http://www.game-debate.com/hardware/?gid=1958&graphics=Radeon%20HD%208400
The only settings that we know for sure to cause problems on ATI cards, is the "Adaptive Anti-Aliasing", because it will create parts of objects randomly disappear, which is why we explicitly tell to turn it OFF in the "Design Notes" on our manuals for the more recent sceneries like KLAX or CYVR.
Of course, these is what we found using dedicated graphic cards, but when you run on integrated graphic, all bets are off, and you are really on your own on that one, because such cards don't have the same level of support for advanced shaders, they are really good for casual gaming only and in FSX, for older sceneries that don't push the graphic hardware a lot, not in the sense of scenery complexity, but in the usage of advanced material.
I can only say that, this is why we have Trial versions for,
-
Ok thanks for the help I guess its because my graphics card sucks ;D
So if I get a new graphics card will it possibly fix the disappearing buildings problem?
-
So if I get a new graphics card will it possibly fix the disappearing buildings problem?
Since the vast majority of users don't have any problems, especially not as you reported them ( *randomly* missing buildings, usually it's either all visible or it's nothing visible ), I think you will fix the problem.
But you shouldn't think you are required to change your graphic card just because our products, your *entire* flight sim will benefit greatly from a new card, compared to the one you have now.
I suggest something good but not necessarily hi-end, like the GeForce 770 or the 780, as you can see, they are in the sweet spot between price and performances:
http://www.tomshardware.com/reviews/gaming-graphics-card-review,3107-8.html
-
I'm not saying its impossible but it will be hard to get a new video card because I only have a PSU of 220W and most "good" graphics cards need a PSU of 400-500W.
I recall in an older computer I was able to run CYVR perfectly for some reason and the thing is that this computer is way better than my old one, I was actually running it(my old computer) at about 3-5 fps in a default aircraft.
-
It happens to me too, same simptoms, I see it mostly on cyvr, bu again it happens on all other airports by fsdt and flightbeam that I have, not always but it does, where a part of the terminal or a complete building won't appear. They reappear if I move closer to them. So you are clearly not the only one. I just learned to live with it :-)
Sent from my Lumia 900 using Tapatalk
Do you know the system specifications for your PC? It could help this problem.
Two other things when restarting couatl while reading my task manager the "Disk" jumps to 100% when loading or restarting couatl could this contribute to the problem? GPU temp's also stay at around 65'C when restarting. I also read that the shader's for the 8400HD version ins 5.0, is it any good?
I'm currenty still considering a new graphics card, but its a risk because it might not fix the problem. It could also bottleneck my PC at the same time making it almost no faster than my old GPU therefore a waste of $200-300.
There was also a time when I reinstalled addon manager's latest update but for some reason couatl(lets say 1) didn't close so there where two open couatl 1 and couatl 2. When restarting couatl, the buildings from couatl 2 stayed on(couatl 1 buildings dissapeared) but there was only a small pack of buildings and coincidentally it was the missing buildings without help from the 2nd couatl it wouldn't have displayed. There was no conflicting buildings, or textures, (just the missing buildings) and performance didn't decrease or increase.. There is no way I could recreate this situation but two coualt engines running seemed to have fixed it somehow.
-
Two other things when restarting couatl while reading my task manager the "Disk" jumps to 100% when loading or restarting couatl could this contribute to the problem? GPU temp's also stay at around 65'C when restarting. I also read that the shader's for the 8400HD version ins 5.0, is it any good?
I'm currenty still considering a new graphics card, but its a risk because it might not fix the problem. It could also bottleneck my PC at the same time making it almost no faster than my old GPU therefore a waste of $200-300.
I'll say it again, for the last time. That card is NOT ENOUGH for serious gaming, and FSX and P3D even more, need all the graphic card power you can get, especially for detailed add-on products. The shader version level doesn't say much (FSX uses 2.0 and P3D 4.0), if the card is too slow executing them.
You shouldn't buy it for CYVR, of course, you should buy it because with that card, FSX is on the borderline to be usable.