Attempting to rename the United Earth Defense Vessel crashes the game

damocles2209

As per the topic title, any attempt to rename the United Earth Defense Vessel crashes the game. This crash is reproduceable and occurs whenever an attempt is made.

baucoin

Known issue, no word on when a fix will be incoming.

azrael

When the term "known issue" is mentioned, it usually implies something that devs are going to be constantly working to remedy, unless it is minor and doesn't cause game-breaking issues. In this case, however, the simple act of renaming a ship becomes a game of Russian roulette (where firing the bullet = game crash), so it definitely qualifies as significantly more than minor.

I would likely expect a patch to fix this within the next few days. Until then, just...don't rename any ships you get. Better to just deal with the sometimes clunky names (and have a functional ship) than try for that last bit of immersion/personalization and risk crashing your game.

Whilst this bug is somewhat annoying (really want to rename that To'Duj fighter I just claimed, but...meh, it is what it is), it is NOT game-breaking as long as you don't attempt to rename any ships.

I can append my previous statement about how you can safely rename any ship that requires a prefix--it does NOT hold true for small craft; they seem to still crash even if they are a prefix-mandatory craft.

unrealt

Like the OP and the topic title, But it appears its any attempt to rename a few ships crashes the game with a crash report. This crash is also reproduceable and occurs whenever an attempt is made. Its known and on X

https://twitter.com/trekonlinegame/status/1808190597762633985

Star Trek Online
@trekonlinegame
There's currently an issue on all platforms where attempting to rename any of your ships will cause a crash. We are working on a fix right now, but until then, we recommend not renaming any ship.

azrael

Could I please ask a community manager to merge all these related threads (and any future ones--there are going to be more, trust me)?

icetyger1

Worked fine after the Patch on Tuesday 2nd July evening. Bought a new Fleet ship as our fleet unlocked Tier 5 Shipyard. Renamed the new ship. No trouble. Next day. Lobi Sale. Bought two Ships from the Lobi store I'd be waiting for a sale, to buy them. A T6 and a Shuttle. Any attempt accessing the renaming UI result in the game crashing. Noticed while looking for this issue here that Players on Xbox one have the same issue.

ktstgt

I'm encountering constant crashes for a few days now on any ship with different accounts. The crash log reflects the attempts to rename a vessel:

240626 22:41:37 799 Client[P[13626992@33983712 Char1@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240627 11:55:11 503 Client[P[13626992@33983712 Char1@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240627 14:00:12 454 Client[33983712]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240627 22:16:32 811 Client[P[13626992@33983712 Char1@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240628 06:01:00 495 Client[P[13655082@33983712 Char2@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240628 12:15:34 686 Client[P[13667872@33983712 Char3@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240628 13:57:27 455 Client[33986673]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240628 22:38:47 818 Client[P[13667872@33983712 Char3@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240629 18:53:12 947 Client[P[13655082@33983712 Char2@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240629 22:02:15 548 Client[33983712]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240630 16:04:29 889 Client[P[13626992@33983712 Char1@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240630 21:58:41 642 Client[P[13626992@33983712 Char1@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240701 09:50:30 658 Client[P[13626992@33983712 Char1@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240701 18:33:24 825 Client[P[13655082@33983712 Char2@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240701 21:43:06 660 Client[P[13667872@33983712 Char3@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240702 08:09:07 485 Client[P[13667872@33983712 Char3@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240702 11:09:09 463 Client[P[13626992@33983712 Char1@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240702 13:29:12 563 Client[P[13626992@33983712 Char1@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240702 14:29:01 444 Client[0]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240702 15:04:02 444 Client[0]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240702 15:09:50 444 Client[0]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240702 23:10:27 481 Client[33983712]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240703 10:45:12 663 Client[P[13655082@33983712 Char2@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240703 11:17:03 463 Client[P[13678942@33983712 Char4@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240703 12:22:03 447 Client[P[13655082@33983712 Char2@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240703 17:54:59 600 Client[P[13678491@33986673 Char5@account_two]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240703 18:18:28 459 Client[P[13630169@33986673 Char6@account_two]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240703 23:31:39 606 Client[P[13678942@33983712 Char4@account_one]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
240704 13:10:27 522 Client[33983712]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()

The names are anonymized. The issue popped up a few days before I authorized the second account on my pc (see bottom of the log). The account owner of the second accound has renamed one of his vessels a few minutes ago, while I still can't do the same, so it's rather not related to the server implementation, accounts, or vessel types.