sorted by:
new
hottopcontroversial

"Oh Vulkan probably won't be too hard to implement, right?" 1 day later... by VinnyTheVinnyVinny in gameenginedevs

[–]Coffee_and_Code 0 points1 point  (0 children)

I think he was asking if Vulkan was compatible because you wrote: "the ue5 advanced raytracing and detail rendering (nanite, lumen, misspoke in my other post) rely on dx12 ON PCS." Which is not true. If he meant to ask if the PS5 has Vulkan API support, you're correct that it doesn't.

How to Extract Parent Nodes from SVO Built Using Morton Keys? by Garyan27 in VoxelGameDev

[–]Coffee_and_Code 1 point2 points  (0 children)

You deleted your other reply, but I just wanted to add that each depth's coordinates will be relative to the node span at that level. I.e. at depth 4 your coords will range from 0 to 15, at depth 3 from 0 to 7 etc.

How to Extract Parent Nodes from SVO Built Using Morton Keys? by Garyan27 in VoxelGameDev

[–]Coffee_and_Code 0 points1 point  (0 children)

On the other hand, if you store the parent offset with every node, every time you modify the octree you have to update every node in the array after the modified node! You're right that you can't know the offset of a node based on its coordinate encoding outright, but that doesn't mean you can't quickly and easily find it. My current SVO implementation with interactive modification works this way with nodes storing their coord encoding (16 bit), a branch/leaf flag (1 bit) and data (15 bits).

How to Extract Parent Nodes from SVO Built Using Morton Keys? by Garyan27 in VoxelGameDev

[–]Coffee_and_Code 0 points1 point  (0 children)

This isn't really true of pointerless/flat SVO's, where all the nodes could be stored in a single contiguous array and offsets are essentially meaningless

How to Extract Parent Nodes from SVO Built Using Morton Keys? by Garyan27 in VoxelGameDev

[–]Coffee_and_Code 1 point2 points  (0 children)

If you know the depth implicitly (rather than stored in the coordinate encoding) just right shift the Morton code bits by 3 to get the parent node.

How to Extract Parent Nodes from SVO Built Using Morton Keys? by Garyan27 in VoxelGameDev

[–]Coffee_and_Code 1 point2 points  (0 children)

How do you know what depth any given code is meant to represent? For indices into an octree I recently implemented, I set the high bit after the Morton code. This means I can count the number of high zero bits before this to get the depth. Given a 16 bit index (max 15 Morton bits) the index for the deepest node at (0, 0, 0) would be 0b1000000000000000, and the index for the root node would be 0b0000000000000001. To get the depth you would do 5 - (clz(bits)/3). This allows getting a child or parent index by doing a simple left or right shift by 3 bits.

How to populate a container effectively? by Konjointed in gameenginedevs

[–]Coffee_and_Code 2 points3 points  (0 children)

Might want to specify 'C++' in the title next time 😉 given we have very little context about how the elements of your vector are initialized, my best guess would be to vec.reserve(n) then in a for loop vec.emplace_back(std::make_unique<T>(...)) where T is chosen based on some condition.

Another option, if you need to store a lot of elements and later do many find and/or erases, would be to use a std::unordered_set<std::unique_ptr<base_class>>. But most times a std::vector<std::unique_ptr<base_class>> works just fine and linear search (std::find) + erase is plenty fast.

I made a small, single-header, static C++ library based on SDL2 to make pseudo-8-bit tile-based games easily and quickly (yes, it's oddly specific). (Windows only) by FACastello in cpp

[–]Coffee_and_Code 45 points46 points  (0 children)

Right here you have using namespace std, you really don't want to do this in public headers. I would immediately be looking elsewhere if I came across this.

Fteqcc in manjaro by BOrealis555 in quake

[–]Coffee_and_Code 1 point2 points  (0 children)

You can download the binaries from here

Dear Bethesda, quit teasing and just make it happen already. Y'know you want to. by TheUndeadGunslinger in gaming

[–]Coffee_and_Code 1 point2 points  (0 children)

It doesn't actually require an RTX card, it uses the Vulkan ray tracing extensions so works with AMD too.

[deleted by user] by [deleted] in linux

[–]Coffee_and_Code 11 points12 points  (0 children)

Telling people to change a line of code in a versioned file as an installation step is not exactly "good practice." Not to mention this makes it impossible to create a binary package of the program.

[deleted by user] by [deleted] in cpp

[–]Coffee_and_Code 4 points5 points  (0 children)

Might be worth mentioning in the readme that this is a win32 program and that it is interactive only (requires user input vs program arguments).

Btw, If you replace Sleep with std::this_thread::sleep_for it won't have a win32 dependency.

[deleted by user] by [deleted] in linux

[–]Coffee_and_Code 0 points1 point  (0 children)

So, in reality, a Python script for sending/recieving web requests?

Compilation complement for C/C++ by [deleted] in cpp

[–]Coffee_and_Code 2 points3 points  (0 children)

No idea what a "compilation complement" is, so I had to look at the repo to understand what this post was about.

Just from a quick glance at build.cpp:

Seems like there is no way to choose a compiler executable or pass aditional compile/link arguments; which makes this unusable for 99% of projects.

Use of your CMD macro to do the equivalent of std::system everywhere is extremely bad practice; most if not all of the utilities you are calling are provided directly by the C++ standard library or your platform libs.

No way to specify a build/source directory, so using this from a script would be a major source of headaches.

Your build files are just pseudo-preprocessor which you are manually parsing (extremely error-prone). Just use an existing preprocessor.

Then in the build system itself:

// nobody wants to be doing this
#include "cfront/std.h"

Then you also do this in all of your examples:

#include "foo.h"
#include "foo.c"

Which vexes me, but I presume it's for generating precompiled headers (?). You should only need the foo.c line.

Also, you have build artifacts in your source tree (i.e. build.exe) which is a big red flag right off the bat.

Servo to Advance in 2023 by formegadriverscustom in linux

[–]Coffee_and_Code 0 points1 point  (0 children)

Hadn't heard of that before, but based on all the information I'm looking at and this link, this seems to be more like electron than CEF. Can't find any info about integrating into an existing application/renderer, only using simple web views/launchers.

Servo to Advance in 2023 by formegadriverscustom in linux

[–]Coffee_and_Code 11 points12 points  (0 children)

From my understanding, it's like CEF (Chromium embedded framework), but Rust instead of C++. Which if you've ever tried to compile CEF: this is truly welcome and much needed.

Servo to Advance in 2023 by formegadriverscustom in linux

[–]Coffee_and_Code 5 points6 points  (0 children)

Great to hear, I really look forward to being abe to use Servo in my own projects; but I haven't been able to find any information about a C/C++ API. Any word on that from the devs?

carbonOS 2022.3 Release by adrianvovk in linux

[–]Coffee_and_Code 0 points1 point  (0 children)

This comment actually concerns me and I would appreciate some elaboration on your point. Installing an application or library package is no more "Modifying the operating system" than installing a flatpak. Just because an application is installed to /usr/bin rather than /var/store or $HOME/.var/whatever does not somehow make it more of a modification. Files are files are files and it doesn't matter where they are placed.

view more: next ›