| Time |
Nick |
Message |
| 00:14 |
|
v-rob joined #minetest-dev |
| 03:01 |
MTDiscord |
<MisterE> Yay! But I would like to be able to control bloom on individual parts of individual textures. So, make a torch very bright for ex. I guess that's planned eventually? |
| 03:02 |
MTDiscord |
<MisterE> Or, make something glow with a specific color |
| 04:00 |
|
MTDiscord joined #minetest-dev |
| 04:16 |
|
v-rob joined #minetest-dev |
| 04:39 |
|
v-rob joined #minetest-dev |
| 05:01 |
|
calcul0n joined #minetest-dev |
| 07:56 |
|
smudge-the-cat joined #minetest-dev |
| 07:56 |
|
smudge-the-cat left #minetest-dev |
| 08:04 |
|
appguru joined #minetest-dev |
| 08:07 |
Zughy[m] |
sfan5: I think that for now it'll suffice, icons are not mandatory for now. I mean, it's not like the mainmenu is great anyway |
| 09:43 |
MTDiscord |
<luatic> I would like to draw some attention to #11913. If merged, it will allow to greatly improve debugging (although I'll probably have to hackily override debug.traceback for that; I'd prefer if this was querying minetest.traceback or something similar...). See my comment on the issue: https://github.com/minetest/minetest/issues/11634#issuecomment-1253459944. |
| 09:43 |
ShadowBot |
https://github.com/minetest/minetest/issues/11913 -- Call tostring in the error handler by TurkeyMcMac |
| 10:01 |
|
Fixer joined #minetest-dev |
| 10:39 |
|
Fixer_ joined #minetest-dev |
| 11:09 |
|
appguru joined #minetest-dev |
| 11:35 |
|
cranezhou joined #minetest-dev |
| 11:57 |
|
appguru joined #minetest-dev |
| 11:59 |
|
appguru joined #minetest-dev |
| 13:26 |
|
wsor joined #minetest-dev |
| 13:28 |
|
wsor joined #minetest-dev |
| 13:34 |
|
proller joined #minetest-dev |
| 13:40 |
|
fluxionary joined #minetest-dev |
| 14:59 |
|
vampirefrog joined #minetest-dev |
| 14:59 |
MTDiscord |
<FatalError> What are the chances of server sent settings being implemented? If we font have sscsm, we should at least get settings to work with |
| 15:00 |
MTDiscord |
<FatalError> Especially with how problematic some of these settings are for modding |
| 15:00 |
sfan5 |
with few exceptions overriding client settings is basically a hack |
| 15:00 |
sfan5 |
the relevant stuff should be changed to be directly controllable by mods via usual APIs and client-side settings be removed |
| 15:03 |
MTDiscord |
<FatalError> Yes, but thats not going to happen |
| 15:03 |
MTDiscord |
<FatalError> And if it does itll be what... a year or three from bow |
| 15:03 |
MTDiscord |
<FatalError> Now* |
| 15:03 |
MTDiscord |
<FatalError> A hack is better then nothing. |
| 15:03 |
MTDiscord |
<FatalError> Clientside settings are needed though either way |
| 15:04 |
sfan5 |
the amount of work needed for either is about equal |
| 15:05 |
MTDiscord |
<GoodClover> Specifically for camera smoothing I'd be surprised if it couldn't easily be wriggled in alongside with the camera API. |
| 15:06 |
MTDiscord |
<FatalError> You mean reworking the entire visuals system, basically creating an entire system for clientside server-sent animations, (for camera smoothing, view bobbing etc) would be easier then sending some plaintext |
| 15:06 |
MTDiscord |
<FatalError> Ntm all the other shit loaded in client settings |
| 15:06 |
MTDiscord |
<GoodClover> The camera API is already been worked on, have you not seen the videos? |
| 15:06 |
MTDiscord |
<FatalError> Somehow i dont think itll fix anything |
| 15:07 |
MTDiscord |
<GoodClover> have some hope man, insisting the engine can never progress is a waste of time |
| 15:08 |
MTDiscord |
<GoodClover> (camera API vids: https://www.youtube.com/channel/UCL3-3UWAMEjalYeGYzZvjxg/videos ) |
| 15:14 |
rubenwardy |
Settings act as a central storage hub, allows a single protocol to change a lot of data |
| 15:24 |
MTDiscord |
<Jordach> Just do as set_sky does: load user settings once, and if set by Lua and should it be invalid, reuse the original user setting value |
| 15:25 |
MTDiscord |
<Jordach> So in the extreme event of a Lua sided mess it’s not possible to break things by pure accident |
| 15:47 |
MTDiscord |
<FatalError> Will the camera api fix this? No, probably not. |
| 15:47 |
MTDiscord |
<FatalError> That is assuming its done this year also |
| 15:48 |
MTDiscord |
<GoodClover> Idk the camera API being able to change smoothing sounds reasonable to me. Changing settings, no, but that's not what I was saying if you read. |
| 15:49 |
MTDiscord |
<FatalError> The main issue is that the smoothing doesnt show up in any of the get:offset shit |
| 15:49 |
MTDiscord |
<FatalError> Or the height |
| 15:49 |
MTDiscord |
<FatalError> Etc |
| 15:49 |
MTDiscord |
<FatalError> Its a problem |
| 15:49 |
MTDiscord |
<FatalError> I doubt and I mean doubt the camera api will fix the clientside api problems |
| 15:49 |
MTDiscord |
<FatalError> Clientside camera problems* |
| 15:49 |
MTDiscord |
<FatalError> But theres that too kek |
| 15:51 |
sfan5 |
if you require the exact position a player clicked at for your mod disabling smoothing is also just bandaid |
| 15:51 |
sfan5 |
might work, but bandaid |
| 15:52 |
MTDiscord |
<FatalError> Its not that, its the player attached objects |
| 15:53 |
MTDiscord |
<FatalError> They look like shit because of the smoothing, they go ahead of the camera on stairs and blocks and shit |
| 15:53 |
MTDiscord |
<FatalError> Its infuriating |
| 15:58 |
sfan5 |
ah that sounds like it exposes the workaround nature of the smoothing, indeed |
| 16:01 |
MTDiscord |
<FatalError> Who knew making a 3d guns mod would make me want to throw a 800 dollat laptop out a window |
| 16:16 |
|
v-rob joined #minetest-dev |
| 16:28 |
MTDiscord |
<Jordach> why are you getting mad over a FOSS game engine |
| 16:53 |
|
Desour joined #minetest-dev |
| 16:55 |
|
ely-the-kitsune joined #minetest-dev |
| 17:04 |
MTDiscord |
<FatalError> Jordach, shut up. |
| 17:05 |
MTDiscord |
<FatalError> So, i feel like ive asked this before, but is there any change the camera api will allow entity attachments? |
| 17:10 |
kilbith |
man |
| 17:10 |
kilbith |
I've answered it several times already |
| 17:10 |
MTDiscord |
<FatalError> Ou fuck |
| 17:10 |
MTDiscord |
<FatalError> Oh* |
| 17:10 |
MTDiscord |
<FatalError> Yeah, kilbith, but theres no way to ping me |
| 17:11 |
MTDiscord |
<FatalError> So i believe ive missed it |
| 17:11 |
MTDiscord |
<FatalError> That or i forgot |
| 17:11 |
MTDiscord |
<FatalError> Maybe both |
| 17:11 |
MTDiscord |
<FatalError> This camera api is hawt though ? |
| 17:12 |
MTDiscord |
<FatalError> Just cant wait for it to not be merges |
| 17:12 |
MTDiscord |
<FatalError> Merged* |
| 17:12 |
|
ely-the-kitsune joined #minetest-dev |
| 17:50 |
|
appguru joined #minetest-dev |
| 17:53 |
MTDiscord |
<MisterE> The answer was yes |
| 17:53 |
MTDiscord |
<FatalError> Neat! |
| 17:53 |
MTDiscord |
<FatalError> Thatll be really nice, when can it be expected to be released? Is it going to be done by 5.7 |
| 17:53 |
MTDiscord |
<FatalError> ? |
| 17:54 |
MTDiscord |
<FatalError> Whos making it anyway |
| 17:54 |
MTDiscord |
<MisterE> Ie the camera attached to an entity |
| 17:54 |
MTDiscord |
<FatalError> Oh... thats not quite what i mean... though regardless, that may be even better for my uses |
| 17:54 |
MTDiscord |
<MisterE> You may expect it whenever you like, throw a dart at a calendar |
| 17:55 |
MTDiscord |
<FatalError> Ok, so... uknown? Whos making it |
| 17:55 |
MTDiscord |
<MisterE> Kilbith |
| 17:56 |
MTDiscord |
<MisterE> I guess he could speak to when he would like it done but thats not the way these things work usually. if he gets it done, then it may miss a release after that waiting to be merged. Or it might be merged instantly. Who knows? |
| 17:57 |
MTDiscord |
<MisterE> Also to add that it can't get done soon enough ? |
| 17:58 |
kilbith |
it depends on two things: 1. the priorities that my hierarchy assign to me and 2. the core-devs |
| 18:00 |
kilbith |
it's unlikely that the core-devs are ready to take a diff of +2.5 KLOC in the face |
| 18:01 |
kilbith |
and touching 25 files |
| 18:01 |
kilbith |
* 23 |
| 18:10 |
kilbith |
plus I had to bring back lots of stuff from irrlicht that hecks removed in the past; I'm not sure that sfan5 would accept it following the current trend to shave everything down to the last hair that sticks out |
| 18:49 |
MTDiscord |
<FatalError> So... you mean we're probably not going to get the amazing camera api thatd open up incredible possibilities to modders |
| 18:49 |
MTDiscord |
<FatalError> ? |
| 19:00 |
kilbith |
nothing without a major collective effort |
| 19:00 |
kilbith |
I insist on the word collective |
| 19:00 |
|
Fixer joined #minetest-dev |
| 19:00 |
kilbith |
s/nothing/not |
| 19:02 |
MTDiscord |
<FatalError> sfan5, what do you say about this |
| 19:04 |
MTDiscord |
<luatic> we need a larger core dev collective |
| 19:04 |
MTDiscord |
<luatic> hopefully TurkeyMcMac has joined the core devs by the time the camera PR is submitted for review |
| 19:04 |
MTDiscord |
<luatic> (will have joined*) |
| 19:58 |
|
jwmhjwmh joined #minetest-dev |
| 20:05 |
|
proller joined #minetest-dev |
| 20:39 |
|
ely-the-kitsune joined #minetest-dev |
| 20:49 |
sfan5 |
@FatalError I don't see why the camera api would fail because of that |
| 21:08 |
MTDiscord |
<Jordach> oh no a PR took 3 weeks instead of a week to review and merge |
| 21:22 |
MTDiscord |
<Jordach> that and i very much doubt having a new fangled camera api will solve your issues anyway |
| 21:50 |
|
proller joined #minetest-dev |
| 22:35 |
|
panwolfram joined #minetest-dev |
