ztimbre

Sorry to come late to the party.... can someone point me to where Carenado said they'll add GTN integration? Did they make any mention of the RealityXP units? Thanks. Z.

That's fixed it for me! Thanks for the speedy update! Z.

Hi Shez, Thanks very much for the new version. Ground flickering is solved! I am still having frame rate drops. I took some time this afternoon and isolated the problem to the file "LGBrunwaylights.bgl" It looks like you are using SCASM lights, and considering the runway headings at LGB, I think you are encountering the problem described in this thread: http://www.fsdeveloper.com/forum/threads/scasm-lights-kill-my-fps.21793/#post-194616 This problem will not appear for people using FSX+SP2, only those using acceleration (which I am). I've checked the scenery at night, and it appears that the problem sections are the runway overruns. I am a scenery designer, and would be happy to test/tweak, if you like. Thanks again for a great scenery! Z.

Well, I am always open to learning something new. I'm no expert, but I can think of many factors that would have a big influence on the sink rate at touchdown in different aircraft/situations, such as different autopilot software, inaccurate payload data in the FMS, errors in the air data system, pilot carrying extra speed, etc.I respect PMDG and LVD's work, and their dedication to accuracy. Personally though, I am not really interested in comparing the CS behavior to other sim aircraft. I am only really interested in comparing with what the real world aircraft does. So, My comment comes from numerous discussions on aviation forums, for example this thread at, ironcially, the CS forums.http://www.captainsi...?num=1300307356Now whether you believe the user "LOU" is a real commercial pilot is up to you. But google will turn up a bunch of the similar discussions I'm sure.This document is the one that was sticking in my memory.http://www.smartcock...ted_Runways.pdfwhich gives the rationale, and says that average touchdown rates are 3 ft./sec. (180 fpm), with as low as 2 ft/sec. (120 fpm) and up to 5 ft/sec. (300 fpm) being very common, and up to 10 ft./sec. (600 fpm) permitted. (yes, the doc is about airbus, but I've seen the same for boeing.)So the 400 fpm of the CS 757 maybe a bit on the high side, but none of these sources say that typical autoland systems are striving for sub 100 fpm touchdowns.Anyway, I've just emailed a friend of mine who, until recently, flew 737s and (I believe) 767s. He says he will check the AFM to see what it says.p.s. -hell just froze over. Never thought I would find myself 'defending' anything CS does....

400 FPM is not really excessive for an autoland, according to everyting I have seen. The computer is not trying to 'grease it on'. The goal is to make a firm landing so that there is no delay in getting the autobrakes engaged and the spoilers up to provide maximum stopping distance.My only question is: will the CS 4.6 meet descent crossing restrictions when in VNAV mode? Previous versions were absolutely terrible in that area. (For example, the KEPEC2 arrival into KLAS which is pretty demanding and was absolutely mangled by previous versions of the CS 757.)

very nice shots BrzI! Would you mind another request for you config files.? I'd be grateful if you would send them to me at madroad41 [at] hotmail [dot] comCheers!

Great, thanks!

Hi Dick,Sorry to intrude, but can you recommend a good screenshot program? What do you use? I have had trouble finding a good program that will capture images larger than my screen resolution (currently 1600 x 1086).cheers,ZI have

Thank you Carenado, fantastic aircraft! I've been flying the wings off all models (and no bouncing issues at all). :)Thanks for remembering your FS9 users. I bought the standard FSX version as well, specifically to thank you for continuing to build for FS9.

Great news, thanks Carenado!!

I've purchased the FSX version and it is great. However, I still prefer to fly FS9 and can't wait to get the C185 in that sim!Eagerly awaiting news from Carenado :D

Just a thought... but are you guys using that utility that resets the tower view to the nearest airfield as you fly along? (I believe it is called "autower")

Hi Jim,Thanks for the continued suggestions. Altimeter is still set to the 'B' key, and does work some of the time, as described above. The weather theme in FS when ASE is running does show as User Defined.Over the past couple days, I have continued to test various configurations of FS and ASE in an attempt to isolate the conditions that cause the problem. At this point, it appears to be caused by DWC. Every flight I have done with DWC on has suffered some problem (including, in one flight, the 'reversed winds' described in another thread here). SO FAR, every flight that I have done with DWC OFF has been error free. Altimeter, winds, visibility all render correctly at all stages of flight. I have only done three or four flights with DWC off, so I want to test further before definitely saying it is the faulty element.

Hi Jim,29.92, as usual.

