FSDreamTeam forum
Products Support => Los Angeles support FSX/P3D => Topic started by: audiohavoc on September 16, 2011, 11:31:11 pm
-
FYI
After installing KLAX V2, all the building disappeared after about 5 minutes, and they were also gone at KDFW, KFLL, KMDW, KORD, and KFJK. I had to uninstall and reinstall all of my FSDT airports, but now everything is as it should be. I posted this in case other users experience this phenomenon.
-
This shouldn't simply happen, but if it does, check if you have a couatl.err file in the %APPDATA%\Virtuali folder and if you have it, post its content here. In any case, there wasn't any need to reinstall all the other sceneries.
-
This shouldn't simply happen, but if it does, check if you have a couatl.err file in the %APPDATA%\Virtuali folder and if you have it, post its content here. In any case, there wasn't any need to reinstall all the other sceneries.
Here is the contents of the couatl.err file:
couatl v1.0 (build 1024)
panic log started on Mon Sep 13 14:42:37 2010
Traceback (most recent call last):
File "couatl\KDFW\__init__.py", line 65, in onAppStart
AttributeError: 'KDFW' object has no attribute 'getRwsl'
couatl v1.0 (build 1024)
panic log started on Mon Sep 13 14:46:42 2010
Traceback (most recent call last):
File "couatl\KDFW\__init__.py", line 65, in onAppStart
AttributeError: 'KDFW' object has no attribute 'getRwsl'
couatl v1.0 (build 1024)
panic log started on Mon Sep 13 14:51:36 2010
Traceback (most recent call last):
File "couatl\KDFW\__init__.py", line 65, in onAppStart
AttributeError: 'KDFW' object has no attribute 'getRwsl'
-
The error log only shows errors from Sept. 2010, this means no other errors happened after that date. If you want to be sure you have everything updated, install KLAX as the last scenery.
-
The error log only shows errors from Sept. 2010, this means no other errors happened after that date. If you want to be sure you have everything updated, install KLAX as the last scenery.
Thanks, that is what I figured and I did install LAX last. By the way, it is amazing and so nice to see the Westchester Parkway, In-n-Out, Sepulveda Blvd passing under the 25's, and the I-105. Excellent work.
-
What about only having partial buildings show up?? Like only half of the building shows up, and I also dont have any jetways that show up either. Just bought tonight.
-
What about only having partial buildings show up?? Like only half of the building shows up, and I also dont have any jetways that show up either.
That looks like another scenery in conflict. Jetways are the only thing in the scenery that are not handled at all by our two software modules (Addon Manager and Couatl), which is why they are the only thing left at the end of the Trial.
They are plain and simple standard .BGL so, and the only thing that can prevent jetways to show, it's another AFCAD from another scenery (or AI package) in conflict, you'll have to use the free FSX Airport Scanner to find AFCAD duplicates and remove them.
-
I Believe I'm having this problem as well. The scenery at times will be missing buildings/and or jetways. Rebooting FSX will correct this and all the buildings will show. As seen on the attached images the buildings are not showing up. If there is another scenery or file conflicting causing the problem, wouldn't the issue persist even after a reboot? Any assistance with this would be appreciated. Thanks a lot.
-
This is what my scenery looks like. I removed the other lax afcad that i had, and this is still what it looks like
-
I Believe I'm having this problem as well. The scenery at times will be missing buildings/and or jetways. Rebooting FSX will correct this and all the buildings will show
Buildings and jetways are not the same problem, they are entirely unrelated.
Missing jetways can ONLY be caused by another scenery in conflict.
Missing buildings, instead, might be caused by the modules not running for some reason. Check if you still have *both* the Addon Manager menu and the Couatl menu under the Addons menu, whenever you are seeing missing buildings.
-
This is what my scenery looks like. I removed the other lax afcad that i had, and this is still what it looks like
The AI parked in the wrong position can only be caused by another AFCAD in conflict which you haven't spotted yet. Nothing else can misplace an AI parking location.
-
The ai are in the right spot....
-
The ai are in the right spot....
Your screenshot clearly shows they aren't, at least one of them (the white/green one) it's not.
Or it's your airplane ? Not a very good idea taking a screenshot in that position, it really confuse things.
Anyway, do you have set any of the Compatibility modes for the FSX.EXE file ? If yes, right-click on the FSX.EXE file, select "Properties", select "Compatibility" and turn off everything in that page.
-
Find attached what i mean about missing jetways and in the background missing buildings.
-
Ya thats the user aircraft, i was slewing to the problem. Problem still persists, compatibility is off too.
-
Find attached what i mean about missing jetways and in the background missing buildings.
Ok, you are not missing any buildings: you are missing *parts* of them, which means, it doesn't have *anything* to do with installation, Addon Manager, Couatl, antivirus or anything like that. If it was, you wouldn't see anything.
Buildings with missing pieces, if you are not enabled any of the "Compatibility" options for the FSX.EXE (see my previous message) can only be caused by a wrong tweak in the FSX.CFG or a video driver issue.
You might try deleting your FSX.CFG file located at %APPDATA%\Microsoft\FSX, and let FSX rebuild one with default settings, maybe it's a tweak gone bad.
When you restore the FSX.CFG to default, be sure to re-enable the "Force HD textures" option in the Addon Manager, otherwise KLAX will look blurred. The KLAX installer automatically sets it but, if you restore the FSX.CFG, you have to set that option back.
-
I have partial buildings with pieces missing from the buildings and no jetways. everything else seems to work fine.
-
Have you tried resetting the FSX.CFG to default, as I've suggested above ?
-
not yet, i have a few tweaks, but i dont think any of those should visually affect an airport scenery..
-
not yet, i have a few tweaks, but i dont think any of those should visually affect an airport scenery..
Then make a backup of it first (for example, move it to your desktop) so you can try and eventually restore it.
-
The issue has not duplicated, yet its sporadic so I will keep you posted with the results
-
Reset my fsx.cfg and the problem still persists.
-
Reset my fsx.cfg and the problem still persists.
Try to reset also your video card driver settings to default.
-
Ok, still did it.
-
Ok, still did it.
Try updating/changing the video driver.
It's obviously a video-card related bug, there's no way we could command a building to appear *partially*, the only thing that can cause this, it's either a wrong setting or tweak in the fsx.cfg or a video card setting, or a video driver bug.
-
But why then out of all of your airports, would it only affect LAX?? Wouldnt the jetways show up still if it was indeed a graphical bug and not a programming bug or glitch?
-
But why then out of all of your airports, would it only affect LAX?? Wouldnt the jetways show up still if it was indeed a graphical bug and not a programming bug or glitch?
Not all sceneries use the same materials and shaders features, which translates into graphical commands that gets sent to the video card, the more a scenery use them, the more it might be affected if the video card driver has problems. And yes, jetways use shaders too, of two kind at the same time (vertex shaders for movement and pixel shaders for their materials).
-
I currently have the latest nvidia driver that is offered for the geforce 520
-
Here is what happens at night.
-
I currently have the latest nvidia driver that is offered for the geforce 520
The latest drivers is not always automatically the best one to use, see here:
http://www.fsdreamteam.com/forum/index.php?topic=4662.msg43219#msg43219
According to this user, the latest drivers could create issues with FSX. You might want to try the solution suggested there: lower the Scenery Complexity, maybe your system is simply too overloaded and graphic memory might be close to exhaustion.
-
I have an i7 quad, i dont think my system is overloaded.
-
Have you tried or not lowering the Scenery Complexity, which seemed to have fixed the issue for the other user in the post I've linked ?
-
I did try that, and it still didnt fix the problem.
-
Have you checked if you have the "Transparency anti-aliasing" option of the video card settings turned on ? If yes, turn it off because it creates visual problems, and the manual alerts about this.
If it's not that, then I'm sorry but, although it's clearly a problem with your system (there are exactly 2 users that reported parts of objects missing, and jhonarmstrong said it hasn't replicated), I think to have exhausted all the possible solutions.
-
Ill check that once I get home, im currently at work.
-
How many bgl files are there supposed to be in the scenery folder?? Right now I only have 6 bgl files and 80 texture files. Is that right?
-
That's how many I have. I would imagine its correct.
-
How many bgl files are there supposed to be in the scenery folder?? Right now I only have 6 bgl files and 80 texture files. Is that right?
Yes, that's correct, we don't put much in the scenery folder anymore, most of the scenery is in the Simobjects folder. The installer can't fail to copy files without giving some kind warnings and it has self-integrity checks so, it won't even start if the download was somehow corrupted.
-
This problem just doesnt make any sense.... Every other fsdt scenery works, no other lax scenery, brand new computer, have no idea what is making this happen...
-
This problem just doesnt make any sense...
Exactly, there's no way we could let just a piece of a solid object disappearing unintentionally, it would take quite a bit of modeling and programming to do it on purpose, the only possible reason is something related to the rendering system so, either it's an FSX setting, or it's a video card setting.
-
Just have no idea what setting that could be. Really unfortunate. Man you outta have me as a beta tester since im always having problems.
-
Do u think that the problem could be from me having ground environment x and ultimate terrain x textures installed but currently having utx disabled which still leaves the utx textures active??
-
I don't know if this can cause the problem but, I think those products can't by simply disabled in the scenery library, because they replace default files, so the default files should be restored.
-
Any ideas as to what could be causing my partial blurry textures as well?? My hotels, some of the terminal buildings are blurry, and the parking space spots with the different stop spots for the different aircraft are blurry.
-
Any ideas as to what could be causing my partial blurry textures as well?? My hotels, some of the terminal buildings are blurry, and the parking space spots with the different stop spots for the different aircraft are blurry.
First of all, as explained on the manual on the "Design Notes", be sure you have the "Force HD textures" option enabled in the Addon Manager, otherwise you are running at 1/4th of the overall resolution. The installer automatically sets it but, if you manually change the option or reset your FSX.CFG or edit it manually, it has to be enabled again.
If it's still blurry even with HD textures on, be sure you have Anisotropic Filtering enabled at 8x or 16x on your video card control panel.
-
I have both on, and they are still blurry... This problem is bizzare, some of the buildings are underground...
Correction I thought I had both on, but only one was on. Fixed the blurry textures part. As far as the buildings not having sides and partially underground for some, I have no idea. Still have no jetways.
-
I have both on, and they are still blurry... This problem is bizzare, some of the buildings are underground...
Blurred textures doesn't have anything to do with underground buildings or the rest of your problems.
Correction I thought I had both on, but only one was on. Fixed the blurry textures part.
I was fairly sure of that...it's seems you had multiple issues at the same time that affects visual quality, because you are getting different problems all at once.
Correction I thought I had both on, but only one was on. Fixed the blurry textures part. As far as the buildings not having sides and partially underground for some, I have no idea. Still have no jetways.
Fact you don't have jetways, clearly confirms the problem is nothing related to the scenery or our program modules, since jetways are one of the only things left in the scenery which are plain standard BGL and they have to be made in a very specific way according to the SDK, otherwise they won't move. When the Trial end, or the software are not loaded for any reason, the only thing that remains in the scenery, are the jetways.
The only things that can make jetways disappear, it's another AFCAD in conflict OR (which seems more likely in your case, considering you also have problem with partial buildings) a video driver problem.
-
Hi I also have the problem of some buildings showing up and some not. I have tried all of the things previously mentioned and I have installed the latest stand alone addon manager and also tried AI setting 0% and still the same. When the scenery loads the pillars for the buildings show but then disappear??
(http://screenshot2.BMP)
-
Hi I also have the problem of some buildings showing up and some not
No, you don't have the same problem. The problem discussed here it's that PARTS of buildings are missing, which can only be caused by a video driver problem.
Your problem is entirely different, from your screenshot it shows you have some buildings appearing entirely, and some entirely not visible. And, you are seeing the apron lights, which shouldn't appear at day.
Have you set any of the Compatibility modes for the FSX.EXE file ? If yes, right-click on the FSX.EXE file, select "Properties", select "Compatibility" and turn off everything in that page.
-
Just had a problem with the buildings disappearing after a couple minutes, but there is no error log.
-
Just had a problem with the buildings disappearing after a couple minutes, but there is no error log.
Is the scenery reported as active ?
If it's still in Trial, it just normal they would disappear, and 5 minutes are counted from the moment you select the airport in the menu so, if you wait or you FSX loads very slow, it might seem as only a couple of minutes into the flight.
-
I activated it by putting in my keycode and it reads as active and valid, but 5 mins or so into it the buildings disappear as though it's still in trial mode.
-
I tried resetting my graphics card settings, and still the problem persists.
-
I activated it by putting in my keycode and it reads as active and valid, but 5 mins or so into it the buildings disappear as though it's still in trial mode.
I got it fixed. I completely restarted FSX instead of just starting a new flight and that seems to have done the trick.
-
I tried resetting my graphics card settings, and still the problem persists.
This can only mean your graphic driver has a bug that can't be fixed by restarting settings. Have you tried to let this site:
http://www.venetubo.com/fsx.html
making an optimized fsx.cfg ?
-
Ya I have tried that website. Works great.
I guess so. Ill have to manually download some new drivers or something.
-
I just did a clean install of my graphics drivers and that hasnt worked either.
-
I just did a clean install of my graphics drivers and that hasnt worked either.
What driver version ? Did you use driver sweeper in safe mode after uninstalling your drivers ? The most stable driver is the 270.61, I would suggest trying that one. Do not use the clean install within the driver, sometimes it can cause a nvdumm.dll error in fsx, use the method above.
It would help if you post a screenie of your nvidia settings. ( Nvidia Inspector).
-
I believe its 280.26. No I did not, but I did uninstall the original ones in safe mode. Still nothing. All of my other fsdt scenerys work. I used driver sweep once, and I had major problems, and so I tend to stay away from it now.
-
I believe its 280.26. No I did not, but I did uninstall the original ones in safe mode. Still nothing. All of my other fsdt scenerys work. I used driver sweep once, and I had major problems, and so I tend to stay away from it now.
I have all the FSDT airports, including KLAX and no problems, sometimes a complex addon, like klax or even the NGX can bring out any weakness in your system, even a corrupt reg. Even your scenery config could be your problem. And of course a afcad buried somwhere. If it was KLAX, we would all have the problem. Too be honest, I would not use the 280.26, I have a GTX580, and found that driver made the card run hotter. There was reports from users that it was not all that stable with FSX, but if your happy with it, so be it. Good luck.
-
Hi I also have the problem of some buildings showing up and some not
No, you don't have the same problem. The problem discussed here it's that PARTS of buildings are missing, which can only be caused by a video driver problem.
Your problem is entirely different, from your screenshot it shows you have some buildings appearing entirely, and some entirely not visible. And, you are seeing the apron lights, which shouldn't appear at day.
Have you set any of the Compatibility modes for the FSX.EXE file ? If yes, right-click on the FSX.EXE file, select "Properties", select "Compatibility" and turn off everything in that page.
No I have never changed the FSX.EXE compatability settings, I checked just to make sure and all are un-checked. Do you have any other ideas what it might be, I have also used the FSX CFG tweak site
-
No I have never changed the FSX.EXE compatability settings, I checked just to make sure and all are un-checked. Do you have any other ideas what it might be, I have also used the FSX CFG tweak site
You are really sure you don't have another product in conflict, and you also tried resetting the FSX.CFG to default and the video driver to default, and you are sure you are not running into XP Compatibility mode, then sorry, but there's no explanation: either the software is running or it's not. If you see some buildings, it's obviously running, and they are either created all together, or none at all.
Do you have a file named Couatl.err under the %APPDATA%\Virtuali folder ?
-
I checked for that file on my system and i did not have it. I also installed the 1.1 update, but did not have time to check to see if it potentially fixed the problem.
-
I checked for that file on my system and i did not have it
scarebus has an entirely different problem than yours. Your problem can't be caused in any way by any of our programs so, it's useless in your case checking the error log because, no error of any kind could possibly cause part of objects disappearing.
I also installed the 1.1 update, but did not have time to check to see if it potentially fixed the problem.
Very unlikely, since your problem it's related to video settings, but worth trying anyways.
-
Still missing pieces with an older set of drivers.
-
What about only having partial buildings show up?? Like only half of the building shows up, and I also dont have any jetways that show up either. Just bought tonight.
YES YES this is my problem! check out my thread pls, i need help badly. With me theres no taxiway and runway textures too :/
-
This means there are two users now with the same video driver problem. But you have an additional issue too, which might be caused by another product.
-
Potentially, Im debating on reinstalling fsx or not to see if the problem persists, but I thought the cause was coming from UTX, but I uninstalled UTX and the problem still is there. I honestly have no idea what could be causing this.
Currently I am running REX and GEX. I have all FSDT sceneries except for Genieva and hawaiian vol 1 and 2.
-
I thought the cause was coming from UTX, but I uninstalled UTX and the problem still is there. I honestly have no idea what could be causing this.
As I've said, if you are still having the problem as in your previous messages (missing jetways and partial buildings) it can only be caused by a video card/driver problem, it's very unlikely a scenery or a addon like UTX could cause this.
I'll repeat it another time: jetways are the only thing we don't handle with ANY of our software, in fact they are the only thing left when the trial period ends, or the only thing that shows when our modules don't run for any reason.
The ONLY thing that can exclude jetways it's another AFCAD from another scenery that excludes them OR, if you are 100% sure there's no such file, a video card/driver problem, because they are made (by FSX, entirely out of our control) with vertex shaders so, they might be affected by video card/driver bugs.
-
Do u think having the shader 3.0 or something can cause some problems with this??
-
Do u think having the shader 3.0 or something can cause some problems with this??
Shader 3.0 is for ATi cards. The drivers you are using 280.26 are troublesome in fsx, I told you that in a previous post. You will never overcome your problem till you sort your graphic card drivers. There is no benefit upgrading to the latest drivers if FSX is all you use, no benefit whatsoever. 270.61 seem to be the most stable.
-
Idk if anyone wants to look at these, but here is a copy of my fsx.cfg and graphics card settings.
// This file was tweaked on Aug 25, 2011 at 00:56 GMT using Bojote's automated FSX Tweaking & Tuning Service
// Your 'original' fsx.cfg file was backed up at http://www.venetubo.com/fsx/47d35c12e38b80422c225dc5801dc2ad/backup/fsx_backup.cfg
// This file is optimized as follows: 4 core(s), CPU speed 3, HT 1, GPU 4, PREF 2
// You can visit Bojote's FSX Tweaking & Tuning service at http://www.venetubo.com/fsx.html
[BufferPools]
RejectThreshold=131072
UsePools=1
PoolSize=5000000
[VirtualCopilot]
VirtualCopilotActive=1
[SOUND]
AmbientUI=0
AmbientUIMusicVolume=-6.000000
PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}
SOUND=1
SOUND_LOD=0
SOUND_QUALITY=2
UISound=1
VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}
[SlewTextInfo.1]
AirSpeed=1,5
Altitude=1,3
Heading=1,4
Latitude=1,1
Longitude=1,2
[AContain]
LabelColor=FFFF0000
LabelDelay=1000
ShowLabelAirline=0
ShowLabelAirlineAndFlightNumber=0
ShowLabelAirspeed=0
ShowLabelAltitude=1
ShowLabelContainerId=0
ShowLabelDistance=1
ShowLabelFlightPlan=0
ShowLabelHeading=0
ShowLabelManufacturer=1
ShowLabelModel=1
ShowLabelTailNumber=0
ShowLabels=0
ShowUserLabel=0
[ATC]
AutoOpenAirTrafficWindow=1
COMM_MSG_AI_ATC_COLOR=FFFF7840
COMM_MSG_ATC_AI_COLOR=FF00FF00
COMM_MSG_ATC_USER_COLOR=FFB6FFB6
COMM_MSG_NONE_COLOR=FFFFFFFF
COMM_MSG_USER_ATC_COLOR=FFFFD21B
PilotVoice=0
ShowATCText=1
UsePilotVoice=1
[TextInfo.1]
AirSpeed=1,5
Altitude=1,3
Heading=1,4
Latitude=1,1
Longitude=1,2
WindDirectionAndSpeed=1,6
[INTERNATIONAL]
ASLAT=2
ASLON=1
MEASURE=0
[CONTROLS]
Controls_Current=Standard
Controls_Default=Standard
KBDAIL=64
KBDELEV=64
KBDRUD=64
[FACILITIES]
CITY=
COUNTRY=
GTL_BUTTON=1232
STATE=
[TextInfo.3]
AirSpeed=1,5
Altitude=1,3
FrameRate=2,1
FuelPercentage=2,4
GForce=2,3
Heading=1,4
Latitude=1,1
LockedFrameRate=2,2
Longitude=1,2
WindDirectionAndSpeed=1,6
[PointOfInterestSystem]
CycleSetting=0
[GRAPHICS]
AC_SELF_SHADOW=1
AIRCRAFT_REFLECTIONS=1
AIRCRAFT_SHADOWS=0
COCKPIT_HIGH_LOD=1
D3D10=0
EFFECTS_QUALITY=2
GROUND_SHADOWS=0
HIGHMEMFIX=1
IMAGE_QUALITY=0
LANDING_LIGHTS=1
NUM_LIGHTS=8
See_Self=1
TEXTURE_MAX_LOAD=4096
TEXTURE_QUALITY=3
Text_Scroll=1
SHADER_CACHE_PRIMED_10=1693458432
SHADER_CACHE_PRIMED=1693458432
ForceFullScreenVSync=1
[TrafficManager]
AIRPORT_SCENERY_DENSITY=4
AirlineDensity=100
FreewayDensity=20
GADensity=100
IFROnly=0
LeisureBoatsDensity=40
ShipsAndFerriesDensity=40
[DynamicHeadMovement]
HeadMoveTimeConstant=0.000000
LonAccelOnHeadLon=-0.000000
LonAccelOnHeadPitch=-0.000000
MaxHeadAngle=0.000000
MaxHeadOffset=0.000000
RollAccelOnHeadLat=0.000000
RollAccelOnHeadRoll=0.000000
YawAccelOnHeadLat=-0.000000
[DISPLAY.Device.NVIDIA GeForce GT 520.0]
Mode=1920x1080x32
TriLinear=1
AntiAlias=1
[REALISM]
AutoCoord=True
AutoTrim=False
CrashDetection=False
CrashTolerance=0.000000
CrashWithDyn=False
GEffect=False
General=0.000000
GyroDrift=False
GyroEffect=0.000000
ManualLights=False
PFactor=0.000000
RealMixture=False
StressDamage=False
Torque=0.000000
TrueAirspeed=False
UnlimitedFuel=True
[Weather]
AdjustForMagVarInDialog=1
CLOUD_COVERAGE_DENSITY=7
CLOUD_DRAW_DISTANCE=4
DETAILED_CLOUDS=1
DisableTurbulence=0
DownloadWindsAloft=0
DynamicWeather=4
MaxGustRampSpeed=200
MaxGustTime=500
MaxVarRampSpeed=75
MaxVarTime=50
MinGustRampSpeed=1
MinGustTime=10
MinVarRampSpeed=10
MinVarTime=5
THERMAL_VISUALS=0
TurbulenceScale=1.000000
WeatherGraphDataInDialog=0
WeatherServerAddress=fs2k.zone.com
WeatherServerPort=80
WindshieldPrecipitationEffects=1
[Misc]
Com_Rate=7
[Main]
FIBER_FRAME_TIME_FRACTION=0.20
HideMenuFullscreen=1
HideMenuNormal=0
Location=440,130,1480,908,\\.\DISPLAY1
Maximized=1
SimObjectPaths.0=SimObjects\Airplanes
SimObjectPaths.1=SimObjects\Rotorcraft
SimObjectPaths.2=SimObjects\GroundVehicles
SimObjectPaths.3=SimObjects\Boats
SimObjectPaths.4=SimObjects\Animals
SimObjectPaths.5=SimObjects\Misc
SimObjectPaths.6=SimObjects\AI_Airplanes
User Objects=Airplane, Helicopter
ProcSpeed=8178
PerfBucket=7
[Trusted]
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Cessna172.DLL.zzwqutoweiueiwwthcuuitbbnbeiterrieuiewkc=2
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\KingAir.DLL.aqtulqirziluhrerbbcbqeicubuohnrctlrbukkl=2
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\KingAir_Radio.DLL.wktrkholiktlrrqultekzqacokiwcccbaebqkzhb=2
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Magnetic_Compass.DLL.ricltukekiznalrbuouktqzqtuhruqezaruaehqi=2
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\RCB_Groundhandling5_Sound.DLL.wzbqlukucqezrlqabiiriallwbnwezriuzrrkttl=2
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll.ckoaqblunewiebhacuiwrbohnzqlrrralirozthi=1
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\bglmanx.dll.acwezbrteucatubwtaohqczotwitqllahkqabokb=1
C:\Program Files (x86)\Real Environment Xtreme\rexwxengine2.exe.rkiqqbnbbcnkztarooeleniikieoorlluiznzhbc=1
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\737-400.DLL.zlchbkrnhqauewultkbweaiqaaawzaluqbibcohh=2
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Qw757.GAU.hitqtzhtubckwiaobezrhbzkwuahnlctutokwqqk=2
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Qw757_TCAS.GAU.twooutbhlkibchnoqlcwczucwlrqthckhkclocrn=2
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Mooney_Bravo.DLL.ohuqalcltuzoalcietlqotwnlrnbleqilubktqkl=2
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\GPWS_Sound.GAU.kentubccwezeaabtltrooqnknouoihanlknnlaht=2
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Dreamwings Dash 8 -Q400\panel\dsd_xml_sound3.GAU.ecizlhtwroocalhtauwctlzneeoqirokkaqehhli=2
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Dreamwings Dash 8 -Q400\panel\FsP_LvarSupport.GAU.ieeiuliozbaanoektnozqwlokoezokuthuaqoizo=2
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\bglmanx.dll.hlqnhkizzhaquqawnklwctntinneczwwlhrutbqa=1
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe.zbzozhcuwhnkwwrwunwzobcqwbatwcazbquzuunb=1
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\bglmanx.dll.ttblhhklhriblrzktaeanqlehuqnurqhonzcohte=1
[TextInfo.2]
FrameRate=1,1
FuelPercentage=1,4
GForce=1,3
LockedFrameRate=1,2
[USERINTERFACE]
Map_Orientation=2
OpenATCOnCreate=0
PAUSE_ON_LOST_FOCUS=1
PROMPT_ON_EXIT=1
PageID=1
SHOW_MISSION_CAPTIONS=0
SITUATION=C:\Users\Brian Kircher\Documents\Flight Simulator X Files\KYUM
SelectAircraftManufacturer=All
SelectAircraftPublisher=All
SelectAircraftType=All
ShowAllACPaintSchemes=1
DisplayFuelAsWeight=1
[SIM]
SYSCLOCK=1
[Display]
ActiveWindowTitleBackGroundColor=0,28,140,64
ActiveWindowTitleTextColor=255,255,255
BLOOM_EFFECTS=0
ChangeTime=4.000000
InfoBrakesEnable=True
InfoLowerLeftBackGroundColor=255,0,0,128
InfoLowerLeftTextColor=255,255,255
InfoLowerRightBackGroundColor=255,0,0,128
InfoLowerRightTextColor=255,255,255
InfoOverspeedEnable=True
InfoParkingBrakesEnable=True
InfoPauseEnable=True
InfoSlewEnable=True
InfoStallEnable=True
InfoUpperRightBackGroundColor=0,0,0,0
InfoUpperRightTextColor=255,0,0
NonActiveWindowTitleBackGroundColor=24,33,87,64
NonActiveWindowTitleTextColor=255,255,255
SKINNED_ANIMATIONS=1
TEXTURE_BANDWIDTH_MULT=70
TextureMaxLoad=3
TransitionTime=4.000000
UPPER_FRAMERATE_LIMIT=0
WideViewAspect=True
[JOBSCHEDULER]
AffinityMask=5
[SlewTextInfo.3]
AirSpeed=1,5
Altitude=1,3
FrameRate=2,1
Heading=1,4
Latitude=1,1
LockedFrameRate=2,2
Longitude=1,2
[PANELS]
DEFAULT_VIEW=0
IMAGE_QUALITY=1
PANEL_MASKING=1
PANEL_OPACITY=100
PANEL_STRETCHING=1
QUICKTIPS=0
UNITS_OF_MEASURE=0
[STARTUP]
DEMO=0
LoadWindow=1
SHOW_OPENING_SCREEN=1
STARTUP_DEMO=0
[SlewTextInfo.2]
FrameRate=1,1
LockedFrameRate=1,2
[TERRAIN]
AUTOGEN_DENSITY=3
DETAIL_TEXTURE=1
LOD_RADIUS=4.500000
MESH_COMPLEXITY=90
MESH_RESOLUTION=23
SWAP_WAIT_TIMEOUT=2
TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=2500
TEXTURE_RESOLUTION=28
WATER_EFFECTS=5
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=3000
[SCENERY]
DAWN_DUSK_SMOOTHING=1
IMAGE_COMPLEXITY=5
LENSFLARE=0
MAX_ASYNC_BATCHING_JOBS=2
SmallPartRejectRadius=4
[FlightPlanMap]
LineWidth=2
SHOW_AIRPORTS=1
SHOW_VORS=1
SHOW_NDBS=1
SHOW_APPROACHES=1
SHOW_INTERSECTIONS=1
SHOW_VICTOR=0
SHOW_JET=0
SHOW_AIRSPACE=1
SHOW_FLIGHTPLAN=1
SHOW_WEATHERSTATIONS=1
SHOW_WEATHERSYSTEMS=1
SHOW_DATATAGS=1
SHOW_TERRAIN=1
show_waypoints=1
show_airways=1
show_markers=1
show_volume_boundaries=1
show_ac_twr=1
[MAPVIEW_MAP]
SHOW_AIRPORTS=1
SHOW_VORS=1
SHOW_NDBS=1
SHOW_APPROACHES=1
SHOW_INTERSECTIONS=0
SHOW_VICTOR=0
SHOW_JET=0
SHOW_AIRSPACE=1
SHOW_FLIGHTPLAN=1
SHOW_WEATHERSTATIONS=1
SHOW_WEATHERSYSTEMS=1
SHOW_DATATAGS=1
SHOW_TERRAIN=1
show_flight_history=1
[FSDREAMTEAM]
AntiPopUp=1
AltitudeCull=1
[MULTIPLAYER]
condAccoutPassword=0
Ambient Occlusion: Off
Anisotropic filtering: 16x
Anti aliasing gamma correction: On
Anti aliasing mode: enhance any application setting
Anti aliasing setting: 16xQ
Anti aliasing Transparency: none
Cuda: Use global setting
Extension Limit: Use global setting, Off
Max Prerendered Frames: 0
Multi Display/mixed-GPU Acceleration: Single Display performance mode
Power Management setting: Adaptive
Texture Filtering Anisotropic Sample Option: off
Texture Filtering Negative LOD Bias: Clamp
Texture Filtering Quality: Quality
Texture Filtering Trilinear Optimization: On
Threaded Optimization: Auto
Triple Buffering: On
Texture filtering – Anisotropic filter optimization: off
Vertical Sync: Force On
-
Try
Ambient Occlusion: Off
Anisotropic filtering: 16x
Anti aliasing gamma correction: OFF
Anti aliasing mode: enhance any application setting
Anti aliasing setting:8xS or 4XS
Anti aliasing Transparency: none
Cuda: Use global setting
Extension Limit: Use global setting, Off
Max Prerendered Frames: 3<<<<<That was at 0
Multi Display/mixed-GPU Acceleration: Single Display performance mode
Power Management setting: Performance
Texture Filtering Anisotropic Sample Option: off
Texture Filtering Negative LOD Bias: Clamp
Texture Filtering Quality:High Quality
Texture Filtering Trilinear Optimization: OFF
Threaded Optimization: Auto
Triple Buffering: OFF
Texture filtering – Anisotropic filter optimization: off
Vertical Sync: Force On
-
Also, turn off aircraft self shadows.
here is mine,
Compare to yours.
[GRAPHICS]
SHADER_CACHE_PRIMED_10=1693458496
SHADER_CACHE_PRIMED=1693458496
SHADER_CACHE_VERSION=64
STALE_BUFFER_THRESHOLD=2147483647
D3D10=0
HIGHMEMFIX=1
//mipbias=6
ForceFullScreenVSync=1
ForceWindowedVSync=1
TEXTURE_MAX_LOAD=4096
NUM_LIGHTS=8
AIRCRAFT_SHADOWS=0
AIRCRAFT_REFLECTIONS=1
COCKPIT_HIGH_LOD=1
LANDING_LIGHTS=1
AC_SELF_SHADOW=0
EFFECTS_QUALITY=2
GROUND_SHADOWS=0
TEXTURE_QUALITY=3
IMAGE_QUALITY=0
See_Self=1
Text_Scroll=1
[BufferPools]
//PoolSize=30000
UsePools=1
PoolSize=30000
RejectThreshold=131072
[SOUND]
AmbientUIMusicVolume=-6.000000
PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}
VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}
SOUND=1
SOUND_QUALITY=2
SOUND_LOD=1
UISound=1
AmbientUI=0
SOUND_FADER1=0.500000
SOUND_FADER2=0.500000
SOUND_FADER3=0.500000
SOUND_FADER4=-0.500000
AmbientUIMusic=FSX01
[Display]
ChangeTime=4.000000
TransitionTime=4.000000
ActiveWindowTitleTextColor=255,255,255
ActiveWindowTitleBackGroundColor=0,28,140,64
NonActiveWindowTitleTextColor=255,255,255
NonActiveWindowTitleBackGroundColor=24,33,87,64
InfoUpperRightTextColor=255,0,0
InfoUpperRightBackGroundColor=0,0,0,0
InfoLowerLeftTextColor=255,255,255
InfoLowerLeftBackGroundColor=255,0,0,128
InfoLowerRightTextColor=255,255,255
InfoLowerRightBackGroundColor=255,0,0,128
InfoBrakesEnable=True
InfoParkingBrakesEnable=True
InfoPauseEnable=True
InfoSlewEnable=True
InfoStallEnable=True
InfoOverspeedEnable=True
BLOOM_EFFECTS=0
SKINNED_ANIMATIONS=1
RUNWAY_LIGHTS_APPROACH_SCALAR=1.2
RUNWAY_LIGHTS_STROBE_SCALAR=1.0
RUNWAY_LIGHTS_SURFACE_SCALAR=1.2
RUNWAY_LIGHTS_VASI_SCALAR=1.2
SKINNED_ANIMATIONS=1
TEXTURE_BANDWIDTH_MULT=70
TextureMaxLoad=30
UPPER_FRAMERATE_LIMIT=0
WideViewAspect=True
[JOBSCHEDULER]
AffinityMask=14
[Main]
DisablePreload=1
HideInfoText=1
HideMenuFullscreen=1
HideMenuNormal=0
User Objects=Airplane, Helicopter
SimObjectPaths.0=SimObjects\Airplanes
SimObjectPaths.1=SimObjects\Rotorcraft
SimObjectPaths.2=SimObjects\GroundVehicles
SimObjectPaths.3=SimObjects\Boats
SimObjectPaths.4=SimObjects\Animals
SimObjectPaths.5=SimObjects\Misc
SimObjectPaths.6=SimObjects\UT2 Aircraft
ProcSpeed=17675
PerfBucket=7
Location=628,116,1668,906,\\.\DISPLAY1
Maximized=1
[PANELS]
IMAGE_QUALITY=1
DEFAULT_VIEW=1
QUICKTIPS=0
PANEL_OPACITY=100
PANEL_MASKING=1
PANEL_STRETCHING=1
UNITS_OF_MEASURE=0
[Weather]
AdjustForMagVarInDialog=1
CLOUD_COVERAGE_DENSITY=8
CLOUD_DRAW_DISTANCE=6
DETAILED_CLOUDS=1
DisableTurbulence=0
DownloadWindsAloft=0
DynamicWeather=2
MaxGustRampSpeed=200
MaxGustTime=500
MaxVarRampSpeed=75
MaxVarTime=50
MinGustRampSpeed=1
MinGustTime=10
MinVarRampSpeed=10
MinVarTime=5
THERMAL_VISUALS=0
TurbulenceScale=0.500000
WeatherGraphDataInDialog=0
WeatherServerAddress=fs2k.zone.com
WeatherServerPort=80
WindshieldPrecipitationEffects=1
[DISPLAY.Device.NVIDIA GeForce GTX 580.0]
Mode=1920x1080x32
TriLinear=1
[CONTROLS]
Controls_Default=Standard
Controls_Current=Standard
KBDAIL=64
KBDELEV=64
KBDRUD=64
[TextInfo.1]
Latitude=1,1
Longitude=1,2
Altitude=1,3
Heading=1,4
AirSpeed=1,5
WindDirectionAndSpeed=1,6
[TextInfo.2]
FrameRate=1,1
LockedFrameRate=1,2
GForce=1,3
FuelPercentage=1,4
[TextInfo.3]
Latitude=1,1
Longitude=1,2
Altitude=1,3
Heading=1,4
AirSpeed=1,5
WindDirectionAndSpeed=1,6
FrameRate=2,1
LockedFrameRate=2,2
GForce=2,3
FuelPercentage=2,4
[SlewTextInfo.1]
Latitude=1,1
Longitude=1,2
Altitude=1,3
Heading=1,4
AirSpeed=1,5
[SlewTextInfo.2]
FrameRate=1,2
LockedFrameRate=1,2
[SlewTextInfo.3]
Latitude=1,1
Longitude=1,2
Altitude=1,3
Heading=1,4
AirSpeed=1,5
FrameRate=2,1
LockedFrameRate=2,2
[Trusted]
C:\Program Files (x86)\EZCA\EZCA.exe.zrheiotbarrehizlbwunetowcruceerralqbewib=1
C:\Xaddons\FlyingWSimulation\SuperTrafficBoard Data Server V3.1\StbDataServer.exe.lznwlaoqezzzkotnwahwhinliblahewutuwknkbn=1
C:\Xaddons\FlyingWSimulation\SuperTrafficBoard V3.1\STBServer\STBServer.dll.zktittqnbrouqqtukqhqzzbriluqinwobrtaroch=1
D:\Flight Simulator X\FS2Crew2010\Versions\Jetstream\Gauges\FS2CrewPMDGJ41.GAU.zaikentqiclkozcrirwourkuqcowtectnhbozltq=2
D:\Flight Simulator X\FSVideoMarshaller\Gauge\FSVMJ41.GAU.nlwbzluzqnnbanawilehwhtualqwqoekbokuwaoz=2
D:\Flight Simulator X\GAUGES\AS_FS_B7.DLL.zuwubklbnbhwaccirawuouauhqoiubruqoabtioq=2
D:\Flight Simulator X\GAUGES\Bell_206B.DLL.hebchwkiwnuazincqwulwlcwkobbhuoinubtbrzq=2
D:\Flight Simulator X\GAUGES\Bell_206B.DLL.kcwuwlrtaozlqqtwcuhakkewowbrauwokzlraqek=2
D:\Flight Simulator X\GAUGES\Bendix_King_Radio.DLL.akcteuolzrekktnrlbulbqtarclrnrkztozcuila=2
D:\Flight Simulator X\GAUGES\Bendix_King_Radio.DLL.kzbackzicubtqbknleizunuzeakouacuchcwuhwa=2
D:\Flight Simulator X\GAUGES\Cessna.DLL.wlhaekzcbbwzocrokwtcbrunzttnwbhhtooqwzzb=2
D:\Flight Simulator X\GAUGES\Cessna.DLL.zwaewltlerzrkculneokczeotiaucuwhqoweouno=2
D:\Flight Simulator X\GAUGES\Cessna172.DLL.hulhtenqbnqkibtnecnatirontltankauntlewzu=2
D:\Flight Simulator X\GAUGES\Cessna172.DLL.wnwcktiteqntwqhckbchktottrohtbkhhzaorzln=2
D:\Flight Simulator X\GAUGES\Cessna182s.DLL.neckabhlalracrttqlctnnawaaaonicrlbnwhlch=2
D:\Flight Simulator X\GAUGES\Cessna182s.DLL.weabekcqqwrcnhlebqthtwrrbkzeocheqaqkblhr=2
D:\Flight Simulator X\GAUGES\CessnaWAlpha.DLL.erilzzqnurwctqnhbwqhuwzkrcrillwzunekoooo=2
D:\Flight Simulator X\GAUGES\CessnaWAlpha.DLL.nanhrzutrloicuhlcbnonzwueaciowlwecuirkeb=2
D:\Flight Simulator X\GAUGES\PMDG_747400_ACS.DLL.cwhitkbcihbkkqczbiororaurinlzuluzthlcetl=2
D:\Flight Simulator X\GAUGES\PMDG_747400_Center.DLL.uiahhuzqwqlkataulluibnewoinkbznwuotwbzkz=2
D:\Flight Simulator X\GAUGES\PMDG_747400_Main.DLL.rczqubanahetaqrhculolqqcrewknqqwqahlqhti=2
D:\Flight Simulator X\GAUGES\PMDG_747400_Main.DLL.thqwieeirrrlrwhqkclwiziaaiquozzqwaielibb=2
D:\Flight Simulator X\GAUGES\PMDG_747400_Overhead.DLL.uqzloblrlwkuubehitlnhluzlknqweiwiqolehbk=2
D:\Flight Simulator X\GAUGES\PMDG_BAe_JS4100.DLL.wkziqcwqitbrzbcurlkqubhhrkbwqtzunnantlnb=2
D:\Flight Simulator X\GAUGES\PMDG_BAe_JS4100_3.DLL.anntcwoobkukrtucuhqtoeuwlweewlnhhuqbkzoo=2
D:\Flight Simulator X\GAUGES\PMDG_MD11.DLL.hzwtohhzctilzezbibekrclwwniohaoewuqtualu=2
D:\Flight Simulator X\GAUGES\PMDG_MD11_ACS.DLL.zecqnohieqalawcwiinqihabitrqeictbqtluaai=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\crew22.GAU.nitathozuntrorckezcaqqbncqizzebwetzhioza=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\dcrew0.GAU.zoonoazelzohuhahuwoialbbczunibzhbuktltob=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew0.GAU.eeeqrtqkoezzzbkahwatiwzuaaqkaoqrlaawuwzw=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew1.GAU.qhztnqzehbbetrulrulluwwewthattkniqwrewzk=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew10.GAU.ehutlkhocnnraltrrwczhlkuwuaehlqkanwewucz=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew100.GAU.luchkcbazkheeolbazuzotulouqhhqzotqbwknol=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew11.GAU.aqbhbowtnlihtwiahqknhoorqoctbcenelnoarlu=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew110.GAU.ubweaqnotwbnqbqczkkbtqnatlqwzaackelbkore=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew120.GAU.eulqabwtqkkuktznzaqkueheiactkzelolauanbq=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew13.GAU.tkluuwcrqaukerbwcnqqaulbbzniaccqrarnuzou=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew130.GAU.ezkkqcaweaarnlwuwilkrlwuonuwtkkwrciulutl=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew15.GAU.keuqktlzkutucqerzcbtzblwbaioenqnutcnwqzc=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew16.GAU.cioczqohecaokuibineatancbetaltraknunnlih=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew18.GAU.rqhlieqhcezloczatoohaowrorebwqbeubhbzqeq=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew19.GAU.rhuhooorqqrcanazzuhrchwehleaeiltrihtqerh=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew2.GAU.eleqbkqtlklehzluuhbrcautecnziiqureuktctt=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew22.GAU.zwckckhbrearqwnenokwiwiiwikuuwwaqtqokhcr=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew23.GAU.cruznrhliurwzzqbhaozcnqwlhazhcckizwacabu=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew24.GAU.ntktehhbqarcnehbwhibrbzwuuuqbnhnlokurrqn=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew25.GAU.ztzuuelkrzlkiuiiuqtarirqnhwalkcewknziqae=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew26.GAU.ttacatkintbczrkbkuttnrhebznuaziuqwznlznl=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew27.GAU.uiwebztihaqkwuluezlkuiilzbqatuekbubkuona=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew28.GAU.uzlozrinknezwqrczkncbaaoabhlnunwczokeirn=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew29.GAU.ohqahnuhqqtrezraackwrlkrlnqurwnzoeazeeuw=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew3.GAU.rcnnwlrwqezeoqnzoqthionbhqnuioclcrtrlzhn=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew30.GAU.oetnabuuwwkbckluwllzctrrarallultcooicktn=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew31.GAU.nzzcwzotkqnqwtkoewntwkebracnicnbabluuluw=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew4.GAU.hlhwzoccenikirczwakihhtwnakazubuwqwnrntq=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew5.GAU.cttoauebureintohzlwlaoiakkqnzhzulrqrhqco=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew50.GAU.nnebooahrzrabcktuarlltaninneiwtqchbolwie=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew51.GAU.bcoboweckckzzchnbhqrebttioiochueukoloqce=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew6.GAU.iqeoeekthaclkcocbzhanqtrkibntbqzrqnehzbq=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew8.GAU.lqwhennqblqcikwetwrhrbqkkkuknnablubnlebu=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew80.GAU.ntorqnkliwqbkceekqbenieehrlqittlkbzzucur=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew9.GAU.hkbbkaktezuthaboaokrhutnlrrwrzlanbrcozct=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\gcrew90.GAU.bilwaroezlwalezucrznztkrnbrucutuwckarwwl=2
D:\Flight Simulator X\GAUGES\fs2crew\747P\weight_share.GAU.cttbcuqwonqnnqrwbenbhzilhtubzrzbiruwuebz=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\dcrew0.GAU.birqkhqahwchtbzcaralritouqriqkliuqbibice=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\dcrew0.GAU.biwnecklraebitltwrnenhohurzbrncliwilzbii=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew0.GAU.bbbhwaowakllhqzwerhuhttlwrztettoielunbeu=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew0.GAU.rwtikuqbchouectbuqrucehirwltzaqzreznliar=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew1.GAU.iitzhqicrrtzcnltqchraiihbiqozltqzqnbbuca=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew1.GAU.nelwcurnhriuwoerqeokqkakolbbkwtoluuioncl=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew10.GAU.oqkrrbrnqrcoluabnhnqtaatuhbcnboulqeuoeor=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew10.GAU.uwacboteanktintbocuriqztkheathbehtibztuw=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew12.GAU.abokcbthlzcrcuzutiwrbeiuutalcqwwbzinqwza=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew12.GAU.ccorkhroohnneraztqkinaknewozrlzbqlanuuwn=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew3.GAU.utbcwcrrhqeozznznkcoreqtzutcqzbobuihlnzr=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew3.GAU.zkorbaqlcbuanwircbeebwuulzbznabeacuaaznn=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew3w.GAU.nkntrewtczbkekztizbokhckewhikueiobkatqcz=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew5.GAU.cbtalqnlitihbinnakbobwlrboiiczketntocequ=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew5.GAU.ickictoraeubniwrazliiawtuukloaazllnnhuzr=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew6.GAU.cnkbtoieiwwtetecuqwhcztzrrcrhbekzlqbrntq=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew6.GAU.kctakqtewrrwoloenqloukieeccauqtqnornluea=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew7.GAU.kaneauwhrzuqiktttqzaeuuqwonrlibrneoibaie=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew7.GAU.occibeiuoqwoiqnaatutqikarezettarihczchwn=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew8.GAU.qenhrkwzclnioozbhhuwlilwchrktkhualcrhnoq=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew8.GAU.tzhruhhacotkbrwotnacnklaiqzzzcwnebqnuqci=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew9.GAU.hlntcecihukbqiokueeukzzozzrozobliulnkwzz=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\mcrew9.GAU.qrzwwubarbzuzucqirahlwhrzwnuhehztbhittnk=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\vcrew0.GAU.iuuntnnntquuwictqaekacqlwtkhabnetqezqlbo=2
D:\Flight Simulator X\GAUGES\fs2crew\MD11\vcrew0.GAU.rbeuboquhnzwutwoiotthzlnuqzhuzhttzhwuqtu=2
D:\Flight Simulator X\GAUGES\fs2crew\md11\mcrew13.GAU.nbuwwiqqhiqnzezceuinnzcarwncleqlzthbhbkc=2
D:\Flight Simulator X\GAUGES\fs2crew\md11\mcrew13.GAU.oiwazlcwaouhuhowhkzntnkacqaqqwtzwukizkic=2
D:\Flight Simulator X\GAUGES\isg1.GAU.trarkobuuwroklheaahlwhrcciahquowuqhiearn=2
D:\Flight Simulator X\Modules\GPSModule.dll.ukwnkaewhihoeuhwatrcrealltbaacecowlwtorr=1
D:\Flight Simulator X\ORBX\FTX_AU\FTXAA_YBCS\scenery\ObjectFlow_YBCS.dll.chbkacznwrrknkbkenhrqahrrztczettturicrcq=1
D:\Flight Simulator X\ORBX\FTX_AU\FTXAA_YMML\Scenery\ObjectFlow_YMML.dll.chbkacznwrrknkbkenhrqahrrztczettturicrcq=1
D:\Flight Simulator X\PMDG\DLLs\PMDGEvents.dll.kozncuhucktnnichanchtwntulbqucowerkiurul=1
D:\Flight Simulator X\PMDG\DLLs\PMDGOptions.dll.kllcqekzqeublhiqzberkbuwczrllikeczuarhrz=1
D:\Flight Simulator X\PMDG\DLLs\PMDGSounds.dll.zlbwzkqqbicebeatroaktebbwbwrictciucuzwbq=1
D:\Flight Simulator X\VistaMare\ViMaCoreX.dll.lnnibonckocutrbihiluozioancizanbltawiooo=1
D:\Flight Simulator X\\Flight One Software\Ultimate Traffic 2\UT2Services.exe.turtrtuzknwanohtiwcoqutlcauhtahhcarqbltn=1
D:\Flight Simulator X\bglmanx.dll.ctahccizraizeotwuekhurenetwieawthltotlrt=1
D:\Flight Simulator X\GAUGES\Magnetic_Compass.DLL.keqrebqwrzartnzibzwkwqwwhlicnorawirwclte=2
D:\Flight Simulator X\GAUGES\KingAir.DLL.acthbwhletikiutrzroucztbwzwzkaekbiktbkcl=2
D:\Flight Simulator X\GAUGES\KingAir_Radio.DLL.iaqaweoahkacwbbqataqwlrckbeilruteuaqcrhe=2
D:\Flight Simulator X\FSVideoMarshaller\Gauge\FSVM.GAU.cniwhawlcoezkkqkokieutulcnutnttbuotkeiuu=2
D:\Flight Simulator X\GAUGES\Qw757.GAU.eatrolkwqlrtqbubwnlbiqqwckizrcucltwqcurh=2
D:\Flight Simulator X\GAUGES\Qw757_TCAS.GAU.ccuwtecauewwozwaauttewhuurrwckztrrbialzu=2
D:\Flight Simulator X\Modules\FSUIPC4.dll.qbhwrztnqnzqeeqokbwbhizauzhzizlqknaqzlzb=1
D:\Flight Simulator X\bglmanx.dll.tzrwrznknqeuhzzzwakeoqzunbuzkqqkkaaohewq=1
D:\Flight Simulator XVistaMare\ViMaCoreX.dll.lnnibonckocutrbihiluozioancizanbltawiooo=1
C:\xaddons\Flight One Software\Audio Environment\AEMODULE.dll.zwohlarnorrztznqhztrczbiaqznnewzezobwaia=1
D:\Flight Simulator X\\Flight One Software\Ultimate Traffic 2\UT2Services.exe.enheehwzctuahbqlqrhzqinnqatoltwoqeubwlrq=1
D:\Flight Simulator X\fsdreamteam\couatl\couatl.exe.wrnlwtzihbleeceohqrzuaznqhazolhiiiucizcu=1
D:\Flight Simulator X\Modules\FSUIPC4.dll.uabekeilioubritwhbzilataiaekukaznznttokr=1
D:\Flight Simulator X\fsdreamteam\couatl\couatl.exe.behleknulwktzlwbinahaazcehkkqotqtleaqlee=1
D:\Flight Simulator X\bglmanx.dll.icrqhluwalnobneuaneokqebzzbtwborqhiwkenb=1
D:\Flight Simulator X\PMDG\DLLs\PMDG_HUD_interface.dll.uthaahknohkeelehohcneaawubhuieecauebrrol=1
D:\Flight Simulator X\GAUGES\PMDG_737NGX.DLL.akurkbolacotbrrtbcrbrkwquibqqtczczbhbwcb=2
D:\Flight Simulator X\GAUGES\PMDG_737NGX_3.DLL.eakblhakharlhqoouwwkltrnthubzocciklczblo=2
[DynamicHeadMovement]
LonAccelOnHeadLon=-0.020000
LonAccelOnHeadPitch=-0.010000
RollAccelOnHeadLat=0.010000
YawAccelOnHeadLat=-0.100000
RollAccelOnHeadRoll=0.100000
MaxHeadAngle=5.000000
MaxHeadOffset=0.300000
HeadMoveTimeConstant=1.000000
[VirtualCopilot]
VirtualCopilotActive=0
[USERINTERFACE]
DisplayFuelAsWeight=0
Map_Orientation=2
OpenATCOnCreate=0
PAUSE_ON_LOST_FOCUS=0
PROMPT_ON_EXIT=1
PageID=1
SHOW_MISSION_CAPTIONS=0
SITUATION=C:\Users\FSX\Documents\Flight Simulator X Files\mystart for NGX
SelectAircraftManufacturer=All
SelectAircraftPublisher=All
SelectAircraftType=All
ShowAllACPaintSchemes=1
[ATC]
ShowATCText=0
COMM_MSG_NONE_COLOR=FFFFFFFF
COMM_MSG_ATC_USER_COLOR=FFB6FFB6
COMM_MSG_USER_ATC_COLOR=FFFFD21B
COMM_MSG_ATC_AI_COLOR=FF00FF00
COMM_MSG_AI_ATC_COLOR=FFFF7840
AutoOpenAirTrafficWindow=0
UsePilotVoice=0
PilotVoice=0
[PointOfInterestSystem]
CycleSetting=0
[SCENERY]
// To show alerts or areas, set to = 1
// To hide alerts or areas, set to = 0
// Alert for missing textures
//ShowMissingTextureAlert=0
// Alert for missing objects
//MissingLibraryAlert=1
// Render Trigger areas as visible boxes
//ShowTriggers=0
DAWN_DUSK_SMOOTHING=1
IMAGE_COMPLEXITY=4
LENSFLARE=1
MAX_ASYNC_BATCHING_JOBS=3
SmallPartRejectRadius=4.0
[TrafficManager]
AirlineDensity=0
GADensity=0
FreewayDensity=16
ShipsAndFerriesDensity=16
LeisureBoatsDensity=15
IFROnly=0
AIRPORT_SCENERY_DENSITY=0
[TERRAIN]
LOD_RADIUS=5.500000
MESH_COMPLEXITY=100
MESH_RESOLUTION=23
TEXTURE_RESOLUTION=29
AUTOGEN_DENSITY=5
DETAIL_TEXTURE=1
WATER_EFFECTS=6
SWAP_WAIT_TIMEOUT=2
[AContain]
ShowLabels=0
ShowUserLabel=0
ShowLabelManufacturer=1
ShowLabelModel=1
ShowLabelTailNumber=0
ShowLabelDistance=1
ShowLabelAltitude=1
ShowLabelAirline=0
ShowLabelAirlineAndFlightNumber=0
ShowLabelFlightPlan=0
ShowLabelContainerId=0
ShowLabelAirspeed=0
ShowLabelHeading=0
LabelDelay=1000
LabelColor=FFFF0000
[INTERNATIONAL]
ASLAT=2
ASLON=0
MEASURE=0
[REALISM]
PFactor=1.000000
Torque=1.000000
GyroEffect=0.520000
CrashTolerance=0.000000
General=1.000000
UnlimitedFuel=False
TrueAirspeed=False
AutoCoord=False
RealMixture=True
StressDamage=False
GEffect=False
ManualLights=True
GyroDrift=True
CrashWithDyn=False
CrashDetection=False
AutoTrim=False
[SIM]
SYSCLOCK=1
[STARTUP]
DEMO=0
SHOW_OPENING_SCREEN=1
STARTUP_DEMO=
LoadWindow=1
[FACILITIES]
COUNTRY=
STATE=
CITY=
GTL_BUTTON=1272
[Misc]
Com_Rate=7
[MULTIPLAYER]
condAccoutPassword=0
VoiceVolume=-1.000000
-
You will also notice that I have fsx installed in it's own HDD, and not in the infamous proggyfiles x86. Your asking for hassles having it installed where it is. It's not a tweak, but a fact.
-
Ill try those settings when I get home. Thanks for the help.
-
This shouldn't simply happen, but if it does, check if you have a couatl.err file in the %APPDATA%\Virtuali folder and if you have it, post its content here. In any case, there wasn't any need to reinstall all the other sceneries.
WHERE CAN I FIND THIS FILES I AM EXPERIENCING THE SAME PROBLEM WHEN START THE GAME ALL THE BUILDINGS ARE VANISH AND JUST REMAIN THE JETWEYS
-
Hey I tried those settings you recommended me applying, and I still have nothing.
-
This shouldn't simply happen, but if it does, check if you have a couatl.err file in the %APPDATA%\Virtuali folder and if you have it, post its content here. In any case, there wasn't any need to reinstall all the other sceneries.
WHERE CAN I FIND THIS FILES I AM EXPERIENCING THE SAME PROBLEM WHEN START THE GAME ALL THE BUILDINGS ARE VANISH AND JUST REMAIN THE JETWEYS
Stop yelling!!!!
-
Hey I tried those settings you recommended me applying, and I still have nothing.
You have someting configured wrong, You might have alread done this, have you installed stand alone addon manager ?
-
Yes.
-
Yes.
By any chance using UTX ? An if so, is it in the scenery layer below all FSDT airports ?
-
I bought LAX just the other day, Saturday night I think and it worked fine for the few minutes I tested it with the default Jet Ranger.
The next day, I fired up FSX with LAX again and spent about 30 minutes looking around the airport, then switched to night time and looked around more. Everything worked fine and no problems.
A few hours later I returned to FSX, loaded up LAX with the default Ranger again and for some reason all the building were missing this time, except for the jetways. Total mystery since I had already used FSX and LAX a few times already, hadn't made any changes in FSX or on my computer, checked the exe.xml and dll.xml to make sure all the entries were still there, which they were, and also checked Addon Manager while in FSX to make sure it was activated, which it was.
Turned out for some reason, even after FSX has been closed, I opened the task manager and the Couatl process was still running, which after shutting down FSX it usually closes. I manually closed the process, started FSX again and went to LAX and the buildings were back. For some reason I have noticed the once in a while with the latest version of Addon Manager installed, couatl keeps running or doesn't shut down upon the exit of FSX.
Not sure if this is the case with why you guys are having a problem with the buildings disappearing, but I thought I would mention it since the same thing had happened to me and I was able to fix it by closing the Couatl process myself.
-
I confirmed this.
But the couatl not closing is the first session of FSX only. After that, second session, third session......everytime the couatl closed normally.
-
I confirmed this.
But the couatl not closing is the first session of FSX only. After that, second session, third session......everytime the couatl closed normally.
I noticed that after I closed it manually the first time, when I exited FSX the second time it was still running again and had to manually close it again.
Not sure if its a bug as Ihave never checked in the past, but in all the years using FSDT airports, I have never noticed Couatl running after FSX was closed. Perhaps a bug? I dont know, maybe its something Umberto can check and get back to us on.
-
Yes, you're right about the second session.
I'm sure Virtuali will check it and do something about it, because at least two users confirmed that.
-
By any chance using UTX ? An if so, is it in the scenery layer below all FSDT airports ?
I used to have utx, and yes it was below most fsdt sceneries. Now, I no longer have it, I uninstalled it and reinstalled the GEX textures.
Also what is this about the coutl engine?? What do I need to look for so I can confirm it as well.
-
Also what is this about the coutl engine?? What do I need to look for so I can confirm it as well.
Just press ctrl-Alt-del and bring up the task manager and click on the processes tab and see if couatl is still running after you exit FSX. It should turn off once you exit FSX but in my case it hadn't and when I started FSX again with it still running and went to LAX all the buildings were gone.
-
There's no bug, it's just that, if you are using lots of memory-hungry addons that takes lots of memory, it will take a while for FSX to close properly, even if you don't see it on screen anymore so, if you launch it again, it's possible that couatl didn't get the chance to be properly shut down by FSX.
Just to be clear: it's FSX itself that has to shut down couatl.exe when it closes, it's not couatl.exe that needs to take care of its own shut down, it's entirely outside our control, maybe if it *was* under our control, it would work...
-
Thanks Virtuali.
I didn't know "it's FSX itself that has to shut down couatl.exe when it closes, it's not couatl.exe".
I should have known it. I knew it takes some time to shut down FSX completely............
Your explanations are always logical and clear that I've been quite impressed by.
-
In any case, we are working at adding additional safety measures to have Couatl self-quit in case FSX panics is some way and can't shut it down properly.
-
I dont think that problem of the coutl engine shutting off will help my case of partial buildings.
-
I dont think that problem of the coutl engine shutting off will help my case of partial buildings.
Surely not, if there's a Couatl process stuck from the previous run, you would see no buildings at all and no Couatl menu on the next FSX run. Your problem is clearly caused by a video driver/card issue.
-
Man Ive tried everything, all the recommended settings, drivers, and I still get nothing to work.
-
I installed DTKLAX yesterday. Am having the same problems. No buildings.
Have read through all the forums.
I have the add-ons drop down, and the add on manager, with the virtuali page.
I also installed with the Avast, anti-virus turned off.
Thanks,
JerryF
-
Man Ive tried everything, all the recommended settings, drivers, and I still get nothing to work.
Since your problem can only be caused by a video driver problem, there's nothing in the KLAX installation that can fix it, you need to fix your video driver problem.
It get confusing here, because we are mixing problems and suggestions related to simply missing buildings (which *are* created by errors in installation and can be fixed using the proper install procedures) and your specific problem of partial building missing, which is entirely different and it's not related in any way to the scenery.
-
I have the add-ons drop down, and the add on manager, with the virtuali page.I also installed with the Avast, anti-virus turned off.
As explained in all the thread, having just the Addon Manager under the addons menu it's not enough: you need to have BOTH menus, Addon Manager AND Couatl powered products. If one is missing, no buildings will show.
Do you have both menus, or just one ?
-
It just sucks that nothing can be done.
-
Hello,
It could be important, not only looking to the differences of the problem, but try to find out, if there is some connection between all those people, having a problem with disappearing buildings, partial or all buildings.
For instance: who of you had installed KLAX2 V1.0, and then after unstalling this, installed the update KLAX2 V1.1?
Kind regards,
Henk
-
if there is some connection between all those people, having a problem with disappearing buildings, partial or all buildings.
As already explained, partial or all disappearing buildings are ENTIRELY different problems.
PARTIAL disappearing buildings don't have anything to do with KLAX and its different releases: they are a video card/driver problem, don't waste your time trying to uninstall/reinstall KLAX, because it doesn't depend in any way by it.
ENTIRELY disappearing buildings are most commonly a problem of the antivirus so, first check that one and check that both the Addon Manager and the Couatl menus are there.
If you are reasonably sure it's not the antivirus, install KLAX 1.1 and, if you reinstall another FSDT scenery using an older installer, either install the Stand-Alone Addon Manager for FSX OR reinstall KLAX 1.1 again.
-
Umberto,
Thanks for your answer. However, I did not ask you for this answer, because your answer is exactly a beautiful example of the way you lead this forum. Beleive me, I have read this thread (and many other threads) carefully, and I know what you have answered to all of the posts in this thread.
My question was clear: I invited the forum members to answer my question, and I really hope they will react. I'm a member of many forums, and in almost all forums: forum members try to help other forum members, and the forum leader is (of course) invited to contribute, no doubt. But, please don't make this a two-way discussion again. We are not little children anymore, that should be guides by Daddy alone.
Sorry for saying this, but it irritates me.
So again to the forum members: let's try to find the solution together.
Best regards,
Henk
-
However, I did not ask you for this answer
Since this is our own support forum, replies will come whenever we believe they are necessary.
because your answer is exactly a beautiful example of the way you lead this forum
Exactly: with the utmost attention to giving correct answers and trying not to confuse people.
Since discussing two things that are ENTIRELY unrelated, which is partial vs entirely missing buildings, as if they were in some way related, WILL confuse people and will only result in wasting their time applying solutions that are correct for only one type of the problem, to an entirely unrelated one, it's important I will always repeat this, because not everybody (nobody, in fact) reads all threads entirely.
I'm a member of many forums, and in almost all forums: forum members try to help other forum members, and the forum leader is (of course) invited to contribute, no doubt. But, please don't make this a two-way discussion again
This is not a public discussion forum, it's our own support forum, which means users should always ask to the source for support, if they have to rely on other users for help because we can't fix their problem, it means we are failing doing our job as support, and we don't have the slightest intention of even start giving the impression we don't support everyone as best as possible.
So again to the forum members: let's try to find the solution together.
There's nothing to be found, because there's such thing as "the" problem. There are lots of different things that can happen, which requires to be dealt separately and with different solutions.
If anyone still doesn't see buildings after installing the latest KLAX 1.1 and after being sure no older installers were launched after it (in this case reinstalling the latest KLAX 1.1 or the latest Addon Manager will fix it), report here, and will see his own specific case and will look for his own specific solution.
If anyone still sees partial buildings, it's probably better to open a separate thread about this, because it's nothing related to KLAX, not directly at least, meaning KLAX is made in a way that is triggering some kind of video driver problem that you already had, or a memory leakage you already had.
-
Lets not fight about whose who and who can do what. That will solve nothing
I just would like to find a solution. To me I honestly have no idea how it could be a video card issue. Ive never had any issues with any scenery or fsdt scenery in particular as far as video card settings go. Ive tried everything that could potentially make a difference, and nothing works, which is why to me I think its something other than a video card problem.
-
Ive never had any issues with any scenery or fsdt scenery in particular as far as video card settings go
This is fairly different that any of our other sceneries. KDFW maybe it's the closest thing, but KLAX is way more complex, meaning it require a bug-free video driver, because it relies MORE on shaders than KDFW. All other FSDT sceneries don't have anything in common with KLAX.
Ive tried everything that could potentially make a difference, and nothing works, which is why to me I think its something other than a video card problem.
It's surely a video card/driver problem and, even if you tried acting on the video card settings and nothing happened, it can still be a video card/driver problem, which probably doesn't manifest unless you have a specific combination of installed addons under a specific combination of video cards/drivers and settings.
If the problem was the scenery, everyone would see it but, instead, I think there are 2-3 users at most that reported *partial* buildings which, as I've said, it's really a unique problem. Those buildings are modeled to be solid meshes, we wouldn't be able to make them disappearing in parts even if we wanted to do it on purpose.
-
Its like your suggesting me to buy a new card just to run this scenery. I wont do that. If i had probelms with video card drivers, id be having problems with my other games as well. I dont. They all run just fine. I love your guys' support, but Im kind of getting frustrated because the common goal here should be to fix the problem and make it run for everyone, yet thats not exactly happening here. Im sorry but I wish something else could be done.
-
Its like your suggesting me to buy a new card just to run this scenery. I wont do that. If i had probelms with video card drivers, id be having problems with my other games as well. I dont. They all run just fine. I love your guys' support, but Im kind of getting frustrated because the common goal here should be to fix the problem and make it run for everyone, yet thats not exactly happening here. Im sorry but I wish something else could be done.
Don't compare using other games when it comes to FSX. Your problem is your video card is not rendering correctly, and the main reason for that is your driver, as I have stated several posts back. To overcome this ambiguity you are having with partial building will require you to ditch your current driver, 280.26 (assuming you are still using it) and install 270.61.
The 270.61 display driver is the best for rendering in fsx Nvidia display cards 200,400 & 500 series. As Umberto said, unless you adress the video card driver issue, you will continue to see partial buildings and other weird things, and not just in KLAX either.
The downside for you is not having a dedicated fsx computer, and as you run other games, you have to decide which is more important.
-
Don't compare using other games when it comes to FSX. Your problem is your video card is not rendering correctly, and the main reason for that is your driver, as I have stated several posts back. To overcome this ambiguity you are having with partial building will require you to ditch your current driver, 280.26 (assuming you are still using it) and install 270.61.
Ive mentioned before that I have tried that driver........ Nothing works!
-
Don't compare using other games when it comes to FSX. Your problem is your video card is not rendering correctly, and the main reason for that is your driver, as I have stated several posts back. To overcome this ambiguity you are having with partial building will require you to ditch your current driver, 280.26 (assuming you are still using it) and install 270.61.
Ive mentioned before that I have tried that driver........ Nothing works!
Ok, then something is causing your driver to not render correctly, maybe a rouge file from previous install. The ultimate test would be to try another video card. I know you don't like driver sweeper, but I have been using that for yonks, without a problem. You might have to bite the bullit and try it again...then install the 270.61 driver again. When troubleshooting, it is not over till the fat lady sings.
-
Can u give me some detailed instructions on how to use driver sweeper? Ill be willing to try it, I just dont want to mess anything up.
-
Can u give me some detailed instructions on how to use driver sweeper? Ill be willing to try it, I just dont want to mess anything up.
Ok, Step1: go to add/remove in control panel, uninstall nvidia driver
2: reboot, as the bios loads, tap F8 and go into safe mode. Windows help will load, slowly (remember you in safe mode, everything runs slowly) close that.
3: Open Driver Sweep from the icon on the desktop
4: You will see a list of installed drivers like sound and graphic drivers, just make sure any entries ticked are only Nvidia.
5: click Analyze, then remove.
6: Reboot when fin.
7: Now install your 270.61 drivers, select custom install, and if you do not use 3D Vision, untick all the boxes except Graphics drive.
8: Reboot PC
9: Now the setting up the driver will require NVidia Inspector. http://hw-lab.com/nvidia-inspector-1-9-5-5.html
10:install if not already, and adjust your display setting. Do not use Nvidia Control panel. For instructions on setting this up, go here
http://www.simforums.com/forums/nhancer-settings-for-new-drivers-updated-v1932_topic36586.html
-
6: Reboot when fin.
Reboot to what, reg or safe mood?
-
6: Reboot when fin.
Reboot to what, reg or safe mood?
Reboot after driver sweeper has finished, back into normal windows mode. then install 270.61
-
Ok thnaks, what is your current ds version?
-
Ok thnaks, what is your current ds version?
3.2.0
-
Ok thanks, do I need nhancer?
-
The setting names dont match your link with how to set it up.
UPDATE
Followed your steps and I still have the problem.
-
Ok thanks, do I need nhancer?
Use the link #9 Nvidia insp. Nhancer no longer works with driver version 195.xxx above
-
The setting names dont match your link with how to set it up.
UPDATE
Followed your steps and I still have the problem.
Nothing else I can suggest. As it is not a error with FSDT KLAX, you will need to look at something else. Scenery config could be corrupted, or something in your windows registry moe like.
-
Ok, Im gonna reinstall fsx, and see if that does anything. In the process of backing everything up.
-
FINALLY!!!! I finally got it working with the reinstall of FSX. Thanks to all that helped, it turned out to be I guess a faulty cfg and not a video driver error.
-
FINALLY!!!! I finally got it working with the reinstall of FSX. Thanks to all that helped, it turned out to be I guess a faulty cfg and not a video driver error
Were you able to identify which .cfg was ? The fsx.cfg maybe ? In fact, this was one of the first suggestions I've made:
http://www.fsdreamteam.com/forum/index.php?topic=4687.msg43546#msg43546
But you said you already tried that. Note that, it could be still a video driver issue, which was triggered by tweak in the fsx.cfg that might affect only some cards.
If it's not the fsx.cfg, it would be helpful to know which one was, perhaps we could detect it in the installer and fix it.
-
FINALLY!!!! I finally got it working with the reinstall of FSX. Thanks to all that helped, it turned out to be I guess a faulty cfg and not a video driver error
Were you able to identify which .cfg was ? The fsx.cfg maybe ? In fact, this was one of the first suggestions I've made:
http://www.fsdreamteam.com/forum/index.php?topic=4687.msg43546#msg43546
But you said you already tried that. Note that, it could be still a video driver issue, which was triggered by tweak in the fsx.cfg that might affect only some cards.
If it's not the fsx.cfg, it would be helpful to know which one was, perhaps we could detect it in the installer and fix it.
Umberto, I noticed the user had a few pre SP2 tweaks in his FSX config, it did not concern me at the time as I thought he deleted the cfg and was using a rebuilt one. Maybe not ? That's why I concentrated on the video driver.
-
I stated quite a bit earlier in the topic that it was not the fsx.cfg, cause I did what you said to do virtuali, which was to delete the cfg and let fsx rebuild it. I believe it was a faulty scenery.cfg. I had a funny feeling that it was that to begin with due to ultimate terrain changing so much and then me not using it.
-
I stated quite a bit earlier in the topic that it was not the fsx.cfg, cause I did what you said to do virtuali, which was to delete the cfg and let fsx rebuild it. I believe it was a faulty scenery.cfg. I had a funny feeling that it was that to begin with due to ultimate terrain changing so much and then me not using it.
Glad you got it fixed. BTW, don't put the following back in your fsx.cfg
FIBER_FRAME_TIME_FRACTION=0.33 & SmallPartRejectRadius=2 - useless after SP2
TERRAIN_MAX_AUTOGEN_TRESS_PER_CEL=1200 &
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CEL=800 - may cause stutters
-
I have done a fresh install of FSX and I still have the problem of some buildings not showing. I have the HD textures setting in my FSC.cfg and I have my scenery settings set as per the operations manual. I am using an ATI video card. As it stands I am un able to use this addon since I purchased it on release day and wanted to know if a fix has been found for this problem?? The only other addons installed are FSGX 2010 Ultimate Terrain USA and Ground Enviroment Nhanced USA.
-
As it stands I am un able to use this addon since I purchased it on release day
The Trial version was available since release day, you could have chosen not to purchase it, if it didn't work on your system.
Have you installed the current 1.1 version ?
and wanted to know if a fix has been found for this problem??
The problem is not the scenery, the only thing we can found, is what wrong setting in FSX affects it. Your FSX install is surely not fresh, since you installed two very large addons. Did you tried the scenery *before* installing them, when FSX was *really* fresh ?
However, from your description of the problem, it doesn't seem to the the same of bkircher: you said you have *some* buildings missing, he had *parts* of buildings missing. Please, describe exactly if this is your problem, and which buildings are missing and if whole buildings are missing, or just parts.
-
I should have said I installed v1.1 the main terminal complex is visible but others not but the jetways are visible, also the cargo buildings are not visible. I have taken some screenshots to show you what I mean.
-
Your problem seems to be different that bkircher, he had *parts* missing from all buildings, you have *some* buildings entirely missing.
However, since I see non-default AI in your screenshots, you surely added other addons in addition to FSX. Since you said your FSX install it's "fresh", couldn't you simply try to install KLAX 1.1 as the FIRST thing you do after installing FSX *really* fresh (maning FSX + SP2 and nothing else) ?
BTW, I have FSX+UT2 installed, and of course there are no problems whatsoever at KLAX. And yes, I have an ATI too.
-
ok I will try with just fsx and lax v1.1 and see what I get, thx for your help so far.
-
Ok after just installing a clean fsx and sp1+2 and default ai all buildings displayed correctly but then after 2 or 3 times of loading the airport the same problem returns of only some buildings displaying. I am really stumped do you think it is a problem with my graphics card because when i come out of windowed mode and go back into full screen mode most of the textures are gone and the sky is black so i have to close fsx and restart.
-
I am really stumped do you think it is a problem with my graphics card because when i come out of windowed mode and go back into full screen mode most of the textures are gone and the sky is black so i have to close fsx and restart.
Yes, that would indicate your video card has issues.
Exiting/Entering full screen mode IS a tricky operation, it's likely the driver could have problems, and it usually quite slow (it takes up to 10 seconds on my system, but it works ok), so I guess if the video driver has some issues, this could be critical.
-
I will try updating the driver then and see if that sorts. Thx ;)
-
I have installed the latest driver but still have same problem. Is there something in the Catalyst control centre that I am not setting correctly, wot do you have yours set to?
-
I have installed the latest driver but still have same problem. Is there something in the Catalyst control centre that I am not setting correctly, wot do you have yours set to?
Everything is reset to default, except Force Antialiasing 4x and Force Anisotropic 16x.
-
I finally managed to sort the problem of only some buildings appearing by re-allocating the memory in the bios settings which i forgot to do when i recently re-built windows but now each time I load a flight at klax i am getting an ntdll.dll fault and ctd. It is really weird because if I load a flt at any other airport which are all default as KLAX is the only addon airport i have installed it loads correctly and no ntdll.dll ctd.
-
I finally managed to sort the problem of only some buildings appearing by re-allocating the memory in the bios settings which i forgot to do when i recently re-built windows
So that's confirms what I was saying all along, that it was something related to the video card.
but now each time I load a flight at klax i am getting an ntdll.dll fault and ctd
ntdll.dll crash doesn't have anything to do with the scenery either, it's a low-level memory allocation problem, possibly related to the above video card issue, but it's difficult to say. As usual, fact that it happens at KLAX only, doesn't mean anything, since you said it's the only addon airport with everything else default, it can simply mean your memory problem happens only when more than a certain amount of it is requested, and the default airports are not complex enough to trigger it.
-
hello together..just wanted to chime in...the reason i registered i downloaded the trial of FSDT LAX 1.1 today and what do you know? with addonmanager 2.8.1.0 i got the VERY same issue...no buildings at all at any given FSDT scenery...
i found with older versions (2.8.0.8 ) i do get buildings for a short while before i get the couatl error (cryptographic panic bla bla)
and btw i highly doubt its related to the graphics card or anything else...it ALL basically points to the addon manager itself causing the problem i can run trial versions of the sceneries just perfectly fine with any addonmanager version BELOW 2.8.1.0....very interesting i most certainly will refrain from purchasing this very fine looking scenery with problems like that
btw: running a slightly OC'd i7 with an nvidia 480 on w7 x64
-
hello together..just wanted to chime in...the reason i registered i downloaded the trial of FSDT LAX 1.1 today and what do you know? with addonmanager 2.8.1.0 i got the VERY same issue...no buildings at all at any given FSDT scenery...
It's not possible that, by downloading KLAX today, you would end up getting the 1.1 version, since the current version is 1.2.1 and it's online since October 25th, I've downloaded it again now, just to be absolutely sure, and I can confirm it IS version 1.2.1 (check the installer when it starts)
So, if you really have version 1.1, is expected it won't work. It's possible you downloaded before th 25th, but you installed it only now ? Or you downloaded it again but you already downloaded before, so your browser has cached the download giving you the previous version again ?
Try to download after clearing the browser cache, and be sure the installer reads 1.2.1 when it starts.
and btw i highly doubt its related to the graphics card or anything else...
You are confusing with an entirely different problem a couple of users had, with *some* parts of buildings missing, not just the whole scenery missing, and THOSE are surely caused by video card problem, but have nothing to do with your problem.
-
alright yes you are correct that was a bit weirdly stated it IS 1.2.1 i didnt know you updated it internally i was referring to 1.1 of the scenery (with the updated buildings etc.) but the problem remains unfortunatley
so what has to do with my problem? i double and triple checked a good install of the trial and the state of my machine and FSX... as i said i can run older FSDT releases just fine with the older addonmanager but as soon as i got 2.8.1.0 on my system stuff starts to go downhill
-
so what has to do with my problem? i double and triple checked a good install of the trial and the state of my machine and FSX... as i said i can run older FSDT releases just fine with the older addonmanager but as soon as i got 2.8.1.0 on my system stuff starts to go downhill
Don't install the old Addon Manager, remove it, uninstall KLAX, reply YES to the question "Do you want to remove the Addon manager?" and reply YES to the question "Do you want to remove the Couatl scripting engine?" which are made at the end, then reinstall KLAX 1.2.1 and it will work.
Of course, be sure you HAVE the Addon Manager menu AND the Couatl menu in FSX, because if you don't, that's a whole entirely different problem that just not having the current version of KLAX, and it's surely related to antivirus or other issue that prevent the program to run. And, if you see startup error messages, please report them here.
-
so what has to do with my problem? i double and triple checked a good install of the trial and the state of my machine and FSX... as i said i can run older FSDT releases just fine with the older addonmanager but as soon as i got 2.8.1.0 on my system stuff starts to go downhill
Don't install the old Addon Manager, remove it, uninstall KLAX, reply YES to the question "Do you want to remove the Addon manager?" and reply YES to the question "Do you want to remove the Couatl scripting engine?" which are made at the end, then reinstall KLAX 1.2.1 and it will work.
Of course, be sure you HAVE the Addon Manager menu AND the Couatl menu in FSX, because if you don't, that's a whole entirely different problem that just not having the current version of KLAX, and it's surely related to antivirus or other issue that prevent the program to run. And, if you see startup error messages, please report them here.
alright so...i did run a clean install as you said my antivirus, firewall etc. are OFF and disabled...my UAC and DEP are also OFF and have been for a long while...
the only messages at FSX start where the ones to allow the modules to be loaded...confirmed with YES as usual
result: NO buildings NO addonmanager and NO couatly menu in FSX
proof: see attach
-
the only messages at FSX start where the ones to allow the modules to be loaded...confirmed with YES as usual
result: NO buildings NO addonmanager and NO couatly menu in FSX
Ok, so your problem is not the scenery version, is that BOTH modules are not even *running*. Fact that both are not running, seems to indicate that, more than an antivirus problem (which usually affects Couatl only), could be a problem with your Windows configuration, you are likely missing some system libraries, or some of them are corrupted.
Some users fixed this by running Windows Update and being sure everything on the system is updated.
-
i *AM* 110% *SURE* that my system is A. UP-TO-DATE and B. Configured *CORRECTLY*
again: FACT that i can PROOF: if i install any given scenery with any given older addon manager it WORKS till i get the cryptographic signature panic from couatl but that IS normal i KNOW
but for the sake of argument i tried the very same KLAX 1.2.1 installer on my notebook with a basic FSX SP2 install and it DID NOT WORK!
you want to teamview onto my system to see for yourself? or do you have any more "advice" for me to follow before you actually _START_ to investigate the problem?
-
i *AM* 110% *SURE* that my system is A. UP-TO-DATE and B. Configured *CORRECTLY*
And HOW I was supposed to KNOW, without ASKING first ?
again: FACT that i can PROOF: if i install any given scenery with any given older addon manager it WORKS till i get the cryptographic signature panic from couatl but that IS normal i KNOW
This simply means that what's wrong on your system which is preventing the current version to work, wasn't affecting the previous version, but still doesn't mean the new version doesn't work, otherwise it won't work for *everyone*, not just you...
but for the sake of argument i tried the very same KLAX 1.2.1 installer on my notebook with a basic FSX SP2 install and it DID NOT WORK!
Sorry, but this can't be. Before replying to you yesterday, I downloaded the installer again from our website (just to be sure there was nothing wrong with it), and of course it worked right away.
you want to teamview onto my system to see for yourself? or do you have any more "advice" for me to follow before you actually _START_ to investigate the problem?
Yes, please send me a PM with your session code. And please, stop communicating this way, what's those double quotes around "advice" and that emphasis on _start_ as if you WEREN'T being supported already ?
[/quote]
-
but for the sake of argument i tried the very same KLAX 1.2.1 installer on my notebook with a basic FSX SP2 install and it DID NOT WORK!
Sorry, but this can't be. Before replying to you yesterday, I downloaded the installer again from our website (just to be sure there was nothing wrong with it), and of course it worked right away.
well i am most certainly not lying to you fact of the matter is i tried a freshly(!) downloaded LAX 1.2.1 installer on my laptop with an almost identical FSX configuration and again i didnt have either the addonmanager nor couatl in the addons tab
both my desktop and laptop are kept in as perfect as possible condition system wise the only other idea that i have is that it MIGHT clash with some other addon i have installed...
further more...for testing purpose i installed a pretty old version, 2.8.0.2 to be exact, of the addon manager and poof...i had both entries in the addons tab same goes for every other version i tested up to 2.8.1.0...so either i am missing some EXTREMLY weird and small detail OR there is a problem with the addonmanager itself...
those are the two options you can hardly argue with that imho...
i am sorry for comming of harsh but im just stressed out by that and pretty angry i cant use my other FSDT sceneries at the moment without rolling back
-
well i am most certainly not lying to you fact of the matter is i tried a freshly(!) downloaded LAX 1.2.1 installer on my laptop with an almost identical FSX configuration and again i didnt have either the addonmanager nor couatl in the addons tab
You already said this, NOBODY is saying you are "lying", I believe you have this problem, but it's sure it doesn't have anything to do with the Addon Manager or the installer, since (as I've said) it works just fine here.
further more...for testing purpose i installed a pretty old version, 2.8.0.2 to be exact, of the addon manager and poof...i had both entries in the addons tab same goes for every other version i tested up to 2.8.1.0...so either i am missing some EXTREMLY weird and small detail OR there is a problem with the addonmanager itself...
You already said this, and I've already said it's a waste of your time keep trying the old version, which won't work with KLAX in every case so, why keep trying ?
i am sorry for comming of harsh but im just stressed out by that and pretty angry i cant use my other FSDT sceneries at the moment without rolling back
You asked to connect with Teamviewer, and I already said it's OK and you should have sent me a PM with your session code by now, I'm still waiting...yes IT IS Sunday, but I'm still waiting nonetheless to help you so, please, stop the "very angry" thing, and I'll have a check on your system.
-
PM sent...i belive its not in the out box tho
-
ok so after a bit lengthy teamview session the problem was found and solved and what do you know? it was my own fault/problem all along
thanks again to umberto for helping me on a sunday evening now i can go and enjoy these great sceneries the way they're meant...
a word of wisdom: dont EVER try to mess with the fsx.exe...it will do you no good ::)
-
I have a similar problem as (BKIRCHER) either the parts of the buildings are missing or you can just see through the building & You cant see any Jetways at all.
I have both Couatl & addon manager in the drop down menu's.
I have re-installed the KLAX & updated with v1.3 it along with the addon manager & Couatl.
My Video card is up to date (Nvidia 295 update)
I have deleted the FSX.CFG and let FSX create a new one.
I have made sure to un-check the boxes from FSX.EXE
I have put my video card to default settings (with no luck)
I have set the antialiasing to off
I have set my fsx graphics to minimal and traffic to "0"
I have read all 10 pages followed up every possible answer and I can only come up with the following:
1. My video card is what I call maxed out/ cant keep up with what FSX wants to do.
2. I have mega scenery (Los Angeles & Phoenix ) Installed.
3. I have UT2 Installed (but disabled).
4. I think its either (1 or 2) like "virtuali" had previously stated to "BKIRCHER"
5. I would hate to reinstall FSX again but if that's my only option then I guess I will do it.
My system if it helps is a Asus-G71GX laptop
Windows 7
FSX with SP2 installed
2.6Ghtz processor (Intel Core 2 Duo)
6gb Ram
Nvidia GTX 260M video card (with 295 update)
I just purchased FSDT GSX & KLAX and would greatly appreciate some help please thank you.
-
Your problem doesn't have anything to do with the installation of KLAX, which is correct, and doesn't have anything to do with antivirus, etc. You have both the Addon Manager menu and Couatl running and you have the scenery, although it's missing some part, but this clearly indicates everything is running fine, there are no installation problems.
Putting all settings to minimal, also, is not a very good idea, there are bugs in FSX that objects disappear if you turn the Autogen entirely off.
Also, you should first try using *everything* at default on the video card. Something in your screenshot doesn't look right: you have the card set for 8x antialiasing and 16x anisotropic filter, which should give you a very good graphic quality, but your screenshots are really bad, with no antialiasing and no anisotropic at all, so it seems something is wrong with the video settings.
If you are sure you don't have FSX in any of the Compatibility modes (which causes problems with part of buildings disappearing), since the programs are running correctly, it can only be something wrong in your system installation that is affecting the video card, if you can't find it, a Windows reinstall will surely fix it.
-
Thanks for the reply ;D
I put Video Card and FSX Autogen to default settings and it still came out the same. So I went back and set the video card to the previous settings (Since it should give me good graphic quality, which I noticed a big good difference in graphics :o).
Attached are some screen shots that I took with my settings in fsx and with it are a screen shot of the FSX.EXE Compatibility. The Addon Manager is set to default, I just wanted to make sure that I was doing this right.
I'm using a Windows 7 Ultimate 64-bit its a torrent version but its legit and registerd/activated and I can do the updates. Could this be my problem if so how? After I installed windows I went and got the drivers for my graphics card and did all the updates ???
Can my graphics card handle the graphics FSDT KLAX demands? I think I'm on the border line.
Sorry for the big pictures I dont know how to make them any smaller.
-
Your problem is the video card, perhaps you use/used a tweaker which put something wrong in the registry, but the image quality in the screeenshots you posted is *very* bad nonetheless, I'd say disappearing pieces of buildings at KLAX is the less of your problems.
Try reinstall the video drivers using a driver cleaner utility.
-
I finally fixed the problem! Sorry it took me a while as im a flight instructor and barley have time for this now, but anyways I managed too uninstall the FSX SP2 and then reinstalled the SP2 and then wala everything went as you guys said is was supposed to do AND IT WAS NOT MY VIDEO CARD ::) thank god! Now its runing fast and awesome with UT2 and my payeware aircraft. Anyway thanks for the tips, time, and help it was much appreciated.
By any chance do you guys know if you guys will do a KPHX ?