The "Boneyard Project"

mr.bean · Post by **mr.bean** » 22 Oct 2008, 00:35

Jumpshot, since I'm a MAIW fan, I give you no hard feelings.

Ford Friendly · Post by **Ford Friendly** » 22 Oct 2008, 00:48

I appreciate the work that went into the package as well as the thoguht process and accidental button pushing that caused the authorship error. I've done way too many similar things uploading files to other places.

Situation corrected. All's right with the world.

Post by **f4nutter** » 22 Oct 2008, 12:28

and posting forum reply's ford friendly

MACC · Post by **MACC** » 22 Oct 2008, 14:57

For the people who like their sim realistic its better than not having these beautiful models in there sim atall... and its still realistic.

Macc

p.s well done mate, love it!!

Keith Jones · Post by **Keith Jones** » 24 Oct 2008, 15:50

I've just d/l this package and was wondering why it was necessary to include the complete aircraft folders? Have the included textures been changed? If not, then I would have thought it easier (and keep the file size down) to just include the relevant aircraft.cfg files where changes have been made (parking codes, etc.). The rest of it is fine and I'm only experiencing a small drop in frame rates when I look around the boneyard. Great stuff!

fishlips · Post by **fishlips** » 02 Dec 2008, 01:51

Why not contact the model developers to have them convert there model source file to static scenery and add as Ez-scenery. It only takes a few minutes to convert an FSDS or Gmax made aircraft file to a static scenery file and best of all, all the moving parts and code don't get compiled and a few poly's can even be shaved off the model making the aircraft even lighter on frame rates.

When applied on a large airbase like Miramar between working AI models, you never notice that the static aircraft never move and they look just like the real AI model.

Everytime I make a new AI model, I also make several static versions in different modes of maintanence as it only takes a few minutes more to compile it.

Post by **Firebird** » 02 Dec 2008, 08:43

A very reasonable point, fishlips. Very pertinent if he was trying to recreate the boneyard, per se, but on this occasion he wanted to create a boneyard of MAIW aircraft that had been retired.

Am I right in thinking that with a static model you are stuck with one scheme, rather than the ability to have all the MAIW schemes applied?

Jumpshot724 · Post by **Jumpshot724** » 02 Dec 2008, 17:14

That plus in the Boneyard it wouldn't be a bad idea, but for an "active" package like Miramar or Langley etc, sure it would be better on framerates but those static a/c would be stuck in the same spot and never move. I like the dynamics of our bases where you never know what parking spot is occupied or not or even by who until you get there.

It's a good thought in theory, but Firebird is right you would need to create a static for every single repaint. I for one, as well as I'm guessing most everyone else on here, would not be happy with only 5 or 6 "generic" static models to represent a base that has 60+ a/c

fishlips · Post by **fishlips** » 18 Jan 2009, 07:27

Static models are as easy as changing the texture file, of which can be the same ones used for the flight model. So easy! Make as many different paint schemes as you please once the static is completed.

disinfected · Post by **disinfected** » 27 Oct 2009, 21:17

Know it's been awhile, but what about Kenyan Hawks?

Makadocias · Post by **Makadocias** » 27 Oct 2009, 21:33

disinfected wrote:Know it's been awhile, but what about Kenyan Hawks?

If I recall correctly this package was released -from the start- as a retro package.

Hope that helps and please correct me if wrong

Post by **Firebird** » 27 Oct 2009, 21:35

Exactly what do you want to know about the Kenyan Hawks?

disinfected · Post by **disinfected** » 27 Oct 2009, 21:42

Makadocias wrote:
disinfected wrote:Know it's been awhile, but what about Kenyan Hawks?
If I recall correctly this package was released -from the start- as a retro package.

Hope that helps and please correct me if wrong

Weren't the F-14's too?

Also, a good number of the F-15's from the Eglin package of the 58th and 60th Fighter Squadron (deactivated last month, was one of the last to work there!) are also in the boneyard, with some going on display and the rest distributed to the national car.

Post by **Firebird** » 27 Oct 2009, 22:04

All true, but I am not seeing what you are after. Is there a question that you wish to ask?

disinfected · Post by **disinfected** » 27 Oct 2009, 23:56

Firebird wrote:All true, but I am not seeing what you are after. Is there a question that you wish to ask?

Because the fictional boneyard has all of the retired aircraft from MAIW packages?

Jumpshot724 · Post by **Jumpshot724** » 28 Oct 2009, 01:24

I see what he meant. Yes, I will (eventually) be updating the package with the MAIW packages that are now "obsolete", such as you said the Eglin Eagles. Funny you should mention it, I was actually thinking about this last week lol.

When will I update it? I can't say. Between work and the Fire Department, I'm finding it hard to just keep up with the official MAIW work I'm doing 'round here. But rest assured, it will eventually get done

disinfected · Post by **disinfected** » 28 Oct 2009, 19:33

I can see if I can find tail numbers for the ones that went to the boneyard.

Jumpshot724 · Post by **Jumpshot724** » 28 Oct 2009, 21:29

I can see if I can find tail numbers for the ones that went to the boneyard.

I appreciate the thought but save your time and effort, if I were to be that detail-oriented I'd have to re-release a new version of this every other week lol. By the time I get around to the update I will have included all of MAIW Eglin's eagles

fishlips · Post by **fishlips** » 03 Nov 2009, 07:18

Does it really matter if non-developed & packaged textures on the MAIW aircraft models are used here or are you just making a history of past used packages that have gone by the way side due to MAIW package upgrades, etc.

There are some really great repaints of MAIW models that are decommissioned, seems a shame to leave them out. But after all it is your package!!!

Jumpshot724 · Post by **Jumpshot724** » 03 Nov 2009, 22:06

Does it really matter if non-developed & packaged textures on the MAIW aircraft models are used here or are you just making a history of past used packages that have gone by the way side due to MAIW package upgrades, etc.

There are some really great repaints of MAIW models that are decommissioned, seems a shame to leave them out. But after all it is your package!!!

I don't know what you mean by the first part of the question, but yes It's just a history of past (and current) MAIW packages that contain units/aircraft that are no longer flying REAL WORLD. For example, the F-117's from the original Holloman AFB package. F-117s are gone from the "real-world" USAF, and even though they're at Tonapah "real world" I put them in the boneyard for FlightSim purposes instead of just deleting them altogether.

My purpose for creating this package was to display all the hard work that went into creating these models/paints, yet keeping my sim "real world", IE they don't fly. I like to keep my FlightSim as up to date as possible, and I know others do as well. It pains me that the F-14 isn't flying anymore in the real world, but such is life and thus the poor Tom-kitty's are grounded in my Boneyard

It's freeware, no one said you HAD to use it

The "Boneyard Project"

Re: The "Boneyard Project"

Re: The "Boneyard Project"

Re: The "Boneyard Project"

Re: The "Boneyard Project"

Re: The "Boneyard Project"

Re: The "Boneyard Project"

Re: The "Boneyard Project"

Re: The "Boneyard Project"

Re: The "Boneyard Project"

Re: The "Boneyard Project"

Re: The "Boneyard Project"