#Improve the repair sequence.

32 messages · Page 1 of 1 (latest)

charred marsh
#

Now, if you need to repair a succession of blocks one after another, the material for the first block will first be searched, after it is dragged and installed, the search for material for the next block begins, etc.
It turns out that to build a line from the skeleton of a ship 1 cell wide and 10 cells long, only 1 worker will always be used and this is incredibly long.
Solutions. You already have a count of materials for all repairs, as well as the pc sees where they are nearby. Let all the workers allowed for construction be used and the sequence of construction calculated
from one block to another and the workers will already be waiting with materials at their place where they need to be attached and attached as the structure grows. That increase the speed of construction many times over.

clever onyx
#

How CPU intensive would this get on larger ships though?

charred marsh
# clever onyx How CPU intensive would this get on larger ships though?

And it does not matter for the processor how large the ship is. The beginning of the queue is randomly chosen starting from the entrance hatch. But most importantly, as I said, all workers capable of construction should be involved and a chain should be built according to their number. The chain is built, the next chain is being built.

stone hinge
#

If I'm understanding the suggestion correctly this would likely be highly CPU intensive and could cause other problems such as crew getting stuck waiting for something that'll never arrive.

charred marsh
# stone hinge If I'm understanding the suggestion correctly this would likely be *highly* CPU ...

You already had a loader beam getting stuck when the place was already taken for this, but you solved this issue by canceling the task. I think there is a solution here too. For example, take all workers minus 1. This worker will repeat the task of the one who could not do something. You can find solutions, the main thing is to start doing. Because what is happening now is not playable. You need to wait real seconds 40 until the construction of one small thin frame is completed at a speed of 8x. One worker runs after a kilometer for one material, puts it in its place, then fly again for a kilometer, and so on, and everyone looks at him as he, the poor little one, is doing this .. Something must be done with this. I'm not saying that during construction, out of 1200 possible builders, 300 are employed. The rest are resting. Why should the processor be loaded? He has already calculated how many materials are needed, he already knows where they are. Everything is already done. It remains to instruct the workers to take these materials and take the finished construction sequence directly from the ship's plan.

stone hinge
#

The problem, as always, is in crew pathing. Lets take a very simple example of building 6 structure tiles in a row; if only 3 crew are available, how does the game figure out what structure tiles should be built first and which shouldn't? What happens if a crewmember is carrying resources to a tile, but a crewmember that's supposed to build the adjacent tile dies or is rerouted? To avoid a large number of different situations where crew either take horribly inefficient paths or get stuck entirely, the game would need to run connectivity checks on every queued job, with each check getting more expensive the more jobs there already are. It might not matter on a small scale but it could destroy performance with larger edits (which are already laggy to begin with). Additionally those connectivity checks would need to be run very frequently, otherwise if jobs do need to get rerouted it could take a long time for crew to even realise that they need to change destinations.

charred marsh
# stone hinge The problem, as always, is in crew pathing. Lets take a very simple example of b...

Let's be honest with ourselves. I do not want to offend you, but I want to dot the i's. All your excuses are not aimed at improving this wonderful game. And they are aimed at preserving the existing code so as not to remake it. You are not trying to independently answer the questions asked, the answers to which you know better than I do. I gave you an idea, please develop it yourself. I repeat once again, 40 seconds, at a speed of 8x, waiting for one worker to build a line from the frame is unacceptable.

woeful oxide
#

Yikes dude. That wasn't very polite, and especially not how you ask for a favour.
I don't think that it's much of a stretch to say that the game devs have a much better idea than you or I (or most people really) of how the coding of the crew systems work and what kinds of changes might be likely to cause performance/other problems.
Like yeah, I think a lot of people might agree that increasing construction speed would be great, especially for risky mid-combat situations where we might have to risk being stationary in order to repair/modify our ship. I personally think that there's a lot of great potential for different situations, if it were fast enough to be viable. But being demanding towards the devs isn't how to go about getting it implemented, especially after they've explained in detail why it could cause problems.

#

Perhaps if you make a mod that changes construction to work this way without being CPU intensive or causing other problems, it could be a good demonstration about how it's possible.
Especially since you seem to already know all about what the processor has already calculated and all that 🙂

charred marsh
# woeful oxide Yikes dude. That wasn't very polite, and especially not how you ask for a favour...

You have not quite the right idea who owes whom. It's their game, they make money from it. And we are only guests and people who pay them this money. The more we like the game, the more profitable it is for them. Therefore, the fact that I'm trying to improve their game here, wasting my time, desire for free - It's like a big gift to them, and they're not doing me a favor. I hope I've made the obvious clear. It was for this that Walt was grateful in his monologue on YouTube. How could it all be changed.. And when I say that it needs to be fixed, it means that it really sucks. This shouldn't happen in a good game. And no matter how they fix it, it just shouldn't be. Unless, of course, they really want to make a great game. I'm 40 years old, I've played a lot of games in my life, and I know what I'm talking about. And this discord was created precisely for the purpose of having a feedback for the creators of the game.

