eriksenp

I might be all wet on this one but my take on DME arcs is this.DME arcs are flown at a set altitude according to the approach plate. No stacking here. Stacking was done at holding fixes. That is rare today.Before all the fancy FMCs ,etc, you flew them by hand. Enter the Arc where designated and at the proper distance.Fly the plane straight till you notice the distance change, (half a mile,mile? I don't know.) then turn in the proper direction to get the distancenailed again.Also I belive the DME arc is rarely used any more as are procedure turns. Most charts will have a notation of NOPT which means a procedure turn is not necessary. Things change over the years. The next is the current change to the ADSB system. GPS heavily involved here.P

On the NDB and lightning. I believe that if you are near a storm and you tune the receiver off station you will see the needle drift over the the general direction of the lightning strikes. I think that is the way the Ryan stormscope works. Not super accurate but better that nothing.P

The latest in my quest for mitigation of my problem. I put the original executable back in and the problem persists. Long story short. The only places I can think of are the config file, the registry, or a rogue .DLL file that I can't seem to find. I found that when the plane is on the ground everything works as advertised until I make the first move as opening the throttle the least bit (in order to taxi). At that time when I try to use the hat switch to pan left and right all I get out of it is the jitters as I explained before. Also the keyboard controls for panning (shift+ numpad or ctrl+ numpad) do the same thing. In my config file there are only two entries for POV. Not having a config file to compare it to, I don't know if that is all there is or what. Still scratching my head.Paul

Hi, and thanks for the inputs. I was careful to install the correct files for AC. Also, inasmuch as I am using FS 9.1, I installed the no-cd crack for 9.1. But I have other problems. In VC mode I can't use the mouse wheel (pressed) to pan around the cockpit. It will go just so far and pop back to the center again. Another problem popped up. I unistalled AC and removed the registry entry folder. I did a search and removed all the AC stuff I could find. Now with all that stuff removed I can't pan horizontally in VC mode any more. Vertical panning is OK. When I try to pan horizontally the panel just jitters back and forth. I double checked the joystick setting for the hat swich. It's good.----The one thing I did not do yet is put the original (must have CD) fs nine back in. None of the above affects FSX. Stay tuned. Paul

Yes, I did switch off gradual transition...

After a long hiatus I reinstalled AC using all the correct files and procedures. From a clean install I go to the VC and when I turn, the screen moves smoothly. But if I click on any change in the setup menu, when I go back to the VC I get a jumping display.The smoothness is gone. If I invoke anything from the keyboard, such as the magnetic compass,<shft+5> for instance, the jumping display in VC mode goes away and the disply is smooth again. I also tried various values for mximum frame rate and that didn't help. Comments, please.

Just getting started with fs repaint. Using the built-in paint program, when I paint a stripe I cant't get it to merge cleanly with the background. In other words it's ragged. I have a copy of PSP 7. Should I use that?Paul

apt msl is 50 feet. I tried a stock airplane and it enters the runway and doesn't take off. I'll wotk on it. thanks

I tried this several times and it seems that the plane keeps increasing altitude as it approaches. I have the alt set at 2000 but it keeps going up. It enters downwind and still keeps going up. It announces base and final but then goes around. Then it runs out of time and disappears. Odd. I havent tried a stock aircraft like a 172. I will do that and see what happens. Thanks.. Paul

Two airports. one plane....AC#1,N93559,1%,4HR,VFR,15:00:00,15:18:53, 20 ,R,500,KEVY,17:00:00,17:18:53, 10 ,R,500,6565 is an addon airport. When the plane came back to the origin airport (65) he did a go-around and then decided to land. On final he just disappeared. Any thoughts? I am doing this just for fun so it's no biggie. Thanks, Paul.

I might be way off base here but when I use real world weather from Jepp, as I get below trasition level I just tap the "b" key and the altimeter kollsman window shows the current pressure and the altimeter moves accordingly. I also tap the B key occasionally as I go along to make sure I have the current pressure.Paul

I believe mag variation was hard coded into FS when it was developed. All VORs North is magnetic North. When the library comes back, up do a search on Collin or the file SC_FREE_SLAVE_GYRO.ZIP (in the gauges category) . The narration there is a good explanation of mag compass and directional gyro. To be brief, there two things that will affect the accuracy of the DG. One is mechanical precession. (there is a check box in the setings menu that will invoke that). The other is flying from one place to another where the variation changes with location. This shows up as the other error in the DG. This little gauge slaves the DG to the mag compass so that when moving thru changing varitaion the DG automatically follows the mag compass. As for your concern, that data is probably in some sort of data base in FS but I have no idea where.Paul

Is it possible to add Rnav 4 sided stars waypoints to the GPS ? If so, where would be a database to do that?Paul

In the avsim file library seach on Copeland. He has a seat adust gauge that I use. Works great.

Do a search on Glen Copeland in the avsim file library. There is a little utility called seat adjust (I think}. It is a little gauge you put on the panel to adjust the seat up and down. I think you will like it. Paul

I cured my problem ... Paul

I moved a background bmp from one plane to another and it shows up scrunched down in the Y axis. I tried resizing and playing withe the params in the config file file but nothing works. It shows up ok in FSPS and my paint program.. This leads me to believe the problem might be with the cfg file psrams. I am open to suggestions. Paul

Let him play with it all he wants. When it gets to a point where he picks up something heavy and out of frustration whacks the monitor with it, it's time to step in.

In short, All light planes are "safe". Mostly it is the pilot that makes them unsafe. When you get to the point where you strap the plane on and go bore holes in the sky you have it made. Cheers.

Yes. reconfigure to a certain extent. I was trying to do that but the imbeded panel only allowed existing round gauges to be used because the gauges will not overlay the panel. They are behind it. The gauge knobs were also imbedded. MS made a big boo boo implementing that kind of thing. What were they thinking of?

OK. Thanks.

When I do SHFT+1 the 2d panel comes up and overlays the VC. What do I need to do to make the VC disappear when I switch?Paul

Some piston twins have only one generator which may be installed on #1 or #2. So if you can determine which engine(s) has the generator then start that one first. Other than that, I don't think it matters much.

Bill, Thanks for the heads up. My previous post about the gauge wroking was really in error. I think I have gotten myself in trouble. The issues I face now are: The heading bugs on both HSIs are linked. The t/f flags also are linked . The CDI on the one I am working on will not deflect. The unit Iam trying to convert to nav2 was downloaded from avsim (KI525) was made for a payware plane. I have been comparing the code with the one from the Baron HSI. What symbol do I use to coment out lines ofcode? will // do?Paul (w3tzi)still learning.

I was successful in getting the HSI to work on NAV2. This is part of the code I used.<value>(A: NAV2 CDI:2 needle vaild, bool) (More here) <value> Same with the glideslope. The issue for me now is how to get the AP to integrate to nav2. I am not a C programmer and can barely modify XML stuff.Paul