Captain Orso

YISSS the APKWSeseses are my second favorite anti-armor weapon. T-72 and below are nearly 100% certain kill with 4 hits, T-80 with 5 to 6 hits, and you CAN kill a T-90 from a rear aspect with about 6 hits. Setup two firing profiles, RIP PRS, one firing 4 and one 6 rockets and off you go. You have to use this quick-fire method, because most tanks will start to move as soon as one rocket his, and the TGP lags just enough behind the movement for subsequent rockets to miss if they don't hit quick enough.

It's mostly a request for the manual to be updated, which is in a sense a bug, albeit not in the software, but there is no section on the manual, so...

How would the system know whether you were trying to enter 11° 12.345' or 111° 23.45' if all you enter is 1112345?

On page 467 it says: 1) Entering the elevation first is senseless, because when you subsequently enter either latitude or longitude, elevation will be nulled out. Once latitude and longitude are entered, elevation can be entered and will remain as entered. 2) There is no mention of entering N, S, E, W at the beginning of latitude or longitude strings. This is optional and the setting of the previous entry will be retained, but it is also the only way to change the setting from for example N to S. 3) Not sure if this is a bug in the SW or the manual, but to enter longitude, you must use a leading 0 or 1 for it to be valid; otherwise it will not be accepted. 4) While following the above, you can truncate latitude and longitude entry by omitting the entry of trailing zeros behind the decimal point. However if you do this, it will display blank behind the least significant digit entered. In normal programs I would say this is an error, and truncated missing zeros should be filled with '0' digits. Maybe Fairchild was lazy and actually did it this way, IDK, but it seems odd to me.

And what if you are running in on a column or grouping of armor and want to fire more than one Maverick per pass? I can say for myself, before I start fumbling around with blocking one TER over another (god forbid you might not be 100% certain from which TER your will fire in the heat of the battle) I'll fly an unbalanced airframe, if it means I get the extra kill on that attack.

I have the manual. It's installed with the module: 'c:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C_2\Doc\DCS A-10C II Flight Manual EN.pdf'. Which page is your quote from? I cannot find it. But even when I download the manual from the ED site (your link doesn't point correctly) your quote cannot be found.

Could you please quote where that is documented.

I will have to try that, but if when firing it only steps through one pylon before going to the next, I don't know why I should expect stepping to the next missile with China Hat Aft Short should step to the next pylon. BTW I've now noted the same issue with Mk-82AIR's. Mk-82AIR*3 on stations 5 & 7. Create profile with RIP PRS, 4 weapons, 75 feet apart, CCIP, and it drops 3 form station 5 and 1 from station 7(!!) :mad:

They ARE only one type of missile. I'm only using AGM-65D's on LAU-88's at the moment. During flight, I go into DSMS and select both stations, and assumed that since bombs and rockets switch from left to right, missiles must be a given. I'll probably find out next that with AGM-65L's on 3, 4, 8, and 9 they are fired in numerical order.

Thanks for the answer Ramsay. Yeah, that seems to be the issue. So many wonderful solutions in the A-10, that the few sucky things seem all that more sucky.

Thanks for the reply Emmy. I'm only flying the A-10CII for a couple of weeks now, so I don't know a whole lot of the ins-n-outs. But with 2x 3*AGM-65D's hanging on a LAU-88 each on 3 and 9, when I fire the first missile and the smoke has cleared and the missile is still on the way, the second missile is still locked to the target of the first missile. In the Harrier and Hornet I only ever try to "nudge" to the next target through the TGP, but in the A.-10C I've been trying it through the missile itself. What I've noticed is that as soon as I nudge off target the missiles IR camera is no longer ground stabilized. And when I press 'TMS aft short' I'm only ground stabilized until I try to nudge again, which is not what ground stabilized is supposed to be :mad:

Are you running the app with administrator privileges?

