Leaderboard

Added some measurement of real A-10A instrument panel Even if most of you goes for the C-version, overall dims and center part should by correct. Enjoy -edit: dims in Metric (mm) Cheers /Gus

I got a lot of positive feedback when I posted this in another thread (thanks – appreciated!). The kind words made me feel obliged to improve upon it, so I decided to add some graphics, clean it up and make it a thread of its own in order to make it easier to find and understand. Background reading I’d like to begin by pointing you to Military Map Reading 201 by the NGA. It is well worth a quick read. Fifteen minutes, and it will all come clear to you. If it doesn't, I'll instruct over MSN if need be - that's how confident I am in you really getting it. :) In the beginning, there was UTM The world is divided into large grid zones. They're given a number from 1 to 60 based on their east-west position (longitude) and a character based on their north-south position (latitude). You can then give any coordinate as a combination of a grid zone and the distance east and north from the southwestern corner of that grid zone (it's really a bit more involved, but that's the general idea). 38T and two longish figures, for example. This is the UTM system. MGRS grid squares However, UTM is rather unwieldy to work with, especially if you are out in the field trying to call in arty support over the radio, or in an aircraft trying to communicate the position of a target or friendlies on the ground. To make it easier, the MGRS was introduced. Each grid zone is divided into a large number of 100.000 by 100.000 meter grid squares. These grid squares are given designators based on their north-south and east-west position within the grid zone, using one character for north-south and one character for east-west. AM, MM, DL etc. Now you can point out an arbitrary 100.000 by 100.000 meter square anywhere on the planet, using a designator such as 38T ME. Coordinates within the squares - eastings and northings From there, we only need to be able to designate a certain smaller square within that square, in order to point out targets. You do this just in the same way as you did within the grid zone using UTM, by measuring the distance east and then north of the southwestern corner of the grid square. The two distances describe the position within the square and are known as the easting and the northing. As the square is 100 km across, you need two figures per coordinate (east/north) to give 1 km precision (0-99 km east/north of SW corner). If 10 km precision is enough (unlikely ;)), you only need one figure. The first ten km east/north of the SW corner is then 0, the next ten 1 etc. For pointing out targets, you will generally need to get down to ten meter squares. As there are 100.000/10 ten-meter squares to each side of the 100.000 m two-character grid squares, you then need four digits (0-9999) for the easting, and another four for the northing. For one meter precision, you need five digits. Putting it all together A full MGRS coordinate consists of the grid zone, grid square and finally the easting and the northing written together as one long string of digits, with the easting first (XY, not YX). Frequently, the grid zone is omitted once it is assured that everyone else is using the same grid zone. 38T ME04586742 would mean a ten meter square (four digits for easting/northing respectively) within grid square ME in grid zone 38T. To find the position, you'd divide square ME into ten meter squares and find column 458 from the western side. Then you'd find row 6742 from the southern edge of square ME. In reality, there are supporting lines in the maps making finding these coordinates easy. You're really finding a point 4580 m to the east and 67420 meters to the north, and then you know the object for which the coordinate is given to be in the 10 by 10 m square to the NE of this point. Examples I've attached two map images. In both maps, the two fixed points A and B are plotted. Also notice how you have four different grid squares in the map images, each with a different two letter designator. In one picture the coordinates are given using two figures for easting and northing, respectively. Point A is in this case at grid YH2704 – easting 27, northing 04 in grid square YH. In the other picture, the coordinates are given using three figures for easting and northing. Point A is in this case at grid YH278043. It is still in exactly the same position as in the previous example, but the position is given with a higher degree of accuracy. Note how the easting is truncated instead of rounded, i e 278 becomes 27 rather than 28 when going to a lower precision. This is due to the position always being in the appropriately sized square NE of the designated point, as previously described. The coordinates of point B are left as an exercise for the reader. (Ignore the negative coordinates on the axes in the pictures. MGRS coordinates are never negative, I just couldn’t be arsed to edit them out after clipping the pictures from my drawing program of choice Excel . Yes, I’m a worthless artist.) Clear as mud? Didn't think so. Go read the PDF and look at the graphics. Told you it's worth it! DCS caveats (obsolete due to bug having been fixed) Visualization If you want to visualize the MGRS grid system in Google Earth, you can download a KML file which does this. Anecdotes "There were ten of us, living in a shoebox in the middle of the street..." If your head is spinning at this point, consider this: I fly and work using WGS84 (lat/lon). I initially learned one coordinate system in the army, only to later transition to MGRS which I still use for weekend warrior duty. Now, I also fly fire watch missions. When coordinating with the fire services on the ground, we use the first coordinate system I learned as they haven't switched to MGRS. Coincidentally, that coordinate system gives the northing before the easting, but calls the northing X and the easting Y. Now, try to get all that sorted out while circling above a fire in a very warm cockpit being jostled by turbulence and trying to find forest roads to guide the fire trucks in along using a radio with very poor reception... :pilotfly: Please let me know if you have any suggestions for clarifications or improvements, or if my Airman's Prayer ("Please don't let me screw this up!") didn't pay off. ;) Cheers, Fred

