or if you have already cloned dir:
git submodule update --init --recursive
l have cloned it with submodules some time ago and l don't want to clone it again.
l did "git submodule foreach git pull origin master" but it didn't help, cmake tells that CMakesList.txt at jsoncpp is missing.
l run
git submodule deinit --force .
and
git submodule update --init --recursive
and now compiling it works.
but playing still doesn't work, everything is invisible:
Attachments
screenshot_20150927_103248.png (57.67 KiB) Viewed 1414 times
@Inocudom: True. Pls keep up the 32 bit. I found out I did have 2 or three old 32 bit systems laying around, so keeping the options open would be nice.
On my Arch machine, FM 0.14.4 complained about being unable to start a server and then stalled the whole machine by using all CPU cycles. I was able to switch to the console veeery slowly and "kill -9" it from there. It did compile though. :-)
Sorry, I deleted my ~/.freeminer folder because I thought something in the old config was the problem. So no log file.
But I will try again now with a clean slate so to speak. I will SSH into the machine before I start FM this time though so I can kill the task quicker if things go wrong.
Ok, exactly the same thing (high CPU load, unresponsiveness) happened with a newly created ~/.freeminer directory. I simply created a new creative single-player world, no damage, and started it.
Perhaps the problem is that I have IPv6 disabled on this machine? It looks like FM wants to connect via IPv6.
Disabling the kernel parameter ("ipv6.disable=1") fixes this issue, so this is definitely IPv6-related. Looks like the FM config settings do not disable IPv6 entirely?
I spawned on an icy plateau and found a cute bunny nearby! Awww, so fluffy… :-)
by default freeminer use patched enet to support ipv6.
but for reducing patch complexity and size anything converted to ipv6 and v4 used via v6 - it cause completely broken network if v6 disabled in system
but you can use original enet with ipv4 only.
dont disable ipv6 is good solution for year 2016 ;)
proller wrote:
dont disable ipv6 is good solution for year 2016 ;)
Well, IPv6 is kind of a privacy and security nightmare with zero benefits for me, and MT works fine without it, is all I'm saying. :-)
I'm noticing the default game runs fine in FM, but Pixture has a memory leak in FM and mallocs all system memory before it gets terminated by the kernel's OOM killer. In MT, Pixture runs fine with near-constant memory use. Weird.