-
Posts
888 -
Joined
-
Last visited
-
Days Won
7
Content Type
Profiles
Forums
Events
Everything posted by Fish
-
Sorry, only seeing this post now. If u still don't have it sorted, post the profile and i'll try it out. Will tell if its profile or something else Cheers
-
startup procedure problems with TVV and takeoff
Fish replied to foxfour's topic in DCS: A-10C Warthog
FPM comes on AFTER ins alignment is complete (you hit the Nav option on the CDU page, when the INS ALIGN is flashing), and then activate the EGI switch on the nav panel. But you probably know that already .:smilewink: -
QUOTE=Supersheep;1362860]I stopped utilizing speedbrakes. They amplify any trouble you have keeping your speed correct......,Super- When to use SB in refuelling 1. Good on a fast approach to prevent overshoot, 2. Apply a little constant speed brake, if you want to move the 'sweet' throttle position a little forward (i use it to get away from the idle detent with slow tanker speeds, and clean jet.) Also here's an image which might be of help. Can't image it would be much different for an A10c
-
Saving Logbook Entries in reinstall of V. 111
Fish replied to Colonel T's topic in DCS: A-10C Warthog
And remember you will have to re-do your multiplayer callsin, cause its not stored in that file. Otherwise it takes your windows username. -
(not a stupid question) Well its not a 'hotas' function. But I've mapped the 3 radio buttons to a 4 way switch on my cougar, and the spare button, i've programmed for the ESC key. UP/LEFT/DOWN are radios, RIGHT is 'ESC'. I use Foxy for the Cougar. Don't know how its done for the Warthog.
-
Don't know if difficulty was tweaked as its been a while since i crashed the tanker, maybe a tester can comment. I do think it was a little ridiculous, that if you crashed into the boom, more often than not, you would bring down the tanker !!
-
You can shift the throttle position forward by applying some airbrakes. This might give you a more accurate part of your input device. Found if i was light and tanker slow, the throttle was almost at detent.
-
Thats why i got my ESC key mapped to it. Cancels radio commands. :hehe:
-
And use VAC for everything else.
-
Worked for me., Cheers Monk I just backed op the original file, and removed the offending lines from the code.
-
:clap::clap: Well done. Rest is downhill believe me. Up to the first hook up you really don't know what's wrong. Now you do. Said b4, if you disconnect' don't panic!!, get the ready light back on, and ease the controls to get back in place again.. And on the mission freq. Open it in the editor, click on the tanker group on the map, then on the AIRPLANE GROUP, panel, click the 'ADVANCED WAYPOINT ACTIONS' at the bottom, and you should see the 'SET FREQUENCY' action, which displays the KC frequency for the mission. And don't forget to note the radio being used.
-
nice 1 Mule. Think a touch screen is on my santa list !!
-
I'm sure there's emergency protocols based on risk assessment and determined by the seriousness of the damage, and/or systems failure.
-
Only talking about emergency procedures. Don't panic !!. Normally should be no issue with fuel and ordinance, in in fact i prefer the challenge of a loaded hog for me landings. Recent landing with one engine made me think, cause of the yaw induced by throttling up close to the threshold. Would have been better off with a lighter aircraft. If you have progressive systems failure due to excessive damage, patterns to bleed off fuel with a single engine for example is not, i expect, really a good idea.
-
Weight reduction is not the only reason to emerg land low on fuel. In emerg land, risk of a fireball from it is real and constant. (but unlikely the amount of fuel in the tanks and risk of explosion is modelled in dcs anyhow)
-
Can't see anything in the documentation. Perhaps it can't be done in real live also. Be interested to know why. Anyone who knows better like to comment ? Cheers.
-
After patches we have to do everything different
Fish replied to vortex360's topic in DCS: A-10C Warthog
Forget the manual. Loads of tutorials, guides, and helpful chat around here, solves most any problem i've had with any patch. :music_whistling: -
Sweet. No 'anomalies' so far :smilewink:
-
You just need to see the 'ready' light on the canopy rail. If the connection is broken, it gets changed to 'disconnected' automatically. Only then do you need to do the reset. This might be frequent as you connect/disconnect during your first attempts. With 1.1.10, the tanker may also terminate pre contact, with 'return pre contact'. You then have to get close and request pre-contact again. OFF TOPIC. This is where VAC shines, in AAR, cause you can do all the contact stuff with the Hotas mic switch and your voice, and so mantain concentration on the contact.
-
Ha, Its one of those things which is never really finished. However you can get the latest version in my first post. (at the end).
-
Agree, initial contact is text only. Pre-contact works fine but you need to be close to tanker, with pre-contact ligth on canopy rail, displaying 'ready'. You then get audible - 'ready pre-contact', lights go on and boom extends. Nice changes, boom operator gives you a warning if your closure rate is high and you are close. Looks like if over 3knots. Also after a timer, off the boom, the KC will terminate pre-contact automatically, and you will have to request it again. This will be good in MP, and prevent any user 'locking' out the kc contact. I expect it was addressing those items which has left something broken in mp. Other than that it works good for me SP.
-
Pls check the dates of both posts!! :music_whistling: Cheers, will try it when i return from vacation.
-
From the silence i must infer that it can't be done !! hmm :( There's little point in having this functionality if it must be reset each time a new patch comes out.
-
Not sure what you mean by more sensitive? I have had to adjust roll and yaw inputs to get same feel. (reduced / removed the curve in DCS axix profile). So for me it appeared to be 'less sensitive' to my inputs (i.e.) response was less for same inputs. BTW, it was a vanilla install of 1.1.1.0, and i copied over all my input files from 1.0.9
-
Yes, I am experiencing the same problem. Hope there's a fix/workaround soon.