I don't know about 'infinite', but I waited a couple minutes with it selected, and the program never came back into focus.

hm, thats odd.

thank you .. i have seen this error today too.
but wihtout any pipe or console anywhere close or in any hotbar.

test output on that hotfix on Cent OS6 from

I just tried setting the frame cap to 30FPS, it didn't improve anything.

Here is a possible hotfix, place the attached file in "{StarMadeInstallDir}\native\linux" and replace the existing version. Let me know if this fixes the issue. Thanks{F8245}

Please try a fixed framerate.

In T1534#62919, @ghent96 wrote:

True, this is still a bug. Changing the key binding is not the solution, because the game is NOT recommending the key bindings correctly.

-confirmed-

It may be intended that all salvage beams don't instantly salvage like damage beams do.

That's a good point on the CPU usage, I didn't think about it when I wrote that, thanks.

-validated-

Duplicate. What you're seeing is an error message appearing in the wrong sector, somewhere nearby, or another loaded sector is the origin. See merged task for more details.

I'll put it on open, the stacktrace may be enough to fix it.

Would it be possible to hotfix this, as it is a game breaking bug?

Can you upload your settings.cfg file? It's located in the Starmade folder.
Drag and drop into the comment section to upload it.

Closing this task then.

For me it doesn't open when using Tab + F8 or when using shift + Tab + F8.
What version are you using?

Yeah, looks like missiles or an effect that caused this.
Putting stacktrace in description.

Merging into other relevant task.

Your CPU has 4 core. 400% should be your max cpu usage. 250% or so would be a reasonable number for a game that's never minimized (it's windowed).

-rejected-
no answer
assuming error on docking cross border.

Hardware/driver issue not game related

@RoyalWolfe .. do you have a logfile with that error ?
Please do add it here.

i have the same issue. i have tried re installing fresh and it works for one play cession, then suddenly it stops working. it gives an error that sound fails to initialize, then persists regardless of what i set it to.

True, this is still a bug. Changing the key binding is not the solution, because the game is NOT recommending the key bindings correctly.

Memory does not appear to be the problem. CPU usage is an unreal 200 - 250%. I also found that the game keeps going just fine while in the background. I had it displaying on half my screen, while I tabbed to a program on the other half. The game never visibly stuttered or anything, but I couldn't tab back, it was unresponsive, yet still playing.

Yes it now runs smooth @AndyP at 120fps but there is no sound :-)

I never once experienced this issue before that patch, but I can't 100% guarantee that is where it started. I wasn't playing as much around that time. So perhaps I shouldn't have said that.

First occurence is set to the main menu, does that mean that before that version, it was fine?
I don't see anything special in those logs but it might be a memory issue.

no answer

no answer, and assumed user error

concluded to be a player error

Agreed

i havnt seen that problem in Devbuild testing before release, and i cant reproduce it now either.
could you please add a Log.txt.x file from one of those occurences ? (sort by time stamp and choose one that matches)
to be found in {Starmade install folder}\logs
just drag and drop the file in here