It appears that being warned to refrain from politics/political discussion has been conveniently ignored. Deliberately disrespectful, Contemptuous of a reasonable request or an honest oversight? On behalf of those members whose posts have now been removed, I sincerely hope it's the latter....... Politics end here!

Крайние страниц 5, прямо-таки пестрят обсуждением противоракетных манёвров.... АЛЛЁ - тут модераторы вообще есть??? Или на этом форуме могут только говорить не в тему и друг друга какашками поливать? P.S. А вообще, грустно мне в последнее время, на любой форум как не зайдешь (авиамодельный, авиасимуляторный, автомобильный), сплошная "потасовка с плевками в морду", в виде - "тебе лечиться нужно", "руки не из того места" и т.п. Кстати, подобные ответы себе периодически позволяют господа разработчики и иже с ними... Господа, это не приемлемо, Вы должны быть ВЫШЕ!

Of course they are....as well as I'll be sending additional sounds (inverter, APU and engine start) to Olgerd (you're welcome for the true to life canopy sound by the way) mid April after my next reserve weekend. I do all this to help the sim be as true to life as possible and never ask ED for anything in return....

:megalol: One of the funniest animal vid I've seen. not funny but really impressive

Hi guys. After "sometime" of soldering nightmares, the Warning Quadrant is finally operational PCB based on Mike Powells design outlined in his latest book (thanks Mike) Dual high intence green LED in serie driven by a 12V source through an ULN2803A. Each indicator triggered by a OICard Mastercard 5V output. Should be able to drive the real thing or any likewise uptil 50V per indicator. White DILs are resistors. PCB Schematics here Indicators "faceplate" is a three layers OH film 1200 dpi color laserprintout Note that top pic was taken without a flash. The light bleed showing is much lighter then in reality but.. it shows that the glue used had resolved the toner somewhat I might redo it in the future though. Best combination I found with the LED intencity was two with green text on top and the bottom copy with "white" letters. Font used is MS 33558 truetype font created by Derek Higgs on simpits.com (my complements to the creator) Some pics of setup and cabling fuzz cheers Gus

