Wolverine88

No worries and many thanks for this as well. It's also been a while since I checked in as Real Life issues have taken up a lot of my time, as they should. No worries at all about the time it's taken to do this. :thumbup:

Yep, the tail flash looks really good there. We had quite a few of the different tail numbers seen in the flight of four there. My jet had an 82 in front of it but we had tail numbers with the front two numbers being from 78 all the way through 83. Those front two (smaller) numbers were the year that the lot was ordered/paid for. We always referred to those first two numbers as the year that each was "born" in or built during, so I'd refer to my bird being an "'82 model". The Eagle was always both high performance and with that came VERY high maintenance. As Crew Chief (Maintainer) we get to know each air-frame like nobody else. We don't really know how the Eagle "feels" when flown, but we spend a lot more time with them than the pilots do. The pilots track their time as a pilot in hours, we track our time in years so we know those aircraft like nobody else does. Even our avionics/radio/radar specialists spend less time on them than the crew chief does since they've got to move on to other jets with problems on them when they're needed. The Crew Chief must spend most of their day inspecting every inch of the outside and a lot of what's on the inside to include the servicing. I did have the privilege of going for ACT mission in the back seat of one of our two-seaters. The feeling of absolute raw power from those engines and the maneuverability of that airframe isn't like what you'll feel in anything else. I got a little stick time and the impression between the real thing and the flight model in DCS is very comparable. The FS CO's bird was indeed 79-0021. The photo supplied is of the right hand maintainers box. This was taken on the day we sent the jet to the AMARG "Boneyard" so we signed under each name. Not very well either but I'll just blame it on being a little distraught. ;) I don't really know what the font is. For me I'd just choose on that's close, a leaning cursive of any sort would do. The pilot assigned to it was LT.Col Wade Causey (this would be on the top line) and his callsign was "Spike" (this would be on the second line) in the same font as what you'd choose on the maintainers box on the right. It would look like this: Lt.Col Wade Causey "Spike" <----centered under the name in the box

82-0031 This was on the last day she spent at Tyndall AFB. The close up of the Crew Chief's names on the right side of the cockpit is on one pic. The other is on takeoff to Davis-Monthan AFB's bone-yard or AMARG as it used to be called. Let me know if you need some some more pics.

Aw man! you FOUND HER! I remember sending her out to the bone-yard at Davis-Monthan. Then I crewed A-10's there with the 357th FS, I visited the bone-yard and got to say goodbye to 82-0031 again just the way she is in this picture. Kinda sad really. She was a good jet and not because I was any good at keeping her flying, I had a lot of help. My name is actually on the side of it, right side of the cockpit where the DCC and the assistant CC names are. This pic shows the tail detail pretty well too.

Ok, the "American Beagle" Patch goes on the left side of the fuselage a little ways behind the intake and the 325th FW patch goes on the same place on the right side of the fuselage. More to come later.

Wow! Kewl skin proposal! I hope somebody picks this up as I'd like one of those myself! Even if it is one from the 1st FW. ;)

Ok, would any of you out there with skills at making skins out there be willing to make up a skin for the 2nd FS at Tyndall AFB (gold tails)? I'm an old Eagle Keeper who crewed 82-0031 for about 8 years at Tyndall from '03 to when it closed down around 2010'ish. I'd like to get some 'time' in my old jet. :D

Ok, would any of you out there with skills at making skins out there be willing to make up a skin for the 2nd FS at Tyndall AFB (gold tails)? I'm an old Eagle Keeper who crewed 82-0031 for about 8 years at Tyndall from '03 to when it closed down around 2010'ish. I'd like to get some 'time' in my old jet. :thumbup:

So, after much downloading and trying different drivers I found one that gets DCS working again...at least in single player missions. 388.71 for my lame 860m and poor graphix memory seems to make things work quite well. Will have to try some multiplayer yet but thanx again for the help with the DDU. The graphics driver hunt and install/uninstall went so much easier with it!

Some great stuff there folks. Thanx for all the help. I'll be going through all this and making comparisons to help the situation.

Ok, looking at my drivers for NVIDIA I upgraded recently to the 391.35 driver for the 850m card I have. Things seem to work for a bit then this happens this weekend after going to 2.5. I'm not sure what happened but now the 2.5 won't work with it and neither will some of my other games (MWO for example). After rolling back the driver to 368.39 I at least get into a mission in 2.5 before it crashes. Most recent crash log should be here to look at. If you get the time let me know what you see in the log.... dcs.log-20180408-153023.zip

Many thanks for the assist. Been playing the open beta earlier before going with the newest of 2.5 just yesterday and haven't been able to play since. Figure it's time for a new system soon anyway but wondering if moving over to the new 2.5 I've fouled up somewhere.

Ok guys, I need a little help to see if my fears are correct. This game has probably outstripped my meager system and it's time to start saving for a new gaming computer as the game is crashing on startup after going to 2.5 Please review my crashlog and see if I'm right... dcs.log-20180407-202533.zip

