Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Salmeuk]

First contact with baddies. First time using the combat system. I ended up detaching my TIE fighters from the task group then reattaching them. It worked well, five enemy warships down only losing 5 TIE fighters.

You should post your tie specs, I'd like to see!

[RAM]

For my fighter:

Code: [Select]

TIE 1 class Fighter    442 tons     3 Crew     88.9 BP      TCS 8.84  TH 75  EM 0
11312 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 0     PPV 4
Maint Life 0 Years     MSP 0    AFR 88%    IFR 1.2%    1YR 14    5YR 206    Max Repair 31.25 MSP
Intended Deployment Time: 0.1 months    Spare Berths 1   

TIE Engine (2)    Power 50    Fuel Use 154.08%    Signature 37.5    Exp 12%
Fuel Capacity 5 000 Litres    Range 1.3 billion km   (32 hours at full power)

Hephaistos 15cm C1 Soft X-ray Laser (1)    Range 30 000km     TS: 11312 km/s     Power 6-1     RM 6    ROF 30        6 6 6 0 0 0 0 0 0 0
TIE Fire Control (1)    Max Range: 30 000 km   TS: 6000 km/s     67 33 0 0 0 0 0 0 0 0
NanoTrasen NT Stellarator Fusion tiny (1)     Total Power Output 0.6    Armour 0    Exp 5%

This design is classed as a Fighter for production, combat and maintenance purposesIs this good? I plan on mass producing them and using them as meatshields. Are engineering spaces necessary on fighters?

I plan on having my DS be in a battlegroup with 2 star destroyers and all three hold lots of these things

[Micro102]

For my fighter:

Code: [Select]

TIE 1 class Fighter    442 tons     3 Crew     88.9 BP      TCS 8.84  TH 75  EM 0
11312 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 0     PPV 4
Maint Life 0 Years     MSP 0    AFR 88%    IFR 1.2%    1YR 14    5YR 206    Max Repair 31.25 MSP
Intended Deployment Time: 0.1 months    Spare Berths 1   

TIE Engine (2)    Power 50    Fuel Use 154.08%    Signature 37.5    Exp 12%
Fuel Capacity 5 000 Litres    Range 1.3 billion km   (32 hours at full power)

Hephaistos 15cm C1 Soft X-ray Laser (1)    Range 30 000km     TS: 11312 km/s     Power 6-1     RM 6    ROF 30        6 6 6 0 0 0 0 0 0 0
TIE Fire Control (1)    Max Range: 30 000 km   TS: 6000 km/s     67 33 0 0 0 0 0 0 0 0
NanoTrasen NT Stellarator Fusion tiny (1)     Total Power Output 0.6    Armour 0    Exp 5%

This design is classed as a Fighter for production, combat and maintenance purposesIs this good? I plan on mass producing them and using them as meatshields. Are engineering spaces necessary on fighters?

I plan on having my DS be in a battlegroup with 2 star destroyers and all three hold lots of these things

Do you need that much AFR on a fighter? I picture them being out of their mothership for only a few hours at most.

[Mini]

You will note that the maintenance life is 0, and it has 0 MSP, so it already doesn't have any maintenance spaces.

[coleslaw35]

Gah! I made a game where there were three nations on Earth so that I could test out ground combat. Well, I took over one of them, but their population grows faster than I can produce enough units in order to force their surrender. I tried bombing them from orbit with my missiles, but that literally did nothing except increase the radiation and dust in the atmosphere. How can I deal with the pesky population that I want to subjugate?

[Insanegame27]

For my fighter:

Code: [Select]

TIE 1 class Fighter    442 tons     3 Crew     88.9 BP      TCS 8.84  TH 75  EM 0
11312 km/s     Armour 1-5     Shields 0-0     Sensors 1/1/0/0     Damage Control Rating 0     PPV 4
Maint Life 0 Years     MSP 0    AFR 88%    IFR 1.2%    1YR 14    5YR 206    Max Repair 31.25 MSP
Intended Deployment Time: 0.1 months    Spare Berths 1   

TIE Engine (2)    Power 50    Fuel Use 154.08%    Signature 37.5    Exp 12%
Fuel Capacity 5 000 Litres    Range 1.3 billion km   (32 hours at full power)

Hephaistos 15cm C1 Soft X-ray Laser (1)    Range 30 000km     TS: 11312 km/s     Power 6-1     RM 6    ROF 30        6 6 6 0 0 0 0 0 0 0
TIE Fire Control (1)    Max Range: 30 000 km   TS: 6000 km/s     67 33 0 0 0 0 0 0 0 0
NanoTrasen NT Stellarator Fusion tiny (1)     Total Power Output 0.6    Armour 0    Exp 5%

This design is classed as a Fighter for production, combat and maintenance purposesIs this good? I plan on mass producing them and using them as meatshields. Are engineering spaces necessary on fighters?

I plan on having my DS be in a battlegroup with 2 star destroyers and all three hold lots of these things

Do you need that much AFR on a fighter? I picture them being out of their mothership for only a few hours at most.

That's not entirely correct... I made a new game and SM'd me to the top tier in most things. Difficulty at 500%

[bluephoenix]

Has anyone here ever installed "RAMDisk"?
If so have you noticed any performance increase/turns loading faster?

[Reverie]

*picture snip*
Here, have an infographic on the positioning and make-up of my fleets, in the Ship Illustration Style

This is really nice! It looks like you put a lot of thought into your designs :-)

[Paul]

Has anyone here ever installed "RAMDisk"?
If so have you noticed any performance increase/turns loading faster?

I have that set up for my temporary internet files. Makes browsing a bit quicker, and has the benefit of automatically flushing everything on a reboot.

To get that to work you'd likely have to put Aurora on your RAMdisk manually and run it from there. I haven't tried that for fear of my computer crashing or something and losing my Aurora save, lol. Not sure if it would speed things up or not. Depends if it's database read/writes that are taking time or the actual processor needing to compute stuff that's the bottleneck.

[Grunden]

Has anyone here ever installed "RAMDisk"?
If so have you noticed any performance increase/turns loading faster?

It can significantly speed things up. Aurora uses .mdb files (the Microsoft Access datbase format) which is notoriously disk intensive. Aurora itself is not optimized to write changes to memory and then write to disk at some later point, it is constantly writing to disk everytime *anything* changes. Batch files can help automate the ramdisk launch/shutdown process.

[jocan2003]

Has anyone here ever installed "RAMDisk"?
If so have you noticed any performance increase/turns loading faster?

I heard from a few source that it didnt change anything, i am using a solid state disk wich is quite faster than normal drive and yet havent found much difference.

[bluephoenix]

Ah okay, thanks.

[gomez]

Has anyone here ever installed "RAMDisk"?
If so have you noticed any performance increase/turns loading faster?

I tried using a Ramdisk but at the end of the first year I got disk accesess errors.  At the end of each december Aurora dumps all the Event window text for the year in to a log file in C:/logs.
Yes you read that right, C:/logs.

When you use a ramdrive it  tries to make a symlink in the root of the ramdrive to C:/logs and fails horribly.

[forsaken1111]

Has anyone here ever installed "RAMDisk"?
If so have you noticed any performance increase/turns loading faster?

I tried using a Ramdisk but at the end of the first year I got disk accesess errors.  At the end of each december Aurora dumps all the Event window text for the year in to a log file in C:/logs.
Yes you read that right, C:/logs.

When you use a ramdrive it  tries to make a symlink in the root of the ramdrive to C:/logs and fails horribly.

I've played Aurora quite a bit and I have no c:\logs file...?

[Karlito]

Really? I have a bunch of old aurora campaign messages dumped in c:\logs