The Rebel Faction

Register today to customize your account.
Galactic Citizen

Saber Class Fast Attack Cruiser




Type: Fast Attack Cruiser/Fleet Raider

Length: 70 Meters

Weapons: 4 Heavy Turbolasers (foreword facing fixed mount fire linked)
1 Class 2 Proton Torpedo Launcher (5 Torpedoes Equipped)
6 point defense laser cannons

Shields: 400 SBD

Armor: 400 RU

Crew: Minimum 15, Recommended 35, Maximum 40 + 3 astromech droids
(5 bridge officers, 5 torpedo loaders, 15 maintenance/damage control personnel, 10 security guards)

Top Speed: 35 MGLT

Hyperdrive: x1

Troop Capacity: none

Cargo Capacity: 5 Metric Tons

Support craft:
In hangarbay: one small shuttle
In external sockets: 1 Squadron

Passengers: 5

Other systems: Smart Comp, HLS Phantom Generator, QETS, repulsorlift

General Information:
The Saber Class Cruiser was designed to be the best anti capital ship weapon in the Commonwealth Navy. Using its combination of speed, agility, and heavy weapons, it can easily overwhelm the defenses of similarly sized ships.

Explanations:

Class 2 Proton Torpedo Launcher
It is essentially a starship mounted torpedo launcher made to fire proton torpedoes that are 2 meters long and 1 meter in diameter, approximately 2 are required to take out a hard point on a ship. It takes about 10 seconds to reload an only one can be fired at a time.

The Heavy Turbolasers
First of all, each turbolaser has its own power generator. To maintain maximum efficiency and the lowest recharge time, it was decided to have the turbolasers fixed in one direction. Instead the maneuverability of the ship will compensate for this drawback. The turbolasers are able to fire 5 times, but then require 10 seconds to recharge. The ship can also provide continuous fire for up to five minutes at a rate of 2 shots per second, after the five minutes is up they must stop to recharge. Also, to protect against fighters, it is fully capable of flakbursting.

Engine Placement
The main ion engines are placed on the sides to take advantage of leverage as much as possible. There are also smaller ion engines on the front of the main ones to aid in turning and breaking maneuvers, as well as a plentiful abundance of variable geometry maneuvering thrusters strategically placed along the ship’s hull.

Smart Comp
This is just an advanced version of a normal ship’s computer, it coordinates the efforts of all repair droids throughout the ship, sends sensor and navigational data, and, shield and system status to friendly units. Because navigational data is shared, the ship is able to plot microjumps within a solar system as long as a friendly ship equipped with a smart comp is in the desdination area. To preclude the possibility of jamming, all communications are routed through the QETS system, except when using traditional methods are required.

Hull Armor
It is made up a Kevlar like material, bonded together at the molecular level with Ulithium, and coated with blaster and laser resistant materials to provide exceptional energy distribution and projectile resistance, all in a lightweight package.

HLS Phantom Generator
Another, innovative design made possible by Commonwealth scientists, this system can disguise a ship as almost anything by using Hard Light projectors dispersed along the ship’s hull. Because Hard Light holograms read on sensors as real matter, the ship can assume the shape of any preprogrammed designs like asteroids or other ships. It can also assume the shape of anything not in the database if it can get a full sensor sweep of it. Also, multiple systems can be networked together to disguise multiple ships, or to create larger disguises. Theoretically with enough ships, a hologram the size of a super star destroyer can be created.

Backup Power System
In case main power went offline SFA power recievers have been installed to the chances of survivability when heavly damaged

Comments

#68 8:56pm 10/10/06

I was going to post something, but the arguement died without me

*puts away Armor and rattled sabre*

#67 11:19pm 08/10/06

It's been PMed.

#66 11:08pm 08/10/06

[QUOTE]I propose that we do give the Saber a somewhat similar micro-jumping system as the KIBC. I do have an idea in mind for it, and I offer to do the design work for it.[/QUOTE]
alright fine, PM me your thoughts

#65 10:35pm 08/10/06

Yes.

[QUOTE]A. THERE IS NO APPROVAL PROCESSS FOR R&D SUBMISSIONS - so stop pretending like anyone here, save the staff, has any right to say what will and what will not fly.
B. APPLICATION AND DESCRIPTION - do I really need to elaborate?
C. IF THERE IS A PROBLEM HERE WHICH REQUIRES STAFF INVOLVMENT - then make it known to the powers that be and anticipate that it will take some time before a resolution is reached. Also, during this period (should any of the involved parties seek a proper Staff injunction) the R&D in question will be put on hiatus and the thread itself will be moot until such time as that verdict is announced.[/QUOTE]

