Fighter Shanadigans

[Commodore_Areyar (OP)]

(moved from FAQ section)
C_Areyar:

My fighters do not show up in the industry-fighter pulldown.
The design seems to be according to the above criteria.

Code: [Select]


    Scurry class Scout    400 tons     25 Crew     60.4 BP      TCS 8  TH 36  EM 0
    4500 km/s     Armour 3-4     Shields 0-0     Sensors 3/1/0/0     Damage Control Rating 0     PPV 0
    Annual Failure Rate: 2%    IFR: 0%    Maintenance Capacity 47 MSP    Max Repair 9 MSP

    FTR Ion Engine E800 (1)    Power 36    Fuel Use 8000%    Signature 36    Armour 0    Exp 25%    Hyper Capable
    Fuel Capacity 50,000 Litres    Range 2.8 billion km   (7 days at full power)

    Active Search Sensor S6.93-R16 (1)     GPS 110.88     Range 1.1m km    Resolution 16
    Small LR Search Sensor S6.93-R1 (1)     GPS 6.93     Range 69k km    Resolution 1
    Thermal Sensor TH0.5-3 (1)     Sensitivity 3     Detect Sig Strength 1000:  3m km

    This design is classed as a military vessel for maintenance purposes


What am I overlooking?

(p.s. high armour is due to HW being in class7 nebula)

re: James Patten

I think you can research fighter-only versions of active search sensors.

re: Charlie Beeler

Actually I think is issue is the hyper drive added to the fighter engine.

re: C_Areyar:

@ scanners: No. that is only true for the beamfirecontrol systems.

@Hyperspeed: Nah. I have another nonfunctional design with an older fighterengine without the hyperspeed. Also if hypercapable engines were not allowed for fighters, it should not be possible to develop them.

Still a mystery.

Industry for fighter production is on.
I have FTR factories.
These 'fighters' can be built in the shipyard. Which leads me to think I have forgotten to check a box someplace which designates the design as a fighter.
(it is not the class hulltype, those are arbitrary)

edit: actually I checked and the hyper denial is not true, the engine I thought was normal actually has hyper as well.
I tested this now. An FTR engine without hyper capability makes the fighter text appear at the bottom of the summary.
SOLVED: Hypercapable FTR engines are not allowed on fighters and need to be built in a shipyard.

So, is this a bug?
The FTR signature in this case is misleading.
Be sure to add this bit of info in a future tutorial of FAQ on fighters.

Will the small ships (<500kt) with the hypedrives (if build in a shipyard) still be allowed to dock inside a hangar?

[Steve Walmsley]

if you can't figure this out (and I don't see an obvious answer), send me the DB and I will step through the design code to see why Aurora doesn't think its a fighter.

Steve

[Charlie Beeler]

I can confirm that a hyper capable fighter engine disallows the fighter designation.

[James Patten]

A ship will fit in a hanger bay no matter its size, as long as it is as large as or smaller than the hanger.  So a 2500 ton ship will fit in a 2500-ton hanger bay, or five 500 ton ships will.

As for putting hyper capability on a fighter, not a bad idea but I wouldn't see it used much, as I would think most combats take place in the inner system.

[Commodore_Areyar (OP)]

That is good to know. (about ships in hangar-space)
Another method to quickly bring extra ships into a system, circumventing the jump escort limit.

Also didn't know the hyper-limit was indicating an exclusionzone, never used the things yet.
I was hoping it was a way to go faster, but only within close proximity to the star, so that I could get my fighters in combatrange quicker.
Could be a good way to move in those huge systems or in extended doublestar systems though.