Thanks Foka So... - fire missile - switch to DSMS page - switch LAU pylons - return to MAV page - fire missile - ... I work in IT nearly all my life. This is called, IT on foot. I know it's not your fault Foka, but it's just stupid. Thanks Fairchild Republic :mad:

Thanks for all the answers :thumbup: Is this Real-World™ real? I mean, is this they way the real A-10C in reality works? Is there any way to get this to work logically - one missile left, one missile right, one missile left...

So, when you pull up the MAV screen on the left hand MFCD you are looking through the camera of the selected missile, the one you are about to fire, right? So when you fire that missile, it electrically disconnects from the LAU and the next missile to be fired is electronically attached to the MFCS an you see through that missiles camera in the left hand MFCD, right? Since if I fire a missile from the left hand LAU, the next one will be from the right hand LAU, ri... ummm.. correct? So why, if just fired a missile from the left hand LAU, and I an now looking through the camera of the next missile on the right hand LAU, why is the camera obscured with all the exhaust smoke from the just fired missile when it should actually be streaming from 10 yards to the side of where my active camera is now?

I'm still getting used to the new forum format, so I'm still in the 'all change is bad, this sucks' phase, but I'm giving it a try. What I miss -- and maybe it wasn't even in the old forum, can't say for sure -- is at the bottom of a thread, there are not options to return to the parent forum or switch to a different forum. The former is especially annoying, because one is forced to scroll all the way back up to the top to return to the parent forum, which is generally what I do when I've finished reading a thread.

Yes!, I was just searching if anyone else had already reported this, so I guess my timing was perfects :) This is really just totally annoying. Everytime I see this I start thinking, "is there something I don't know?", "do I have mice?", "... ghosts?", "... hermit crabs?"...

What I forgot to mention is, I'm flying in VR. So the keyboard is like going on a date with a catholic schoolgirl with her older brother, the football captain, as a chaperon ....... HANDS-OFF!! Don't even think it!! ... .. damn, them bruises...

