The 1980s computer produces surprisingly gorgeous ray-traced results, but be prepared to measure performance by hour rather than second.
  • Num10ck@lemmy.worldEnglish
    26·
    10 months ago

    i once took 12+ hours to raytrace on an 8mhz Amiga only to realize that it didn’t have any light sources and so was pitch black.

  • teft@lemmy.worldEnglish
    24·
    10 months ago

    The human eye can only see 1 frame per 18 hours so I consider this reasonably fast.

    • aname@lemmy.oneEnglish
      1·
      10 months ago

      You could get a totally playable fps if you play in geological time scale

      Edit. Not really fpS as s stands for second, but …

    • BearOfaTime@lemm.eeEnglish
      21·
      10 months ago

      So true.

      When I switched from basic to assembler on a Trash 80 Model 1, it was truly night and day

  • rockSlayer@lemmy.worldEnglish
    2·
    10 months ago

    I mean that’s pretty fucking impressive imo. I figured a RT frame would take days to render on hardware that old

    • VindictiveJudge@lemmy.worldEnglish
      2·
      9 months ago

      And back when that computer was contemporary, it would have. We’ve learned a hell of a lot since Nvidia announced they had cracked real-time ray tracing all those years ago.

  • Jarmer@slrpnk.netEnglish
    2·
    10 months ago

    700 years worth of compute to do about an hour of gaming that I just did on my pc at home in realtime … damn.

    Did I math it right? I was averaging about 100 fps in hogwarts for about an hour.

    • Illecors@lemmy.cafeEnglish
      1·
      10 months ago

      Say you generated 86’400’000 frames. 17h a frame that’s roughly 16’767 years.

  • hakunawazo@lemmy.worldEnglish
    1·
    10 months ago

    Since my dedicated hybrid graphics card was broken, my gaming experience is almost the same as with this one.

    • Björn Tantau@swg-empire.deEnglish
      1·
      10 months ago

      The strain of going from a 32 x 22 image to a 256 x 176 one is evident in how much longer this secondary image took to render. From 879.75 seconds (nearly 15 minutes) to 61,529.88 seconds (over 17 hours). Luckily, some optimisations and time-saving tweaks meant this could be brought down to 8,089.52, or near-ish two and a half hours.

      Those are really reasonable values. I guess my laptop would take that long to render a 4k image as well.

        • frezik@midwest.socialEnglish
          0·
          10 months ago

          Ray tracing speed primary depends on the number of pixels, not the complexity of the scene.

          • pixeltree@lemmy.blahaj.zoneEnglish
            2·
            9 months ago

            The complexity of your scene makes a huge difference. If your scene has fewer things for light to bounce off of, doing the ray tracing is much faster

            (Source: I do blender renders with cycles)

            • frezik@midwest.socialEnglish
              2·
              9 months ago

              So I’m not exactly sure how Blender implements this. There can be a few details that can make a huge difference. Just for starters, is Blender rendering 100% ray tracing here, or is it a hybrid model with a rasterizer. Rasterizers tend to scale with the number of objects, while ray tracing scales with the number of pixels. A hybrid will be, obviously, something in between.

              Then there is how it calculates collisions. There is a way to very quickly detect collisions of AABB boxes (basically rectangles that surround your more complicated object), but it takes a little effort to implement this and get the data structures right. You can actually do Good Enough sometimes by matching every ray to every AABB, and then you do more complex collision checking against what’s left, but there’s a certain scale where that breaks down.

              Blender is generally very well done from what little I know of it, but I’m not sure how it handles all these tradeoffs.

              • pixeltree@lemmy.blahaj.zoneEnglish
                1·
                9 months ago

                So, as far as I know the cycles engine does ray tracing until it hits a noise threshold, then does ai denoising for the final cleanup. You can see where the more visually complex parts of your render are, because it will take a lot longer to render to a less noisy state. I don’t know specifics of how it works under the hood, but given how complex parts of your image take longer to tender to an acceptable threshold than simpler parts it seems obvious to me that render time scales with complexity.

  • horsey@lemm.eeEnglish
    11·
    9 months ago

    This is what it was like using 3D programs on an Amiga in the late 80s or early 90s. One image took hours and hours to render. 5-6 hours would be a short one, usually it was more like 12.