X marks the spot :-)But you forgot Flight Crew X.So I'm guilty of abusing the "X" thing, too :-)I must admit I did have the same thoughts as the original poster.It gets a bit confusing all these acronyms punctuated with an X.Bryan

>Ah shucks! I was hoping to name my new product "Scenery and>Environment X"...>>you know, SEX for short... ;):-lol :-lolhttp://i5.photobucket.com/albums/y156/awf1/sign.jpg

This thread reminds me of my neighbor ....... He gripes about the money I spend on my car (Tinted windows, wax, polishers, car covers) my money.... not his.

Wait till we get hold of FS 30 I guess it will be FS XXX. That should be interesting!

While we're at it...can developers come up with something different for their "Service Packs" other than "SP1, SP2", etc? I've lost way too much hair trying to figure out if an addon I have with "updates" named "SP1" and "SP2" have anything to do with having to have FSX SP1 andor SP2 installed to make them work!*:-*

The days of getting a patch for a product seem to be gone. A patch would imply that the product was released "broken", while a "service pack" seems to suggest that you are getting more content.I'd file my review of FSX Essex X, but the FSX Essex X SP1 isn't compatible with XP FSX SP2. Jeff ShylukAssistant Managing EditorSenior Staff ReviewerAVSIM