-
Posts
1632 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Bunny Clark
-
No, the monitor config file you posted only includes the two pilot MFDs, so you should not have any issues with that.
-
@16th Widowmakr Have you selected the correct monitor config file as the active one in game settings?
-
Some flight controllers do have default button maps built-in to DCS for some modules. For example, if you buy a Thrustmaster Warthog stick and throttle and the A-10C module, it'll work for you right away. But there are a lot of different controller options, especially if you start mixing and matching sticks, throttles, and button boxes. Making default bindings for all of them would be a huge amount of work. Plus, there isn't always a single correct answer to how a controller should be button mapped. In the case of the Warthog and the A-10C module it's pretty easy - the controller is the same as the one in the aircraft, so it's set up for all the controller buttons to do what they do in real life. But use that same Warthog to fly a Hornet, and how do you map it? There's a lot of personal preference that goes into deciding how you would like to use the flight stick you have to control a specific aircraft. The problem is even more pronounced with something like the X56, which has no real-world analog and will never be a 1:1 map to any aircraft. Where one player likes to map the Weapon Select Switch in the Hornet may be a completely different place than where another player does. Personally, I take quite a bit of enjoyment from planning out what all the different buttons on my controllers are going to do for any aircraft. It's part of my learning process for a new aircraft, as it forces me to understand what the HOTAS controls for the real aircraft do. It's why I've spent a fair amount of time drawing up templates for different flight controllers that I can use to plan out how I want to map a controller, and use as a reference for when I need to remember them after a long time away from a module. If you'd like, you can find PDF templates for the X56 in a link in my signature.
-
Possible Solution to display all Apache MFDs ?
Bunny Clark replied to Hobel's topic in Multi-Display
LOL, yup, there is. I bound both to a single button and then forgot there were two functions. -
not planned Link 4A tactical data link functions
Bunny Clark replied to Northstar98's topic in Wish List
Did Link4 have any tactical functions in the Hornet anymore in the 2000s? My guess is that in the timeframe our Hornet is modeled, ACLS was the only thing Link4 was used for. But I really don't know. -
Why would you like to re-center the pod? If you're looking to get the pod onto a visually acquired target, you have two options: VVSLV (Velocity Vector SLaVe) - this is an option you can select with an MFD button or quickly access with a double-tap of the NWS Undesignate button. It will, as the name implies, slave the pod to your velocity vector on the HUD. This is a good way to "fly" the pod onto a target. With no active designation, a weapon in Auto bombing mode, and the HUD/HMD set as the Priority sensor, you should see an aiming pipper in both the HUD and HMD. Point this at a target, hit the TDC Designate button, and you will create a ground target designating wherever you were looking, and the pod will jump to that point. This is a great way to quickly target anything you can see in any direction.
-
Possible Solution to display all Apache MFDs ?
Bunny Clark replied to Hobel's topic in Multi-Display
It looks like the AV-8B keypresses fire the commands "iCommand_UV26_PowerCover" and "iCommand_UV26_BITCover" which look like they may be Ka-50 commands? I don't own the Ka-50, so I'm not entirely sure about that. But it would indicate that Razbam has done some hijacking of other internal DCS World commands. I don't know a lot about computer programming, I'm just good at poking things, but everything I've seen looks like the AV-8B MFD toggling happens on the backend and not in any way that we can edit. Even if we could find a way to trigger it in the Apache, we don't want to hide all exports, we want to selectively hide some and not others. That isn't something that's done in the Harrier. -
Which lua? The monitor config goes in \Saved Games\DCS(openbeta)\Config\MonitorSetup\ You then need to select it in Opions. The edited display export luas in my zip file go in your DCS install directory in the \Mods\aircraft\ folder.
-
Cougar Throttle TUSBA_R2 and Warthog stick set up.
Bunny Clark replied to MattM1121's topic in Controller Questions and Bugs
If I'm understanding your question correctly, you're just looking to add shifted buttons to command existing DCS functions? That's something you can do pretty easily within DCS. In controls setup select the Modifiers button on the bottom left. Select Add to add a new one. Select the device you want the Modifier button to be on, then press the button to assign it. The only catch here is that you can't also bind a Modifier to a function, it needs to be either a button or a modifier. Once you've assigned a button as a modifier, simply select any available control function and bind it like normal, hitting the modifier and the button you want to shift.- 4 replies
-
- cougar throttle
- tusba
-
(and 1 more)
Tagged with:
-
I think the confusion comes from the concept of track files in RWS. In the Hornet, the radar is building track files while in RWS, and that information can be viewed from RWS mode (assuming LTWS is enabled). The Viper does not build track files in RWS at all, you'll only see raw hits (white bricks) from radar contacts. RWS will display Link16 surveillance tracks on the radar page, which you may be getting confused by. If you want to see track files, you'll need to switch to TWS. Not being able to lock / bug a search brick is another thing. I'm not sure what's going on there. I'd imagine that once the radar can see the contact and display it as a brick, it should be able to lock on and elevate it to a bugged target. I'm not sure why the radar will show that something is there, but refuse to track it for a while.
-
I've been working on one for about a year now. The Viper has been out for a while, but it was missing some capabilities that really limited the variety of missions that it could undertake and stories that could be told with it. In my case I was also waiting on the Syria map to be released before I could start working on it.
-
Nope, it has no way of detecting an incoming IR missile. I recommend keeping your manual program or the Slap Switch set to dispense flares.
-
The basic workflow is to select VIS or DTOS as the delivery mode, push TMS Up Long until the TD Box is slaved to the HMD cross, then look at the target and press TMS Up to lock it in place. You can then slew it around with the Cursor. All other sensors and weapons will slave to that point, so select another sensor as SOI and refine your target from there. DTOS stands for "Dive / Toss" and was originally conceived as a automated delivery visual bombing mode using the HUD as the targeting sensor. Fly or slew the TD box over the target, TMS up to ground stabilize, slew to refine. Then either fly the ASL in a dive delivery, or pull up on cue to toss the bomb. Because it uses the computer to release the bomb, it's generally considered to be more accurate than CCIP. The A-7 had a very similar bombing mode, and the Hornet's Auto bomb mode is pretty close too. In the Viper, this mode gained new functionality as an easy way to visually designate a target using the HUD or HMD and get the TGP on it.
-
Nope. Some of the export versions of the F-16 have a built-in jammer, but none of the USAF Vipers do.
-
If you enter MRM from Nav, you will return to Nav when canceling MRM. If you were in A/G, you'll return to A/G.
-
MRM Override Mode sets up the MFDs for BVR combat (which can be customized, like any mode) and will automatically select the longest range missile currently on the jet. Deselecting it will return you to the previous mode you were in with the previous weapon selected, unlike A/A Master Mode, which will always return you to Nav.
-
Radar Elevation axis functionality
Bunny Clark replied to Zergburger's topic in Controller Questions and Bugs
Yah, that could be confusing for some people. I think making it jump to the axis value would be reasonable compromise. For now I just have my axis set to a very low saturation with a wide dead zone, which makes it work mostly like a pair or variable speed buttons.- 12 replies
-
- hotas-controls
- bindings
-
(and 2 more)
Tagged with:
-
This is certainly true in commercial aviation (and I suppose technically true for GA as well, not that I've ever seen anything remotely close to 18,000 in my Cessna). But it's my understanding that military aircraft, or at least fighters, do not use a Transition Altitude and always keep their altimeters set to local QNH.
-
reported earlier TGP or Maverick won't follow GMT target lock
Bunny Clark replied to RPY Variable's topic in Bugs and Problems
Following GMT targets is I think a WIP thing that should be added eventually. Getting stuck in Freeze sounds like a bug. Trying to track and bomb a moving target sounds like a mix of WIP stuff, realistic limitations, and tactics. Following a moving target you should be in POINT track, if it's in an inertial track (P-INR) it does not have a valid visual contrast lock on the target, you should maneuver for better visibility. Point tracks will absolutely be broken by trees or other objects passing in front of the target, that's entirely realistic. They'll also break if the TGP looses sight of the target due to masking for any amount of time. Point is done by image analysis, it needs an uninterrupted visual of the target at all times to work. If you're getting tagged by a ZSU making your bomb runs, you're too low. Being higher will give you better visibility, and reduce the LOS rate of the moving target, making it easier for the TGP to track. It makes bombing a bit more difficult because of the higher bomb TOF, I have best luck making my runs perpendicular to target motion and manually leading the ASL. Do not bomb in the same direction your target is moving, as that will extend the bomb fall range to impact, potentially outside of max range. I increase my lasing time, usually to 15 or 20 seconds depending on target speed. If you need to be low because of cloud cover, an LGB probably isn't the best weapon to take out that ZSU. A Maverick would be better. -
Radar Elevation axis functionality
Bunny Clark replied to Zergburger's topic in Controller Questions and Bugs
Oh certainly not, it first came up years ago. But nothing has ever happened ...- 12 replies
-
- hotas-controls
- bindings
-
(and 2 more)
Tagged with:
-
requested How to Set laser code for GBU on hot aircraft
Bunny Clark replied to RTS354's topic in DCS Core Wish List
Huh? There is no inconsistency in reality. It is impossible to set the code on a Paveway II seeker head from the aircraft, regardless of who made the aircraft. All aircraft that align a Maverick seeker head to a targeting pod need to boresight the Maverick seeker in reality. ED has just implemented these restrictions differently in different modules. Presumably, this will get rectified at some point in the future. Boresighting should come to the Hornet and Hog. And hopefully all the disparate methods of setting LGB laser codes get replaced with a unified pre-light planning / datacartidge system. -
requested How to Set laser code for GBU on hot aircraft
Bunny Clark replied to RTS354's topic in DCS Core Wish List
Agreed. So long as someone can approach the bomb with a screwdriver, they can change the code. -
Yup, me too. Unfortunately ED hasn't even acknowledged the issue, so I have no idea if or when a fix will arrive. For now I'm just flying the Apache on Open Beta and everything else on Stable.