Doughboy

Part 2 will be much better! The missions will be more fun since it will be about weapons/tactics with the admin stuff already laid down in Part 1. I've also learned so much in the past few years regarding comm flow and all that. I think it will sound much more authentic. I've also learned quite a lot in the A-10 so hopefully some of that will spill over into Part 2 as well!

Hi, sorry I'm a little late to the party here. Right now I'm indirectly working on pt.2. I've been learning a tremendous amount of stuff recently and I plan on incorporating a lot of what I've learned into pt.2 where I can, where it makes sense and what I'm allowed to share/use. I'm about start on training on the weapons/tactics/procedures of flying the A-10C which is what pt.2 will be all about. As I learn my plan is to work on scripts parallel to that. Me writing the script has always been the pacing item with Iron Flag, Baltic is a Machine and never sleeps so it is in my lap. As it is, yes it is in the works, right now the pace is very slow. Hopefully before too long pace will pick up and we can give you guys some legitimate news on it.

Wow! Not sure how we missed that... Thanks for the heads up on that! Correct VO recorded and script updated and it's added to the list of things to get fixed.

Thank you for your review. Glad you enjoyed it and got a kick out of Biff (me)! -D

Try cycling the trim and flight controls stop-to-stop and holding the controls centered. You may need to F2 the jet for some of that. IIRC the elevators in particular gave me fits.

Man where were you years back when we started writing this?!?!? In all seriousness though, of the all the folks I would have liked to have helping us, a controller would be second only to a current A-10 pilot! I wrote most of the ATC stuff and as you can tell, I'm not a pilot or controller. Some of the mistakes, and/or inaccuracies, are down to what we can and can't do within the ME, with AI as it is and also what we're doing. For instance, I can't have Kermit say "Departure Tusk 2 4 miles North passing 3 thousand for 6" because you may be at 3k or 1k or 15k when that VO is triggered... Some of the things you mentioned are us trying to put something together around the limfacs of DCS, and some of those solutions are less elegant than others (ILS part). There are also outright errors like the Lima and Romeo versus Left and Right thing. I've noticed some other things like "Tusk 3 cleared for takeoff" without mention of a runway number and some other nonsense that slipped past us and things I/we just don't know any better, more on that later. I've learned a tremendous amount about the whole ATC process in the past year. My current job has me flying with the plane I maintain here and there so sitting in the cockpit listening to that has highlighted a lot of things I would have wrote more better! I'm still learning. I learn every time we go out on a lunch and back. I learned a lot for your post above! For me the ATC is VERY high on the list to get right because getting it right adds so much to the experience for everyone especially those in the know! With that said, I definitely don't think you're nit-picking and I think it is worth it to get it right. Thank you for taking time out of your day to give us your feedback and for being candid about it!!! If you're up for it we sure could use your help fixing some of this and proofing Pt.2 scripts for us going forward! Like I said before, we've needed a controller for some time. Check your PMs. -D

About a year and a half or so ago Wags looked me square in the eyes and told me that there is no way ED would ever upgrade the A-10C with things like a HMS, AGRs, and GBU-54s. I've never been so happy to have been lied to my face! I told him I'd gladly pay full module price for the HMS alone. I'm glad its only $10 though, which I think is a steal! Thanks ED!!

We're seeing the exact same thing. I don't think you're/we're doing anything wrong.

Can anyone expand on what exacty we may be able to do and see with the Data Link PPLI and EPLRS features of the Scorpion/SADL?

So we went up and tried it this evening. Everything worked fine in MAN mode. No idea what I was or was not doing but it seems fine now. Thanks for the input folks!

Ok, we'll check it this evening as well. Thank you.

Both

I want to say that we did try that with not luck, but I'll put it on the list of things for us to try this evening. Thanks!