HawgTouch is a simple light-weight framework which allows you to create your own cockpit panels for DCS-10C. The software is bundled with 2 MFCD's, a UFC panel (Thanks to jeffyd123 @ ED forums): Included profile ShowcaseProfile.xml which demonstrates tabs, scaling and latest additions Version 1.25 changes - Fixed a bug where keystrokes of Rocker Switches weren't sent - Fixed a bug where keystrokes of Two State Switches weren't sent - Fixed a bug where keystrokes of Three State Switches weren't sent - Fixed panel closing and tab switching crash - Added a "drag" button to the top right, to drag, click and hold the button - Optimized code and image handling - Profile parsing improved, now showing detailed exceptions if profile is illegaly formatted - Two State switches now support multiple types: - On/On - Momentary/On - On/Momentary Take a look at the "TestPanel" tab in the ShowcaseProfile.XML to see how to assign switch behavior - Three State switches now support multiple types: - On/On/On - On/On/Momentary - Momentary/On/On - Momentary/On/Momentary Take a look at the "TestPanel" tab in the ShowcaseProfile.XML to see how to assign switch behavior - HawgTouch now ships in two executables. x86 and x64 Version 1.2 changes - Fixed bug in ClickButtons long press. Now working - Added support for tabs - Added panel scaling mechanism - Added audible clicks option - Better keypress engine, no more flashing HawgTouch now supports tabs. At least 1 tab must exist in every profile. Once a profile is loaded. A tab control box appears which allows you to switch between tabs. The tab control box can be latched to 9 locations of your chosen monitor. This is done by specifying 2 parameters in the profile XML <LatchTo></LatchTo> Available parameters: - UpperLeft - UpperMiddle - UpperRight - MiddleLeft - Middle - MiddleRight - BottomLeft - BottomMiddle - BottomRight The tab control box is also dragable. <MonitorID></MonitorID> Specifies which monitor the tab control box will latch on to. To get the ID of the monitor you'd like to latch the tab control box to, click on the "Monitors" link on the main HawgTouch window. It will display your local monitors setup. Sample profile XML with 1 tab and 1 panel: <?xml version="1.0" encoding="utf-8" ?> <Tabs> <LatchTo>UpperLeft</LatchTo> <MonitorID>2</MonitorID> <Tab> <ID>1</ID> <Name>Test</Name> <Controls> <Control> <Name>Up Front Controller</Name> <PanelImage>\Images\UFC\ufc-main-panel.png</PanelImage> <X>80</X> <Y>10</Y> <ShowTitleButtons>true</ShowTitleButtons> <SizePercent>100</SizePercent> </Control> </Controls> </Tab> </Tabs> Supported controls in 1.1: - Click Buttons - Rocker Switches - Two State Switches - Three State Switches HawgTouch is fully "customizable", allowing you to use your own skins and graphics in any size you choose to make. Setting up exported MFCDs: 1.HawgTouch comes with a default skin in which the MFCD "transparent" zone is 400x400 pixels. With additional 186x146 pixels for the bezels. Therefore the MFCD's rendering in your multi monitor setup LUA file should be to 400x400 pixels to fit inside the frames. This is my multi-monitor setup: (1x 24" @ 1920x1080 and 1 x 22" @ 1280x800): _ = function(p) return p; end; name = _('My_example'); Description = 'Two monitor configuration'; Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.6; } } LEFT_MFCD = { x = 2050; y = 105; width = 400; height = 400; } RIGHT_MFCD = { x = 2650; y = 105; width = 400; height = 400; } UIMainView = Viewports.Center2. Now you will need to set up the keys in DCS A-10C control settings which are mapped to the MFCD profiles in HawgTouch. HawgTouch comes with 2 MFCD profiles which are configured to the following keys: Left MFCD OSB1 through 10 - Left Control + 1 through 0 Left MFCD OSB10 through 20 - Left Control + Left Shift + 1 through 0 Right MFCD OSB1 through 10 - Left Alt + 1 through 0 Right MFCD OSB10 through 20 - Left Alt + Left Shift + 1 through 0 Here is in-game screenshot of the controls binding: You can set any key combination you want. Here are the key shortcuts: (Made identical to TouchPal for easier transition) {BACKSPACE} {TAB} {CLEAR} {RETURN} {LSHIFT} {RSHIFT} {LCONTROL} {RCONTROL} {LALT} {RALT} {PAUSE} {CAPSLOCK} {ESCAPE} {SPACE} {PAGEUP} {PAGEDOWN} {END} {HOME} {LEFT} {UP} {RIGHT} {DOWN} {PRINTSCREEN} {INSERT} {DELETE} {LWIN} {RWIN} {APPS} {NUMPAD0} {NUMPAD1} {NUMPAD2} {NUMPAD3} {NUMPAD4} {NUMPAD5} {NUMPAD6} {NUMPAD7} {NUMPAD8} {NUMPAD9} {MULTIPLY} {ADD} {SEPARATOR} {SUBTRACT} {DECIMAL} {DIVIDE} {F1} {F2} {F3} {F4} {F5} {F6} {F7} {F8} {F9} {F10} {F11} {F12} {NUMLOCK} {SCROLLLOCK} You can mix all sorts of shortcuts for your liking. Most will work but I can't gurantee crazy combos since I haven't checked it myself. Creating your own panels: HawgTouch gives you the liberty to create any panel you find useful for your simming pleasure. Take a peek at the TestPanel.xml file for information of how to use the different controls HawgTouch supports. With time and by request more complex controls will be added! UFC bundled in 1.1 (Thanks to jeffyd123 for the image works!) NOTE: The key commands for the UFC are not set! Once you set your UFC key bindings in-game, open up UFC.xml and fill in the KeyCommand slots! My setup: Download: HawgTouch 1.25 x86 [1.03MB] HawgTouch 1.25 x64 [1.03MB] Extract anywhere. In this version the last known position of the panels is not saved. You will have to manually set it to the specific panel. To help you achieve that a new button has been added to the panels which shows the current windows X/Y positions. Once you are happy with your position you can type that data into the panel XML and it will be launched in the position you saved. IMPORTANT NOTE: If you are running any Windows version with UAC enabled (Vista and higher) and you are running DCS A-10C as Administrator you will have to launch HawgTouch as Administrator aswell. Orelse the keystrokes wont be sent to the game. You will need .NET 4.0 to run this so if you don't have it installed make sure you run a Windows Update or download it from here : .NET Framework 4.0 Download Tested on WinXP 32/64, Win7 32/64 Enjoy! ClearDark

