#eulora Logs for 31 Jan 2020



January 31st, 2020 by Diana Coman
feedbot: http://ossasepia.com/2020/01/31/euloras-default-island-sand-grass-rocks-and-nothing-else/ << Ossa Sepia -- Eulora's Default Island: Sand, Grass, Rocks and Nothing Else [12:51]
diana_coman: mircea_popescu: re ^ let me know if that is enough for "terrain" or if you want me to look into the rest of prettifying it aka using "fertility" maps + windspeeds and additional materials to generate procedurally "3d grass" and artefacts of that sort. [13:17]
mircea_popescu: diana_coman, i just finished with spyked's, this is next in line [13:18]
diana_coman: no rush, I'll take a break from it tomorrow anyway because it'll help. [13:18]
mircea_popescu: diana_coman, http://ossasepia.com/2020/01/14/notes-on-computer-graphics-formats-exporters-and-blendering/#comment-7494 << amusingly, your own site's modqueue triggers at log links. [13:30]
diana_coman: hmm? /me looks [13:30]
diana_coman: mircea_popescu: it triggers at any links, why would the log ones be special? [13:32]
diana_coman: logger is not even on same ip anyway [13:32]
mircea_popescu: you can add as many links to trielma you want to a trilema comment, it won't triegger [13:32]
mircea_popescu: yours is likely th same wrt ossasepia, but not log.ossasepia [13:32]
mircea_popescu: which seems to me fixworthy [13:32]
diana_coman: uhm [13:32]
mircea_popescu: diana_coman, answered. all good! [13:57]
diana_coman: glad to hear it; re the ideals there, I'd have preferred to have *no* files needed for defaults at all, tbh [13:59]
diana_coman: but that's way too far a step for legacy client & cs. [13:59]
mircea_popescu: why not ? [14:02]
mircea_popescu: i mean, what sense does it make ? [14:02]
diana_coman: it makes for fewer possibilities for defaults to fail; I like my defaults unfailing, lolz. [14:03]
mircea_popescu: yes, but think logically, how could there be a display default file-less ? [14:04]
mircea_popescu: it's like default computer generated voice without some kinda saved sound parameters somewhere. [14:04]
diana_coman: uat? simple: it's anyway a bloody list of vertices and triangles etc [14:04]
diana_coman: wtf [14:04]
diana_coman: it can be in the code as it can be in the file on disk [14:04]
mircea_popescu: humans are peculiar, to make the display work you gotta somewhere inform the machine of some of those peculiarities no ? [14:04]
mircea_popescu: but it can't be in the "code" unless let a = 1,0,0,0,0,1,0 counts as code to you [14:05]
diana_coman: well, it counts as code to client, what can I tell you [14:05]
diana_coman: the point there was re "won't fail no matter what", not re "let it be actual code" since this last part is not code [14:05]
mircea_popescu: imo it's better to have the few piles of arbitrary parameters needed to bridge the biogap in dedicated raster files than in "code" which is just adnotated... raster files. [14:06]
diana_coman: and for that matter even code: let it have the function to generate the bloody vertices [14:06]
mircea_popescu: i do not believe this'd have been an improvement. [14:06]
mircea_popescu: you expect files implicitly fail somehow ? [14:06]
diana_coman: but as above, why "too far a step for cs/client": because can't define the terrain procedurally directly in cs atm [14:06]
mircea_popescu: diana_coman, and when you can, you'll want to also define the gui procedurally ? [14:07]
diana_coman: no, that I want gone :D [14:07]
mircea_popescu: so how is someone to switch tools ? [14:07]
diana_coman: shortcut keys ! [14:07]
mircea_popescu: and how do they know they did it or just misclucked ? [14:08]
diana_coman: what do you mean? if tool is switched, they did it; if not, they didn't; or what ? [14:08]
mircea_popescu: how do they SEE they did, if no gui. [14:08]
diana_coman: ah, you meant the whole display rather than just the interaction part? (didn't quite make sense since terrain part of display); at any rate, if cli, then it *says* ack. [14:09]
mircea_popescu: you're a software radical. [14:09]
diana_coman: getting to the...root of it! [14:10]
mircea_popescu: let's put it this way : while 0 files is indeed a recognizable ideal, which in some circumstances (such as, it being available) might even be better than current situation ; nevertheless 1 is exactly equal to 11. [14:10]
diana_coman: I can see that; and as seen, I can work fine with it, as such. [14:11]
mircea_popescu: now in other practical concerns, does the vierwport change still work ? [14:11]
mircea_popescu: ie, switch from camera view to first person ? [14:11]
diana_coman: the camera modes are still there and working, yes; when I got to make the camera working, I got this back in as well. [14:12]
mircea_popescu: cool. [14:12]
mircea_popescu: i really don't see problems here. [14:12]
mircea_popescu: i honestly don't even see the problem with ditching the "gui" and using cli. [14:13]
diana_coman: cool, I'll move next week to go through the rest and make defaults and I'll see there; the cal3d might be the most intricate as far as I can currently see, but I'll know exactly when I get to it. [14:14]
diana_coman: well, iirc the idea was to avoid being pegged as "cli only" or other such nonsense; but at any rate, my idea was that once 2.0 is out there, since things are more separated *anyway*, it won't be all that big deal to make myself a cli client out of it too, pretty much one cut and done. [14:15]
diana_coman: but it's time will come when it comes. [14:15]
diana_coman: will bbl [14:16]

Comments feed: RSS 2.0

Leave a Reply