Jump to content

elmerfudd

Registered Users
  • Posts

    84
  • Joined

elmerfudd's Achievements

Community Guru

Community Guru (4/7)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later

Recent Badges

10

Reputation

  1. Col. As noted above, I've installed the Albatross radios. I've done three flights since then, and the problem has not recurred. Thanks so much, for the tip. Regards, Terry
  2. I use a Logitech Extreme 3D Pro. I like the stick, with its 12 buttons, but the stick feels more like an exercise device with it's heavy centering spring. Of late, this has become a problem for me. I have tennis elbow, and I don't play tennis. The stiff stick is the most likely culprit. The Thrustmaster T.flight stick x has a spring tension adjustment, and I'm wondering if this will alleviate the problem. Can anyone advise? Thanks in advance.
  3. Col, I've installed the radios that came with the Albatross. I don't recall why I was using the default radio stack, but I suspect it may have something to do with the fact that when I installed the Albatross radios, I had some trouble turning them on (they are not on by default). When I clicked on the volume control/ on-off switch, nothing happened. I had to click to the right of the control to turn them on. The radios are actually quite nice and realistic looking. I will give them a try and see what happens when I next land at a controlled airport. Thanks again. Terry
  4. David, I have an old Core 2 Duo with Win 10 installed, that a relative of mine brought me from his workplace. It originally came with XP, was upgraded by a refurber with Win 7, and then some brilliant soul thought it was a good idea to upgrade it to Win 10. Win 10 has no business being in this old box. At any rate, I poked around in it just for yucks, and I don't like Win 10. I hope I never have to go down that road, although I suppose it's inevitable. If that day comes, I'll just bite the bullet and get a Dell with the appropriate specs. In the meantime, if any of my XP boxes bites the dust, I have spares. Regards, Terry
  5. David, As stated above, I run my sims in old XP boxes. I believe the reason that FS9 doesn't run well on my Win 7 comes down to the el-cheapo video card that they put in the box. I specified a dedicated video card when I ordered it, with the idea that a separate card would work better. We also have a near-identical computer with onboard video, that doesn't exhibit the problems I'm having. Of course, another advantage to using my old XP boxes is that I can use my Win 7 to surf the net on those long over-water flights. Works for me. I'm debating getting a new computer to run the new Flight Simulator 2020. Regards, Elmer J. Fudd
  6. Col, You may have a point. I've taken a look-see at my Albatross, which I installed nearly ten years ago. It came with some custom radio gauges, but for some reason, I didn't use them. I installed the default radio stack from a Cessna. Being so long ago, I don't recall why I did this. I'll have to do some investigation, maybe try the gauges that comes with the Albatross. Thanks for the tip. Regards, Elmer J. Fudd
  7. David, Thanks for the tip. I've checked the Weather.DLL files, (keep in mind that I run my sims on old XP boxes. I bought a new Win 7 computer about nine years ago, with the hopes that it would run FSX, but found that it would not even run FS9 properly. FS8 runs fine on it). The Weather.DLL files I have are the originals, installed by FS9. I'm beginning to suspect that the Grumman Albatross may be the culprit. When I finish this trip, I'll switch planes and see what happens. That'll take awhile. In the meantime, I've mitigated the problem by landing on the water nearest my destination. No ATC, no problem. I have another box with Golden Wings and Silver Wings installed, and have no problem there. If it turns out to be the Weather.DLL, I can copy the good one from there. Regards, Elmer J. Fudd
  8. Tom, I have no add-on scenery. I tried that once, in the FS8, and didn't like the results, so I left things the way they are. Right now, I'm doing a flight around the world, using the Grumman Albatross. I wonder if the plane has something to do with it. I did another flight yesterday in another machine using an A35 Bonanza, and didn't have the problem there. I guess I'll have to wait until I finish this flight, before I switch planes and see if the problem continues. Regards, Elmer J. Fudd
  9. After a flight, I turn off at a taxiway, and ATC says to contact ground. As soon as I respond, the program crashes. My old Dell used to do this, but my newer Dell did not, but now it is, as well. I used to use some tricks to mitigate this, such as saving the flight before I turn off, which worked for a while, then it didn't. I then started delaying my response to the ATC until they repeat the instruction to contact ground, which worked for a while, then it didn't. The longer the flight, the more likely this is to happen. Recently, it happened after a short flight. It messes up my logbook, (the flight doesn't get logged), and the state.cfg file (the time doesn't get added to the file). Any solution to this vexing problem? Elmer J. Fudd
  10. Tom, I've figured it out. I did a search on state.CFG, and one of the threads brought up the subject of the Hobbs meter in the C172. In actual fact, the meter in the C172 tachometer is not a Hobbs meter. The Hobbs meter is a separate instrument from the tachometer hour meter. The Hobbs meter runs at the same rate as a clock whenever the engine is running, regardless of engine RPM. (Flight schools love those.) The hour meter that is built in to the tachometer runs at a normal rate at a normal cruise RPM, but runs slower at lower RPM. Of late, I've been flying old birds with radial engines, at 2,000 RPM. I suspect that is the cause. I don't know, how I could have forgotten. Been too long, I guess. Regards, Elmer J. Fudd
  11. Thanks, Tom. Now, if I could only figger out why the FS9 records 3.2 hours in the state.CFG file for an aircraft when the logbook shows 4.4 hours. Regards, Elmer J. Fudd
  12. Thanks, Tom. I just wasn't sure if the difference between FS8 and FS9 was normal. I should have clarified: I got FS9 within a year of getting FS8. I use the FS9 for long-distance flights, and FS8 for local flights and IFR practice flights. I got used to the world disappearing when I entered the clouds, and was surprised when that didn't happen in the FS9. Regards, Elmer J. Fudd
  13. There was a time when I used to just download real world weather, but of course that doesn't work anymore. So, I look up the weather from The Weather Network, (or some other site) and feed in the settings. In FS8, when I select "overcast", I get exactly that: an overcast. If I fly above the altitude in the settings, the view out the windows turns milky white. In FS9, when I select "overcast", I get a few clouds, but not the solid overcast I am expecting. Maybe my memory is playing tricks on me, but I seem to recall that this used to work better. I have the same problem on three different installs in three different machines. I should note that things seemed to start going wonky when I created a Silver Wings install and a Golden Wings install on another computer, and copied them over so that I had multiple installs. I'm having all sorts of problems, even though I have since removed those from two of my machines, leaving only the FS9 installs. Things like the timer not keeping accurate track of the flight time, or the state.CFG not keeping an accurate account. For example: I fly five hours, and the state.CFG file for that aircraft increases by 3.5 hours. I'm beginning to wonder if I need to re-install from scratch. Advice would be appreciated. Elmer J. Fudd
  14. I can't say I recall other problems. It was too brief an experiment, and too long ago. It was mainly not being able to make changes to .air files. I gave installing in C: in my Win 7 box a try, but I decided not to bust my head against it. Elmer J. Fudd
×
×
  • Create New...