Jump to content

VF31_Subsonic

Members
  • Posts

    150
  • Joined

  • Last visited

Everything posted by VF31_Subsonic

  1. Finally a way for my RIO to kill me instead of the other way around. Thanks for all the work Mike!
  2. Try this.... https://github.com/Munkwolf/dcs-community-keybinds
  3. Got this working after going through the instructions. Great work thanks! Question is....where can I find the additional "device commands: definitions? I am looking to add the working clickable RIO pit controls to RIO panels I am building. The RIO files in the community files are, empty. Thanks
  4. Faster solution may be to look at the virpil warbird base and the vfx twist grip. Devs adding something the jet did not have may just not happen since t s a lot of coding.
  5. I've been slowly working on this... Ignore the wires they are just there for testing
  6. Page 17 has the design. I do not share stl files here...sorry.
  7. https://www.amazon.com/gp/product/B07PBR871M/ref=ppx_yo_dt_b_asin_title_o08_s00?ie=UTF8&psc=1
  8. Finally got these wired into PDCP... pdcp.mov
  9. Question for Devs... I have been using VCP and AIRIO since forever. Great app and ESSENTIAL for VR...IMHO. I fly with a human rio often and like to use ICS hotmic. Problem is..no ,matter what I do or configure, VCP begins to listen for commands in hotmic and well things can get silly. I know I can go in a turn it of an restart the app. but I am looking to smooth the workflow. My thought was to create an OVGME mod...essentially a config file change to load VCP without AIRIO enabled...or maybe even have a different VCP shortcut for no AIRIO when I will have a human in the back. SO....where is this config file, or is there one, which I might edit and toggle with OVGME? Part two...what could I be setting up wrong causing the hotmic issues? I am using a global push to listen key, only listen when held. But hotmic over rides this Thanks fellas!
  10. PSA... As everyone here can see Andre is very active in the forums and always patient and very helpful. I just want to say....if you have hardware issues and ever need support, his support through e-mail is prompt and spot on. He knows his product and responds fast and is very helpful. I had a power issue on my machine that took out several usb peripherals (not gonna go into the boring details), and the Jet seat was one of them. A few e-mails back and forth and I know what parts are required and they are on the way. Flying without the jet seat is like flying without a joystick, or VR for that matter. Once you have one you will never go back. I have had mine for 4 years and countless hours and it has been rock solid...until this mishap having nothing to do with the JS. Awesome support Andre and thanks for being part of the community! Subsonic
  11. Thanks, I have been thinking about it since I have had a few questions and commissions for some of the guys in my Sim group. Many of my designs are very use case specific for my application, so I never expected much interest. It is something I do plan to look into.
  12. I would remove power, pop the offending motor assembly apart and spray the motor with some electrical contact cleaner. I have had a vibration motor get weak or seize up from time to time and this always gets them spinning again.
  13. We are still testing in my group, but feel like this is related to possibly an old moose script. Mission designers may not update this every time they update a mission. still testing
  14. Unsure...only use tacview and srs. Both work just fine.
  15. Clearly this is something mission related as I am seeing the same behavior. The question is...what about a mission, be it moose script or something else, would stop VCP from detecting the mission start and or the jet entry? I have had this issue with a fresh start of VCP and DCS. I can bounce from one server to another of the servers we have and never see a problem, until I get to this one mission.
  16. Ok, so I though this may be connected to the radio assets setting of mission options. But setting this to the same as working server, had no effect. I can take a track file of the non AIRIO working mission and change it to a miz file...load it up locally and still AIRIO commands no go, with the same "AIRIO command not available". Viacom logs show same error and nothing in DCS logs at ALL. Question is...what about a mission or settings could derail AIRIO? Version is open beta Server is using moose scripts....so are all the other working servers. Current mods in mission are 476 vFG Range Targets by Noodle & Stuka Ze Dim new static pack ED TF-51D I can verify that for this mission ONLY viacom pro DOES NOT detect me entering an F-14. Neither for a hot start or a cold start jet. Additionally, I tested the mission skunk160 posted and AIRIO works ok in SP. The plot thickens. Thanks
×
×
  • Create New...