Time  Nick       Message
03:00 sofar      I'm at a loss how to generate nice normal maps
03:00 sofar      the script isn't very useful, it doesn't produce anything usable for me
04:21 kaeza      merry christmas, all.</offtopic>
04:34 kaadmy     mry xmas(2 la-z 2 spell)
04:38 kaeza      ic :P
04:38 VanessaE   merry something-or-other :)
15:30 paramat    will merge game 745, 753, 736 in a moment
15:34 paramat    now merging
15:44 paramat    merged
19:37 rubenwardy https://github.com/minetest/minetest_game/pull/751#issuecomment-166579022
19:37 rubenwardy wow
19:39 alket      lol
19:39 kaadmy     =-O
19:40 alket      out of blue
19:40 rubenwardy That's the same guy that made the "girls" mod
19:40 kaadmy     why am i not surprised in the least?
19:41 sofar      just ban/report
19:41 sofar      then ignore
19:42 kaadmy     also, this is why noone gives a f*** about some people
19:45 sofar      I'm not saying I don't care. I'm saying that the best way to deal with this from an internet side of view is to not engage
19:45 sofar      if you do engage, you'll likely just enrage the person or worse
19:46 sofar      if you don't engage, they may come to their senses and later make useful submissions
19:46 sofar      he's clearly admitting he has mental health issues, so, just keep that in mind for the future
19:46 sofar      he/she
19:46 sapier     wow that's even special or minetests rough discussions :-)
19:47 sofar      wholly appropriate discussion to have in #minetest-dev IMO
19:47 sofar      if you run an open project, you'll get these type of encounters
19:47 sapier     https://github.com/minetest/minetest/pull/3467 anyone to check this one? I'm quite annoyed about my console being spamed  ;-)
19:47 sofar      yeah, I've seen these
19:51 kaadmy     are entity models re-loaded from disk when then entity becomes loaded into a chunk?
19:51 sapier     yes ... quite ugly
19:52 sapier     relic of entity models being aded long after minetests basic engine was written
21:05 est31      I have removed that comment, it was past a line.
21:07 est31      I wondered whether it would survive on the forums, and I thought no.
21:08 est31      but idk, dont want to start a discussion now about what to censor and what not
21:08 est31      not today
21:40 sapier     we have to do something about find_node_near ... it's highly abuseable ;-) if you call it with a radius of 50 for example it's gonna hang main loop by > 700ms on my cpu ... guess it's doing quite some trouble on other os too
21:40 sapier     -os + cpu's
21:47 kaadmy     yep
21:47 sapier     same for find_nodes_in_area ... imho there should be at least a warning about this to cause trouble
21:48 kaadmy     (total time) = (time per node) * (x * y * z) = very large number
21:49 kaadmy     although I use it quite a lot for villages in pixture, and i've benchmarked it(inaccurately), and it's pretty fast
21:49 kaadmy     place_schematic is probably a little slow, too
21:49 sapier     exactly ... and it's even worse as time depends on not finding ... meaning if you happen to test it while something is close you'll probably not notice at all
21:49 kaadmy     ah
21:50 kaadmy     it it's in C++, it shouldn't be that slow.
21:51 kaadmy     i've done loops of 10000+ before while printing stuff, and it runs nearly instant.
21:51 sapier     it's terribly slow
21:51 sapier     it's far from constant
21:52 sapier     https://gist.github.com/sapier/6082c894cae0345dd371 shows how time builds up
21:52 kaadmy     wow
21:52 sapier     each loop is a shell
21:52 sapier     a single shell !
21:52 sapier     I did only print as of shell time of 5ms
21:53 sapier     so you see as of radius 17 5ms time is passed
21:53 kaadmy     and 24 node radius is twice
21:53 sapier     yes only the 24 radius shell! the inner times add to it
21:54 sapier     that's why not finding something within a radius of 49 nodes takes more then 700ms on my machine
21:54 kaadmy     yes
21:54 sapier     quite bad
21:55 sapier     guess I have to do that check in lua doing it in small parts
21:59 sapier     wow calculation the positions takes 2.2ms on loop 49 ... that's quite strange numbercrunching should be way more fast
22:03 sapier     great
22:04 sapier     this isn't a find_nodes_near at a..
22:04 sapier     all
22:04 sapier     radius ain't really a radius but the size of the CUBE it's looking within
23:41 celeron55  oh nice; that's originally my code
23:41 kaadmy     hi c55
23:42 celeron55  well it was meant for radiuses of like 1 and 2 and it is meant to find the closest one
23:42 celeron55  no wonder it fails at 49
23:45 sapier     Well I don't know how to do this in a clean way I'm implementing it in lua now