I love the Lancair Legacy by Robert Christopher. It is a beautiful well done aircraft. I prefer to fly it from the virtual cockpit, but the guages are not as fluid as I would like. I was wondering if there is anything in the panel or aircraft config files that can be edited to fix this?

Hi,No, there is no "quick fix" for this problem, it seems that the VC gauge refresh rate is hard-coded into the game engine.Dan.

NEW CoF panel & guage SDK is out now..so there's a ray of hope.

Yeah, I saw that, has anyone looked in it yet?, is there anything "new" in it?.CheersDan.

I haven't found anything new concerning VC refresh rates, but I'm not an experienced gauge programmer. The biggest news seems to be the AI traffic interface that should make TCAS displays easier to implement - or was that already available in the 2002 SDK?VOlker :]

Hey Boris, I feel your pain!When I was developing the Legacy I wanted the gauges to be smooth, but I also wanted the feeling of flight very smooth when sitting in the VC. Also I wanted the gauges readable and illuminated at night. In my experiments I found that to get really smooth flight performance the gauges would suffer. Therefore the delema, what was more important. To me, the smoothness when yanking and banking. More experienced designers have found ways to deal with this a bit better. I still have a lot to learn yet.Appreciate your trying the Legacy!!Regards to all!Robert Christopher

>Yeah, I saw that, has anyone looked in it yet?, is there>anything "new" in it?.Dan,Short answer: NOLong answer: Yes, a few appendixes were added that are almost (in my eye) irrelevant. However there appears to be some new information on AI traffic, so easy(er) TCAS systems may be simple to make, as opposed to the old FSUIPC way. However, we will need to wait for the master programers to figure that out :)There is nothing new other than that.This link is to the thread in the developers forum:http://forums.avsim.net/dcboard.php?az=sho..._id=16833&page=

There has been a thread about exactly this lately in this forum:http://forums.avsim.net/dcboard.php?az=sho...&mesg_id=181049Hope this helps!

Thanks for your replies everyone. I just love the Legacy Robert, and you did do a very nice job with the smoothness in flight, and I don't get the stuttering that I get with other add-ons. It is a delight to fly, and the gauges in the VC are just a minor annoyance, not a showstopper.

Just thought I would toss in a few tid bits of trivia I had found out about VC panels.Panel guru's chime in and correct or expand as needed. This is meant to be very basic in scope. 1) Basic panels are designed with the gauges placed on one plane, say one big sheet of paper that represents the face of your panel. In this case you would experience the standard refresh rate applied across the group. If your panel is designed to use multiple small pieces of paper to fit groups of instruments on, such as radios, engine, etc., well your frame rate starts deviding, or getting slower. The more individual pieces of paper you have the slower the rate.2) Pixel size has a large impact on rate also. The higher the number the more load on the system. If you have a large piece of paper, and you want to be able to read the gauges, you need to use a higher pixel size so the numbers are crisp and clear, such as 1024,1024. But the large pixel size presents a sizable impact on frame rate and smoothness, hence the choppy flight performance. If you lowered the pixel size, the gauges then became blurry, depending on how far down in size you go.One thing I found when developing the Legacy was if I made an individual plane (piece of paper) for each gauge, I could use a very small pixel size and still get a clear readable gauge, and minimal impact on frame rate. See example below. But since I was using numerous planes for all of the gauges needed, the refresh rate of the gauge suffered. So a compromise was needed, thus the choice that yielded good appearance and smooth flight.(Vcockpit01)Background_color=0,0,0 size_mm=128,128visible=1pixel_size=256,256texture=$AirspeedAnother benifit of the individual planes was it made the night illumination of the gauge a bit easier. There are many differing opinions on how best to layout the panel, but the above represents what I felt gave the best overall performance for my project based on my knowledge at that time. Hopefully it didn't bore you to tears. Cheers!!Bob C.(aka Robert Christopher)

Same thing applies for the captainsim's 727. (at least on my rig; amd 2600 w. geforce fx5200) Makes it impossible to fly on instruments.At the other end of the spectrum too fluid gauges drain the cpu to the point that textures are drawn real slow and frames drop. As always there is the tradeoff.