The reason the system was changed was to prevent this sort of obsessive debating. For those of you of old; You know Better! For those of you too new to remember the old; Read the rules and don't follw the bad examples being set by a few r-tards. If you're stuck in between; look to the western sky.

#64 10:30pm 08/10/06

Telan has also stated a very similar viewpoint on AIM to that of Kach and myself. I don't think there is going to be a very clear-cut general consensus about this issue.

I propose that we do give the Saber a somewhat similar micro-jumping system as the KIBC. I do have an idea in mind for it, and I offer to do the design work for it. That or the current system is a one-time occurence of anything being R&Ded so closely to an existing technology.

However, I do think that in the future, anything that looks so conspiciously close to an existing technology should be permanently removed from the said R&D unless there is a valid IC reason, such as the technology was captured in a battle with the faction's original creator. Any thoughts?

#63 8:26pm 08/10/06

NVM

#62 8:26pm 08/10/06

[QUOTE]Integrated Kashan Battle Computer: The Integrated Kashan Battle Computer is actually multi-purpose network that is connected to every vessel of the Kashan Fleet, whether it is a patrol starfighter or a Seraph-class Cruiser. The main purpose of the Battle Computer is to intertwine, triangulate, and transmit sensor data collected from each ship.

This allows the ships to instantly gather target acquisition data and triangulate that data. The triangulation process ensures excellent target data, foiling most anti-targetting and sensor-jamming systems.

More importantly, the network can also provide navigational data from each ship along. Each vessel automatically transmits its location to the other vessel and shares navigational data with it as well. This allows the vessels of the Kashan fleet to act as navigation beacons for hyperspace jumps. As such, it is possible for Kashan ships to make instant intra-system micro-jumps to a Kashan vessel with the Battle Computer.[/QUOTE]


[QUOTE]Smart Comp
This is just an advanced version of a normal ship’s computer, it coordinates the efforts of all repair droids throughout the ship, sends sensor and navigational data, and, shield and system status to friendly units. Because navigational data is shared, the ship is able to plot microjumps within a solar system as long as a friendly ship equipped with a smart comp is in the desdination area. To preclude the possibility of jamming, all communications are routed through the QETS system, except when using traditional methods are required.[/QUOTE]


Seriously, is this what you all are debating? C'mon! Three pages?
A. THERE IS NO APPROVAL PROCESSS FOR R&D SUBMISSIONS - so stop pretending like anyone here, save the staff, has any right to say what will and what will not fly.
B. APPLICATION AND DESCRIPTION - do I really need to elaborate?
C. IF THERE IS A PROBLEM HERE WHICH REQUIRES STAFF INVOLVMENT - then make it known to the powers that be and anticipate that it will take some time before a resolution is reached. Also, during this period (should any of the involved parties seek a proper Staff injunction) the R&D in question will be put on hiatus and the thread itself will be moot until such time as that verdict is announced.

Or 1, 2, and 3 if you like.

#61 8:18pm 08/10/06

You think your tech is special because it does something so uncharacteristically easy? I don't think so man. As far as I'm concerned, he can leave the idea within his tech because it would be easy to develop.

#60 8:05pm 08/10/06

[QUOTE]It is simple because it is easy. One ship has a beacon read by another ship. How hard is that? Seriously man, stop being so thick-headed.[/QUOTE]

Another relative term; great. Seriously Kamon, develop your own tech. I will not let the precedence of allowing people to simply copy another person's tech to happen under my watch without a debate, regardless of whose technology it is to begin with. That sets a dangerous precedence if we do.

[QUOTE]I just dont see how complex the calcuations can be epecially if you have live sensor data from other ships, or from an ASCA.[/QUOTE]

Exactly. That's the idea behind the KIBC, continually providing sensor and communication's feed to eliminate many of those calculations...

#59 6:30pm 08/10/06

I just dont see how complex the calcuations can be epecially if you have live sensor data from other ships, or from an ASCA.

#58 6:11pm 08/10/06

It is simple because it is easy. One ship has a beacon read by another ship. How hard is that? Seriously man, stop being so thick-headed.

#57 5:22pm 08/10/06

[QUOTE]There are some technologies that are so expressly unique to their respective factions that allowing others to grab them would be bad. This I agree with in some respects.

However, there are some technologies that it would seem would be easy to come across within the confines of other groups. For instance, this one that you have been arguing about.[/QUOTE]

But then how do you define the uniqueness of a technology so that it can't be grabbed by another? The KIBC has given an unique advantage in nearly every KDF engagement. In fact, it is the only reason why the fleet survived in some cases. Based on its importance and uniqueness to the KDF, I can't agree that it would be easy to come across.