Here is my latest singleplayer mission, "The Bear Came Over the Mountain". Some of you might have played a Beta version; thanks for your help with tracking down the crash bug to my system settings. The attached, "Final", version has improved timings, altered JTAC tasking and, above all, detailed, tactical voice comms for player, OP commander and Stryker leader roles. To summarise: - This is a half-hour sortie that starts in the air, at Angels 20. - The player leads a 2-ship tasked with escorting a Stryker convoy en route to defend an isolated Blue Observation Post that is under threat from an imminent Red armored assault. - The mission was inspired by footage of A-10s supporting infantry in mountainous terrain in Afghanistan; this battle takes place around a contested valley pass in the Caucasus mountains. - Ground combat is plotted in some detail (driven partly by the player's actions) with a 26-man Stryker team named individually after the mission author's high school classmates. Tips: - Use your wingman, both for datalink target i/d and target prosecution. - Respect the SA-9 engagement envelope - Maintain SA of targets, and prioritise. Threat prioritization is the tactical "essence" of the mission. There is an early decision point and either choice you make will have consequences. - At exactly 30 minutes from mission start you will receive a Success/Fail message from ground units via radio. - Accomplishing all mission goals is relatively easy for the intermediate-to-advanced DCS A-10 pilot but avoiding all Blue casualties amongst ground forces is not. There is one way to approach the mission goals that, if properly executed, will result in a Blue victory with zero friendly casualties. - The mission rewards competent use of both Mavericks and CBUs while under threat. - Use of JTAC is optional. The Predator is helpful under certain circumstances. - Make sure you alter the incorrect default NET settings in the TAD screen to 01/01 so that datalink works properly for both JTAC and wingman data. In general I do not intend to build scenarios in the ME that start in the air, or even on the runway, being a bit of a purist, but glitches in AI flight members' behavior on takeoff and climbout have frustrated my attempts at ground launched missions and I await the next patch to address this. In the meantime, as I say, this mission is a good half-hour workout in Maverick and CBU deployment, JTAC and wingman interaction and tactical threat prioritization. Good luck, have fun and please post comments. (Thanks go to WarriorX, Apples and Audacity for realistic voice comms) The Bear Came Over the Mountain_Final.miz

After getting 3 photos rejected, I finally got a photo published over at airliners.net: Link to larger size is here: http://www.airliners.net/photo/USA---Air/Fairchild-Republic-A-10A/1882481/L/&sid=b995a7769f6918720e64eb83b72982fe Here are two that are currently in queue: Hope you enjoy it, and hopefully more are to come. Regards, Diego

Im in the same situation ;) Lets call it even :thumbup:

Don't forget 6DOF support! :D

Non sara' il software.. ma devo dire che A-10 e' davvero innovativo....sopratutto il multiplayer.. ricordo tante serate aspettando di entrare nel server con falcon.. oppure dopo ore di volo un bel crash.. ! Aspettando patch mai uscite... :music_whistling: Sono un grande appassionato di Falcon.. ma questo ha davvero un'altra marcia..! :thumbup:

Not so much funny: but great. Watch only with stereoheadset! Increase the volume a tad, sit back and relax. It's really cool! http://www.wimp.com/holophonicsounds/ And if your a (lamborghini) car fan, watch this: :shocking: go6kxyKSDZ0

Sov13t Спасибо.

One of my favorites: "Das Lцffelspiel" - "The Spoon Game" No need to understand the language - just enjoy the show :lol:

