More than 100 years of Klingon history. From the Enterprise Era to TNG era, 12 ships for your enjoyment. D-2, D-3, D-4, D-5, D-6, D-7, D-7A, D-7R, K'Tinga, Qonos One, Romulan K'Tinga and the K'Tinga TNG. The perfect match for the Connie Pack.
Klingon D-Pack for Bridge Commander == CREDITS ============================================================= Pre TOS ships D-2, D-3, D-4, D-5, D-6 Model/Textures by Jeff Wallace (firstname.lastname@example.org) TOS ships D-7, D-7A, D-7R Model/Textures by ATRA-HASIS (email@example.com) - http://www.geocities.com/atrahasis1/index.html Credits: Some mesh components borrowed from Moonraker's Ktinga model. TMP & TNG ships KTinga, KTingaR, Qonos One, KTingaTNG Model/Textures by WickedZombie45 (firstname.lastname@example.org) - http://www.nightsoftware.com/omega/drs/ Script for the Romulan Torpedo by edtheborg All convertions/hardpoints/sounds by Zambie Zan (email@example.com) == INSTALLATION ========================================================= Unrar into a temp folder and copy all the files into your Bridge Commander directory. Tested in BC 1.1 == BUGS ================================================================= None that I'm aware of. == REQUIREMENTS ========================================================= - SubMenu - FTA v2 ================================================= Model made/edited using: Lightwave 5.6, 3d Studio Max 3.1, Paint Shop Pro 7, Uview, Taldren's .mod plugin I have no problem with kitbashes/conversions 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 and dynaverse downloads 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 "Sure, do whatever you want" 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. ================================================================ THIS 3D model for SfC is a product of hard work and Aristic Interpretation by its creators Any Similarity to any other works is purley coincidental, It is not intended to represent accuratley or otherwise any Model ship , drawing OR computer generated image of any kind in anyway, either past ,present or future. This model is intended for free distribution and Cannot be sold in anyform without the creators express consent. A lot of time and effort has been spent on this model by the group to get it as close to the source matrerial as possible and we may well release further updates based on weather ADB produce better SOURCE material or our own personal tastes dictate.. IF YOU WISH TO REPOST, RE-TEXTURE OR REWORK THE MESH I ask you seek prior approval BEFORE RELEASING ANY SUCH RE-MODELS. ================================================================ Copyright and Distribution Permissions -------------------------------------- THIS PATCH IS NOT MADE, DISTRIBUTED, OR SUPPORTED BY INTERPLAY TM & (C) INTERPLAY & TALDREN & PARAMOUNT PICTURES. Copyright notices: 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 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.
There are no comments yet. Be the first!