Jump to content

James8133

Members
  • Content Count

    85
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by James8133

  1. Should I uninstall my PMDG 747 and then reinstall the FS2Crew?
  2. Good morning, I recently updated my PMDG 747 QOTS II for FSX. When I turned on the crew, I got a message saying there was an SDK Error. When I updated the Crew, I didn't uninstall the crew because I saw on the forums, that it wasn't required at all in order to update it. How can I fix the SDK error so that the Crew can function again smoothly. I look forward to hearing back as soon as possible.
  3. Good morning, just to clarify things so that I can remember this in case it happens again; in order for the FS2Crew (Button Control) to work, I need to have the AutoFeather Key Assigned, the main button, which is the Alternate Static Source, and the Propeller Sync correct? Thanks again for the help, I really do appreciate it.
  4. I got the Autofeather setting fixed. What was the other secondary button that I need to fix? Was it Alternate static source? Note my PMDG 777 is up to date.
  5. I'm really hoping that there can be a way where we can find a resolution to fix the issue.
  6. Good morning, I did select a key for the auto feather, and it's still not popping up at all in my flight simulator.
  7. Good evening, Thanks for the quick response! How can I find the Instrument Panel menu in the 777? I can easily find it in the NGX, but not sure for the 777. Also, are you saying I should check the Autofeather settings?
  8. Good Afternoon, I apologize if I made a double post. In the manual for the crew, it talks about creating a hot key assignment for the crew to work. I did that and saved it into FSX. When I open FSX and try to push any of the keys, nothing is showing up. Everything was working a few days ago, and my crew is currently up to date. How can I fix this issue? Thanks again. https://imgur.com/gallery/itE2aWB
  9. Good afternoon, I noticed that my FS2Crew Button Control isn't working at all in FSX. My Crew is up to date. On the manual for FS2Crew, it talked about setting a key for the alternate static source, and propeller sync. I did that, and saved it to the settings. When FSX loads up, and I press the keys, nothing shows up at all. I don't know what to do in order to fix this solution. https://imgur.com/gallery/itE2aWB
  10. VirtualAli hasn't been real helpful at all when I originally reached out to them about this issue.
  11. I thought that everytime I reinstalled an airport, I would have to enter the activation code?
  12. The last time I uninstalled KLAX and reinstalled it, the activation code was already entered. Another thing that I ran into, last time it wanted me to remove the FSDTLive Update Application. I clicked "no" because it would impact all the other FSDT products not to work well. Any advice?
  13. Here is what I found. https://imgur.com/a/Rw2kEdl
  14. How do I run the reg file again? That's not the airport scanner that you were talking about?
  15. Good morning, I apologize for the late response. I've been sick with a cold over the past week. I think it's because it's that time of the year. I will try that and I will get back to you.
  16. Do you think uninstalling the airport and reinstalling it could help?
  17. Thank you for the response AirErnie, I can reach out to FSDT again. I apologize for the late response. I've been sick with a cold over the past couple of days, and I haven't had time to check the forums. When I first reached out to FSDT, the only answer that VirtualAli could give me was; "I'm sorry, but I cannot reproduce the problem. Everytime I load up KLAX, I get this message that says; "KLAX trial period has begun." I went into my addon manager and found that KLAX was already activated. So, I'm confused to why each time I load my plane at KLAX, that message still appears. VirtualAli then went on and said; "Do you have an addon scenery for KLAX from Ray Smith maybe? This can only be caused by another scenery for KLAX installed, the one from Ray Smith had this problem." All I want is to find a solution to why this is happening. I know that FSDT recently updated their products. After I updated them via the FSDT Live Update application, AES was still able to work. I understand that GSX is available for all their FSDT products. However, I'm not a big fan of GSX. That's why I've been using AES all of these years. What else can I do to resolve the issue? Do you think I should uninstall ALL of my FSDT products and reinstall them again? I do appreciate all the help that is given towards me. I hope we can get the problem fixed ASAP.
  18. I've also ran into this problem too. Is there anyway where I can fix it? https://imgur.com/a/p5cK6ll
  19. What else can I do to try and resolve the issue? Also, s having duplicates at KJFK a bad thing?i
  20. Here is another one that I found. https://imgur.com/a/SUD7S5J
  21. Hello, I apologize for the late response. I have been busy with work over the past few days. I did do what you asked, and this is what it shows. https://imgur.com/01R1QyA
  22. It couldn't find ANYTHING at all. not even my current airports. It gave me the same message? I'm really confused here...
  23. Then it said when I tried to close the application: "Some files extracted from SimpleAirportScanner.zip were found or new files were created. Do you wish to put them to the archive?" I don't know? I don't want to accidentally mess thing up.
  24. It said "Found to be empty Parameter name: pathToSceneryCfgFile" Which I don't know what it means?
  25. I have uninstalled it completely and reinstalled it. And it still gives me the same message. 😕
×
×
  • Create New...