Jump to content

Warhog

Members
  • Content Count

    745
  • Joined

  • Last visited

  • Days Won

    1

About Warhog

  • Rank
    Member
  • Birthday 06/06/1954

Personal Information

  • Flight Simulators
    DCS A-10C
  • Location
    Nova Scotia, Canada
  • Interests
    Photography, Shooting, Modelling, Astronomy
  • Occupation
    Landscape Architect RETIRED

Recent Profile Visitors

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

  1. Thank you for the response Yurgon.
  2. Well it looks like the change to the new A10C II CMS button has in fact been carried over to the old A10C. Was this an oversight? Will the original functionality be restored to the old A10C... hope so.
  3. It began immediately after the update. I checked the button mapping and nothing changed but when I try changing to another program it just displays Z and then flips to A. I'll check the A10C II manual but the old A10c should not have changed.
  4. I can no longer change counter measures programs using button on stick.
  5. I had the same problem last week with com 4 and com 5. After rebooting the PC, everything connected properly. I have 9 USB connections using the DCS BIOS Hub and this situation has only occurred once.
  6. How many motors do you want to drive? With exception of the EMI on the A10C, I am driving that same stepper motor right from a pro mini. Very smooth and its based off the Arduino library by Guy Carpenter. No driver board is necessary. Each motor takes four GPIO pins but if you only run a couple of motors from a single Nano or Pro Mini, then who cares. If your set on using a driver board, look at the Easy Driver board... http://www.schmalzhaus.com/EasyDriver/Examples/EasyDriverExamples.html
  7. This is what you need to use... #define DCSBIOS_IRQ_SERIAL #include "DcsBios.h" //************** AOA INDEXER ********************** DcsBios::LED aoaIndexerHigh(0x1012, 0x1000, 4); // Red LED on pin 4 DcsBios::LED aoaIndexerNormal(0x1012, 0x2000, 5); //Green LED on pin 5 DcsBios::LED aoaIndexerLow(0x1012, 0x4000, 6); // Red LED on Pin 6 //************** AAR INDEXER ********************** DcsBios::LED airRefuelDisconnect(0x1026, 0x0200, 9); DcsBios::LED airRefuelLatched(0x1026, 0x0100, 8); DcsBios::LED airRefuelReady(0x1012, 0x8000, 7); void setup() { DcsBios::setup(); } voi
  8. It would be great if DCS BIOS and all the sketches that have been written for the original A10C would still work with the new A10C. Obviously new features would have new variable names for those functions. But common functions between versions such as landing gear, battery switch,UFC buttons, etc., should work with DCS BIOS across both A10C versions.
  9. I didn't see any A10C airframes when I was checking out the descriptions and lists of airframes available. Are you planning on adding some?
  10. I had almost the exact same issue with the trigger on my TM Warthog stick. The fix you mentioned was the same as what I did to fix my trigger. I still use that stick but it’s now on the Mongoose base. Love that base! Virpil makes great controls and their customer service is fabulous. BTW, the title of this thread is certainly not warranted.????. It should be edited by the op.
  11. No there is no auto coordinate feature so you will have to assign it to something. The A10C doesn’t use rudder that much but when you need it ... you really need it. If you plan to fly on a regular basis you will buy Pedals. The twist stick is not very precise and has issues when you need good solid control. So you will either get very frustrated and then buy Pedals or you can eliminate that whole process of getting frustrated and buy some now. But fly for a bit with an assigned rudder and see if you like flying. If so... :D
  12. DCS BIOS Modules written for airframes that are no longer in beta tend to never break. If, over time, new features are added to the airframe, those features tend not to disturb previous command arguments. DCS BIOS modules for Airframes that are still under development can always break because... those Airframes are still under development:doh:. I would never start building panels for something that may change completely for some unknown reason. I would wait for the release version. Now with the help of some enthusiastic persons, DCS BIOS modules have been written for beta airframes
  13. You should post your full code otherwise its hard to tell what may be causing this. Also, this may be better served by using a rotary encoder. Regardless, lets see your code and maybe we can fix this.
  14. Potentiometers are only suitable for controlling things like volume or brightness types of controls. But 10k is a good selection for a pot. For items like channel selectors, course and heading knobs(HSI), altimeter pressure and even volume controls, I use a rotary encoder. To control how large a step the rotary encoder makes is done by adjusting the code as follows: This is the basic rotary encoder code from the control reference docs for course knob on the HSI: DcsBios::RotaryEncoder hsiCrsKnob("HSI_CRS_KNOB", "-3200", "+3200", PIN_A, PIN_B); To adjust the size of the step, you
  15. I was just wondering, when you tested four stepper motors running, was it in a mission where these motors could all be moving simultaneously? My concern here is about lag. The pro mini and the Nano are relatively slow processors and may not be able to drive all 4 motors at the same time without loosing steps or having substantial lag. Otherwise, it looks like you are on the path to creating a great cockpit. Keep posting those pics. It can really help others who are not yet at your level.:thumbup:
×
×
  • Create New...