Зачет=) Я факультативом все хочу заняться японским, но не получается=)

But this can be taken to far. In the real world you'd taxi back to the hardstand and probably scrub the mission and go play golf. Perhaps when the plane breaks we should just play Tiger Woods Golf over a beer for added immersion. Sorry I don't want to be crude but I think only a true git would fail to understand why this is nonsense. If players want to deal with random failures then let them check the boxes to experience them. Otherwise, ESPECIALLY IN MULTIPLAYER, leave random failures out. Because as this thread makes clear, the things that are failing are not necessarily items which fail IRL and in any case the rate of failure far exceeds reality. In my job things break regulary. I write them up and the flight gets delayed. Is it fun? No. That's why I get paid for the experience. The great thing about an Air Combat Simulator as opposed to Air Combat is that I don't have to worry about the drudgery of being an A-10 pilot. And I don't have to worry about dying. And I don't have to worry about hitting innocents. And I don't have to worry about cluster-bombing good guys. And I don't have to worry about all the squadron admin stuff that takes up much of the time in a combat pilot's life. So when you try to separate the DCS player's experience from that of lesser mortals playing HAWX, you should probably consider that when seen from the high vantage point that is real life, both are just games. The question from the comparison then becomes: Was the experience exciting and/or educational? Or was it just a time-wasting PITA?

People fly DCS because it's a sim. People 'play' HAWX and Over-G fighters because they're not. Compare ArmA to Counter Strike or Mechwarrior to MechAssault...

Я тоже так думал, но когда попробовал читать и переводить французский мануал по ка50 гугл переводчиком, я понял что это пздц:D.

Grazie spinter del consiglio, ma con quello che gira adesso Falcon purtroppo mi sembra ormai obsoleto, non credi??? e poi non voglio diminuire e modificare i settaggi grafici per poter volare con Falcon 4, preferisco un buon livello grafico e di realta' su game e simulatori nuovi.

Use the link post #22 is working :)

Lots of free time on my overnights at work, so no problem. And you're welcome! I'm downloading the latest update to Xcode and I'll start working on it tonight. So please, anyone, start showering me with some ideas of what you'd like to see. :) Thanks!

I, me, and my self,:D you are saved cause I'm in thesis now, but give me time and the fury of my R-77 are going to show you the truth in the glass of the monitor. You better find a nice 42" monitor so you can see the misiles on time for EM. I'm going ask buddy of mine that has some intel on that, that enter the forum so he makes you enter in sense. Cause I'm a little busy right now. Shinigami Out... PS: Wen I finish the thesis less play and who ever wins has to admit what the other says.

Grazie dei complimenti Extender72, ha compiuto gia due anni... Comunque strano davvero, sto leggendo un po nei vari thread per qualche soluzione per aumentare la grafica e risoluzione a 1920x1200. tenendo sott occhio gestione risorse e tutto tranquillo, bho ps: Complimenti a te con il tuo PC

536 стр. мануала

'<Non-American fighter> in <Googled exercise name> shot down <number greater than one> <fifth generation US fighter>s! <Generic ethnocentric whinging and anti-American sentiments>!' The only thing MiGs are good for: Crashing into spectators at airshows is also a cool trick.

help ..got one 32" 1920x1080 Tv , and a 19" 1280x1024 ....lcd up high on the right corner of the 32" tv...i would like to set up main cockpit on 32" screen and the one MFDs on 19" screen , running off a single GTX570 ..ANY IDEAS ..help ..lol ...not that clever with this stuff.. oh screen 2) is DVI- and screen 1) is HDMI...SINGLE CARD

I think you missed this one :D

http://www.getdropbox.com lets you upload files for public download. Quite useful. Sadly it won't tell you how many times it was downloaded.

Thanks for reporting this issue. I dove in the code and saw the problem. Since this is a major "show-stopper" ill release a new version later today addressing that issue among with some other bugs and optimizations. I don't see why not :)

You need to edit some lua. files to make it work. Do a search there is pleanty of threads that show how to do it.

Really nice F15J landing video.

Correct. There's a special video I've prepared for such occasions :P Just asking here... Is it that IR image in Warthog should show different levels of IR spectrum on hot parts of vehicles? BTW, here's s thermo imagery done in a primitive graphics engine of Steel Beasts Pro Pe. Here's how it would look like in B/W:

