frumpy

Members
  • Content count

    205
  • Joined

  • Last visited

Community Reputation

90 Excellent

About frumpy

  • Rank
    Advanced Member

Profile Information

  • Gender Not Telling

Recent Profile Visitors

2,534 profile views
  1. Aircraft Specifics

    That's a point. Personally, I don't undertake this detail of planning. I check fuel, weight, CG and off I go. Study qualities, but consumer market. A sidenote: In PSX I saw graphically how a gradual increase in fuel shifted CG back and forth. Extremely detailled and exact with the numbers, it's got vulcanic ash and elms fire simulation too. Maybe that's what you are looking for.
  2. Aircraft Specifics

    How do you define "study-level"? Concerning the MTOW, 138,500 vs. 139,274lb: Would you notice the 700 pounds difference? I wouldn't. And that pretty much summarizes what this is all about: in a flightsim you'll have to make concessions. Even a $350 tagged PSX does have some (okay, very little) things that are not "real". I mean do you go in a level D sim and complain about the duration of g-load in certain situations? I think the bottom line is that the IXEG is one of the best (...) aircraft for XP. Don't you agree? Glas is still half empty? Why don't you look at the things that were done very good, rather than trying to find things you don't like?
  3. Need a MCP command

    That's great news, thank you very much!! That'll make a nice toy.
  4. Need a MCP command

    No, the encoder sends twice the signals that I need, thats why I use only every second signal. This way one click equals one degree in heading change. The thing is really that the HDG_bug_inc_90 command from the first post should only move by one degree, not 90 - then it would work like the course knob as you see on the video. I'll check Ben's recommendation tonight, however I think I would stil be bound to the time delay due to reading&writing the dataref. Olli
  5. Need a MCP command

    Well, the IXEG runs at about 35fps, I assume this is also the frequency the datarefs are updated. I am using Air Manager v3 as a plugin, I am not too familar with programming. Also due to my encoder setup, I can only use every second signal. Here is the code: hdg_counter = 0 -- init function hdg_dial_change(hdg_direction) print(tostring(hdg_direction)) hdg_counter = hdg_counter + 1 if hdg_counter == 2 then hdg_counter = 0 -- use every second click else if hdg_direction == 1 then new_hdg=hdg_act+1 xpl_dataref_write("sim/cockpit/autopilot/heading_mag", "FLOAT", new_hdg) elseif hdg_direction == -1 then new_hdg=hdg_act-1 xpl_dataref_write("sim/cockpit/autopilot/heading_mag", "FLOAT", new_hdg) end end end hw_dial_add("ARDUINO_MEGA2560_A_D37", "ARDUINO_MEGA2560_A_D36", hdg_dial_change) -- thats the encoder function hdg_dtaref(heading) hdg_act=heading end xpl_dataref_subscribe("sim/cockpit/autopilot/heading_mag","FLOAT",hdg_dtaref) -- subscribe to the dataref, save as global variable every time it's changed I made a video while toying around with it, the Course knob uses a command, the Heading knob the change of dataref:
  6. Need a MCP command

    Thanks for answering - thats what I did, but basically it's not usable because the transmission of signals takes too long. It's working almost realtime with the other encoders, but with writing the dataref it's just slow...
  7. Need a MCP command

    Hi guys, I'm doing some interfacing with buttons, LEDs and switches. I'm almost done programming a MCP testbed. Unfortunately these ones: ixeg/733/autopilot/HDG_bug_inc_90 ixeg/733/autopilot/HDG_bug_dec_90 change the heading by 90°, but I need a command for 1° steps. Also there is no command for the altitude knob! I can use the default X-Plane ones, but thats 10' increments, not hundreds. Besides that, everything seems to work. Could you please add those commands? Thanks, Olli p.s. Sending the command 10 times will take care of the 10' steps^^ But still no help for the heading
  8. Format of dataref?

    It's float! But that wasn't the problem: correct dataref name is ixeg/733/MCP/mcp_a_comm_ann and should be corrected in the interface guide
  9. Format of dataref?

    Hi guys, I'd like to use this dataref, which is either 0.000000 or 1.000000: ixeg/733/MCP/mcp_a_cmd_ann Whats the format I can pass on to LUA? INT? Bool? Float? I tried it all, but didn't work. Thanks, Olli
  10. Gizmo is break after install beta 8.

    You are right, I missed that one. I just felt irritated by the tone.
  11. Gizmo is break after install beta 8.

    I think he could need some help, rather than being rebuked.
  12. MIP measurements/layout

    Did you find any? There are the measurements for the NG floating around, you might need to start from there. The main instruments in the B58 have a diameter of 3 1/8", this seems like a standard size and might also apply to the ALT/VS indicator. You can also check the IXEG textures folder, if you find the background texture - then resize and print it (not sure if that texture is there, though). If everything fails, you might still be able to check out an old 737 sim and take measurements.
  13. Pitch nose down in flare

    Try sandwich tactic: Praise the product first, place your input, praise again
  14. Did you try to delete&reinstall? Everything else works expected?