Midway Carrier Pack

The Midway class carriers served a vital role in the later days of the 23rd century, not only as large fighter platforms but also as self co...

Download

Uploading...
Do not refresh or leave this page!

File Description

The Midway class carriers served a vital role in the later days of the 23rd century, not only as large fighter platforms but also as self contained mobile command centers. Built to replace the aging Napoleon CVAs of the previous era, the Midways sport the latest in sensors, weapons, and communication technology. In addition to their large contingent of fighters, the Midways also carry a number of shuttles, workbees, transports, and dropships. When one of these massive vessels enters a sector of space, order is soon to follow.

The pack includes the USS Ark Royal (carrier) , 2 fighters (Peregrine and Wraith) and the Type 3 shuttle from ST:V. Each is launched from a different shuttlebay.

Download QBAutostart and the Techframework from Defiant's homepage here http://defiant.homedns.org/~erik/STBC/ if you don't have them already otherwise the fighters won't launch.

Read More

Download 'midway_carrier.rar' (2.5MB)

Screenshots
Readme
 THIS PACK INCLUDES 4 SHIPS

 - Midway Carrier
 - Peregrine Fighter
 - Wraith Fed Fighter
 - Shuttle Type 3





 Midway Class Carrier/Space Control Ship - U.S.S. Ark Royal + Fighters


The Midway class carriers served a vital role in the later days of the 23rd century, not only as large fighter platforms but also as self contained mobile command centers. Built to replace the aging Napoleon CVAs of the previous era, the Midways sport the latest in sensors, weapons, and communication technology. In addition to their large contingent of fighters, the Midways also carry a number of shuttles, workbees, transports, and dropships. When one of these massive vessels enters a sector of space, order is soon to follow.



== CREDITS ==================================================================


Mesh/Textures Midway: WickedZombie45 (wickedzombie45@aol.com) - http://www.nightsoft.net/omega/drs/index2.htm

Mesh/Textures Peregrine: Michael Frederick (aka Zorg) - zorg0001@hotmail.com - http://www.zorgspace0001.com

Mesh/Textures Wraith: Activision (from SFC:OP)

Mesh/Textures Type3 Shuttle: Jayru

BC convertion/Hardpoint/Speculars/Sounds: Zambie Zan (alexandre.marques@gmail.com)



== SPECS ====================================================================


Midway Class Carrier

626m
4 Photon Torpedo Launchers (2f/2a - shots 6f/6a)
15 Phaser Banks (2f/2fp/2fs/2p/2s/1dp/1ds/1vp/1vs/1a)


Peregrine Fighter

25m
2 Micro Photon launchers (2f)
6 Pulse Phaser Banks (6f)


Wraith Federation Fighter

25m
2 Micro Photon launchers (2f)
4 Pulse Phaser Banks (4f)
1 Phaser bank (1f)


Type 3 Shuttle

10m

1 Phaser bank (1f)




== INSTALLATION ==============================================================


Unrar the file into a temporary folder
Copy all the files into your Bridge Commander folder
Overwrite if asked


== REQUIREMENTS ==============================================================


- SubMenu 


== GLITCHES ==================================================================


None

Tested in Bridge Commander v1.1



Enjoy


=====================================================

== Midway ==

This readme is to be included with this ship at all times - Dynaverse mods are NO exception!


Model made/edited using: Lightwave 5.6, 3d Studio Max 3.1, Paint Shop Pro 7, Uview, Taldren's .mod plugin

Please note: This policy is open to change following developments concerning my work which may not have been an issue previously. I suggest you check back frequently in order to keep updated on the current policy status. Copies of the policy included with the files may not be as up-to-date as the one posted here.

I have no problem with kitbashes/alterations as long as the following procedures are followed:

1.) Everyone involved with the kitbash/modification is to be credited. That includes the original model author(s), anyone involved with the design (if different from the modeler), and the person who created the alteration. This will set up a history of the modifications and give credit to all involved.

2.) If a ship is to be converted to another game (Bridge Commander, Armada, Klingon Academy, etc.) I prefer being notified of any alterations to my work as most times the credits are not listed properly, the ships aren't converted correctly, etc.

3.) If the ship is to be released to the public, no parts from a restricted model are to be used. Some modelers don't want their work to be altered and I would expect everyone to respect that. If there is a part or parts that are restricted, I can possibly create a replacement for you to use.

4.) If the ship is to be released to the public, I would ask that you contact me first. This is to make sure you have the proper credits listed and to make sure no restricted parts are being used. On some occasions people have credited me for work that I have never seen before.

5.) Please do not post these models on other websites (with the exception of mod/dynaverse downloads, kitbashes, and conversions to other games). I prefer keeping my ships on a single site so I can better control their distribution and make sure the correct files are updated. I know this sounds rather strict but it becomes a bit tedious when trying to update a ship and having to contact dozens of other websites to inform them of the changes as well.

6.) If I grant permission for alterations to a single model, that is not to be interpreted as a base acknowledgment for further alterations/conversions/kitbashes/etc. to any other ship that I have created. Approvals of alteration requests apply only to individual ships, not all of them at once unless otherwise stated in my response.

