Jump to content

davedontmind

Members
  • Posts

    41
  • Joined

  • Last visited

Everything posted by davedontmind

  1. Can you be more specific? Which LUA file? And how do I use the toggle switches in Black Shark?
  2. Aww. I was hoping to avoid Target, because I don't need or want it for the A10 module, so using it for Black Shark would mean having to exit DCS World, start up Target with the right profile, then restart DCS World when I want to switch aircraft. On the other hand, it *is* rather flexible! Thanks very much for the script, I might just give it a go!
  3. I'm trying to configure some of the Ka-50 commands on my TM Warthog HOTAS, but I'm not sure how to do it correctly on some of the toggle buttons/switches. For example, I'd like to use the "speedbrake forward" switch on the side of the throttle unit for autopilot on/off, but physically the switch is flipped to the on position and remains there until I move it to the off position, which means in game I have to move the switch forward and back to centre to turn the autopilot on, then repeat that to turn it off; what I'd prefer is to move it to the "on" (forward) position to turn the autopilot on, and return to the "off" (centre) position to turn the autopilot off. Is this possible and, if so, how?
  4. Same problem here - I get a comms menu when I'm on the ground, but as soon as I take off, the \ key does nothing.
  5. I love it. The joystick in particular is solidly built and feels great to fly with. For me the controls are now much more intuitive - on my old x52 I was constantly having to remember which button combination I'd put speedbrakes, or china hat on, etc, but with the Warthog it's easy for me to remember which buttons do what (and a lot of that is because there's no need for me to give multiple functions to buttons). On the other hand, if you want to stray from the default buttons (which just work with DCS-A10C out of the box) and get all complicated with macros etc (which you need if you want to map things like snapviews to your stick, as far as I can tell) then have to deal with the TARGET software and configuration, which is very powerful, but has been a little time-consuming for me to learn and configure (and I've still not got it quite right). I have no regrets, and am very happy with my purchase. Now I just need to get the hang of all the weapons systems in game!
  6. That's where I got mine from last week. Ordered on Saturday and it turned up on Tuesday - not bad service at all.
  7. Thanks - somehow I missed this, despite reading through the manual a couple of times. I'm off to get new glasses...
  8. Is there any way in the TARGET scripting language to do something when a controller button is released? What I really would like to do is have a button press send one keystroke, and a button release send a different one so that, for example, on the Warthog throttle unit I could use the APU Start switch to send one keystroke when I flip it up, and a different one when I flip it down. I couldn't see how to do it. Is this possible? Also, is there another forum which might get a better response to TARGET/Warthog questions? I couldn't see forums on the Thrustmaster site.
  9. You just need the serial number from Steam; download the A10 module for DCS World from http://www.digitalcombatsimulator.com/ and use the Steam serial number with that.
  10. It's my first serious sim too - 6 months in and I still don't have a clue what I'm doing half the time, but I love every minute of it. I've just splashed out on a TM Warthog (it should arrive in the next day or two) which is my early Christmas present to myself. While you're investing in the game, I highly recommend getting a printed copy of the manual - I got mine from here - it's much better than having to refer to a PDF on screen.
  11. I use the pedals from my Driving Force GT steering wheel, which work well enough for me. It saved me splashing out on even more hardware. So if you already have a steering wheel & pedals, it's a good way to save a bit of cash.
  12. This is excellent, thank you! I've tweaked my version slightly to improve the experience. In MissionEditor.lua I set the screen size to 1920x1040 windowed (the height is 1080 minus the height of the win7 task bar) as per PeterP's post, then I use AutoHotkey with the script below, which will detect the DCS World window, remove the Windows title & border, and move it to fill my middle monitor entirely (except the win7 task bar), giving the appearance of almost full-screen. You'll need to tweak the values on line ~28 of the script to fit your monitor configuration. See the comments in the script. If you set your win7 task bar to autohide you could make the DCS window fill the middle screen entirely (just change the 1040 in the AHK script and in MissionEditor.lua to 1080). Caveat: I'm no AHK expert (the script is adapted from one I found for Skyrim) so use at your own risk, but it's working fine for me. AutoHotKey script: #SingleInstance Force #Persistent ; Check every 1 second SetTimer DCS, 1000 Return DCS: ; Find the DCS world window WinGet IDs, List, ahk_class DXGUI Window Loop %IDs% { ID := IDs%A_Index% If ID not in %Old_IDs% { WinActivate ahk_id %ID% ; Remove window border & title WinSet, Style, -0xC40000, A ; Reposition the window ; 2064 = X position for DCS Window, = x pos of my middle monitor when in Eyefinity mode (1920 + bezel compensation border) ; 0 = Y position for DCS window ; 1920/1040 = dimensions for DCS window - should match values in MissionEditor.lua, lines 244/245 WinMove, A, , 2064, 0, 1920, 1040 WinActivate, A } New_IDs .= ID "," } StringTrimRight Old_IDs, New_IDs, 1 New_IDs = Return
  13. Is there a way to customize the main menu, map screen, or mission editor to restrict them to the middle screen only, on a triple head setup? They're all rather clunky when spread over 3 screens.
  14. Along these lines, the radio menu & messages appear on the far right & left screens respectively when in Eyefinity mode. I worked out a fix to move them both to my central monitor (this is for DCS World): Load up DCS World\Scripts\UI\RadioCommandDialogPanel\CommandDialogsPanel.lua into Notepad (or your favourite text editor). NB: Make a backup copy of this file first, in case you screw it up! Change line 166 from this: local window = Window.new(0, 0, screenWidth, height, "CommandDialogsPanel.Window") to this: screenWidth = 1920; -- width of your central screen. If you find the radio menu is still too far right after this fix, reduce this value local pos = 1920 + 60; -- width of your left screen, plus any bezel compensation margin. If the messages are too far left/right then decrease/increase this local window = Window.new(pos, 0, screenWidth, height, "CommandDialogsPanel.Window") How it works: As far as I understand the code, an invisible window is created which holds all the radio info. The messages you receive appear on the left side of this window, and the radio menu appears at the right side of this window. Normally it covers the whole 3 screens, from (0,0) to (screenWidth, height), but my fix changes the dimensions of that window so that its left edge starts at the left side of your central monitor, and its width is as wide as your central monitor (thus the right edge is at the right edge of the central monitor), so now all the radio text appears on the central screen. Hope that helps someone.
  15. I'm pretty new to BS2, and am currently trying to figure out how to fly this thing. I've got the basics figured out (especially the crashing - I'm almost an expert at that!), but I've just been trying to figure out the trim & auto hover. After watching a video on the topic of trim, I was pretty confident I'd got it all figured out, but my experience isn't matching my expectations. When I try a test flight, I apply a little collective until I start to rise, and notice the nose pulls up, so I add some forward on the cyclic to balance it, apply some more collective until I'm a reasonable hight above the airfield, then reduce collective until I'm at a steady altitude. At this point I'm still pushing forward on the cyclic to keep it level. As I understood it, pressing & releasing the trim button tells the helo that the position I have my stick in at release time is the new neutral position, so if I hit the trim at this point I'd expect that when I release my joystick back to center, the helo would behave as if I've still got it pushed forward a little, so it would be balanced still. But what seems to happen is that when I release the stick, the nose pulls up to about 8 degrees on the HUD pitch ladder and we start moving backwards. Similarly, if I hit the auto hover button, the nose comes up and we start moving backwards. And on a possibly related issue, I notice that when I've lifted off the runway, if I move the stick so that the pitch is 0 on the HUD pitch ladder, it looks like the nose is somewhat down, and the helo accelerates forward. What am I doing/understanding wrong?
  16. You could perhaps use the 3rd-party program AutoHotKey, which allows you to change the keystrokes sent to a game or application based on a user-supplied configuration / script. I've not tried it with A10C, so I don't know if it works, but I've used it for this sort of task successfully with other games.
×
×
  • Create New...