As the title states, I've tried getting LBGs (G-10/12/16/24s) off of the jet in Manual Attack Mode without any success. However, as soon I placed the Attack Mode Switch in the CMPTR PLT position the bombs come off the rack no problem. RedKite's video tells me to put the Attack Mode Switch into the Manual position. When I do this my Pilot gets nothing in the HUD (like "ORD" in the bottom or a PBIL/Pipper) indicating that the aircraft is ready for weapons employment. It should be noted that I've only tried to drop in these two attack modes. We can drop unguided MK82s all day long in MAN mode but as soon as we try to drop LGBs with no Armament Panel Switch changes aside from changing the Weapon Type and Station Selection we get nothing. Changing only the Attack Mode Switch to CMPTR PLT, we get good drops. In the TGP everything looks great, I've got all of the symbology you'd expect to see indicating you're ready to press the attack. We've got the Bomb Release Cue ladder on the right side and we get a time to release and even a time to impact after we've passed the point of release. There are no differences in the pod page or use from us trying it in MAN or PLT. I'm still learning the F-14 and RIO role so it's very likely that I'm missing something fundamental in setting up the jet for LGB employment in MAN Attack Mode. Can anyone corroborate what we are observing or identify what I/we are doing wrong here? Thanks! Armament Panel Settings: Weapon Type - As Applicable Attack Mode - MAN Delivery Mode - STP / SGL Electric Fuze - INST Mechanical Fuze - N/T A/G Gun - Off Delivery Options - 05msec / 1 QTY Jettison Options - WPNS Tank Jettison - Safe Station Select Switches - SEL As Applicable Pod Settings: On Laser Armed AG mode Point Track Mode Designated Point Set PRF Matched and Set Lase set to Auto AGC Selected Front Seat Stuff: Master Arm - Armed Mode - A/G VDI - TV Mode Steer CMD - MAN

I should really check the boards more often. I've had this problem for several weeks and have done all kinds of things up to and including a complete removal and fresh reinstall. I did need to do it anyway so I'm not too upset. I'll be glad when this issue is fixed though!

It has not Quax.

Hello again, I've had this persistent issue with my center main display being repeated in my MFCDs in the A-10C and I get no black background in the AV-8, MK2 and F-15s dispalys. I've dealt with it for this long but not I can't see the gunner status when I fly the Huey, my kneeboard is cutoff and now in 2.5 my NVGs are totally useless. In other words I need to figure out what is the problem and resolve it. I've leaned on what resources that I have and can't figure it out. Maybe someone smarter than I can see something wrong. Here are screen shots of the issue: Here is my windows display settings: And my DCS settings: My LUA: _ = function(p) return p; end; name = _('3ScreenMFCDS1'); Description = 'Configuration with 3 identical monitors each with its own camera and MFDs' Viewports = { Left = { x = 0; y = 0; width = 1920; height = 1080; viewDx = -1; viewDy = 0; aspect = 1.77; }, Center = { x = 1920; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.77; }, Right = { x = 3840; y = 0; width = 1920; height = 1080; viewDx = 1; viewDy = 0; aspect = 1.77; }, LEFT_MFCD = { x = 52; y = 1081; width = 565; height = 565; }, RIGHT_MFCD = { x = 1150; y = 1081; width = 565; height = 565; }, } UIMainView = Viewports.Center LEFT_MFCD = Viewports.LEFT_MFCD RIGHT_MFCD = Viewports.RIGHT_MFCD

Thanks, Hansolo!

Yeah the DCS manual was the first place I went for answers but it did not answer the questions I came here to ask.

I have crappy rudder pedals (Pro Combats) that always sit slightly off center so I get a constant but slight pull to the right. If I can remember I give them a little tap to the left once I'm lined up on the active and it seems to help a bit. Once airborne, if I dont tap them, it usually translates into just a bit of roll.

I'm trying to wrap my head around this Minimum Range Cue and I could use some clarification. As I understand it the MRC really is a Minimum Altitude cue yes? It starts moving 5-seconds from you busting whatever MIN-ALT you have set for the gun. I've played around with it and it seems to rely solely on MSL. Near sea level, it is pretty damn close to where I want to be but if I head up in the mountains I can fly into the ground without it moving off the top clamped position. Am I doing this correctly and am I interpreting my results correctly? Does the MRC only compare your inputted MIN-ALT to MSL and not DTS Elevation or RAD-ALT? Is this the proper behavior of the MRC function?

Sobe- Check the TOLD data in the kneeboard for speeds etc. Radio presets are covered in a later sortie. (Maybe mission 2) It seems like the recovery portion of the mission is bugged. With that being said Ground gives the flight taxi instructions, there is an airport diagram in the kneeboard and I think the IP tells you want to do when things work correctly. N19- Nope not at all. There are instructions for taxi, parking, shutdown and other stuff. Again, post landing is bugged. Yurgon- Copy that dude I think that stuff is already on the list but ifor not it is now. Thanks again for the kind words and feedback folks!