First you have to understand the each payload profile has a task stored in it. If you add an A-10C II group and select task CAS, you will only see CAS payload profiles. If have a profile you want to be able to use in other tasks, copy the profile and save it under a different name. EG: -- You have a group with CAS task. It has a profile named 'Iron Hand 01' loaded, and you want to use the same loadout in a group with the Ground Attack task. - Create a group with task CAS and click on the profile 'Iron Hand 01'. The payload will appear at the top of the payload profiles page with the name 'Mission payload". - Chang the task to Ground Attack, or any task with which you wish to use this profile. The makeup of the payload stays at the top of the list with the name 'Mission payload'. - Select the 'Mission payload' and click [COPY] at the bottom of the window. - A popup will appear, enter the wished name and click [OK], for example 'Iron Hand 01 GA (it must be different than the original under CAS). If you just want to have similar payloads under the same task for the same aircraft type: - Add/Select an aircraft of the correct type and give it the correct task. - Create from scratch, or copy and rename a new profile - insure the profile is as required. - While the profile is selected for your aircraft, it will appear at the top of the payloads page under 'Mission payload'. - You can modify and then copy this and rename this profile as often as you wish, as long as the payload makeup and names are unique (you cannot have two payloads with exactly on 4*AGM-65K's but stored under two different names, nor can you have two different payloads for the same aircraft and task with the same name). I suggest adding a task identifier to the name for clarity EG 'Iron Hand 01-CAS' for CAS tasks, and 'Iron Hand 01-GA' for Ground Attack.

I'm assuming you are using SRS because you are flying with a squadron, or friends, or whatever, but that you will probably be using the SRS radio to actually talk with real people, and the in-game radio far less. Here's what I did. - Add a modifier. I have a TM Warthog HOTAS, so I'm using the stick's pinky paddle as a modifier named 'Paddle'. - I have changed the HOTAS setting for 'Mic Forward', 'Mic Aft', 'Mic Up', and 'Mic Down' to 'Paddle+Mic Forward', 'Paddle+Mic Aft', 'Paddle+Mic Up', and 'Paddle+Mic Down' so that all four 'Mic' switches are free. - In SRS assign the Mic switches as you wish for easy use. It's very easy to get used to using Paddle+Mic and just as easy to use just the Mic switches for talking.

But not down and up. Down and up describes how a keyboard key works. Down = pressed = asserted, up = released = unasserted. The toggle switches on the TM Warthog HOTAS Throttle are On-Off - APU START - Forward is On, aft is Off On-Off-On - Boat Switch - Has two electronic circuits. Forward closes one of the two circuits, while aft closes the other. In the center neither circuit is closed. On-Off-(On) - ENG OPER L & R - Same as the Boat Switch, except when the switch is in the forward position and released, it will spring back to the center position. (On)-Off-(On) - China Hat - The same as the Boat Switch, except that the switch falls back to center automatically from both directions. Directions in parentheses (On) are spring loaded and spring back to the center or other position when released. Combo controls need to be named for what they do. EG 'Undercarriage Down else Up' for a switch with aft = On and forward = Off. If your switch aft = Off and forward = On you would need 'Undercarriage Up else Down'. The default setting is always assigned to the On position of the switch. The flaps switch is an On-Off-On switch, so it requires two controls to configure: 'Flaps UP else MVR' and 'Flaps Down else MVR'. If we look inside 'Throttle - HOTAS Warthog.lua' that's exactly what we find for the flaps switch :thumbup:.... except they are named 'Toggle Flaps Up' and 'Toggle Flaps Dn' :doh: To compromise with ED I'd could live with 'Flaps Up else MVR' and 'Flaps Dn else MVR', not that I actually expect ED to do anything at all with this. *sigh*

Thanks for the reply Frederf! Everything is clear now. Small caveat though, at least on my installation, the device specific file is 'Throttle - HOTAS Warthog.lua'. I don't actually have 'Thrustmaster Combined.lua'. This naming concept is actually a bad idea from ED. In 'default.lua' 'HOTAS Boat Switch Aft', 'HOTAS Boat Switch Center', and 'HOTAS Boat Switch Forward' are defined, which are good for key-press and (On)-Off press-button switches. In 'Throttle - HOTAS Warthog.lua' is the 'combo' definition for actual On-Off switches. 'HOTAS Boat Switch Aft' in this file actually configures, if your physical switch is in the asserted position (aft), then it does 'iCommandPlane_HOTAS_BoatSwitchAft', but if it is NOT in the asserted position (it is in the middle -- this is the combo part), then 'iCommandPlane_HOTAS_BoatSwitchCenter' is done. The actual issue is therefore that in 'Throttle - HOTAS Warthog.lua' the control is not named for what it actually does. It should be named 'HOTAS Boat Switch Aft else Center'. Additionally, since this is in the 'Throttle - HOTAS Warthog.lua' file, it is not accessible to users of any non-standard controllers, for which ED has not provided a pre-configured lua file, thus forcing them to mod their 'default.lua' to create their own combo control to use. IMHO a more universal and streamlined method would be to have 'HOTAS Boat Switch Aft else Center' and 'HOTAS Boat Switch Forward else Center' in 'default.lua' in addition to the 3 key-press definitions. Well-known controllers could have a file defining the default switch assignments only.

Thank you CombatWombat! :thumbup:

+1 The so-called flashlight in the F/A-18 is actually a hand lamp, mounted in the rear right of the cockpit above the right console with a coiled cable. That is real nice, but I would be happy with a 2*AA battery MagLite™, very happy of it had a twist-to-dim function, and orgasmic... -- well, maybe not quite orgasmic, but you get the picture... NO! no pictures!, just... get on with it -- if you could go into Setting - Special - A-10C II and install a red or green lens filter if you wished.

This should have been done many years ago. But that's water under the bridge. But now ED has the opportunity to start with a clean slate and do things right. Please, ED, these are the kinds of very simple fixes which everyone sees every day. If you ever wanted to do something for polishing up the ol' ED image, this would be one of the best opportunities.