Jump to content

skypickle

Members
  • Posts

    1087
  • Joined

  • Last visited

Everything posted by skypickle

  1. I downloaded a fresh copy of dcs open beta. Deleted the saved games folder. Restarted the game , bound some controls for basic flight. Now, scan zone up and down work, but scan zone left and right do nothing still. Changing from TWS to RWS gives me a narrower scan angle but even in TWS, I cannot move the 'cone' of the scan volume left/right.
  2. C. I just copied the installed version from F to C drive
  3. antenna elevation does not exist in the control binding options for the F-15C.
  4. my regedit has three entries: DCSWorld is 1 locates a non existent copy on my C drive (I must have deleted it long ago) DCS World Openbeta locates to my F drive which happens to be the largest SSD DCS World OpenbetaServer locates to my D drive. If I try to instal a 'virgin copy' it just looks to my F drive and puts a shortcut to the single thread executable on the desktop. If I rename the folder on my F drive and then try to reinstall, it creates a whole new folder on the F drive. It never bothers to look at the C drive and install there.
  5. I want to install a fresh, virgin copy of DCS open beta. I download the installer file, run it, it updates itself first. Then it goes through a few EULA screens. Then it creates a desktop shortcut to an installation that already exists on my SSD (my H drive, not my C drive which is smaller but also has a DCS open beta installation). What? So I renamed the folder on my H drive SSD to DCS.original. I rerun the installer. Go through the same motions, Now it's downloading 142 gig of the base install to the same SSD (H drive). Why does it choose the largest SSD and not give me a choice?
  6. yes. i even tried binding hotas buttons to the different functions. scan zones dont move. time to repair dcs
  7. yep, not working for me. can only move TDC
  8. Thank you , I get that. But how do I point the funnel up and down? I cannot get the numbers to change without moving the TDC. Using scan zone controls seems to not work.
  9. here are two more pics: cursor at top alts 16/6 cursor at bottom alts 25/20 shouldnt be the other way round? all i did was move the tdc also moving the scan zone left/right/up/down does nothing. should it?
  10. where do you see the elevation? I try using scan zone up/down but see no indications.
  11. Here I am in an F-15C trailing two MiG29 drones, each about 8 nm ahead. The radar shows nothing. The TDC cursor is ar the top of the display. Here I move the TDC cursor to the bottom of the display. Shouldnt the numbers at the left hand margin be closer together indicating a narrower vertical slice of the sky? Why am I not finding the targets on the scope?
  12. SHUCKS..I wanted to export the RWR of the F-15C
  13. Doesnt the project ‘dcs moving map’ already do this? https://movingmap.bergison.com I only wish it would use the same map as in the game
  14. adding these lines to your default.lua (located in the DCS game folder under Mods\aircraft\A-10C_2\Input\A-10C_2\joystick) -- Lights {action = 3009, cockpit_device_id = 49, name = _('Form Lights Axis')}, {action = 3001, cockpit_device_id = 49, name = _('Engine Instruments Lights Axis')}, {action = 3002, cockpit_device_id = 49, name = _('Flight Instruments Lights Axis')}, {action = 3003, cockpit_device_id = 49, name = _('Auxiliary Instruments Lights Axis')}, {action = 3005, cockpit_device_id = 49, name = _('Flood Light Axis')}, {action = 3006, cockpit_device_id = 49, name = _('Console Light Axis')}, {action = 3009, cockpit_device_id = 4, name = _('CMSP Light Axis')}, {action = 3006, cockpit_device_id = 5, name = _('CMSC Light Axis')}, {action = 3007, cockpit_device_id = 5, name = _('CMSC Vol')}, will allow you to assign analog axes to your A10 lights (if you have added a button box to give you more axes) However, I cannot figure out how to add an axis to dim the HUD. The device ID of the HUD is 19 and the buttons to control its intensity on the UFC are 28 and 29. I tried adding {action = 3028, cockpit_device_id = 19, name = _('HUD Int')}, or {action = 3029, cockpit_device_id = 19, name = _('HUD Int')}, to the default.lua but no success. Also, I cannot figure out how to dim that blazingly bright clock.
  15. @Bailey Thank you. BTW, I am trying to find which argument DCS uses for the ARC210 freq. How do I find that so I can put it into the A10c_2 lua in the DCSExportScripts folder? As per the DCSExport Scripts Wiki, I added the following codein the A10c_2 lua to the function: function ExportScript.ProcessDACConfigLowImportance(mainPanelDevice) --log ExportScript.Tools.WriteToLog('list_cockpit_params(): '..ExportScript.Tools.dump(list_cockpit_params())) ExportScript.Tools.WriteToLog('CMSP: '..ExportScript.Tools.dump(list_indication(7))) local ltmp1 = 0 for ltmp2 = 0, 13, 1 do ltmp1 = list_indication(ltmp2) ExportScript.Tools.WriteToLog(ltmp2..': '..ExportScript.Tools.dump(ltmp1)) --ExportScript.Tools.WriteToLog(ltmp2..' (metatable): '..ExportScript.Tools.dump(getmetatable(ltmp1))) end I then loaded up an A-10C_2 on the runway, played with the radio, quit. but the Export.log in the saved games folder was no different than usual.
  16. Sometimes the streamdeck plugin goes stupid. I have gotten the same symptoms. I have had to alt tab out of the game, quit streamdeck and restart it . Then it works
  17. @bones1014This is for the A10C-2 with the ARC - 210 radio. The description in the dialog from the plug in just says ARC-210. The extra description from the clickable data extract that identifies the button function is not shown for me in the stream deck plugin dialog.How do you identify what each button does. What popup are you talking about? As for which aircraft, I thought it is obvious that I am speaking about the ARC-210 radio.The freq selector doesn't work. For the 100 MHz, I can only get it to go up. For the 10 MHz it goes from one extreme to the other with one click even tho the increment is set to 0.1. Is this your experience?
  18. I cannot get the freq selectors to work. For example, a rotary assigned ID 3023, Device 55 with increment 0.1 and range 0.1 to 0.9 flips the knob all the way. Is there something else I should be using?
  19. Is there a way to improve the description that the plug in gets for the functions of the buttons of the arc210 radio? Presently it looks like this: I found this with clickable data extract: VHF_AM_RADIO(55) 3001 VHFUHF18P BTN 564 1 0 1 ARC-210 Time of day send No function VHF_AM_RADIO(55) 3001 VHFUHF18P BTN 564 1 0 1 ARC-210 Time of day send No function VHF_AM_RADIO(55) 3002 VHFUHF17P BTN 565 1 0 1 ARC-210 Time of day receive No function VHF_AM_RADIO(55) 3002 VHFUHF17P BTN 565 1 0 1 ARC-210 Time of day receive No function VHF_AM_RADIO(55) 3003 VHFUHF16P BTN 566 1 0 1 ARC-210 Global positioning system No function VHF_AM_RADIO(55) 3003 VHFUHF16P BTN 566 1 0 1 ARC-210 Global positioning system No function VHF_AM_RADIO(55) 3004 VHFUHF15P BTN 567 1 0 1 ARC-210 Select receiver - transmitter No function VHF_AM_RADIO(55) 3004 VHFUHF15P BTN 567 1 0 1 ARC-210 Select receiver - transmitter No function VHF_AM_RADIO(55) 3005 VHFUHF19P BTN 563 1 0 1 ARC-210 upper FSK VHF_AM_RADIO(55) 3005 VHFUHF19P BTN 563 1 0 1 ARC-210 upper FSK VHF_AM_RADIO(55) 3006 VHFUHF20P BTN 562 1 0 1 ARC-210 middle FSK VHF_AM_RADIO(55) 3006 VHFUHF20P BTN 562 1 0 1 ARC-210 middle FSK VHF_AM_RADIO(55) 3007 VHFUHF21P BTN 561 1 0 1 ARC-210 lower FSK VHF_AM_RADIO(55) 3007 VHFUHF21P BTN 561 1 0 1 ARC-210 lower FSK VHF_AM_RADIO(55) 3008 VHFUHF22P BTN 560 1 0 1 ARC-210 brightness increase VHF_AM_RADIO(55) 3008 VHFUHF22P BTN 560 1 0 1 ARC-210 brightness increase VHF_AM_RADIO(55) 3009 VHFUHF23P BTN 559 1 0 1 ARC-210 brightness decrease VHF_AM_RADIO(55) 3009 VHFUHF23P BTN 559 1 0 1 ARC-210 brightness decrease VHF_AM_RADIO(55) 3010 VHFUHF13P BTN 569 1 0 1 ARC-210 Menu pages VHF_AM_RADIO(55) 3010 VHFUHF13P BTN 569 1 0 1 ARC-210 Menu pages VHF_AM_RADIO(55) 3011 VHFUHF12P BTN 570 1 0 1 ARC-210 Amplitude modulation / frequency modulation select VHF_AM_RADIO(55) 3011 VHFUHF12P BTN 570 1 0 1 ARC-210 Amplitude modulation / frequency modulation select VHF_AM_RADIO(55) 3012 VHFUHF11P BTN 571 1 0 1 ARC-210 Transmit / receive function toggle VHF_AM_RADIO(55) 3012 VHFUHF11P BTN 571 1 0 1 ARC-210 Transmit / receive function toggle VHF_AM_RADIO(55) 3013 VHFUHF10P BTN 572 1 0 1 ARC-210 Offset frequency VHF_AM_RADIO(55) 3013 VHFUHF10P BTN 572 1 0 1 ARC-210 Offset frequency VHF_AM_RADIO(55) 3014 VHFUHF9P BTN 573 1 0 1 ARC-210 Enter No function VHF_AM_RADIO(55) 3014 VHFUHF9P BTN 573 1 0 1 ARC-210 Enter No function VHF_AM_RADIO(55) 3015 VHFUHF14P TUMB 568 1 0 1 ARC-210 Squelch on/off VHF_AM_RADIO(55) 3015 VHFUHF14P TUMB 568 1 0 1 ARC-210 Squelch on/off VHF_AM_RADIO(55) 3017 VHFUHF8P TUMB 558 -0.1 0 0.3 ARC-210 25 KHz Selector VHF_AM_RADIO(55) 3017 VHFUHF8P TUMB 558 0.1 0 0.3 ARC-210 25 KHz Selector VHF_AM_RADIO(55) 3019 VHFUHF7P TUMB 557 -0.1 0 0.9 ARC-210 100 KHz Selector VHF_AM_RADIO(55) 3019 VHFUHF7P TUMB 557 0.1 0 0.9 ARC-210 100 KHz Selector VHF_AM_RADIO(55) 3021 VHFUHF6P TUMB 556 -0.1 0 0.9 ARC-210 1 MHz Selector VHF_AM_RADIO(55) 3021 VHFUHF6P TUMB 556 0.1 0 0.9 ARC-210 1 MHz Selector VHF_AM_RADIO(55) 3023 VHFUHF5P TUMB 555 -0.1 0 0.9 ARC-210 10 MHz Selector VHF_AM_RADIO(55) 3023 VHFUHF5P TUMB 555 0.1 0 0.9 ARC-210 10 MHz Selector VHF_AM_RADIO(55) 3025 VHFUHF4P TUMB 554 -0.1 0 0.3 ARC-210 100 MHz Selector VHF_AM_RADIO(55) 3025 VHFUHF4P TUMB 554 0.1 0 0.3 ARC-210 100 MHz Selector VHF_AM_RADIO(55) 3027 VHFUHF2P LEV 552 1 0 1 ARC-210 channel select knob VHF_AM_RADIO(55) 3043 VHFUHF1P TUMB 551 -0.1 0 0.6 ARC-210 master switch VHF_AM_RADIO(55) 3043 VHFUHF1P TUMB 551 0.1 0 0.6 ARC-210 master switch VHF_AM_RADIO(55) 3044 VHFUHF3P TUMB 553 -0.1 0 0.6 ARC-210 secondary switch VHF_AM_RADIO(55) 3044 VHFUHF3P TUMB 553 0.1 0 0.6 ARC-210 secondary switch
  20. I read this: https://wiki.hoggitworld.com/view/DCS_export and the example file here: https://wiki.hoggitworld.com/view/DCS_Export_Script There is a lot of data one can get about the airframe. However, I would like to know the joystick position and where DCS thinks the centerpoint is. For example in the F18C,MiG29,A10-A(and all Flaming Cliffs jets), the A10-C, and A10C_2, the joystick centers forward of the midpoint of the controls indicator. Below is a pic of the A10-A This results in limited forward excursion. Whereas in other jets- the Viggen, the cross of the axes allows equal excursion inputs. The F5e is a little weird-the crossed lines are displaced upward but the stick center is in the middle.
  21. For the flaming cliffs modules, I was wondering where the location of the indicators is specified? I would like to move them FC3 jets do not have an obvious lua file for them.
  22. Calibrated the stick but after takeoff, neutral flight requires the stick to be pushed halfway forward. In the picture below, you can see that windows says the stick is forward but the in game control indicators (in orange) the stick is centered to the crosshairs. But the crosshairs (neutral position?) are not centered in the box.
  23. @=475FG= Dawger thank you. subbed to your videos (though it would be nice to see a playlist labeled 'instructional'. but your content is engaging) that word, predict. now all the crazy moves in BFM and ACM start to make sense. So many tac views are analyzed but that word is never mentioned. Your lead turn is smooth. And achieves what I want to do with a pirouette that I can never make 'violent enough'. Of course, who would think of telegraphing his intentions to a bogey coming straight at you. but that cost is well worth the result. Unfortunately, the bandit will respond in kind and as you turn left, so will he. And the one circle will be born again. And when I see that, the gentle turn you scribed in your tacview then needs to become tighter.
×
×
  • Create New...