Mbot, thank you. As a former member of the 58th I'm VERY interested in trying this out!

Will try that...Thanx for the help! :smilewink:

More info... Looked into all the log files for both of the DCS sims (2.0 and 1.5.6) and found nothing as far as a recent crashlog for the connection timed out so that's out. Still searching for a reason that I'm connecting and crashing right out or just unsuccessfully connecting because it times out on me... :joystick:

thanks for the help...will try that and see what happens... :helpsmilie:

Bump, Also, single player works fine for both 2.0 and 1.5.6....

Did a search for the "Connection Timed out" and subsequent crash of the game on joining ANY mulitplayer 2.0 or 1.5.6. Game will try to load and sometimes hang-up at that point. Mostly both sims have me loading up the server that I join into but giving me a connection time out message on the way to joining in or even working until I place myself in an airframe A-10C or F-15C, either one, and then hanging up and giving me the connection timed out message. Some times there's no message at all just a general hang-up of the game. For the most part as it's both sims, Nevada and the 1.5.6 arenas, I think it's on MY SIDE since that's the only thing both hang-ups seem to have in common...maybe. I have Webroot and I've tried joining up after taking off the web-shield and firewalls and such which doesn't help either. Reaching into my bag of tricks and coming up with a handfull of lint currently.... Any ideas out there? RW:joystick:

if my canopy ever looked anything like that, with that much 'crazing' I'd have it changed out the next phase dock that it went to...or directly as soon as a canopy showed up in supply. Especially if it looked THAT bad! The other thing that would happen would be a 'de-lamination' where the layers in the plastic would get air in between them...also a 'no bueno' by the Tech-data.

Ok, I get how things are working (or not) for fire support NOW. How do you see some possible future confrontations with say Russia, in maybe...Eastern Europe...with a more "symmetrical" type of warfare? My dad was a FIST guy during the Vietnam war and I've had training as an AF TACP. I remember my dad saying what my instructors used to, that an FO has his battlefield survivability measured in seconds or minutes. My hat's off to you red-legs! huah.

Yeah, gotta say that i'm not sure exactly why the media always have the quotes from the A-10 pilots. Maybe because they really have to worry about their careers or something or that because they're officers their word has more weight (which it shouldn't). The people the media/government should be asking is the word of the people on the ground who count on the CAS that they provide! I guess the people in flight-suits garner better ratings...

On that same note...I almost always get rid of some/all of my wingmen on some missions... I tell my wingman to engage and I listen to his radio calls...He calls: "Fox-3" and almost immediately I hear <<BOOOF...>> then: "Right Engine Fire....Right Engine Fire..." I look over and my right wing is gone and I'm on fire of course... <sigh> :cry: He had lagged back instead of firewalling the throttles and I'd caught his slammer in the tukus as it came off rail...yaaaay.

IMHO...use the F35 to "kick the door down" by doing the SEAD mission and have the A-10's follow them in to the FEBA to put a serious hurtin' on the AFV's...

Ok, take this from a guy who's done some work as a USAF TACP...nothing will beat the A-10 for CAS. Not the F35...not F15's or F22's or the F16's. Period. Army/Marine gunships were the only thing that could hold a candle to the work the A-10's did for us. In any kind of airplane except a hovering gunship helicopter you cannot see individual soldiers unless you want them to shoot at you with small arms...which would be a big mistake, you're way too close in that case. Most small arms will knock down pretty much anything flying if they hit you in the right place. Using the targeting pod means you're too high and showing up on most all radars in the area. Same goes for an AC-130...too high for most threats if they're facing enemy air and AC-130's aren't any more capable versus the same anti-aircraft stuff SOMEBODY said made the A-10 fold. Not sure who/what you're reading Tirak. Don't know who wrote the crap about A-10's being pulled out of the CAS mission during DS but they got that wrong...they just changed their tactics since the threat of enemy fighters disappeared. It was always expected the attrition for A-10's would be high during a war in Central Europe. It would be for everybody I think. And take this from a guy who has spent MOST of his time in the USAF as an F-15 and A-10 Crew Chief: F35 can't even get up in the air right now anyway...and once it is the low observable system/airframe it has will make sure that it will spend most of it's time on the ground being fixed once it is deemed combat capable....someday...maybe...in it's dreams. Final point FOR the A-10, just look at how many munitions the F35 can carry vs. the A-10..the F35 will spend most of it's fuel/time going back and fourth from FEBA to the base to get more munitions. My poor weapons loaders will work themselves to DEATH and so will I doing 30-45 minute turns and getting it back up in the air...if it's not broke/NMC! If you want the F35 around for more than 15 seconds he will have to carry a bunch of stuff on him that will NULLIFY his radar-stealthy airframe and make him no more stealthy than an F16. So, all you NON-er's STFU while I build my 9-line dangit! ;)