MarvK

Wow, I can't believe that no one has a solution to this.

Hi all, Hope everyone had a good Christmas. :smile: I purchased several FS9 Carenado aircraft during their holiday sale. Every single one of them requires the landing lights to be on in order to have instrument lighting. I know this is a pet peeve for many of you, myself included. Is there any way to fix them so the instrument lights are on without having the landing lights on also? I seem to remember having to alter/add the alpha layer. I've tried, with no success. :( I have PSPro and dxt2bmp so I could do them myself but, I don't know what to do, or what to look for. Any guidance would be appreciated. Thanks, Marv

Double check to make sure the file is in the effects folder. It works for me at higher thrust settings, and it's not a heavy black smoke effect as you would expect from say, a B707 or DC-8. But it is there. :(

Thank YouI managed to find his website here; http://janswebsites.110mb.com/flightsim/index.html I assume this is what you were referring to? Now, I need to see if I can sort out which are the one that are having the problems.Thanks Again

Thanks for the info Scott. When I do see it happen, it's not IFR conditions. Doesn't sound like there's anything I can do about it. I just never noticed it this often before. I recently added a bunch of WOAI flight plans and models, so I thought maybe the .air file was off. I didn't notice it at all when I had Project AI installed.

What would cause AI Aircraft to land 1-3 miles BEFORE the runway? Is it the .air file, flight plan, or the airport itself? Or maybe something else I'm not considering? It's a bit disconcerting to begin pulling onto the runway and have a B737 come screaming out of the weeds and onto the runway in front of me. :(

Found the base package, but I can't find the 1.1 update either. :(

I don't know why, but I just "discovered" the freeware Project Fokker-100/70. Probably because I was more into the GA aircraft up until recently. I understand that it's only available at AvSim but, it's not. It's one of the many that have been lost in the hack. Is there anywhere else that it can be obtained from?Thanks,Marv

I think in the conversion, they forgot to add the (VIEWS) section in the panel cfg. I started with the settings that Graeme posted above and it's quite convincing now. (thank you) I also agree that it is "twitchy". I've been tweeking the (flight_tuning) section and came up with these 3 settings. Still need to test some more, but here's where I started;elevator_effectiveness = 0.6 //0.8pitch_stability = 1.2 //1.0elevator_trim_effectiveness = 1.4 //1.5

Hi Damian,Thanks for the quick response. I was flying in Alaska, started near PAYA, and flew to PAOR. Come to think of it, that's where I've been doing most of my flying this past week or so. I changed locations, moved to Portland, Oregon and all is well. Seems to be working fine at this location. Could it be the Alaska reporting stations are not reporting correctly?Thanks Again,Marv

I've been using AS4.5 Build193, for at least 1.5yrs now. Never had a problem until just recently, about a week ago. When I hit refresh after loading FS I'm now getting an error that says; "Main Thread Process Error- Retrying at next interval"I was just wondering if ver4.5 is no longer able to read the info from the server, or if the server has changed?Thanks,Marv

Hi Moose,I hated that outside looping sound on the 182 too. I fixed it by making a copy of the xrpm4.wav and renaming it to xrpm3.wav. So in effect there are 2 wav files that are the same, #3 & #4. These are the external sound files located in the sound folder. Maybe not the perfect fix, but it gets rid of the looping sound that we all hated. :) Oh, and don't forget to keep a copy of the original #3 file somewhere.To the original question, if I were only getting 1 Carenado plane, I'd get the 206.

Is there another 6x series set of drivers that does work with the preview window and still be able to set AA to 8? The 81.98 set seems to work fine in the sim, it's just the black preview window that's not working properly.

This topic has been moved by the moderator of this forum. It can be found at:http://forums.avsim.net/dcboard.php?az=sho...&topic_id=13255

Thanks Rick,That was it. I had AA set to 8x. Put it back to 4x and all is well with the preview window.I find it hard to believe I have to much horsepower for FS. Nah ;-)You also don't realize how much stuff you've accumulated until you have to reinstall everything!! :-eek Thanks again,

Hi all,I just put together a new pc. AMD64 X2 4400+ w/Nvidia 6800GS 256, card, and 1gig of ram. FS looks awesome now, and I can run with 25-30fps consistantly. The only thing that isn't working right, is now there is no plane in the preview window when I create a flight or am changing planes.Does anyone know why? I have the latest Nvidia 81.98 drivers which is supposed to fix some FS9 issues.Thanks in advance,

Would you mind sharing your tweaks, especially for the 180? It is annoying sometimes when it won't fly level. Not at all like the rw plane.Thanks,MarvOh, BTW, I agree with the offerings from Carenado. The 206 and the 182 are both fine flyers.

This was my first payware aircraft. Bought it the first week after it was released, and it's still one of my favorite GA aircraft. It does take a little getting used to as far as flight dynamics go, but you'll soon begin to love it. Never had the DF Archer II so I can't compare. Besides, I'm hoping that DF will re-release the Archer with the upcoming Dakota package. (fingers crossed)As for trimming it for straight/level flight, After you reach your cruising altitude, set the elevator trim for a very slow climb, and then back off the throttle ever so slightly until you maintain level flight. And for trimming for straight flight, it will never truly fly straight, at least not for me anyways. But from what I've read from RWP's, with only a rudder trim and no aileron trim, the real 180 won't either. Constantly correcting left/right.Here's what I use for the panel.cfg file that seemed to help me alot with the forward view in the VC;VIEW_FORWARD_ZOOM=1.000VIEW_FORWARD_DIR=7.400, 0.000, -1.500 //4.500, 0.000, 0.000The numbers after the // are the original view settings.Oh, btw, good choice. ;-)Marv

Hi Chris,That's what I did the first time, manually. Obviously it doesn't work that way. After I did it through the FSW2004 interface, all went back to normal.Thanks,Marv

Chris,Did as you suggested and installed all default textures from FS Sky world 2004, and the sky ended up looking like picture #1. Then I shut the sim down, installed cirrus clouds & cumulus from FS Sky World 2004, and now it looks like pic #2. Whew... had me worried there for a min. But now everything seems to be working as it should. Even the visibility limit appears to be working also. :-)This was a different ovc condition than what I had the other night. I don't know if it made a difference or not with how the clouds are drawn?BTW, do you know what would cause the condition of the cirrus clouds in pic #1? I used restore default textures from FS Sky World.Thanks again for your help,Marv

Registered ver 3.4.7Marv

Hmmm....As per Chris' reply, the only 3rd party clouds I have installed are the FSW clouds. But I will reinstall the default cirrus clouds and see if that makes a diff.I'll play around with it some tonight and try some different settings. I was going to reinstall AS and go back to build 174 and see if that made a difference, but if Jim says B193 is working properly for him, I'll keep trying.Anything else I could try?Thanks for all the help....Marv

OK,Just did another flight around the area for about 45 min with clouds drawn set to 70nm and I saw no difference. The clear band was still there. For some reason it seems that the 50nm visibility isn't being enforced. If I ALT to the menu, and look at the settings for weather, it's set to user defined and unlimited visibility. If I change it to 50nm vis, it wipes out all the current weather settings and I have to refresh AS. Then it reverts back to unlimited?Everything in AS options are still set the same as above.Thanks,Marv

Hi Jim,I tried putting my cloud distance to 80nm after I landed, and left the visibility @ 60. Maybe I didn't give it enough time to process?I'll try again shortly and fly in the same area with yesterday's METAR, and see if there is a difference. FYI I started near KOSH.Might there be a setting in FSUIPC that I need to change or activate? Have registered ver 3.4.7.Thanks for the help, will report my findings.Marv

Hi all,I have a question about my settings within AS. I just made a short flight with OVC conditions. AS depicted the ovc weather convincing enough, (no holes in the clouds) but there was a clear band at the horizon all around the aircraft the entire flight. I'm sure it's some setting that I'm missing, or don't have set correctly. This was the active METAR for the flight;KAIG 282155Z 27009KT 10SM OVC050 05/M03 A2989 RMK AO2 RMK SUPPRESSEDI have the visibility in FS set to 60nm and clouds drawn at 60nm. In AS I had the visibility set at max 50nm but I still have this clear band at the horizon.This is the ini that I'm using;//AS2004.5 configuration file B193[General]WindowPosX = 2400WindowPosY = 1920DefaultWeatherFolder = E:Flight Simulator 9ModulesActiveSky2004SuppressionCeiling = 2000SurfaceWindLimit = 10CloudLayerLimit = 5LocalSuppressionRange = 60MinimumVisibility = 0.5MaximumVisibility = 50LastPlanFolder = C:Documents and SettingsUnkownMy DocumentsFlight Simulator FilesIncreasedWake = FalseDisableWindsAloft = FalseForceTstormsWithCB = TrueAutoConvertPlanFiles = TrueDisableVisGraduation = FalseDOWNLOADTHROTTLE = FalseForceDestinationWeatherZone = TruePreventIcing = TrueOnlineUpdates = TrueExtendedDestinationWindsForce = FalseDisableAllGroundUpdates = FalseGlobalWrites = FalseDepictFS9HazeLayer = FalseExtendTstormLayers = TrueDisableDirectWindControl = FalseVoicePlayback = FalseLocalSuppression = TrueStartupSound = TrueDisableGroundUpdates = FalseUseProxyServer = FalseFogLayerGeneration = TrueUpdateSuppression = TrueOvercastEnhancement = TrueIgnoreFSReadyStatus = FalseFSUIPCWindSmoothing = TrueLimitSurfaceWinds = FalseLimitCloudLayers = TrueAutoGlobalWriteToggle = TrueRainWithTS = TrueDisableUpperLayerGeneration = FalseVisibilitySmoothing = TrueDisableMessages = FalseAutoTimeZoneDetection = TrueUpdateInterval = 15VATSIMData = FalseZuluConversion = -4AloftPredictability = 90WindDriftRate = 3TAFProcessing = TrueEnforceVisibilityLimits = TrueWakeTurb = TrueStartPaused = TrueUseSystemTime = TrueDisableCAVOKClouds = FalseProxyAddress = NONECould someone please tell me what I have set incorrectly, or what the proper setting would be to eliminate this banding that I'm seeing?Also trying to attach a pic for visuals.Thanks,Marv