7.) All work on this site is property of the respective owners. If anyone attempts to steal or take credit for work they did not do, I will hunt you down and feed you to a pack of bloodthirsty wolves.

Star Trek, Star Fleet Command, Star Trek: Bridge Commander, Star Trek: Deep Space Nine, Star Trek: The Next Generation, Star Trek: Voyager (and the various logo devices used in them) are copyright Paramount Pictures, as are the characters, related images, and sound from the productions.


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

== Peregrine ==

Model made/edited using: 3ds max3.1, Photoshop, Paint Shop Pro

Credit Request:  If you distribute, post or share any of these models or alter them and subsequently distribute, post or share any of these models please be nice and give credit where credit is due.  This readme should always accompany these models wherever they go. Thanks.

Star Trek, Star Fleet Command, Star Trek: Deep Space Nine, Star Trek: The Next Generation, Star Trek: Voyager
(and the various logo devices used in them) are copyright Paramount Pictures, as are the
characters, related images, and sound from the productions. 

LEGAL STUFF: This file is not supported or affiliated with Interplay Productions. While most who have used these files have had no problems, we will not be held accountable for any damage done to your computer by use of these files or techniques. USE AT YOUR OWN RISK! This file is freeware. It is not to be sold.

Copyrights
User-created missions contain source-code that is the property of Interplay Productions and Quicksilver Software. In addition, Star Trek is a property of Paramount Pictures. Star Fleet Battles is the property of ADB, Inc.

You may not sell user-created missions commercially.
You should respect the rights of the property owners.
Missions created based on Star Fleet Battles material must be marked "Based on copyrighted material by ADB, Inc." in the documentation or mission briefing. ADB also requests that these missions not be placed on "out of network" SFB web-sites.

SOFTWARE USE LIMITATIONS AND LIMITED LICENSE
Any Star Trek: Starfleet Command mission (each, a "Mission", and collectively, "Missions") created using the Star Trek: Starfleet Command Mission API ("SFC Mission API") is intended solely for your personal, noncommercial home entertainment use. You may not decompile, reverse engineer, or disassemble SFC Mission API or any Mission, except as permitted by law. Interplay Entertainment Corp. ("Interplay") retains all rights and title in SFC Mission API and the Missions including all intellectual property rights embodied therein and derivatives thereof. SFC Mission API and the Missions, including, without limitation, all code, data structures, characters, images, sounds, text, screens, game play, derivative works and all other elements may not be copied (except as provided below), sold, rented, leased, distributed (except as provided below), used on pay-per-play, coin-op or other for-charge basis, or for any commercial purpose. You may make copies of SFC Mission API and any Mission for your personal, noncommercial home entertainment use and to give to friends and acquaintances on a no cost, noncommercial basis. This limited right to copy or provide public access to the SFC Mission API and the Missions expressly excludes any copying, access or distribution of SFC Mission API and the Missions on a commercial basis, including, without limitation, bundling SFC Mission API or any Mission with any other product or service, selling SFC Mission API or any Mission, and any giveaway in connection with another product or service. Any permissions granted herein are provided on a temporary basis and can be withdrawn by Interplay at any time. All rights not expressly granted herein are reserved. No technical support from either Interplay or Quicksilver Software, Inc. ("Quicksilver") shall be available for SFC Mission API or any Mission.

INTERPLAY AND QUICKSILVER DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, RELATING TO SFC MISSION API AND THE MISSIONS (INCLUDING WITHOUT LIMITATION, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT), AND NEITHER INTERPLAY NOR QUICKSILVER SHALL HAVE ANY RESPONSIBILITY OR LIABILITY REGARDING SFC MISSION API AND THE MISSIONS, INCLUDING, WITHOUT LIMITATION, ANY RESPONSIBILITY OR LIABILITY REGARDING USE OR OPERABILITY OF SFC MISSION API AND THE MISSIONS. YOU ASSUME ALL RISK OF LOSS IN CHOOSING TO USE SFC MISSION API AND THE MISSIONS. 

SFC Mission API and all Missions © 1999 Interplay Entertainment Corp. SFC Mission API and Star Trek: Starfleet Command are trademarks of Interplay Entertainment Corp. All Rights Reserved.

USE OF SFB SHIP MODELS IN SFC: 
This can be done if you include the statement below and comply with the policy 
it covers. 

This 3d "ship model" for Star Fleet Command is based on a ship published in STAR 
FLEET BATTLES. The original SFB ship is copyrighted to ADB Inc., which has 
granted blanket permission for the use of its property on the basis that: 
1. The original ADB Inc. copyright is recognized by placing "(c) ADB Inc" on the 
3d ship model itself. 
2. The resulting 3d ship model is not distributed for profit (except with 
approval of ADB Inc.). 
3. The resulting 3d ship model is uploaded ONLY to a site which complies with 
ADB Inc.'s web policy (posted on its web site). 
4. The copyright to the resulting 3d ship model is freely transferred to the 
sole ownership of ADB Inc. Any subsequent use of the image by ADB Inc. will be 
subject to negotiated compensation. 
5. This ENTIRE notice is included with the 3d ship model file. 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Read More

Comments on this File

There are no comments yet. Be the first!

Zambie Zan


50 XP


Registered 26th September 2004

58 Files Uploaded

Share This File
Embed File