Jump to content

gypsyczar

Members
  • Content Count

    72
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

19 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    No

Recent Profile Visitors

1,495 profile views
  1. Bryan, Thanks. I'll initially try it without the pre-flight events and see what happens
  2. Obviously I have not had time to read through all of the manual. However I'm sure that some of the beta testers know the answers Just how does FS2Crew integrate with the ATSU flows implicit in the FSLabs software? Are there any conflicts with some of the GSX interactions or door openings/closings? If running the FS2CREW cockpit preparation countdown are there any impact on the ATSU flows or timings
  3. Thanks I think I understand its all in the threads.
  4. Sorry I wasn't very clear. I want to assign a button in FSUIPC to execute a Mycode.lua that I will write. Within Mycode.lua I would like to call functions in actions.lua. I do not want to call the actions.lua functions directly from FSUIPC I understand that I could use the LINDA GUI to do the button assignments but I'd rather do it all through code if it is possible. If not I can use the GUI Thanks for helping a stubborn newbie
  5. Sorry for this stupid newbie question, but it is hard to figure things out without documentation. There is a nice aircraft specific actions.lua file with hundreds of wonderful functions available for my aircraft. I would like to create my own lua module that uses logic that calls some of these existing functions in the actions.lua file. My lua file would then be called by FSUIPC as a button press to do amazing things :-). Is there a way to call functions that exist in the actions.lua file or do I have to copy the actual function code from Actions.lua to my lua code for this to work? I guess, in other words, is there an "include" directive or something similar that I could put in my code to avoid having to copy the actual code from actions.lua?
  6. Once again, Please remove any logic inhibiting the use of flaps. The DC9 era aircraft had no other system other than the PNF politely letting you know or slapping your hand if you were going to do something exceedingly stupid with the flaps. Or, how about the BAW 777 at EGLL where the captain raised the flaps on short final to make the overrun after the double flameout? Why would Fs2Crew implement something not present in the real A/C?
  7. Bryan. Sorry, but I am very passionate about this issue. One question, Does the real aircraft have anything other than the mechanical detents on the flap lever to prevent you from doing anything you want with the flaps? If I want to be asking the computer for permission to do something I have an Airbus and a FA18 for that. The DC9/MD series is not of that genre. Please, please, at least give us the option to turn off the FS2Crew imposed artificial constraints on the pilot that are not found in the real A/C. Thanks
  8. Bryan, This flaps situation is just too complex with too many prerequisites, triggers, and conditions. Please give the PIC total control over the flaps and slats in all phases of flight. If I give a flaps command at any time from pre-taxi to short final the PNF should immediately set the flaps accordingly if within the extension/retraction limit.
  9. Bryan, I am still having the problem, For example after landing saying "flaps up" shows correctly in the green bar yet nothing happens, OK, sitting "ready to fly". TAXI showing in the FS2Crew window. I say "flaps full" the green bar says flaps forty and nothing happens. The ONLY flaps binding that I have is through FSUIPC for flaps Incr and flaps decrease
  10. Thank you! Minor rectal cranial inversion :-) Too Many switches
  11. P3DV4.2 - just recently when I start cold and dark, both of the FMA's do not "Light" and are totally dark. If I load ready to start they are fine. Am I missing a light switch to light them up or is this a bug? I am using real light and glass at 4096. The only thing that I have changed is adding FS2Crew
  12. Some more things. "Set 110.7 on Nav1" It shows correctly in the green bar, but nothing happens in the A/C. Once again, are default control assignments needed?
  13. For some reason none of the flaps commands work. Most other commands work fine. Since I use FSUIPC almost exclusively to assign controls I have cleaned out the P3D control assignments. Do the FS2Crew flap commands require some default control assignments to function? Also, is there something that precludes setting speed and heading on the ground? Setting either in the air works fine.
  14. I cannot pull up the views panel using shift + 1. Obviously something is trapping that key combination but I sure can't find it. Is there any way to change the default shift + 1 key combination to bring up the view selector? Or can a key be assigned to toggle the yoke visibility? Found it..... Shift + 1 was not assigned to the panel view 1 event in P3D
  15. Although the setup app has a measuremnt units option that can be set to LBS it appears that the FMS and aircraft fuel displays only work in KG. Am I missing something here?
×
×
  • Create New...