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

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

1

Suggestions / More weapon groups and new firing mode

« on: March 11, 2012, 04:02:36 AM »

When I get to the larger ships I often find myself wanting more weapon groups than just the four. Take the onslaught for example; it could easily use 6-7 different weapon groups (one for PD, one for the small/medium turrets, one for the large turrets, one for the large hardpoints, up to four different missile types). With only four groups you have to choose between flexibility (different kinds of weapons) and control (which weapons to use, flux management etc).

I'd also like to be able to set a weapon group to a third firing mode, "selected", which fires the weapons when you try to select the group (without actually switching weapon group selection). This is mainly for missiles, where you don't really have a need to have the group selected for some time, you just need to shoot something real quick before going back to your cannons.

2

Bug Reports & Support / 0.51a - Unavoidable collisions on spawn

« on: March 09, 2012, 04:24:46 AM »

Sometimes a ship will spawn directly behind another ship. Sometimes both these ships are large. Sometimes the ship in back is faster than the one in front. This creates many near-collisions, and some entirely unavoidable collisions. Since the ships are off-field, there's nothing you can do to stop or swerve.

Once I spawned in an Odysseus behind an Eagle, and they appeared to spawn inside eachother, taking continous damage until they were both on the field and the collision resolved itself.

3

Bug Reports & Support / Re: Java Heap Space

« on: March 04, 2012, 02:40:33 AM »

I haven't tried this to see if it actually works, but in the installation folder there's a file called "vmparams". Open this in notepad and look for the part that says "-Xmx256m" and try increasing the 256 to something higher like 512 (this, plus the -Xms256m part, is the max amount of memory the program can use). This could result in some slowdowns, especially if you don't actually have that much memory. If you still get the same error after increasing the memory, increasing it further probably won't help for long.