well, this is awesome! Thanks be to forum member reemit0772 who told me how to enable mouse clicking in the communications menu! Guess it was here all along: In the folder: FUI/resources/radio. Edit 'menu.res' and change 'acceptmouse{0}' to 'acceptmouse{1}' Works a treat for me. Just unbound the function keys from my X-52.

http://forums.eagle.ru/showthread.php?t=49150 There Arma 2 Sound mod by =STP= Dragon The sound from Diveplanes soundmod is taken from this onboard video :) but proplem i have with the sound mod from Diveplane is that it seems to be reversed this choppersound comes up when the Helicopter gets faster or the Rotorblades get some angle and not when you get in a Hover ,or it sounds like a loop. And im sure it was a hard jop to be done but in my opinion it misses a little bit the point.

Hey Guys, will this work with the smaller G13? thx

She is looking better and better, can't wait.

to Mustang

Thanks guys, Here are the three photos that were rejected: I was most surprised by the Harrier not being accepted. Regards, Diego

You got US-hardware in almost every media format, it's starting to get tired. Just watch back and tell me, what planes you were able to fly in the past 15 years. So after a DCS F/A-18, you will want another one after 5 years? And another one after 10 years for the same reasons? Do you even know, how European, Chinese etc. aircrafts cockpit look like? Do you know more Weapons except of the AIM-9, AIM-120, Mavericks etc.? It just feels one-sided. Instead of the F-18... I would be more happier flying a full detailed and realistic MiG-21.

After seen an interview with Warthog Producer Matt Wagner it seems that the next aircraft would be a US fighter what a shame, I was hoping for a russian one. Well next time lest hope for a russian one. Shinigami Out...

In the release version screenshots are saved to ...\Users\Username\Saved Games\DCS Warthog\ScreenShots. That is for Win7.

An old thread but it seemed suitable :thumbup: This is to share some material on the Thrustmaster Cougar MFD button panel setup I did. Just in case someone finds it useful. The Cougar MFD panels are mounted on either 24" main screen (1920x1200) corners or on a separate 15" screen (1024x768, analog vga) using small velcro strips. For Black Shark use, I set image on them with 4:3 and 3:4 ratio and the sides are used for labeling the buttons. I attached a powerpoint file (black&white) which can be printed and cut with scissors to fit in the Cougar MFDs. Either print on paper and set between the plastics, or print on a transparent film... Just modify it to your key assignments and fine-tune according to your viewing angle/perspective. When panels are attached on the monitor, just the 3:4 screen area is seen between the button labels - see the picture. Works well.:prop: Below are the monitor setup files (config\monitorsetup). 24" screen: 24" + 15" screen (horizontal spanning for fullscreen and good FPS on windows XP; with 1920x1200 scrolling area and 1024x768 viewable area on the 15"):

Hehe, it reminded me of Wall-E becuase of they way the cameras/binoculars are modeled :P

TM HOTAS COUGAR PROFILE FOR A-10 TM HOTAS COUGAR PROFILE FOR A-10 Please let me know if there are any problems or changes you would like made. This is intended for use with TrackIR and Rudders. But I can make a version without that if anyone wants it. By the way please check the attached thumbnail before downloading. I have had one or two complaints about the few functions. I have copied the real A10 controls exactly like in the real jet except for a couple of minor differences. I prefer to do it like real pilots. I believe looking for a keyboard switch would be the same distraction a pilot would have going heads down in his cockpit. Its the way I like to fly OF and now A10. DCS A10-C TM HOTAS COUGAR PROFILE DX Version.zip

Serial #: 00836 Location: Cheshire UK

I had taken TriggerHappy69 Mig-29 manual and made it searchable. It should be much more useful this way if you were looking for specific data... http://www.megaupload.com/?d=JTJ5XF82

My Resimay To hoom it mae cunsern, I waunt to apply for the job what I saw in the paper. I kin Type realee qwik wit one finggar and do sum a counting. I think I am good on the fone and I no I am a pepole person. I no my spelling is not too good. My salerery is open, I kin start emeditely. Thank yoo in advanse fore yore anser. Sinseerly, Tiffanny PS : Becauze my resimay is a bit short I sent a pickture of me. Employer's response:... Dear Tiffany, It's OK honey, we've got spell check.