Freeminer

[proller]

latests win32 build: http://freeminer.setun.net/build/freemi ... -win32.zip
win32 minetest compatible: http://freeminer.setun.net/build/freemi ... -win32.zip

[proller]

new build server name: http://build.freeminer.org/
always fresh win32 , win32 with minetest protocol, android builds!

[proller]

win64 builds available!
http://build.freeminer.org/?C=M&O=D

is anybody who now use windows 32 bit? exept Krock ?

[philipbenr]

I use win64/build my own on Linux... so not me.

Edit: Krock makes his own, doesn't he?

[Inocudom]

win64 builds available!
http://build.freeminer.org/?C=M&O=D

is anybody who now use windows 32 bit? exept Krock ?

Very good, proller! If you want people to continue trying out/using Freeminer, it would be wise to keep this service up.

[philipbenr]

@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.

[proller]

Freeminer 0.4.14.8 released!
based on minetest 0.4.14
https://github.com/freeminer/freeminer/ ... g/0.4.14.8

[philipbenr]

Build failing last time I checked... Probably better give it a go now.

[Morn76]

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. :-)

[Morn76]

(deleted double post)

[proller]

show log please

[Morn76]

show log please

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.

[Morn76]

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.

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all


-------------
  Separator
-------------

2016-05-25 15:00:14: ERROR[LanAdvClient]: LanAdvClient: An unhandled exception occurred: Failed to create socket: error 97
2016-05-25 15:00:29: WARNING[Main]: BanManager: creating /home/martin/.freeminer/worlds/test/ipban.txt
2016-05-25 15:00:29: ERROR[Main]: mod "hazmat_suit" has unsatisfied dependencies:  "technic"
2016-05-25 15:00:29: ERROR[Main]: mod "technic_armor" has unsatisfied dependencies:  "technic_worldgen"
2016-05-25 15:00:29: WARNING[Main]: Could not load map metadata
2016-05-25 15:00:29: WARNING[Main]: NodeDefManager: Ignoring CONTENT_IGNORE redefinition
2016-05-25 15:00:30: ACTION[Main]: Serving 869 files, 3632726 bytes
2016-05-25 15:00:30: ACTION[Main]: freeminer v0.4.14.8     THREADS     cpp=201103     cores=2
2016-05-25 15:00:30: ACTION[Main]: World at [/home/martin/.freeminer/worlds/test]
2016-05-25 15:00:30: ACTION[Main]: Server for gameid="default" mapgen="indev" listening on :::50626.
2016-05-25 15:00:31: ACTION[Main]: Connecting to server at [::1]:50626
2016-05-25 15:00:32: ERROR[Main]: Connection error: Failed to connect

[proller]

Yes. run with
freeminer -ipv6_server=0 -enable_ipv6=0

or add to config:
ipv6_server=0
enable_ipv6=0

[Morn76]

Now it's using IPv4, but it still gets stuck the same way as before:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

-------------

2016-05-25 15:24:00: [Main]: Automatically selecting world at [/home/martin/.freeminer/worlds/test]
2016-05-25 15:24:00: ERROR[LanAdvClient]: LanAdvClient: An unhandled exception occurred: Failed to create socket: error 97
2016-05-25 15:24:06: WARNING[Main]: BanManager: creating /home/martin/.freeminer/worlds/test/ipban.txt
2016-05-25 15:24:06: ERROR[Main]: mod "hazmat_suit" has unsatisfied dependencies:  "technic"
2016-05-25 15:24:06: ERROR[Main]: mod "technic_armor" has unsatisfied dependencies:  "technic_worldgen"
2016-05-25 15:24:06: WARNING[Main]: Could not load map metadata
2016-05-25 15:24:06: WARNING[Main]: NodeDefManager: Ignoring CONTENT_IGNORE redefinition
2016-05-25 15:24:06: ACTION[Main]: Serving 869 files, 3632726 bytes
2016-05-25 15:24:06: ACTION[Main]: freeminer v0.4.14.8     THREADS     cpp=201103     cores=2
2016-05-25 15:24:06: ACTION[Main]: World at [/home/martin/.freeminer/worlds/test]
2016-05-25 15:24:06: ACTION[Main]: Server for gameid="default" mapgen="indev" listening on 0.0.0.0:50504.
2016-05-25 15:24:07: ACTION[Main]: Connecting to server at 127.0.0.1:50504
2016-05-25 15:24:09: ERROR[Main]: Connection error: Failed to connect

[Morn76]

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… :-)

[proller]

because internally ipv6 still used.

but you can build ipv6-free version :

cd src/enet && git checkout master && git pull && cd ../.. && make -j4

[Morn76]

because internally ipv6 still used.

but you can build ipv6-free version :

cd src/enet && git checkout master && git pull && cd ../.. && make -j4

So the problem is using Arch's enet for FM? Or what is the difference here to the way FM is compiled by the AUR PKGBUILD (https://aur.archlinux.org/cgit/aur.git/ ... =freeminer)?

[proller]

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 ;)

[Morn76]

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.