[QUOTE]taken from dictionary.com:
simple:
1. easy to understand, deal with, use, etc.: a simple matter; simple tools.
6. not complex or compound; single.

if you actually take the time to look it up, it says nothing being a relative term
[/QUOTE]

Simply because it isn't stated in the dictionary as being relative does not make it not so. For example, differientating equations is simple (or easy to understand) for me, but is not simple(or easy to understand) for a preschooler.

[QUOTE]networking computers together is nothing new, its a very SIMPLE concept and requires a very basic level of technology to accompish. in fact i am using a home network right now.

now the only slightly complicated part of the equasion is a little bit of software to plot a course around a few obstructions.
[/QUOTE]

Nothing wrong with the networking aspect of it; as Kach has stated, most factions do that already. But calculating hyperspace jumps, especially micro-jumps, is significantly more complicated than simply plotting a course around a few obstacles; if you're simply going to use an equation to make the jump, that's going to take a lot of time; As I've already stated, the Millenium Falcon's microjump at N'zoth took around twenty minutes to simply calculate its jump, and even then, it was still considered risky because the data taken for the calculations was considered already old by the time they were ready to make the jump.

Kach brings up a good point about the latest rendition of this being very vague on how it actually works. If it is simply both ships doing part of the calculations for a single ship, that's new, and then I have no problem with that, because that is different from the KIBC or other micro-jump technologies developed so far. But like Kach has also stated, that's going to take the ships a lot of time to compute still; roughly ten minutes if it's between two ships. The time to calculate will lessen with more ships doing part of the computations for one ship as well though.

Sorry Wilkar, I will start referring to as the Commonwealth from now on.

#56 2:11pm 08/10/06

[QUOTE]I/they will stick 10 miniutes of helplessness prepairing for hyperspace while I/they blast you[/QUOTE]


What the fuck is that supposed to mean?

#55 2:03pm 08/10/06

NOT VC!

COMMONWEALTH PLEASE!

#54 1:20pm 08/10/06

So here's Corises problem.

[QUOTE]Smart Comp
This is just an advanced version of a normal ship’s computer, it coordinates the efforts of all repair droids throughout the ship, sends sensor and navigational data, and, shield and system status to friendly units. Because navigational data is shared, the ship is able to plot microjumps within a solar system as long as a friendly ship equipped with a smart comp is in the desdination area. To preclude the possibility of jamming, all communications are routed through the QETS system, except when using traditional methods are required.[/QUOTE]

And the accusor...

[QUOTE]Integrated Kashan Battle Computer: The Integrated Kashan Battle Computer is actually multi-purpose network that is connected to every vessel of the Kashan Fleet, whether it is a patrol starfighter or a Seraph-class Cruiser. The main purpose of the Battle Computer is to intertwine, triangulate, and transmit sensor data collected from each ship.

This allows the ships to instantly gather target acquisition data and triangulate that data. The triangulation process ensures excellent target data, foiling most anti-targetting and sensor-jamming systems.

More importantly, the network can also provide navigational data from each ship along. Each vessel automatically transmits its location to the other vessel and shares navigational data with it as well. This allows the vessels of the Kashan fleet to act as navigation beacons for hyperspace jumps. As such, it is possible for Kashan ships to make instant intra-system micro-jumps to a Kashan vessel with the Battle Computer.[/QUOTE]

I can defenitly see Corises problem. In addition, I belive this "Smart Comp" shares a little bit with our own Multi-XMAP, but we are here to talk KIBS and Smarts, not XMAPs.

So is it plagurism? Honestly, if you guys didn't know, all ships in a flotilla share sensor, navigational, and all that other sorts of data, and that dont' do a damn for their calculation times. It's common sense. However, a KIBC works by using another ship as a "beacon" to home in on in a microjump. The SmartComp works by sending navigational data it has collected about the space around it to another ship (presumibly small gravitic or gravity or wahtever anamolys). How does this let you calculate a jump faster? We imperials have a bigass supercomputer hooked up to an ultraprecise navicomputer. Kashan has homing beacons taht allow ships to home in on them. You have... a sketchily detailed, origination suspect piece of equiptment that works by sending navigational data... I can sorta see how tha'd work. You could divide the calculations equally amoung the ship's two Navicomputers and cut the tiem in half... 10 miniutes. Woah! Dont' spend it all in one place. Against about any ship out there this thing woudl be vaped in taht time.

I seriously dont' see how tihs works. Give us/me some details dude, or Im going two write this off as a mere attempt... because any RP you do with me or somebody else with one of these, I/they will stick 10 miniutes of helplessness prepairing for hyperspace while I/they blast you. (Read Dolash's art of war for a little more on this one).

Need. MOre Information. To. Make. Good. Decision. eat. more. chikun.

1234>>>