Arnaud_S

Well, thank you anyway Pete for replying. Actually my systrem has a real problem - I noticed recently that ACM's rendere doesnt wotk any longer. Might be DirectX the problem. Thanks for all your help. Best,

Hi Frank, Thanks again. yes, I already tried to remove the fs9.cfg file and let Fs rebuild. That didnt help unfortunately. However I saw just next to the fs9.cfg file a dxdiag.xml file I never saw before. Maybe was put there when i performed the DirectX tests diagnostic the other day. I will wait for Pete's return, and I will probably head for a complete re-install now. Some friends of mine did some test for me: as I suspected my gfx card to be u/s (the screenies looks like 16bit colors), I asked them to turn their FS in 16bit colors and see what happen: nothing like on my screenshots. Sigh... Regards,

Hey Frank, (are you the Frank I know from the AI small world? :) ) Yes, not later than this morning, I uninstalled my gfx drivers, and installed two other versions: with both versions, the problem still occur, and yes, with all default settings as well as custom settings. I changed and tried different values for the monitor gamma, brightness and contrast, but nothing helps here. To tell the whole story, my good old CRT ran out of order two week ago, and someone convinced me to try an LCD 17". What I did. So at first I thought the problem came from the new LCD monitor, but it doesnt: factly, I suspect the LCD (which brightness is a lot higher than on CRTs) just revealed an already exisiting problem that I didnt notice on my CRT. Anyway, if even the problem came from the monitor, you would have seen the screenies normally on your monitor. The fact that you see the problem makes me conclude that it is a software problem. In the meanwhile, and because I still had a doubt on the monitor, I made a test with another CRT and could see the problem was still there. My last fear is that when my old CRT 'burnt', the graphic card got kind of a shock, and that my problem simply comes from the graphic card. Other than that, I am thinking of an FS problem, some .dll screwed. Thanks a lot for replying Frank. Regards, Arnaud

Hi guys, I am a registered FSUIPC user, and I know what I am going to ask has nothing to do with FSUIPC. Simply, in despair, I had the idea that Pete and folks on this board would maybe have a sufficient good FS engine knowledge to help me avoid a re-install. Factly, I think that if on Pete's forum I dont find the soslution, then I will have to re-install. I know Pete is away at the moment and I hope he enjoys his moutains :) . Few weeks ago, I've noticed that the sky in FS has come to a very odd display - again, I know that is not FSUIPC related -. here are two shots: Maybe on the first one you dont see the problem, due to your monitor brightness settings, so here the same screenshot, exagerated with Photoshop so that you see what's wrong: Awfull. What is more important in FS if its the sky rendition? This happens also in the daytime, but its less obvious due to stronger lightening. I have several ideas about what the problem might be, but they all lead me to a system and FS re-install. Either FS dead install, DirectX issue, drivers issue. I use a 1280/1024/32 FS resolution, and the screen support easily that setting, as well as the graphic card (ATI 9800XT). I dont exclude hardware problem. The main question is: is there a known .dll in FS that deals with the sky which maybe got corrupted and that I could replace? I dont use any third party sky textures, everything is default and I havent installed recently anything new. Has anyone ever witnessed such a weird sky display?My FS install was a year and half old, and I take a good care of it, so its always been extremely stable, as I am always very carefull when it comes to install add-ons sceneries or aircrafts. Any tips would be greatly appreciated. Regards, Arnaud

All right, thanks a lot Pete. I have replaced the .dll and everything seem to be working just fine. All of sudden I recalled that the last time I updated my .dll was indeed for the support of 9.1, which I never installed! We forget fast, sometime. Anyway, thanks for all your nice work again, Pete. Regards

hello Pete, I am just about to update my registered FSUIPC version from 3.41 to 3.48. My question is: will 3.48 work fully and properly with fs9, that is, unpatched version of FS? For some reason (mainly fear of problems related to fs9.1 encoutered by many users around) I dont want yet to patch FS to 9.1 untill a complete re-install of my system -and we all know how long it takes ! - I have read the readme.doc files but havent found anything related to that question, that's why I post here. Thanks by advance for your help, Regards

