[Linux] BATTLETECH - Infinite loading

[Kvalme]

One line summary of your issue
Inifinite loading

What platform are you running the game on?

Steam

What operating system do you use?
Ubuntu 18.04
What version are you running?
public_beta_linux

Please explain your issue is in as much detail as possible.
Game starts fine, but loading battle takes infinite time (both campaign and skirmish).

Unable to find any log files in same location as in windows. Where can i find output log in linux?

Steps to reproduce the issue
Start game.
Start skirmish.

Attach DxDiag (PC) or System Info (Mac)

Attach Output Log

Attach Crash Log

Attach save file

Attach screenshot / video

 

[cellisten]

Same problem here and same question, where can I find the log? I logged into my Paradox account to start with.

 

[cellisten]

I have now tried to do a clean install (including deleting all local files that I could find) and that didn't help. When I try a skirmish battle I get to the ready your lance screen. After that I'm back to infinite loading but at least the prepping for combat screen comes up. The mech bay loads.

 

[blackcoffeerider]

I have the very same problem.

Since i found no information on which log file to attach i tried to find open log files like this:

lsof -F -p `ps x | grep -i battletech | grep -v grep | cut -f 1 -d " " |
tr '\n' ','` | grep log | sort -u | cut -c2-​

this is all one line and should tell you where any file open by the battletech executable containing "log" in its name - it only gave me the Player.log - not sure if that is of any help to the developers.

The CPU usage is periodically spiking to 100% on the core running the executable and then dropping again.
For system specs please check the steam system info.

If i can provide any additional information please let me know.


Regards,

Martin

 

[Lugh]

Had the same problem.
If you put: LC_ALL=C %command% into your launch options it should work the way it is supposed to.
Hope this will be fixed for the final release.

 

[AndrewT]

FYI the game log file for the Linux version is at:
~/.config/unity3d/Harebrained Schemes/BATTLETECH/Player.log

I have seen other reports of this happening with the new Linux version, it will need an update to fix I am sure.

 

[Kvalme]

Using LC_ALL=C solved this issue for me. I was able to start skirmish. Thanks, Lugh!

 

[Gagis]

I experience the same issue. The infinite loading starts at either directly after choosing settings for starting a new campaign or when launching a skirmish match.

I have tried a clean install, wiping all additional data I can find and even asked customer support to wipe the remote data associated with my Paradox account. Additionally I have tried both Native and Steam Runtime versions of Steam executable and various in game settings. Nothing has resulted in changed behiaviour and this seems to be a rather critical bug in the game itself. I just noticed the LC_ALL=C thing here and I'll test it too once I get home from work.

EDIT: LC_ALL=C works and everything seems to be working well. What a weird workaround.

The relevant error from my Player.log for reference:

Spoiler: Player.log exerpt

MessageCenter [ERROR] CRITICAL ERROR, PLEASE REPORT:
Delegate RespondToDefsLoadComplete - Standard for message type DataManagerLoadCompleteMessage failed with exception
Unknown char: .
at System.Double.Parse (System.String s, NumberStyles style, IFormatProvider provider) [0x00000] in <filename unknown>:0
at System.Single.Parse (System.String s, IFormatProvider provider) [0x00000] in <filename unknown>:0
at System.Convert.ToSingle (System.String value, IFormatProvider provider) [0x00000] in <filename unknown>:0
at System.String.System.IConvertible.ToSingle (IFormatProvider provider) [0x00000] in <filename unknown>:0
at System.Convert.ToType (System.Object value, System.Type conversionType, IFormatProvider provider, Boolean try_target_to_type) [0x00000] in <filename unknown>:0
at System.Convert.ChangeType (System.Object value, System.Type conversionType) [0x00000] in <filename unknown>:0
at HBS.Util.JSONSerializationUtility.ConvertValue (System.Type targetType, System.Object value) [0x00000] in <filename unknown>:0
at BattleTech.SimGameConstantOverride.ApplyOverride (System.String constantType, System.String constantName) [0x00000] in <filename unknown>:0
at BattleTech.SimGameConstantOverride.AddOverride (System.String constantType, System.String key, System.Object value, Boolean apply) [0x00000] in <filename unknown>:0
at BattleTech.SimGameConstantOverride.AddOverride (BattleTech.DifficultySetting setting, Int32 idx, Boolean apply) [0x00000] in <filename unknown>:0
at BattleTech.SimGameDifficulty.ApplySetting (BattleTech.DifficultySetting setting, Int32 index, Boolean force, Boolean apply, Boolean refreshDifficulty) [0x00000] in <filename unknown>:0
at BattleTech.SimGameDifficulty.ApplyAllSettings (Boolean apply) [0x00000] in <filename unknown>:0
at BattleTech.SimGameState.InitializeDataFromDefs () [0x00000] in <filename unknown>:0
at BattleTech.SimGameState._OnDefsLoadComplete () [0x00000] in <filename unknown>:0
at BattleTech.SimGameState.RespondToDefsLoadComplete (.MessageCenterMessage message) [0x00000] in <filename unknown>:0
at MessageCenter.SendMessagesForType (MessageCenterMessageType messageType, .MessageCenterMessage message) [0x00000] in <filename unknown>:0

Stopping ThreadPool

Threadpool stopped

Internal: There are remaining Allocations on the JobTempAlloc. This is a leak, and will impact performance

I am running the game on Arch Linux with latest updates to Kernel and Nvidia drivers, with GTX 970, previous generation i5 and 16gb of DDR4 memory.

The game's Windows version by the way runs fine on top of WINE.

 

[forlornwongraven]

Lugh's work around fixed this for me as well. Thanks!

 

[Sarios]

Had the same problem.
If you put: LC_ALL=C %command% into your launch options it should work the way it is supposed to.
Hope this will be fixed for the final release.

HEY, thanks for putting this up. I had a guy on steam having this exact same issue and this solved it for him. So its not posted up on steam as well.

 

[Raizok]

Can confirm:
- same OS, distro as the OP
- exact same issue as per OP's description
- setting LC_ALL also works around and allows to load (recommend having a non-American-English-locale machine in the QA pipeline for all platforms to avoid this sort of thing in the future)

Attached logfile (with sanitized filesystem paths).