Jump to content

Frostiken

Members
  • Posts

    1156
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Frostiken

  1. Moar liek 'Option to be a sissy off/on'
  2. I got my printed at Kalkwik, came out very nice :)
  3. http://en.wikipedia.org/wiki/Let_them_eat_cake Try this - go to your local AMU (preferrably for a fighter aircraft), find the spec or APG office, and ask to spend an entire shift with someone. PS: Dress well because you will not be going back inside to 'take a break' for at least ten hours, and eat hearty because you will not be given your usual 1.5 hour break to wander down to Burger King and shove yet another quad stacker down your quivering gullet. PPS: No, we don't get incentive rides when we go TDY, first of all because ops ****ing hates maintenance, and secondly the rare times we do give incentive rides, we're giving them to some A1C piece of shit who fought terror and saved the lives of Army troops by ****ing up my god damn travel voucher and not giving me my pay for six weeks.
  4. Depends on the system really. I can't speak for A-10s but on the F-15, the two systems that fail the most often is the RWR and ICMS. ICMS is a fickle beast and out of all the times they write it up, probably 30% of the time we're able to just reset the system and it'll work another day. ICMS has a maintenance log built in that keeps a record of every BIT failure and when it happened until the log is full (which can take months), or if you replace the Band 3 CO or reload the OFP. The funny thing about this log is we can see if the pilot tried to reset it or not, and they never do. Many times you'll see something like this: 0000 (good BIT pass from sortie last week) 0000 (good BIT pass from sortie three days ago) 0000 (good BIT pass from yesterday) 1342 (bad - pilot will write it up. Never tried to reset) 0000 (we run it up after the sortie... temporary failure, return to service) We have a few maintenance tricks up our sleeves as well - one of them is the non-volatile RAM reset which will flush the ADCP's brains out. Pilots hate doing it because they have to reload their data but it can clear out a lot of failures with the display processor and 'central computer'. Fair enough then :) But you have to admit crew chiefs are to maintenance what pilots are to Hollywood... pilots actually think crew chiefs (APG) are the ones who fix everything even going so far as to call me 'chief' when I'm on comm, people here think crew chiefs are the ones who are sorting out their MFCD problem and fixing their CDU... as far as the F-15E goes crew chief jobs are really just limited to servicing, cleaning the jet, changing actuators and a few other 'dirty' things like AMADs and JFSs, and managing forms. We don't even get our name on a jet and we have to fix the AAI, AFSC, AIUs, AOAs, CMDs, DLPs, EGI, EWS, EWWS, FCC, FDL, HUD, ICS, ICMS, ILS.... :D
  5. Probably because the F/A-18C has a laughably tiny fuel and payload capacity.
  6. On one hand I can see having an option, but on the other, equipment failures are a fact of life. What I would like to see (ED take note!) are equipment failures being able to be sorted out in-flight. Avionics systems are just computers, and if your computer in real life is having a problem, a simple reboot can clear it up. Many times we have pilots come down with broken systems that we can't dupe even in chocks talking them through reset procedures, because powering down and back up is simple enough to fix some occasional glitches. Naturally battle damage isn't going to be 'cycled out', but it would really be nice to have more specific failures (ie: a line on the CDU blanks out, or your MPD color goes screwy) rather than 'it works' or 'it doesn't'. Just my $0.02. <USAF maintenance dickfight> Bah! Crew chiefs know what hole to put the red and yellow stuff in, but ask them how anything works and watch the blank stares all around :D </USAF maintenance dickfight>
  7. There's a difference between a FLIGHTPLAN flightplan and, say, using markpoints for weapon employment...
  8. Video? Not sure, but it's really quite easy to do with Mavericks. You simply pick the lead vehicle, slew the Maverick to it, lock it up, and fire. When the next Maverick comes up, you just tap it towards the back of the convoy and it'll lock up the next vehicle, and so forth. Really not much more to it than that. You *could* use the target pod to assign markpoints on various stationary targets, and just use your DMS with your HUD as SOI to cycle as well.
  9. Markpoints are really just temporary. There's no real reason why you COULDN'T use them, but you can have far more waypoints than markpoints (25) and they won't get erased like markpoints do.
  10. Well keep in mind bird strikes IRL are pretty rare anyway :P How often do you expect / want to injest a bird?
  11. At low altitudes, there's a chance to injest a bird (no indication aside from random engine flameout and failure, not even in the log afterwards). Bird slider adjusts that chance.
  12. According to my Logbook, it took me 10 hours in-game before I really felt comfortable with it. Honestly, if you dedicate a weekend to it, you should be alright. My method was to read a section on the manual, then play with it in-game to see how it really works. About 70% through I just stopped because everything else seemed to be clicking into place by then.
  13. Wholeheartedly agree. I believe a most useful facet of such a wiki would be a sort of organized list of the various Youtube tutorials out there. There's a great many assets on Youtube but wading through and finding the best ones is not the easiest task...
  14. Can you clear up for me what 'every frame' does? I thought it was just a setting for SLI... EDIT: Sorry for the week-old bump, ended up at this topic via a roundabout halfassed way, thought it was that current T-pod target searching thread...
  15. Yes, but here we can go "Horray for surround sound!"
  16. As a sim pilot, I don't get paid to do it and thus after my job of working on real aircraft 10+ hours a day, the last thing I want to do is the mind-numbing frustration of trying to accomplish the overly-difficult task of in-flight refueling in DCS! There's a big difference between the kinds of people who play sims... for example, people who invest the incredible time, money, and effort into building entire cockpits... those who play FSX and join those surreal servers where you have people playing sim ATC to people flying sim cargo planes of rubber dog shit out of Hong Kong... Yeah I'll pass on the six hour sortie.
  17. Frostiken

    SR-71?

    DCS: Dragon Lady :D
  18. I hate landing with combat damage, mostly because I always forget something important. The last one I only had one hydraulic system, and I forgot to disengage anti-skid. The anti-skid system bled PC1 dry and I flew off the end of the runway going "AAAAAAAAAAAAAAAAAAAAAAAAAA" and crashed into some truck.
  19. Disagree with what? Not to drag this off-topic but the simple fact is that you cannot use a LITENING or even a Sniper pod to zoom with the retention of image quality that we have, especially if you're playing with your MFCD screens @ 1024. The entire point of the 'nerf the target pod' thread wasn't "make it harder just because", it was "you guys made a mistake when you modeled the pod". I'll also point out that at 0 zoom level, the image quality @ 256 MFCD resolution is as bad as a LANTIRN pod :p 512 resolution makes it look actually about right, though lower MFCD resolutions will *not* compensate for the fact that you cannot use the pod like some crazy toy from CSI where you just say 'enhance' and can count individual rivets on a target 7 miles away, especially not if it's an IR image - infrared tends to make details pretty fuzzy on its own, to say nothing about an ELECTRICALLY ZOOMED image running through ancient triax wiring on an aging shaky old airframe plugged into an overpriced TV :D 1024 MFCD resolution is cheating, plain and simple.
  20. Pretty much what Rain said. If you compare a pre-Suite 5 F-15E throttle grip alongside the A-10C it's surprisingly different. More than likely what happened is they've been modding the F-15E throttle grips alongside the F-15E SATCOM mod for A-10C integration. But they are not the same throttle grip. The TDC, china hat, mic switch (original F-15E only had two-direction mic switch) and boat switch all look or function differently and have been replaced. This would explain why the throttle grips never issue from supply...
  21. At the same time, the idea of having to hit two tankers every sortie because you burn off half your fuel just flying over the water would make me want to eat a bullet :p
  22. Yeah, because we don't expect a sim to be realistic or anything.:rolleyes:
  23. For the sake of realism, what you really would do is radio in to ops (basically the dude manning the radio in your FS building) who would then call maintenance pro super... though more likely it'd have been pre-arranged altogether.
  24. You need to hold China Hat fwd long in order to slew everything to the SPI. Just setting something as the SPI does little more than change the little dangly-dinger-thinger on your HUD. If you have the HUD as SPI, and then hold China Fwd Long, the TPod and Mavs should follow where you direct the TDC on the HUD.
  25. You don't even have to park in the right space. I fell off the runway and busted my landing gear off, so I yelled out of the cockpit at the nearest knuckledragger to get his lazy ass out of the smoke pit and do some god damn work, and he helpfully drove his Wollard out there, jacked me up, and begrudgingly slapped a new one on :D Was even nice enough to get POL off their asses to gas me up.
×
×
  • Create New...