Thank you for taking the time to look at my problem Pete. As i said before, I dont think either it's a problem linked with FSUIPC. What I was asking was: could FSUIPC fix that, and also which settings would be best to correct the one I have set wrongly. Anyway, I will stick with the one I have now: all default with v 3.40, except the 'add cirrus layer occasionnaly'. I will look further with the ATI drivers, maybe get some newer, sometime it helps too. Regards,

Right, Thank you Pete, I have sent you the zipped files this morning. As for the wrong 80000 miles, that is of course one of the silly setting I had tried after I found out about the issue. The defaut '0' value gave the same result. I have corrected it and joined the fsuipc.ini file too. Regards,

Thanks a lot for replying Pete, I do really appreciate. Everything used for the screenshot was default: aircraft, weather, scenery, simply: everything. It happens, yes, everywhere. About the mountains, sorry, I meant indeed 'flickering' in the remote. I'm using an Asus ATI Radeon 9800XT with Asus Drivers. In fact, I'm quite worried as you write that you dont encounter this kind of issue in your FS. I was about to conclude that it was some sort of known FS bug, but if you dont see this, maybe it means it's only an issue for me. Could you please do the same test as I did: at noon, FL330 for instance, and then switch time 30' before dusk. If the visiblity apsect remain the same for you, then it has to do with me. Thanks again Pete.

Hey All, I'm a FSUIPC registered user, and have to fight with an issue in fs9. I have posted a thread at Avsim Forum too, but I'm trying here to because maybe someone know the solution. Maybe also it's a known bug of fs9, I dunno, but it's very anoying. Here are two screenshots, took exactly at the same place, same settings, the first one around noon, the second one one hour before dusk: On the first one, thanks to FSUIPC visibility settings, the haze on the skyline gives a realistic aspect, but why at night the visiblity settings go away, and suddenly the unlimited visility appear, and you can see the moutian in the remote jumping and dancing, which is awfull and spoil the sim. If it could give any idea, the unlimited visi starts at 12000 feets. I do hope someone knows about it, because flying at dusk becomes not so pleasant. Here is, sorry for the long post, a copy of my FSUIPC log: [General] History=4KKC66KH1BR2HG7AH1UEB TCASid=Flight TCASrange=40 TrafficScanPerFrame=10 AxisCalibration=No CentredDialogue=No ClearWeatherDynamics=Yes OwnWeatherChanges=No WeatherReadInterval=4 MoveBGLvariables=Yes MainMenu=&Modules SubMenu=&FSUIPC ... WindSmoothing=Yes AutoTaxiWind=No WhiteMessages=No ThrottleSyncAll=No GraduatedVisibility=Yes LowerVisAltitude=6000 UpperVisAltitude=30000 UpperVisibility=6000 GenerateCirrus=No WindShearSharp=No UpperWindGusts=No ExtendMetarMaxVis=No PatchSimApAlt=Yes DisconnTrimForAP=No AutoClearWeather=Yes ExtendTopWind=Yes WindSmoothness=5 SmoothPressure=No PressureSmoothness=5 SmoothVisibility=Yes VisibilitySmoothness=2 MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 MinimumVisibility=8000 MaximumVisibilityFewClouds=6000 MaximumVisibility=2000 MaximumVisibilityOvercast=2000 MaximumVisibilityRainy=1000 OneCloudLayer=No ThinClouds=No ThinThunderClouds=No CloudThinness=1000 ThunderCloudThinness=10000 CloudTurbulence=Yes CloudIcing=Yes WindTurbulence=No SuppressAllGusts=No ExternalOptionControl=Yes AutoTuneADF=No KeepFS98CloudCover=No ShowPMcontrols=No MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No TrapUserInterrupt=Yes NavFreq50KHz=Yes ClockSync=No SmoothIAS=No SetVisUpperAlt=No VisUpperAltLimit=6000 MaxIce=3 WindSmoothingDelay=0 WindSmoothAirborneOnly=No VisSmoothingDelay=0 VisSmoothAirborneOnly=Yes SuppressCloudTurbulence=No SuppressWindTurbulence=No SpoilerIncrement=512 ShortAircraftNameOk=No FixWindows=No FixControlAccel=No [JoystickCalibration] FlapsSetControl=0 ReverserControl=66292 MaxThrottleForReverser=0 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 SlopeAileron=0 SlopeElevator=0 SlopeRudder=0 Regards, Arnaud