Hi,Afraid not. No other FS software running.Is there any significance in the fact that, on last night's flight ASE said the altimeter at KECS should be 29.80, but according to the ASE_log file it is sending 29.74?12:49:52 AM:0593 - Sent String: KECS 270159Z AUTO 34011KT 10SM CLR 03/01 A2974 RMK

Nope, the 'supress on ground' option is off..

OK, I did a short flight from KRAP to KECS. Departure weather at KRAP was rendered correctly.On landing at KECS the altimeter in FS was showing 29.92. ASE reported that the altimeter should be 29.80. I immediately saved a copy of the ASE_log file. Hope it is helpful..

Jim,A small update: resetting the config file seems to have solved my original problem. I have switched to a number of different airports, and for each the weather and altimeter render correctly. However, this has exposed another problem. Every flight I have done, the altimeter at the LANDING airport is still stuck at 29.92. The weather/winds seem nearly correct, but nothing will get the altimeter at the destination airport to match the METAR in ASE. This happens with and without a flight plan in ASE (I fly mostly without an ASE flightplan).I wonder if this is related to the destination weather problems others are seeing? Hitting the 'clear weather' or 'weather settings off' buttons in FSUIPC does not resolve the problem. It does seem as thought the 'depiction' cycle is stuck, as the 'depiction output' message does not clear from the bottom of the ASE screen.Thanks for the help so far.

Jim, Tonight I've gone to 14 different airports, spread around the world. At each airport I've let ASE complete at least two 'depiction' cycles. Out of 14 airports, 6 correctly rendered the altimeter. For the remainder, the altimeter stayed at 29.92.I will try to gather more data to discern a pattern, but I should mention that AS6.5 correctly renders the METAR in all of the tested airports so far.Is there a way to reset the ASE options to the default? That might be a logical next step to eliminate variables..Thanks!

Hi guys, thanks for the quick replies.Jim, I have other FS software installed, but nothing else running when conducting the tests. I've deleted/rebuilt the FSUIPC .ini file, and returned the settings to default. Unfortunately, the problem persists.zfehr, I am using default ATC, but actually have all traffic turned off. The only realted thing is that I do have FSInn installed for the vatsim network.

Hi,I am having problems with the weather in ASE not matching what is shown in the sim, most often the altimeter and winds. In fact, the altimeter in FS does not match what is reported in ASE about 60% of the flights I have done so far. I have tried for the last week to get a correct altimeter for KVCV, and could not get a correct reading in eight flights. I have tried both with and without a flight plan in ASE. It never changes from 29.92, thought the activity log in ASE seems to proceed to completion. The cloulds and visibility seem to update OK (I have left the sim alone for approx. 10 minutes each time to see if the altimeter eventually updates -but it never does). I have seen the same behavior at other airports, but have not repeated the experiment there as I have done at KVCV.I am using FS9, FSUIPC 3.90 and have reset FSUIPC to 'weather off' configuration.Am I doing something wrong? Let me know what other information you need from me to help resolve this. Thanks,Ztimbre

Thanks Paul! Your settings were quite a bit higher than mine. So I bumped them up and it did smooth out some. I've also moved to the 186.18 drivers, which appears to have eliminated the remaining stutter. Enjoy your new ride :(

Paul,I just upgraded to a GTX260, which means I now have a very similar system to yours in all respects. Frame rates are awesome, but I am getting some small stutters in windowed mode. Would you mind posting the display section of your FS9.cfg file for comparison? Specifically interested in the texture_bandwidth_mult and texturemaxload (if you are using it) values.Thanks in advance.

Extreme blurriness like this is usually caused by a scenery that has a texture file in DXT1 format without mip maps. Basically, when FS loads a texture it peforms three operations: open-read-close. When a DXT1 texture without mip maps is is the field of view at the same time as any other texture format, FS cannot perform the "close" part of the operation on the file. This makes an instant bottleneck and forces all other textures to their lowest mip map resulting in extreme blurries.The solution: when the problem occurs, take note of every addon scenery in your "sight distance" area. So if your sight distance is set to 100 miles, you need to look at every addon scenery in a 100 mile radius of your plane. I then deactivate each scenery until I find the culprit. Next you must look at every texture in that scenery (use imagetool.exe) and if it is DXT1 format, it MUST have mip maps. When you find one that doesn't, it's an easy matter to tell imagetool to resave the file with mip maps.Sorry for the complicated explanation. Hope you get it solved!

14 is Andover/Aeroflex, NJ airport code 12N