Sorry I'm just now catching up on this. I've had people packing up my house for the last 3 days and it's been hectic. So the IFF stuff... The ins and outs of IFF stuff is an OPSEC issue for obvious reasons. Since we cant validate its proper usage and its non-functional anyway, we've decided to limit the usage of the IFF/SIF panel to that of a transponder only. A lot of people (myself included) have wanted better ATC and more complex ATC for some time. Putting the level of ATC interaction that we have alows us to inject that "feel" of realism into the mission. Using the transponder and having squawk codes added another level to that interaction and introducing Clarence Delivery clears up some issues I had writing the script in later missions. Your usage of the IFF/SIF has no bearing on mission success. You can use it, not use it or squawk 7500 it don't matter. No one is going to get on the radio and bitch at you. So if you're like me and enjoy flipping switches it's there. If you don't want to bother with it since it's non-functional and redundant then you're good to go too! With all of that being said do you like it being in there or prefer to have it left out? I know about the VO telling you to put the switches into the on position when they're already there. I need to fix that VO. Good catch though!! Also I agree the departure procedure could be cleared up a bit. We need to put a Waypoint at Apex and fly to it then turn for Moapa in accordance with your clearance. We'll get that fixed in later iterations with supporting voice overs. I'm glad you guys are playing it, ejoying it and giving us your feedback! Keep it coming!! Doughboy

Hi Folks, Baltic Dragon and I wanted to give you guys a better idea of what we're trying to do with Iron Flag, let you guys have the opportunity to actually get hands on with it and for us to get feedback from you. So with that in mind, we are going to release Mission 01 for free download (link at the bottom). This mission will cover your startup, taxi, takeoff, recovery and shutdown procedures. Additionally, you'll be introduced to our ATC system and some of our Iron Flag/Nellis SOPs (Standard Operating Procedures). Although Mission 01 represents a small portion of what we are planning on doing, hopefully, what we've done thus far stands out and represents the rest of the project accurately. We try to walk a very thin line combining what is possible within DCS, how things are done within the real world and what most people would be interested in learning and doing. A lot of thought has gone into finding that line and I think we're damn close to are a really good blend of fun, realism, and feasibility. Some of the more savvy amongst us may figure out we're not flying that Nellis FYTTR FOUR departure exactly as published or that something we do at the range goes against what it says in AFI 13-212. You should still have the opportunity in Iron Flag to get as crazy as you want with that stuff. At the same time, we're not going to punish the guy who doesn't know how to fly radials or drop bombs using sleds, by making mission success and training progression contingent on those types of things. We also don't want to spend hours teaching someone who is not interested these things either. As far as progress with Iron Flag, progress is being made albeit slowly. Baltic has been pretty busy with family, work, other projects, and travel. I've been blessed with another baby boy, an upcoming PCS move, buying a house for the first time and a shit-ton of research for Iron Flag. Amazing how a little bit of knowledge can show you how much you DON'T know! Things will be slow for the next few months but we should speed things up soon after that. Right now Dragon is getting close to finishing up the navigation and systems side of things. In the background, I'm doing a lot of research for the foundation of the tactical side of flying and fighting in the hog. With those foundations built and ideas on how we want to do things that are applicable to every sortie, progress should pick up a bit. Having said that, we have got 4 missions to BETA status, all of them of similar complexity to what you are about to see in Mission 1. We also consider the copy of Mission 01 you see here as a Beta. More changes are sure to be made between now and the release of Iron Flag. There are known issues even with this release, especially with the AI behavior which at this time cannot be fixed. Again, think of this only as a representation of the final product. Thank you guys, for your excitement and interest in this project. Have a play though and let us know what you think both good and bad. Tell us what we did well and what we got wrong. Above all, just have a good time! -Doughboy Mission 01 Download Link

I thought I'd share with you guys the custom skins we had done for our squadron, the 355th vFS. The boss came across a fella by the name of Komemiute who is quite talented and was happy to do our skins for a quite reasonable price! As you can see we had him do quite a bit of work for us. No less than 12 different custom skins by my count (not all pictured) and we have plans for more including some individual skins! Komemiute has been a real pleasure to work with. He's been very patient with us and our ideas, revisions of ideas, suggestions, and requests. If you're looking for a guy to do some custom skins, graphic design or anything else you want to look good I'd recommend this guy! I'm really happy with the finished product we received. I think we'll give him a little break and then re-engage him with those individual skins and hopefully the Viggen soon :thumbup: