Jump to content

lnuss

Registered Users
  • Posts

    2,565
  • Joined

  • Days Won

    11

lnuss last won the day on March 26

lnuss had the most liked content!

3 Followers

Personal Information

  • Location
    Westminster, CO

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

lnuss's Achievements

Super Grand Master

Super Grand Master (7/7)

  • Reacting Well Rare
  • Dedicated Rare
  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges

84

Reputation

  1. The web shows there's still one in Miami, FL, too. https://www.94miami.com/
  2. I'm not sure- that's over 20 years ago, and I can't quite tell from the picture. It certainly is similar in appearance but there are a few others that look similar and I don't have all the details memorized.
  3. Is that the current name of the one above the Jet Center? If so I've flown in there a couple of times, though it's been over 20 years ago.
  4. A couple of times- food was pretty good, decor was great and plane watching was decent. For others who don't know, the 94th Aero Squadron was a nice restaurant at Denver's Stapleton Airport (since replaced by Denver International), with an excellent view of runways. There are some others, too, at least in San Diego and Miami. Another place I enjoyed (not quite so fancy and it's been over 20 years now) was the restaurant at the Greely, CO airport- used to fly in occasionally for breakfast (yummy breakfast burritos) or lunch (wonderful big, juicy hamburgers), with a nice view of the airport. Below is the L-21 (military version of Super Cub) I had back then at Greeley- the tower looking thing housed the restaurant -- Greeley didn't have a control tower. In the 3rd pic you can see we're not the only ones there for breakfast. In the 4th pic we're turning base to final for GXY's runway 09 (now 10 because of magvar shift).
  5. Paul certainly has had a wonderful website for many years now- he does a great job. I might suggest to developers who build FS airports that they submit to Paul any information that they find in other research, too, whether Paul has it listed (yet) or not. He always welcomes additional information about his listed fields, as well as about new listings.
  6. According to this site: https://gsplanestuff.com/products/telex-a-610-and-mrb-600-headset-technical-data-sheet-circa-1976 the data sheet for the MRB-600 was circa 1976. With a carbon mic, that's quite a likely time frame, perhaps near the end of carbon mics before the electrets, etc. were more common.
  7. As Phrog asked, what model- they made a lot of them. I still have one of their active noise canceling units from the '90s, model ANR-1D, an excellent unit I bought when I still owned a Cub. And as Phrog also indicated, they don't tend to do changes of aircraft stuff on a model year basis (just like ham radio), rather the development costs are fairly high to make them acceptable to the FAA/FCC and the sales volumes are very low compared to normal consumer products, such that they make essentially the same product for many years, perhaps adding a new model once in a while, but nothing regular. If there's a data plate you can look at you might get a clue, but with the actual model number (including any prefix/suffix) it might be possible to determine a range of dates when that model was made.
  8. Glad you found a solution, Bob. Hmmm...
  9. Nice find Zippy- and for 9 Euros it's not a bank breaker either. And it's offset ILS seems to match the approach plates.
  10. OK, one more thing. I just fired up FSX for the first time in years (I use P3D) and sitting on the ground when I tune 108.15 I get no morse ID on that freq, no needle movement slewing side to side (should move with the aircraft that close to the localizer) and no other indication of any kind. Even the built in map doesn't show any indication of an ILS at that airport. So my conclusion is that the ILS was not installed at that airport in the roughly 2005 time frame (almost 20 years ago) when the FSX database was created. And it's certain that there are many, many other places and items that have changed in the last ~20 years, too, so it's unlikely that many approach charts are accurate today for FSX- real world changes are posted on NOTAMS and the changes on charts are reissued (in the US, at least) every 56 days. So perhaps you could find an add-on scenery that contains that ILS, but otherwise that particular one isn't available to you. You can fly other airports, however, and still get some valuable practice.
  11. You didn't mention a problem in your first post about locking onto the localizer, only about the DME not registering a distance. Not locking onto the localizer indicates that you cannot get a left/right needle indication and cannot navigate using the localizer at all. Or perhaps you are thinking of them a bit differently than what is there. In real life the DME is a separate device, copied from the military TACAN (Tactical Navigation) and is even on a different frequency band, than the VOR/ILS of NAV radios, so it has a separate receiver for the DME. But the DME receiver receives tuning information from the NAV radio and the design is such that the TACAN channel for the DME is slaved to the various VOR and DME frequencies, such that for i-LYDD the DME tunes to Channel 18Y. The only reason I'm bringing this up is to be sure that we don't have a confusion in our communications. In the Radios section of the aircraft.cfg there are parameters you can choose. The Carenado Baron 58 has this: //------------------------------------------------------------- [Radios] // Radio Type=available, standby frequency, has glide slope Audio.1 = 1 Com.1 = 1, 1 Com.2 = 1, 1 Nav.1 = 1, 1, 1 Nav.2 = 1, 1, 1 Adf.1 = 1 Transponder.1 = 1 Marker.1 = 1 and its ILS/DME works fine. Note the Radio Type help for the three fields behind the comment (comment is depicted by // before it). If the problem is consistent across several aircraft it may be an error in the scenery design, so if it's an add-on scenery temporarily disable that scenery and see if the problem persists.
  12. Yes it does- in fact one of the charts uses a DME arc, as the OP mentioned. Lots of info, including approach plates, here: https://airwaymap.com/airport/EGMD/charts Bob, have you tried setting DET (117.30) on Nav 1 then select R1 on the DME to see what happens, or setting Nav 2 to LYDD ILS (108.15) and DME to R2? Doing both should tell you whether the NAV 1 connection to DME is working properly. And have you tried an ILS/DME at another airport with both NAVs? For that matter, have you tried setting a VORTAC or VOR/DME into NAV 1 to see if the DME works? If NAV 1's connection to DME doesn't work in any of the above, the problem might be in the aircraft.cfg file in the radio section. You don't mention which aircraft you're using- perhaps try a different aircraft. Get back to us after the above troubleshooting is done if that doesn't help you solve the problem.
  13. Thanks Charlie. Perhaps I should have made it a capital L when I created that screen name, since so many seem to see it as a capital I rather than the lowercase l, but after 25+ years I've long since gotten used to it. But typefaces in use are as much to blame as anything.
  14. If you look back, PP posted a link, but not to Wayback. Zippy posted a link to Wayback- easy to get careless in which link is which...
  15. In fsx/effects, there are several files beginning with fx_snow, so it may be fx_snowspray.fx. I'd suggest that, rather than removing any files, that you rename it/them to something like fx_snowspray.fx.save, so that if you ever want to restore that you will have it.
×
×
  • Create New...