[X] Try the XM4s - they might have issues, but who doesn't want a particle gun?
(Nobody rolled for gun rating, so: XM4 Rating Roll 1d4 = 4)
With only a small amount of fuss, the guns arrive; you note the look of frankly unholy glee on Carson's face with mild worry. After some work getting everything linked up, the team powers on the guns for an initial test.
[Systems Integration: 1d10 (Technician Mod. +2, Weapon Specialist Mod. +2) = 12 - Great Success!]
The blasters power on and link with the systems as if custom-made for them; power draw and heat tests indicate few, if any, problems. Thus, with the major systems mostly sorted, two prototypes are constructed, dubbed 2347-A and 2347-B. [Weapon Rating +1.]
Two UNF test pilots are shipped in to the plant to put the fighter through its paces. Major Don Lewis, taking the first prototype up, runs it through a standard regimen of maneuvering and performance tests, never exceeding twenty klicks altitude.
[Prototyping roll: 1d10 = 1 - Critical Failure!]
Things seem to be going well, right up until you spot the distinctive flare of an ejection seat - followed by the prototype exploding. Not the greatest start.
Lewis proves both unharmed and unshaken, dispassionately noting after the fact that the engine fire warnings went off, followed by power converter overheat warning - at which point the auto-eject kicked in.
Speculating, Carson theorizes that the engine fires must have blown the fuel tanks; Jardin (waist-deep in the other prototype) notes that he isn't finding anything that might have caused both engines to turn themselves into impromptu firebombs.
[Analysis and Troubleshooting: 1d10 (Technician Mod. +2) = 11 - Great Success!]
Blant, going over the engine plans and fuel system, eventually finds the problem - the time-squeeze had resulted in incorrect fuel pumps being installed, leading to an excess of fuel in the reaction chambers - the subsequent overheat-rapidly-turned-fire had ignited the fuel lines, and by extension, tanks.
After some quick (and very heated) words with the parts warehouse, correct fuel pumps are procured and installed; Lewis once again takes the ship up for basic flight tests.
[Prototyping roll: 1d10 (Troubleshooting Mod. +2) = 9 - Great Success!]
Without the engine-bombs, the second craft performs near-flawlessly; meeting the requirements and exceeding them, especially in the acceleration and speed specs. After several days of flight testing, Lewis gives his seal of approval, and the other pilot - Captain Pavan Chatwal, takes over. After some brief familiarization flights, he takes the ship out to the test range.
[Prototyping roll: 1d10 (Weapon Rating Mod. +5) = 6 - Success.]
The guns perform well - engaging both ground and air targets, the particle blasters quite handily melt large holes in most of the unarmoured targets, and leave glowing-hot armour on the rest. Chatwal notes the guns are somewhat slow to recharge, it's not a massive issue, especially given the damage-per-shot.
Further testing confirms the four external hardpoints work as expected - hardly a surprise, given their simplicity - and from there, Lewis takes over once more for space tests.
[Prototyping roll: 1d10 (Troubleshooting Mod. +2) = 7 - Success]
Ascent and descent flights go smoothly - maneuvering tests indicate minor problems with the flight control system, but Lewis seems satisfied regardless. Range proves limited - again, not considered an issue - but the pilot notes that combat endurance lacks somewhat, especially with the powerful, but fuel-hungry, engines.
With prototyping mostly complete, you ponder - you have just enough time to make tweaks to one system, in hopes of improving the performance.
[] Leave it as-is; you'd rather not risk delays.
[] Rework the FCS - satisfactory it may be, but you strive for good - even great.
[] Other; attempt to rework another system? (Specify.)
Additional vote:
[] Suggest a name for the fighter.
Current Summary:
Project 2347-12 Light Fighter
Propulsion 3
Systems 1
Weapons 5
Reputation 0
Total Rating 9
Note: Continuing as-is will lead to acceptance trials and evaluation; reworking a system does include the possibility of delays, which will negatively impact Reputation.
