Fractal Softworks Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Starsector 0.95.1a is out! (12/10/21); Blog post: The Pilgrim's Path (07/19/22)

Show Posts

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.

Topics - Klokinator

Pages: [1]
1
General Discussion / We seriously need better information QOL updates
« on: June 28, 2021, 04:50:16 PM »
I've put hundreds of hours into Starsector but there are a few things about it that really bug me. I've posted about the disconnect between the intel and map screens and how annoying it is, tabbing between them to look up info.



Today I want to talk about... missions.

Missions you accept from bars, specifically.

There is often a complete dearth of really important information in many missions, but bounties and deliveries are awful. Anything that involves "hey you, go to X place and do Y thing" is the worst. Just look at that image.

My target is 15 light years away, in a star system with a randomly generated name. Which one? What direction? All I have is distance and a name.

This issue could be solved by taking the entire mass of empty screen space to the right and left and showing a small window to the left or right indicating where you need to go.

This is what it should show for maximum info:


(Pretend it's showing the correct system because I spent 5 minutes hunting for pixels on the map and couldn't find it, which is why I'm making this post)

Of course, my monitor is 1440p, so you'd have to deal with some size restrictions. What I've shown above is my 'ideal scenario.' You show me a map with a directional indicator leading to the objective.

However, if this is not possible, there is another thing you could do, which is much less user-friendly but still better than what we have now.



Just... put a little arrow pointing in the general direction right next to the lightyear distance.

"It's 32 lightyears northwest of here."

It's still not awesome because to look for the exact system, I have to exit out of all the menus and open up my map/intel to find the system and ensure I can reach it... but it's a decent compromise.

Please, I want to enjoy bounties, trade deliveries, and other such things, but the current implementation makes many of those unpleasant to deal with on a per-case basis. This can definitely be improved.

2
When blowing up ships during a battle, I have this weird issue where every single non-fighter ship causes the entire screen to flash stupidly bright white when destroying them. In past versions, I remember blowing up a MEGA freighter or a BIG space station would cause like a big flash of light. You know, because they're frigging huge and it's a big moment.

But now it's like... oh I just blew up three rinky dinky little Hounds. Guess I can't see my screen for three seconds. Oh, and there went five more enemy ships. Guess I'm just going to have to sit here and wait until I can see my screen again.

Is there a way to modify when the screen flashes? I don't mind if blowing up a capital ship, mine or the enmy's, causes a flash. I do mind, however, if every single no-name skipper melting under a volley of gunfire blinds me in a dying blaze of glory.

3
Suggestions / Can you add a toggle to stop auto-hiding UI elements?
« on: December 04, 2020, 02:22:33 AM »
Right now, the game does this one really annoying thing I don't like.

This is what the UI normally looks like.


This is what the UI looks like when you're flying around.


It hides the personnel, the crew, the marines, and the cargo hold. You can see it if you open up the inventory or something, but still. I don't ever want it hidden, yet when I asked on the discord I found that the UI elements are hardcoded so I can't even mod this change in.

Can you add some sort of a toggle so this bit of the UI doesn't auto-hide? Many thanks!

4
Bug Reports & Support / Infinite, unending battle bug
« on: November 02, 2019, 12:52:47 AM »
This is a really simple, but absolutely awful bug I just found.

Steps to replicate it:

1. Fight a very long battle wherein your flagship is reduced to an insanely slow speed.
2. Order everyone to retreat. Get frustrated at how slowly your flagship is retreating.
3. Transfer command from your flagship at the north end of the map to a ship retreating at the south end.

If all succeeds, your 'commander pod' will fly down to that ship, the last ship to retreat to on the map, right as they retreat. With your target gone, your commander will fly around in circles aimlessly forever. Since my flagship also got destroyed, I had no way to simply end the battle.

All the enemy ships are gone, as are mine. My commander is just flying around like a chicken with his head cut off. I have to just exit the campaign now, losing a solid 45 minutes of battle time. Sigh.

Pic:

https://i.imgur.com/SJReXPY.jpg

5
Suggestions / Having an issue with the combat camera.
« on: November 01, 2019, 01:00:26 PM »
Whenever I enter combat, here is my general flow.

1. Deploy ships.
2. Press Tab, issue orders to those ships.
3. Press F to follow one ship's POV.

I don't like to play as a ship if I don't have to, since the top-downRTS-commander angle appeals more to me. Anyway, once I reach step three, this is where the problem occurs.

If I am viewing the game through a ship's video feed, I press tab (to issue orders or whatever) and press tab again, my view is no longer fixed on the ship, but instead jumps to the very bottom of the screen at the middle. I can press F and view a ship again with F, but if I tab to the overview screen and tab out, I always get forced back to the bottom.

I don't think I have a way to pan the camera, do I? I'm not sure if I'm doing something wrong, if this is a knopwn issue, or if I'm missing something really obvious. Why would tabbing in and out of the overview menu yank my camera to the bottom middle of the battlefield?

This section, for reference:

https://i.imgur.com/ir3PoCW.jpg
https://i.imgur.com/1ByFMHG.jpg

Note: I have six mods installed.



These might be causing the issue, but I think I had the problem before installing them.

Pages: [1]