Tomcat Thanks. I'm not using Makehuman, but I know both softwares somewhat and they are nice... assuming one ever figures out Blender. It was fun to play with, but had a very deep learning curve.

I miss the old Blender versions that I understood.

    Nerdzmasterz assuming one ever figures out Blender. It was fun to play with, but had a very deep learning curve.

    I tried to make it as clear as possible. If something is not clear, you can ask, clarify and I will try to improve the tutorial.

    C++ is really a pile of steaming bovine waste 💩 and should never be used to write safety critical systems. And the more I learn about it the more I understand why the Linux kernel guys do not want it in the kernel.

    Example, who would remember if they not made that error before that indexing with an operator[] into a map for instance actually changes the map if the key is not found, thus provoking ub in a concurrent environment just with supposed concurrent reader access (that actually is no reader access), if not taken special care of ? And who knows what else is hidden as an error waiting to be made 🦶 🔫 ?

    What did Linus say "... and if it is only to keep out the mediocre C++ programmers" or so. Right he is. I would certainly have made that error, wasn't it mentioned as an example in an exercise.

    grumblegrumble

    :-)

    But in C++ you can use cool but obscure expressions such as:
    ***i++

    [was piffle from my part]

    This is why I ditched C++ a long time ago.

    <smoke emitting from ears>

    I would probably go back to Unity in its current state before going back to Unreal.

    There's no way around C++. Rust is gaining territory but has the paradigm "You don't know what you're doing so I won't let you". That's a bit the opposite. No, I fear we must sit down on our behinds and learn ...

    C++ is great, I just don't think most people need that much power or performance. If you do, then you have no choice. But even some of the more advanced ML stuff is moving to GPUs. I think at some point CPUs and GPUs will merge, but the architecture will probably be more like GPUs. Basically a huge set of parallel streams that are fully programmable. Because x86 is a dead end at this point. Or at least it has the potential, but the software can't take advantage. While with GPUs you can essentially reach 100% potential today.

    My beef is that any time I tried to learn C++, they cover the basics only, or only very advanced stuff. It

      The end of the touring machine ? Why not.

      Somehow the programming languages have not kept up the pace with the hardware development, I take it. C++ just has too many elements that change semantics depending on context. Who knows them foot guns all ? Edit: I'd say C++ is very well for programming let's say OSI level 5+. Btw., it has some power to it, but C and lately Rust are quite a bit off, for the sacrifice of flexibility.

      But not all problems lend themselves well to parala pallalel parlay ? Aren't games a good example ? Edit, aside from rasterization and/or ray-tracing ofc.

      Nerdzmasterz My beef is that any time I tried to learn C++, they cover the basics only, or only very advanced stuff

      It took me a lot of books, looking at other code, trying out my own things, until I got a grasp. I may be not the brightest candle in the candelabra, I confess +/-2 years, on and off, and still I sometimes sit there awe struck.

        Better than me. I grabbed Unreal and followed a guy's YouTube to the letter, grabbed courses, left C++, came back a few times, joined the academy and tried to figure it out without much luck...

        Unity was way more my style.

        Maybe I will try to tackle C++ again someday, just for the sake of Unreal's graphics. Sorry, Godot and Unity, my horror games and VR worlds should look very realistic.

        An example of what I mean- this was actually done for my first game in Unreal- it was nothing fancy, just a game I was making with a tutorial, but I went crazy with the look and feel of it. Note the accelerant beneath the explosion- a fallen pipe with who-knows-what in it. I also made note to add a liquid underneath which has smaller flames, but you can't see all that here. I was going for the base tutorial game, then add a little timer to see if the player escapes before everything is decimated by flames.

        There's no such thing as a safe programming language, only safe engineering. We defined how to make provable software decades ago, because I was studying it in college. No one uses those methods unless they absolutely have to, because they're slow and expensive. So the software that was not proven drifts slowly into uses that should require proof.*

        This is not peculiar to computers. Every branch of engineering deals with it, but most of them started longer ago.

        * No one agrees on what should require proof, because everyone values life and safety differently, usually depending on whether it's theirs or someone else's.

          Pixophir But not all problems lend themselves well to parala pallalel

          Yes, that's the point. If you read the OS book I linked to, it might make more sense. Most of the slowdown on computers is not the computation. It's the IO a good amount of the time. And many tasks need to be executed in a particular sequence. So even if we got 4096-core processors tomorrow, our computers would probably not get much faster at all. Some things would be much faster though. Ray tracing, baked shadows (which is sort of ray tracing anyhow), password cracking, search algorithms or other pure data processing. There would be benefits. But in day to day computing, using your web browser, managing files, etc. it's unlikely things will get much faster.

            cybereality It's the IO a good amount of the time.

            SSD drives can be 30x as fast as mechanical hard drives. That makes a huge difference.

              If anyone makes tutorials that show how to create a specific thing, try to make it short. There are some tutorials that take like 3 hours and by the time you carefully follow each little step and copy what the teacher's got you have only a rough idea of what just happened, but there's 0 chance you could recreate it after that long process- most of all you're going to want to feel like it's done.

              It's rough tho, it's hard to know what to google for, as to what feature of an engine to learn and practice. We all get ensnared by the "Recreate a running and shooting talking pilgrim" tutorials.

              DaveTheCoder SSD drives can be 30x as fast as mechanical hard drives. That makes a huge difference.

              Yes, but that's not the whole story. For example, the fastest SSD today can read about 7GB per second. However, reading that, you would think an OS would load instantly, or a huge AAA game could open in a couple seconds, but there is still load time. Because there is a lot more going on.

              duane There's no such thing as a safe programming language, only safe engineering.

              Certainly true. But my uneducated and slightly humorous 🃏 point was C++ (and its STL) is a particularly bad language for safety critical applications. Unlike for instance C or the new kid on the block for systems programming Rust. It is much easier to get an overview of what a C-program does by looking at it, providing some rules for coding style are observed and to prove that it is correct, than it is for a C++ program because C++ hides too much in documentation small print and compiler high-handedness. Not maliciously, it just has become so because of historical reasons.

              And C++, because of all its power, enables newcomers like me to do a for instance a render framework without actually knowing or being aware what's going on in the detail, which bears the danger of making code with undefined behaviour just out of good intentions.

              I may, of course, be totally wrong.