woeful oxide
#

Yeah the discord was made for feedback, and you'll notice that there's a lot of it quite regularly. "I've played a lot of games and I know what I'm talking about" doesn't make your particular suggestion more important than everybody else's, nor does it excuse being rude.
Your idea was pretty good in principle, and you got a response straight from the devs which is more than a lot of suggestions get. But when the devs say that something isn't particularly likely/plausible atm, acting entitled and demanding that they figure out a way to fix it anyway really isn't the gift you think it is.
Genuinely, disagreeing is usually totally fine, but it costs you nothing to be polite about it.

#

On a more on-topic note; your specific "one cell wide, x cells long" scenario is, as far as I understand how construction works, the actual worst/slowest case scenario (since only one piece can be constructed at a time) and isn't representative of how long construction usually takes in gameplay.
One suggestion that might help if you happen to actually be in this scenario often is:
Try ejecting the required resources from your ship and position the ship such that the resources sit next to/on top of what you're trying to construct. This should drastically reduce the travel time of the single working crew member and so hopefully speed up the construction 🙂
(that is, if I'm correctly understanding how it works)

charred marsh
drowsy arrow
#

Gonna be honest, i agree with Yellow Pirate, suggestions are fine, being an ass about it isnt. To further that, flaunting your age and "experience" is just immature. Suggestions are cool, telling the devs theyre making excuses when they are giving you legitimate reasoning on why that wouldnt work is not very respectful.

woeful oxide
#

Nah dude, I just think that its a good idea to be respectful to people is all, especially those who you want to listen to your opinion.
I'm under the impression that that's generally the norm?

And also rule 15 is "be courteous and respectful to others" so 🤷

charred marsh
oak sigil
oak sigil
oak sigil
#

Walt has his own time and just because we suggest something shouldn’t mean it forcibly is added to the game with him listening to every little idea you say just because you don’t like how his game currently works

woeful oxide
# charred marsh If you are not a developer, please do not answer for them. This puts them in an ...

  • I didn't answer for the devs, they answered for themselves. You just didn't like their answer and said they were making excuses

  • This is a public forum, a space where anybody can comment on whatever suggested ideas they wish to, this was never private or "someone else's conversation"

  • If you so dislike the idea of being told that you were impolite and the suggestion to not do that, consider next time preventing the occurrence by being polite in the first place 🙂

  • Additionally, a genuine question. Do you aim to specifically be impolite? and if not, is there any reason to not just acknowledge that it was a mistake, say you'll do better in the future, and move on?
    Otherwise it definitely feels like your lack of manners is deliberate

drowsy arrow
#

Wasnt expecting Azler to agree with me, but hes right. The devs are busy, and theyve already worked very hard for us. To further that, Yellow Pirate never answered for the devs, your just angry, immature, and disrespectful.

woeful oxide
#

Thanks gang, glad to see others advocating for respect too NODDERS

Anyway Leonis, I hope the suggestion of ejecting resources and putting them over the build site is helpful enough to at least alleviate the duration problem somewhat 🙂

white scarab
#

leonis, if you are having problems with it taking too long and not being an enjoyable experience for you with the current crew construction, my recommendation for now is that you play without crew construction enabled, it is a selectable option before starting a career game,

#

with this all construction is instant

jade spire
#

Let's not be so self centerd, just because you give a suggestions does not make you entitled to have it be done, Redstone knows a lot about the back end of the game and Walts goal is to make the game run as smoothly as possible, expally for potato PC's, I'm sure Walt over the 10+ years of working on this game has made it as best as it could be amd ram through 100's of changes and re-wrightings.

stone hinge
# charred marsh Let's be honest with ourselves. I do not want to offend you, but I want to dot t...

I don't actually work on any code directly, so implying (whether intentional or not) that my goal is to do less work doesn't really apply. All I'm trying to do is explain why seemingly-simple solutions to some of the game's problems wouldn't actually work out well. There are a lot of things that sound really easy to add but end up being coding nightmares, such as "crew can build doors without going EVA", which was such a problem it ended up being entirely scrapped.

Regarding the actual problem, I'm happy to try and help come up with a solution, I just don't think that "always queue crew in advance" is a good one. Crew building speed could certainly use improvement, but we need to be very careful about improvements that don't consistently help, or have a major downside (such as lag or pulling too many crew).

charred marsh
charred marsh
white scarab
#

Pretty sure that message wasn't an insult

oak sigil
woeful oxide