Page 1 of 1

A review of some new scenery that includes an MAIW package..

Posted: 03 Oct 2008, 04:57
by KevinJarvis
A review at Flightsim by Kevin Glover about SkySims new Andrews AFB has me a bit puzzled. The reviewer states that in the package is a link to MAIW's Andrews AFB package...I see no problem there.

However, in reading the review this guy states that AF1 is no where to be seen and he also critiques what he states, 'a prop effect' of the C130's "looks sort of weird."

He also states, "there are 737's in the Air Force One scheme".

He also states, "When the E-4's park, you'll find some ground servicing around them (well, I think it's an E-4). Also, in flight, they lower their refueling booms."

Maybe I'm being to sensitive but to me this review makes all the work done here appeart sub-par.

It's clear that Mr. Glover isn't very familiar with Air Force Aircraft, MAIW or Andrews AFB.

Thanks for reading.
Rant concluded. :?

Posted: 03 Oct 2008, 05:25
by Ford Friendly
I read the same review and wasn't too impressed with either his comprehensiveness of critique nor his style of presentation.

Then again, I don't have a stake in any of the pieces included or referenced in the package or the link.


As a slightly off-topic but ancilliary item, I think that I read something about Just Flight's new traffic package referencing the inclusion of MAIW models. Anyone else read the announcement that way? (It's possible I read that completely wrong and I can't find that announcement again.)

Posted: 03 Oct 2008, 05:41
by Jumpshot724
Besides the obvious of the guy being a sub-novice when it comes to all things military, what does he expect? Air Force one to be at Andrews 24/7? Tis a busy plane!!

Posted: 03 Oct 2008, 15:18
by MIKE JG
My Grandpa always said, "son, you can't cure stupid". :roll:

Posted: 03 Oct 2008, 15:18
by CelticWarrior
If it's HT's C130, and the package is for FSX, then the prop textures will look odd. C'est la vie!

Posted: 04 Oct 2008, 05:45
by KevinJarvis
I posted in a forum that the problem was probably caused by using an FS9 package in FSX.