Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
We're currently looking into it, until then, a wired connection is usually the answer.
This would be an option to try if the Macbook Air had an Ethernet adapter. I will try on the mac mini, although it seems other games work fine logging in with steam on a wireless connection.
There also seems to be an issue where Mac and Linux interpret the code wrongly. However it's only on some systems, so it's a slow process of gathering data and testing things, but I can assure you we're currently looking into it.
In the meantime we'd be very grateful if you sent your player.log to us at support@betadwarf.com.
Something that will also help a lot is the output log.
Where you can find the log file:
WINDOWS:
path to executablename_Data folder\output_log.txt;
EXAMPLE (For Steam) D:\Steam\steamapps\common\YOUR_NAME\FORCED_Data\output_log.txt
Mac OS X:
~/Library/Logs/Unity/Player.log
LINUX:
~/.config/unity3d/BetaDwarf ApS/FORCED
dats what you need right thur
I found the player log, it really doesnt have much just, ***Thread 'UnityLookForNewInputDevices' was not cleaned up!***
(Filename: Line: 499)
I can not locate this output_log.txt inside the common\FORCED\DATA folder
I pasted it here,
***Thread 'UnityLookForNewInputDevices' was not cleaned up!***
(Filename: Line: 499)
It doesnt have much
There should be much more than that, so if that's all it contains there's a serious problem.
Can you try to reproduce the bug and then check the log?
Thanks for helping!