dave jones

Yes, Peter, I agree -- his manuals are excellent. Maybe that's why he never did an FAQ. Anyway, the problem is solved. It was a combination of reading the manual and your comment about FS resetting things that made me go back and check the axis assignments the third time -- that's when I finally spotted it. Obviously I was wrong in thinking that I had seen the FAQ. But the way my memory has been getting it's not surprise! Back to the 1965 Eastern AI repaints... Thanks again. ...Dave

Peter- >>If you have changed any of your USB connections since your layoff then the chances are that the flight sim has reset everything to the default settings.<< That's exactly what happened. It had taken over throttle control and was in argument with my external setup. I kind of suspected something along that line because I had disconnected everything to work on the power supply, and on the subsequent boot I got the dreaded "new hardware has been found" message. That concerned me, but a quick 1-2-3 check of the yoke with the default 172 or whatever showed it to be working, so I went on about my other business. The reason I missed the problem before I posted my question yesterday is that in the FS9 "assign joystick axis" screen, there are axes for each engine separately near the beginning of the list, where I noted that there were no FS assignments, which is correct. BUT, at the end of the list there's another engine control with no number given, so it's presumably for all engines. It had assigned that one to my throttle control and I missed it the first w two times I looked. Thanks so much for helping. And back to the first question, is there an FSUIPC FAQ somewhere or do I just remember incorrectly? Thanks again! ...Dave

I kind of vaguely remember seeing an FSUIPC FAQ somewhere, but now can't see any signs of it. I have a problem whose solution might be given therein. So if someone can point me.... Failing that, my problem is simply that my old setup no longer works. I had an intricate arrangement of throttles/reversers for a 727 that used to work great, but after a layoff of several months from flying while working on FS repaints, the setup has quit. I've checked my fsuipc.ini and all seems to be the way I left it. Does anyone have a suggestion as to where I might start looking? Tried searching this forum but this is a difficult topic to search for, even though it might be in here somewhere. Will appreciate any help... ...Dave Dave Jones Fort McCoy, Florida USA

Yes, Frank, that is of a lot of use to me. Sounds like what I'm doing is about right but I will try lowering the upper visbility. Actually, I don't mind seeing the horizon at high altitude -- what I don't like is the way it suddenly pops into view. Yes, I did understand that the lower visibility altitude needs to be zero and I had fooled with the upper limit of FS's own haze layer but the effect did not change. I'll mess with it some more. The main thing is that I'm apparently not doing much wrong; it's just that there is no utopia. Perhaps a better answer would be to make sure there's always a scattered (at least) cloud layer at the altitude where you transition from FS's visibility layer into FSUIPC's graduated layer above? Thanks very much for your help, Frank. Of course any other tips would be most welcome also. Back to the experiments... ...Dave Dave Jones Fort McCoy, Florida USA

I know Pete is off on holiday for awhile, but perhaps someone who is much more familiar with this topic than I can help out. To start with, I'm talking about FS9, using it's own (global) weather, and FSUIPC version 3.71. Like many others, I want to get past the problem of suddenly bursting into clear blue sky above and below as you climb out of FS's own visibility layer which I have set at 8500 feet. I've read the documentation on the subject a dozen times at least, and experimented with all the values with no success. When I climb out of FS's visibility layer, I now get a drastic and rapid -- but not instantaneous -- lightening due to haze of all the ground below both near and far. Then, climbing another 1000 feet, the horizon snaps into view. I know this can work because it does for so many others. There has be something very fundamental that I'm not getting. Here's the relevant section of my .ini file: GraduatedVisibility=Yes LowerVisAltitude=0 UpperVisAltitude=22000 UpperVisibility=6000 GenerateCirrus=Yes WindShearSharp=No UpperWindGusts=Yes ExtendMetarMaxVis=Yes PatchSimApAlt=Yes DisconnTrimForAP=No ZeroElevForAPAlt=No AutoClearWeather=Yes ExtendTopWind=No WindSmoothness=5 SmoothPressure=No PressureSmoothness=5 SmoothVisibility=Yes VisibilitySmoothness=4 MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 MinimumVisibility=0 MaximumVisibilityFewClouds=6000 MaximumVisibility=2000 MaximumVisibilityOvercast=2000 MaximumVisibilityRainy=1000 OneCloudLayer=No ThinClouds=No ThinThunderClouds=No CloudThinness=1000 ThunderCloudThinness=10000 CloudTurbulence=Yes CloudIcing=No WindTurbulence=No SuppressAllGusts=No ExternalOptionControl=Yes AutoTuneADF=No KeepFS98CloudCover=No ShowPMcontrols=No MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No StopAutoFuel=No TrapUserInterrupt=Yes NavFreq50KHz=No ClockSync=No SmoothIAS=Yes SetVisUpperAlt=No VisUpperAltLimit=4000 MaxIce=-4 MinIce=-4 WindSmoothingDelay=0 WindSmoothAirborneOnly=No LimitWindVariance=No VisSmoothingDelay=10 VisSmoothAirborneOnly=Yes Also, it would be helpful if someone could tell me: What is the difference between the "upper visibility" on the lower right of the visibilty setting page and the "upper altitude of restricted visibility" to the left? I just don't understand the documentation about this. What does the "smooth only when airborne" box do? What is the box for that says "but after weather cleared, delay...? FSUIPC is a wonderful set of tools and this visibility bit is fascinating, so I'd really like to get to understand it fully and make it work. Thanks for any replies! ...Dave Dave Jones Fort McCoy, Florida USA