Jump to content

goldleader

Members
  • Content Count

    28
  • Joined

  • Last visited

About goldleader

  • Rank
    Junior Member
  • Birthday 04/15/1977
  1. Hi, I believe Ramp 21 has already been reported for AI issues, but it also causes player aircraft allocated there to spawn in mid air, as does Ramp 51 also at Al Dafayr.
  2. Yep I am aware the Pilot has the -159 but the RIO has ARC-159 Volume and Display Brightness and these binds are functioning properly. Full Radio is ARC-182 as you say, Volume Binds do not work.
  3. The Default Keybinds in the RIO Pit for the ARC-159 seem to be fine, but the Default Keybinds are broken for the ARC-182 With the ARC-182 the increase and decrease keybinds seem to control the Squelch switch on or off depending on where you put the Radio Volume If Radio Volume (using Mouse) is above 50% both keybinds turn the Squelch On If Radio Volume (Using Mouse) is below 50% both keybinds turn the Squelch Off
  4. Thank you so much for confirming it is not just my rig. :thumbup:
  5. As per Jabby's Post The Default Keybinds in the RIO Pit for the ARC-159 seem to be fine, but the Default Keybinds are broken for the ARC-182 With the ARC-182 the increase and decrease keybinds seem to control the Squelch switch on or off depending on where you put the Radio Volume If Radio Volume (using Mouse) is above 50% both keybinds turn the Squelch On If Radio Volume (Using Mouse) is below 50% both keybinds turn the Squelch Off Video Attached showing that I do not have anything bound to the Squelch switch I use Num 0 and Num . first to change the volume of the ARC-159 Radio an
  6. I have done some more testing and completely re installed Both OB and Stable and I am still getting the same thing on both versions OB with all modules and VR Scratchpad, VAICOM, SRS and TacView all installed and a brand new Stable install with only the A-10C and Persian Gulf Map installed, with none of the companion apps installed (Tacview, VAICOM, SRS, VRScrathpad etc...), but it only occurs with the following settings Terrain Object Shadows - Default Shadows - Low or Medium would you be willing to change your shadow settings and do another video if you have the time to spare, I wou
  7. Thank you for that, good to know it is either something on my end or VR related, now if I can work out what is causing it. More testing required.
  8. So I noticed while ago that this was happening but have only just had a change to report it. I am getting some very strange things happening with shadows, I mainly noticed it in VR as this effect on the shadows happens on the peripheral of the extremities of the sides of each eye, but on further investigation it happen in 2D as well, it only happens when Terrain Object Shadows is set to Default but nonetheless it happens in both VR and 2D. I experimented with turning MSAA on and adjusting the Mask Size in VR options, but this had no effect in either 2D (As I expected it would not) and VR.
  9. I had a feeling that would be the answer, :( I found a workaround which while not perfect will suffice. Have just mapped two positions that are most used to those encoders, not perfect but will do.
  10. So here is one for you... I have built a button box with several rotary Encoders which I am hoping to use for a number of dials in the A-10C. Most of them are working as planned, but I am having trouble with some of the binds that are of the type multi-position_switch_limited The example below is from clickabledata.lua for the A-10C and is the UHF Radio 100Mhz and 10Mhz dials. elements["PTR-ANARC164-100MHZ-SELECTOR"] = multiposition_switch_limited(_("100 MHz Selector") , devices.UHF_RADIO, device_commands.Button_2, 162, 3, 0.1) elements["PTR-ANARC164-10MHZ-SELECTOR"] = multipositi
  11. Don't forget there are two bindings for the Autopilot Engage disengage 1. AAP Engage/Disengage which is default bound to the A key and the Black button on the warthog throttle next to the Autopilot mode three position switch (ALT:ALT/HDG:PATH) 2. Left Throttle button which is default bound to the Q key and the Red Pinky button on the front of the left throttle handle AAP Disengage/Engage (A) is not functioning as designed, Left Throttle Button (Q) is functioning as designed quick fix is to bind both buttons on your hardware to the Left Throttle Bind in the game.
  12. Hi, I don't know if this will help but this is my Export.lua using TacView, DCSBios (Facepanels Version) SRS and VAICOM, I found that the order in which everything goes in the export.lua makes adifference, I am not sure why mine works in this order, but everything is working like this. local dcsbioslfs = require('lfs'); dofile(dcsbioslfs.writedir()..[[scripts\DCS-BIOS\BIOS.lua]]) --BIOS = {}; BIOS.LuaScriptDir = [[C:\Program Files\DCS-BIOS\dcs-lua\]]; BIOS.PluginDir = [[D:\Users\Matt\AppData\Roaming/DCS-BIOS/Plugins\]]; if lfs.attributes(BIOS.LuaScriptDir..[[bIOS.lua]]) ~= nil then dofil
  13. Hopefully this has not been asked before too recently, but 429 pages of messages to go through is a lot, so apologies if it has. Havinig a minor issue in the Huey while using SRS, if I set the SRS setting "Use DCS Cockpit PTT" to On everytime I press any of my Viacom keybinds my SRS Radio latches on, I have tried a few things but the only thing that seems to resolve it is turning that setting off, it only seems to affect the Huey Module, but I would like to be able to keep that on, as Intercom has just been implemented and I would like to use the two seperate PTT buttons (RADIO and ICS) for t
  14. Togg What Font did you use for your Icons, I am makng a couple more to suppliment your already awesome Icon set and would like to make the font the same. Thanks
×
×
  • Create New...