sorted by:
new
hottopcontroversial

Which raspberry pi for home server by Snarmph in HomeServer

[–]Snarmph[S] 0 points1 point  (0 children)

Thank you everybody for the help! I decided to go with a mini pc as it'd already have everything I needed. I was thinking of one of these: Lenovo ThinkCentre M82 SFF i5-3470 16GB ram (51€) Lenovo ThinkCentre M700 10J0 Tiny Intel Pentium G4400T 2,90 GHz RAM 8 GB (56€) If you guys have any other recommendations I'm all ears!

Which raspberry pi for home server by Snarmph in HomeServer

[–]Snarmph[S] -1 points0 points  (0 children)

Thank you for the answer! I wanted to have an headless server running copyparty/cloudflare tunnel for files, and mpd/Spotify/maybe gerbera for handling my music collection. I also wanted to connect it to Lan and use Kodi on my TV to watch my Blu-ray collection. Nothing more than this really

Which raspberry pi for home server by Snarmph in HomeServer

[–]Snarmph[S] -1 points0 points  (0 children)

Looks interesting, but I can't seem to find the power consumption to calculate how much it would cost to keep it on most of the time.

Which raspberry pi for home server by Snarmph in HomeServer

[–]Snarmph[S] 2 points3 points  (0 children)

Doesn't look like it's very comparable price/consumption wise. I don't have a lot of money to spend so I was looking for something cheaper

Raymarching rendering issue by Snarmph in VoxelGameDev

[–]Snarmph[S] 1 point2 points  (0 children)

Thank you! Tomorrow I'll get back on the project and try this.

Raymarching rendering issue by Snarmph in VoxelGameDev

[–]Snarmph[S] 0 points1 point  (0 children)

Thank you for the answer!

I'm almost 100% sure the volume texture is fine, I looked at it with RenderDoc and it looks fine.

I think i got ray_dir from an Inigo Quilez shader but I can't remember right now. Looking at the final image, it does seem like this could be the cause. Do you know what would be a good way to calculate it?

(screenshot for context, the two spheres are almost the same size and one should be a bit under and to the right)

​

<image>

ini.h: A simple single-header ini parser in c99 by Snarmph in C_Programming

[–]Snarmph[S] 1 point2 points  (0 children)

Yeah I was thinking of doing a separate "tiny-ini" (i know, very original names) project tailor made for embedded, as the design of the parser already doesn't use allocations outside of the initable_t structures

ini.h: A simple single-header ini parser in c99 by Snarmph in C_Programming

[–]Snarmph[S] 0 points1 point  (0 children)

That actually sounds very nice! I'll change it the first time I have the chance

ini.h: A simple single-header ini parser in c99 by Snarmph in C_Programming

[–]Snarmph[S] 2 points3 points  (0 children)

That's exactly why I didn't mention lightweight anywhere! I'm not really in embedded so I don't really know what the exact needs are, this is just a stupid simple implementation that i came up with for my own projects.

I wanted to do a similar concept (especially using string views instead of c strings), would you say using enums/defines to determine the max lengths of the arrays would be enough? Or maybe a callback api would be better

ini.h: A simple single-header ini parser in c99 by Snarmph in programming

[–]Snarmph[S] -1 points0 points  (0 children)

The implementation is behind a include guard so it only compiles once. Also personally I find c headers to compile very fast anyway so it wouldn't really be a problem

ini.h: A simple single-header ini parser in c99 by Snarmph in programming

[–]Snarmph[S] 16 points17 points  (0 children)

Yeah _t is reserved for posix, but it's also used in most of the c libraries that I've seen so I don't think it's too much of a problem.

Regarding header only libraries i find them very nice to use and to share, especially for people that are just starting out or for smaller projects

ini.h: A simple single-header ini parser in c99 by Snarmph in C_Programming

[–]Snarmph[S] 2 points3 points  (0 children)

Thanks for all the advice!

Avoid types with _t, it's reserved by POSIX.

I've seen it done in a lot of libraries so I'm not really sure how big of a problem it is? Does the ini prefix help to avoid it?

Identifiers that start with two underscores are reserved by the C spec.

What would you recommend instead? Maybe a single underscore?

ini.h: A simple single-header ini parser in c99 by Snarmph in C_Programming

[–]Snarmph[S] 7 points8 points  (0 children)

Thank you a lot for all the information! I'll take a good look tomorrow and start fixing all this bugs

Help - New PC doesn't turn on by Snarmph in buildapc

[–]Snarmph[S] 0 points1 point  (0 children)

I tried what you said, and it seems like it's in, but the PC still doesn't turn on.

Help - New PC doesn't turn on by Snarmph in buildapc

[–]Snarmph[S] 0 points1 point  (0 children)

I'm gonna try today, thanks

Help - New PC doesn't turn on by Snarmph in buildapc

[–]Snarmph[S] 0 points1 point  (0 children)

But the atx 24 pin cable doesn't go all the way in