• Content count

  • Joined

  • Last visited

Community Reputation

17 Neutral

About ddawson

  • Rank

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Ottawa, Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. ddawson

    Realair Duke v2 Piston in P3D v4

    Yes, because the entry in panel.cfg is explicit, you can put the gauge in the main gauges folder. If your panel.cfg looks like this: gauge21=RASDuke_Sound64!Sound, 1,1,2,2,Sound/RASDuke_Sound.ini then the gauge must go in the panel folder. Also, when searching for gauges, P3D looks in the gauges folder first and then in the aircraft's panel folder. This behaviour is the opposite of that of FSX. This can be problematic with gauges using a config file. Doug
  2. ddawson

    Realair Duke v2 Piston in P3D v4

    Ryan, Could you post the panel.cfg entry for the gauge? Also, let me know where the folder of sounds for the panel is (probably within the panel folder.) Doug
  3. ddawson

    Realair Duke v2 Piston in P3D v4

    The CLS products use an older version of the sound gauge, with a different interface. You'll be in pretty tough trying to update them to work with the 64 bit sound gauge.
  4. ddawson

    Realair Duke v2 Piston in P3D v4

    It may be more work than most users are inclined to put into it, but you can edit the configuration file for the sound gauge to use explicit paths for the sounds, something like: Sound00=c:\p3d_aircraft\RealAir_Duke\panel\sound\KEYPRESS_ANNUN.wav, -200 You can do the same thing with the panel.cfg entry for the gauge: gauge21=RealAir_Sound_x64!Sound, 1,1,2,2, c:\p3d_aircraft\RealAir_Duke\panel\Sound\RASDukeTv2_Sound.ini The reason outfits like RealAir don't do that is that they can't know where your FS installation will be. You of course do know that, so, if you wish, you can make the edits to the configuration files to include the specific path references. The examples above are just that, examples. You will of course need to modify them to reflect the paths where the files are actually found on your computer. Doug
  5. ddawson

    The device you never knew you needed - Infinitton ?

    I have a Logitech G13, which gives you more keys, for less money. The downside of the G13 is that the buttons are just conventional buttons, they don't have the ability to display a bitmap. I've been in the process of slowly developing a custom FS interface for the G13, to support FS commands directly, rather than through mapped keystrokes. I might look at doing the same with this beast, as the ability to display an image on the button does look intriguing. Doug
  6. ddawson

    Just Flight DC-10

    Don't waste your time. The CLS products use an absolutely antique sound gauge, with a different interface. I haven't looked at the code for that one in 7 or 8 years, so really wasn't planning on updating it. Doug
  7. ddawson

    FS9 Panel Ident

    From the cpt.icons gauge: <Click>500 (&gt;K:PANEL_ID_TOGGLE)</Click> The ident value from the panel window description in panel.cfg has to match the value you are sending to the PANEL_ID_TOGGLE function. In this case, your panel window has to have an ident value of 500, or you need to change the code, as quoted above, to match the ident value in panel.cfg. Note that you cannot use the text macro values you sometimes see in panel.cfg as ident values in xml code. This will not work: <Click>THROTTLE_PANEL (&gt;K:PANEL_ID_TOGGLE)</Click> Doug
  8. ddawson

    Utility, add-on question

    Well, not quite. I can build you a gauge that will make noise when vertical speed exceeds some predetermined threshold. You would have to turn it off during climb out and descent, or it would get pretty annoying, pretty quickly.
  9. ddawson

    Autopilot/Radio stack

    The autopilot will not function unless there is an autopilot section in the aircraft.cfg file. You can copy that from the stock Cessna file as well. Doug
  10. You can save yourself a small amount of both memory and CPU cycles by commenting out or deleting the debugger line in the panel window outlined in your post. It's unnecessary for the operation of either the sound gauge or the autopilot gauge. Doug
  11. ddawson

    Heading, Altitude, Speed Shortcuts

    A hotkey sequence popping up a small dialog box. That kind of thing?
  12. ddawson


    Maybe this: double getCarbTemp(int engine) { double degC = 0; char var_name[48] = { 0 }; sprintf_s(var_name, "(A:RECIP CARBURETOR TEMPERATURE:%i, celsius)", engine); execute_calculator_code(var_name, &degC, NULL, NULL); return degC; } You need to separate the index from the name with a colon, and you need units for an xml A:var. Doug
  13. The error message means just what it says. The gauge is loading just fine. Where is the configuration file located? Doug
  14. ddawson

    Manfred Jahn DC3/C47

    www.douglassdawson.ca/files/dsd_p3d_xml_sound_x64_gauge_only.zip Please note that this is the sound gauge you will need. It won't do anything for effect files. Doug