Jump to content

Selkan

Members
  • Content Count

    167
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Selkan

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    UK

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No
  1. I had this problem a few years ago. I am using PFC Yoke in a home built Sim, FSX and default 737-800. It was eventually found that I had a faulty Potentiometer in the Yoke Unit. At the time PFC provided a replacement and instructions on replacement. The Potentiometer at the time was about ten years old, and like all things do wear eventually. I would suggest this may be the Yoko Yoke playing up. A Potentiometer is normally quite cheap, so if you can find the right replacement is worth a go. At the time I thought it was a calibration issue and played around with the PFC settings/null positions for ages before finding my solution.
  2. Hi, I have posted a similar Post over aerosoft about the following, but thought I would write it here as well. I have My Traffic X installed and all my AI aircraft at Trondheim are a couple of feet under the Apron. I use GSX and that is fine. Also, have Orbx Vector, but ENVA is not listed within their elevation correction tool. I am not sure that would help anyway, as I believe it is My Traffic reading what perhaps is the FSX default height for the airport. I have also had a look within My Traffic folders and within 'Scenery Folder' found one BGL file - ENVA. I have been advised to turn that to 'off' which I did, but did not change anything. If anyone has experience of this particular problem and a possible answer it would be much appreciated. Thanks
  3. Anyone know if this will work in FSX. I have just returned from a holiday in Rhodes, and would love to have this airport.
  4. Don't know if this helps at all, but some years ago I had a similar problem with a new PC (I run FSX by the way). It was found that the Motherboard required updating. The people who built the PC did this, and all was then O.K. This is not an area I would dabble with, but you might like to look into this aspect.
  5. This may or may not help, but it has worked for me in the past and I know it has helped some others. I see you have 16 GB RAM - I assume 8 sticks of 2GB each. Carefully remove them from your PC and switch around; i.e. place No1 stick into slot 8, 2 into slot 7 and so on. Just mix them up basically. I believe it is something called 'creep' when one of the contacts on a RAM strip looses contact. Probably caused by heating up and cooling down. Give it a go, can't do any harm.
  6. Hi Ivar, what can I say; glad to be of service, and hope all 'stays well' Regards, Steven
  7. This may have nothing to do with your problem, but recently I started to get freezes in FSX at any time of a flight. Some years ago I experienced a similar problem and found that removing all RAM strips from my PC and then replacing them in a different order did the trick. I have 12 GB RAM in my PC (6 X 2GB strips) I simply put number one in socket 6 and so on. (i.e. in a totally different order/position). I did read in the CTD guide that this can be an issue, and has worked for me. No harm giving it a go!
  8. Hi MigzPT, I had the same problem when I installed GSX. It would seem that FSX doesn't really like three button combinations; it's a timing issue. I got around the problem by going into your key assignments within FSX. Scroll down until you find the command for opening and closing doors and reassign a two button combination. I happen to use ` 1, `2, and `3 ( ` is the key left of No.1, 2, 3 etc) This works well for me, but any two key combination will work. If you use FSUIPC and have some spare buttons on Hardware, then Bob is quite right, that would work well.
×
×
  • Create New...