Tobba_

10 ms·

31.
by Tobba_ 9y ago
To clarify: that's more of a problem in programming the GPU in a portable manner, and that may or may not turn into a problem depending on the implementation. GPUs can do loops that run a different number of times per thread just fin
32.
by Tobba_ 9y ago
Yep. There's a billion and a half reasons you wouldn't use full-blown path tracing for games. It'll always perform worse regardless of what you do, the frame budgeting is likely going to be a total nightmare, the tree search
33.
by Tobba_ 9y ago
I'm sure that pile of data will gain intelligence if we stir it hard enough. Any moment now.
34.
by Tobba_ 9y ago
It'd help a lot if the grammar was actually readable. Combinations like .* don't visually "read" like a single unit, and then to make everything worse you often need a crazy amount of backslashes. I'm not sure how
35.
by Tobba_ 9y ago
It's a completely meaningless and plain stupid argument though. There's no reason to believe human consciousness is special and that "understanding" Chinese is at all related to it. One can speculate that the perceptio
36.
by Tobba_ 9y ago
I think the difficulty in 3D polygon modelling is partially a tooling problem, and also a learning curve problem. The usual workflows I've seen/used that didn't involve sculpting (which requires being good at that too) all in
37.
by Tobba_ 9y ago
To attempt to explain (desktop) GPU architecture: you don't just have memory and a bunch of individual cores on a GPU like you would on a CPU. You've got memory, texture sampling units, various other fetch units, fixed-function bl
38.
by Tobba_ 9y ago
Vulkan is almost 1:1 equivalent to "modern" OpenGL except the need for a more advanced allocator. You had to write the exact same thing in OpenGL if you wanted decent performance, except through an entire translation layer. I don&
39.
by Tobba_ 9y ago
CS:GO (and all other source games) do the same lag compensation as CS did (though it's horrifically buggy, but it was pretty messed up in 1.6 as well). People seriously underestimate how impossible it is to play fast-paced games withou
40.
by Tobba_ 9y ago
It's great to actually see a game developer that seems to have some grip on what they're doing. At least writing about issues like clocking, animation quantization, etc is far better than what everyone else does - screwing it u
41.
by Tobba_ 9y ago
CS(:GO) would be completely unplayable at any update rate below 50. Especially with the necessary interpolation, you would end up with delays of over 100-200ms+ at an update rate around 10. Most weapons in the game could even fire more tha
42.
by Tobba_ 9y ago
It does have a slight advantage over ARM / most other RISC architectures in that the instructions are fairly small, meaning that you can get quite good decoding throughput without going wider. That advantage doesn't get entirely
43.
by Tobba_ 9y ago
While they're certainly the correct way of doing this, named pipes don't provide too many benefits under Win32; other than this little problem and having to assign a port number, of course. They're harder to debug, require a
44.
by Tobba_ 9y ago
Enemy AI is most certainly the perfectly wrong place to apply ML due to the wide range of possible inputs (scenarios) and being in the utterly wrong complexity class (I mean, it's ostensibly doable with an RNN, but definitely not worth
45.
by Tobba_ 9y ago
Machine learning really doesn't have many uses for games outside of the development cycle (or non-critical gimmicks). If it's exposed to player input - or especially; random input - it absolutely must have robust, stable and con
46.
by Tobba_ 9y ago
Doesn't really make the interface any less crap; though I've yet to see a GUI that didn't shell out to the command-line interface (which almost always makes them very unreliable).
47.
by Tobba_ 9y ago
You'll still get an increase in the number of things you can have loaded into RAM at once that's proportional to the reduction. That'll give you far more leeway in when trying to load resources on the fly, which most games st
48.
by Tobba_ 9y ago
There isn't really any practical reason for most sites to support users with JS disabled, as they're a pretty small minority. So there isn't really any good reason sites or users would actually care about or bother making the
49.
by Tobba_ 9y ago
What's wrong with the evolution of OpenGL? Everything from OpenGL 3 and on has simply been focused on fixing the API without completely breaking old code, or exposing new GPU features. All of that was necessary.
50.
by Tobba_ 9y ago
You could just ..uh.. acquire a copy of IDA that has the AMD64 decompiler. It's more mature and spits out C code of wildly varying readability, though only for one function at a time.
51.
by Tobba_ 9y ago
Doesn't look that way? https://github.com/avast-tl/retdec/blob/master/src/bin2llvmi... Capstone would probably be the best open-source choice for something like this though.
52.
by Tobba_ 9y ago
Looks like it's also relying on LLVM for disassembly? Ouch; that's an incredibly bad idea if you're trying to analyze malicious or unusual code (it's not designed for that), but I guess it's the easiest for a proof
53.
by Tobba_ 9y ago
Unless, somehow, every one of those sockets happened to share the same port on said machine, say... port 80. So yes, you need to use the mythological TCP server to pull this one off; it's true that you can't have more than 2^15
54.
by Tobba_ 9y ago
I guess what I'm really trying to say is that the performance of the "distributed" part has more to do with the design of the algorithm and less to do with the implementation (i.e Elixir). It's like saying Teslas have re
55.
by Tobba_ 9y ago
I can definitely agree with it being easy to use at least. I'd figure that's the main reason it's as popular as it is (together with the feature set, of course). Being able to click a link and simply join a channel without al
56.
by Tobba_ 9y ago
Have we really regressed to the point where simply relaying data with reasonable performance is considered impressive? Figuring out where to relay everything and keeping it all in sync is obviously hard, but that's a distributed syst
57.
by Tobba_ 9y ago
It tends to fail to register the key being released for one, even occasionally on the desktop client. Last time I tried it the browser app was especially prone to this, to the point of rendering push-to-talk completely unusable.
58.
by Tobba_ 9y ago
I wouldn't really say their client works in that sense considering how notorious it is for flunking out in completely random ways (i.e missing push-to-talk release events, suddenly deciding your speakers or mic don't exist, not
59.
by Tobba_ 9y ago
Unit testing seems to frequently result in overconfidence.
60.
by Tobba_ 9y ago
Pre-MIR, I'm fairly sure the people who would touch the type/lifetime checker could be counted on one hand, and it was borderline obfuscated due to all the pointless type theory thrown around. RFCs would still get rejected as &quo

More ›