twinpropflyer

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About twinpropflyer

  • Rank
    Newbie
  • Birthday January 01

Profile Information

  • Gender Not Telling
  1. Dash 8 Autopilot

    Hi David, I assume, you are climbing with the autopilot, it then levels off at selected altitude and the airspeed starts rising. If it get near the maximum operating speed, the plane starts to climb again. Thats a special function of the default autopilot of X-Plane to avoid overspeed. Since the Dash8 does not have autothrottles, you have to control your speed with the power levers (pull them back). This applies to most of the aircrafts in X-Plane. Happy dashing :-) Jan
  2. Falco 1.1 bugs

    Well, maybe we are talking about the same thing, so just to be sure: In X-Plane we've got a generator switch (for the panel) and comands to operate this switch (via keyboard or joystick). If operated, the generator is directly brought on- or offline. For an advanced electrical system thats not what we want, because (for example) internally the generator is operated via relays which are controlled by a separate computer (generator control unit). So we have to decouple the user input from the simulator and process this inputs with our plugin. To do this, we could create completly new commands to let the user operate the (now virtual) generator switch, or we can just overtake control over the default "generator on" command and don't tell the sim if it was used. This way the user can use the default (maybe already mapped) comands to operate our switches, but in the background our plugin can control the sim systems as needed (hope you got what I mean ;-)). Of course, for systems which does not exists in the sim (like your fuses), custom commands are the way to go. Cheers Jan
  3. Falco 1.1 bugs

    Hi Tom, This will be a lengthier fix. I need to program in several custom commands so that hardware users can map their buttons to my custom commands. I'll put this is a "near" update..i.e .maybe not the next, but the next. ... Why not utilizing the x-plane default commands for similiar functions ? This way users do not have to map new commands to keys to do the same actions in different aircrafts. Your plugin can take full control over default commands and can decide if x-plane should handle the command or not. I just started to use commands in the plugin for my KingAir and it seems to work fine. Just an idea, maybe you thought about this already ;-) Cheers Jan
  4. byte array dataref question

    Ah..., yeah, got it . But it's not a bug, it's X-Plane ;D
  5. byte array dataref question

    Hi Tom, good to hear you figured it out However, I see no reason why the generic text should not work with ATTR_cockpit_region. I just using some generic text instruments which work flawlessly in a 3d pit with 1 region for the entire panel and a dedicated 3d panel setup in planemaker. Cheers Jan
  6. byte array dataref question

    Hi Tom, the "Datab" (or Byte-Array I called it for me ;-)) is used like the other array type datarefs. You need to reserve a memory area for your data, e.g. char MyText[10]. Then, when the user of your dataref calls your provider function, he provides a pointer to a reserved memory area of its own (void* outValue), an offset to your pointer, from which he want to get the data from (int inOffset) and finally the count of data elements he want to get (long inLenght). In your provider function you now just copy the content from your memory area to the memory area of the user, where inOffset defines the starting point from your pointer and inLength defines the size of the copied memory block. In case of the Datab ref, inLength is always the size in bytes already, for other types you have to calculate the bytesize like "sizeof(int) * inLength" for an integer array. Example: "memcpy(outValue, MyRefText + inOffset, inLength)", where inOffset is "0" and inLength is "10", this will copy 10 bytes starting from MyText + 0 to the provided memory pointer "outValue". Of course, you would have to make sure, that inOffset and inLength are always in the allowed range of your reserved memory, otherwise the memcopy function could cause crashes ;-). Thats the solution that works for me and it came straight out of the examples of the SDK, but there may other working solutions too. Also I just realized, that the range checking code in the example from the .org thread is not very robust, so I will have to change my provider functions a bit. Cheers Jan
  7. byte array dataref question

    Hi Tom, you may find this post helpful: http://forums.x-plane.org/index.php?showtopic=37383&view=&hl=byte%20array&fromsearch=1 Cheers Jan