Jump to content

Slayer

Members
  • Posts

    36
  • Joined

  • Last visited

Recent Profile Visitors

1,509 profile views

Slayer's Achievements

Newbie

Newbie (1/14)

6

Reputation

  1. I have very limited programming experience. Here is what Ben had to say on it: http://forums.x-pilot.com/forums/topic/9357-gizmo-x-plane-crash-when-sending-datarefs/?page=2#comment-103628 bottom line is you can use DRE or DRT to change datarefs and they way they access the datarefs works with the IXEG. DRE is open source so possibly have a look at his source code to see why his method works and the FlywithLUA plugin crashes?
  2. reread my post: ixeg/733/MCP/mcp_lnav_ann that is the annunciator light so it's only on when lnav is on and active. Sorry for the confusion. if you want heading select and VNAV those are: ixeg/733/MCP/mcp_vnav_ann ixeg/733/MCP/mcp_hdg_ann
  3. Sorry I misspoke myself. I was looking at the button itself not the indicator light which will tell you if it's active or not. the dataref you need is: ixeg/733/MCP/mcp_lnav_ann
  4. I'm using a Goflight Interface Tool for programming my MCP. I use that dataref but I'm afraid I can't tell you if it's for sure an int as that software handles all the reading and writing internally so I never see it, only the dataref. There is a way to read that info though but I'm not a C++ programmer so I can't tell you the method. Suggest you have a look at the DRT source code , you will find a clue in there .
  5. ixeg/733/MCP/mcp_lnav_act definately works I use that for my profile - it's a 0 or 1 You can't read ixeg/733/autopilot/LNAV_mode_toggle because it is a command
  6. Try "sim/cockpit/radios/nav1_obs_degm" for the left course and "sim/cockpit/radios/nav2_obs_degm" for the right course displays. Works for me.
  7. A bunch of the animations with the commands don't react properly in the VC when used (IE MCP buttons stick in ) but they are still functional. I reported a bunch of button problems too but it's going to be low on their priority list to fix because it doesn't really impact the functionality, it's just aesthetics. You will get stack overflows with FlywithLUA because the method that it writes datarefs isn't quite right for this aircraft. If you can convince the author of the plugin to use the same method to send datarefs that DRT uses you probably won't have stack overflow crashes anymore. Slowing commands down is a bandaid, eventually you get a crash if you use dataref enough times. With a gear lever it should be only a couple of times a flight but eventually you will still get a crash,
  8. My guess is you're manipulating the dataref for the display instead of making your hardware turn the knob left and right. Probably a misplaced decimal or something in there too. Good luck.
  9. Ben, Thanks for the explanation. DRT's method for access works and it is open source.( and a clue on how to make it work) for other hardware plugins and I'll leave it at that. I'm just happy I've got my hardware working no matter how the result was achieved. This thread has probably run it's course and you can close it if you want, there was no intent of finger pointing of blame laying, hope you don't take it the wrong way. I was just providing my findings to help other people get their hardware working too. Your explanations of how things worked were helpful. Thanks
  10. I'm afraid that slowing the events down will not correct the issue, slowing it down just makes it less likely that a crash will happen , but eventually it will unless the plugin is changed. It has to do with the programming method in which the datarefs are sent to X-Plane. Without saying too much that is over my head and I don't fully understand, they need to be sent with a widget draw event not just a plain draw event. I'm not sure that this is completely fully documented in the XPlane SDK or why other aircraft from different vendors work without it being done this way , but it works for the IXEG/GIZMO. But yes you would need whoever made the Teensy plugin change it to send datarefs via that method. I'm sure someone with advanced programming skills in x-plane datarefs would be willing to help, try contacting the author of your plugin and direct him to this thread?
  11. I was referring to Goflight interface tool. Version 1.4 corrected the issue for me, not v 1.04 of the IXEG. Not sure what software you are using to send datarefs but it will probably need to be updated.
  12. This problem has been solved pretty much. The author of the program figured out a work around "all reading, writing and commands are processed off the back of the widget draw event. " (I'm not a programmer so don't ask how:)) was the fix, it may aid others in solving their issues using other software tools and methods to send datarefs to this aircraft. After a few hours of testing I only had 1 crash because I accidentally send a out of range value. Anyone else reading this that may use Goflight interface tool software will need to update to version 1.4 from your user account on PPS website. I'll be releasing a profile with full MCP and EFIS support shortly.
  13. Does the heading selector only increment by 2 degrees in the real aircraft? If I look at the datarefs the numbers go up normally but it takes 2 clicks of the dial and the odd heading numbers do not show so it appears that the MCP display is rounding the value or skipping odd numbers. Not sure if this is a bug or intended behaviour?
  14. In the docs folder of the IXEG there is a .pdf with a big list of datarefs in it, those you will not see in the joystick interface of Xplane. You will though be able to see and configure the "commands" stuff to joysticks and buttons. Those have logic built into them already so all you do is use it.
  15. Thanks for the free vid A2S, I liked it. Who wants a dry video of someone reciting checklists that you can get out of some POH. At that point you're better off just getting the manual. Different people have different learning styles and I appreciate the way you guys present. Most airlines have slightly different procedures and equipment so nothing is as cut and dry as that detractor would have you believe. Their vids cost about as much as a pizza, if you're spending 75 bucks on a virtual aircraft why not get a video or two to learn how to fly it and get some enjoyment from it?
×
×
  • Create New...