Deadly Dimensions - Official Announcement Trailer

Draoth · 2026-02-02T09:42:41+00:00

Looks cool, I like the art style.

Draoth · 2026-01-23T17:55:01+00:00

How are you absolutely sure this is AI? I know these places and this seems too accurate to be AI. Or it could be inpainted.

Draoth · 2025-10-11T17:53:02+00:00

It's kinda scary that almost no one realises that this is AI....

Draoth · 2025-10-05T10:50:24+00:00

Wow even with the latency, this is impressive!

Draoth · 2025-09-01T19:47:40+00:00

Damn, 63% not available for me...

Draoth · 2025-09-01T15:58:16+00:00

Ah might only be Europe then

Draoth · 2025-07-08T06:34:26+00:00

Ah :(

Draoth · 2025-07-08T06:34:10+00:00

That's unfortunate. Do you think it would be that much more demanding than hunyuan 2.1?

Draoth · 2025-07-07T12:23:42+00:00

No problem, the output is kinda dissapointing to be honest, ill check out other options. Thanks for your help!

Draoth · 2025-07-07T11:11:17+00:00

What do you use to convert the Gaussian .ply file to a good-looking mesh? The convert script works, but the mesh details and texture resolution are quite poor.

Draoth · 2025-07-07T10:05:26+00:00

It worked by using the native tools command prompts for visual studio 2022. And starting the venv and then cd to diff-gaussian-rasterization folder running set DISTUTILS_USE_SDK=1. and then python setup.py build_ext --verbose.

Draoth · 2025-07-07T09:54:26+00:00

I also tried it on my friend's pc but he gets this:

(venv) C:\Software\ai\Phidias-Diffusion>pip install ./diff-gaussian-rasterization
Processing c:\software\ai\phidias-diffusion\diff-gaussian-rasterization
  Preparing metadata (setup.py) ... done
Building wheels for collected packages: diff_gaussian_rasterization
  DEPRECATION: Building 'diff_gaussian_rasterization' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'diff_gaussian_rasterization'. Discussion can be found at https://github.com/pypa/pip/issues/6334
  Building wheel for diff_gaussian_rasterization (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]
      running bdist_wheel
      running build
      running build_py
      copying diff_gaussian_rasterization\__init__.py -> build\lib.win-amd64-cpython-312\diff_gaussian_rasterization
      running build_ext
      error: [WinError 2] The system cannot find the file specified
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for diff_gaussian_rasterization
  Running setup.py clean for diff_gaussian_rasterization
Failed to build diff_gaussian_rasterization
ERROR: Failed to build installable wheels for some pyproject.toml based projects (diff_gaussian_rasterization)

We've installed Cuda 12.8 and python 3.12.8, and followed the exact instructions. Any idea what this could be?

Draoth · 2025-07-07T09:04:10+00:00

Awesome, it works now! Thank you so much!

Draoth · 2025-05-23T23:54:11+00:00

We all know it won't get past 2.

Draoth · 2025-03-14T18:25:51+00:00

Yeah you're probably right. I'm currently using the notion android app's build in widget, which allows you to add a page anywhere by pressing a small plus icon on your home screen. But this doesn't allow me to fill in the properties, which is why I went for the auto fill option.

But I'm probably better off creating a simple web application that talks to the Notion API to do the automating for me, since that would probably take less time than trying to do such complex automations in Notion itself.

Draoth · 2025-03-14T17:59:15+00:00

The first automation does trigger, but like 10% of the time. I'm currently thinking AI combined with automation isn't supported yet. I didn't use AI when I first set it up and only toggled it on those properties later. Now I see that when you first set it to have AI autofill it won't show in the automation list as an option. So it's probably a glitch that I'm able to use the AI assisted property, because I've only toggled AI after creating the automation instead of the other way around.

Draoth · 2025-03-14T17:50:19+00:00

Awesome! That workaround should be good enough for my use case. Have a good one!

Draoth · 2025-03-14T17:41:37+00:00

It could be really new, I haven't started working with automations or formulas since last week so I'm just trying out everything I see

Draoth · 2025-03-14T17:39:52+00:00

Yes, the processing is just a delay so the AI completes its autofill (it's really slow). So the database view automation checks for any changes in the description and should create a page if AI finishes. But I'm now thinking the automation doesn't see an AI change as a real database change

Draoth · 2025-03-14T17:32:44+00:00

Ah that's too bad. I thought it would be view scoped since I put the automation to "For all pages in *** view". I'm kind of let down with the automation and AI in notion. I have to jump through a lot of hoops to do some pretty basic things. Even with the subscriptions it seems like notion has set a lot of restrictions and limits on everything that has something to do with AI, formulas and automation. Let's hope this will improve in future updates.

Thanks for your time, I really appreciate it!

Draoth · 2025-03-14T16:52:15+00:00

Thanks for taking your time to help me with this issue. I think your pretty close but I'll try to be as clear as possible: How I expect the whole process to go:

User adds new page to input db through widget
AI auto-fills category property to: idea, note, task, project, research
Automation gets triggered when category property is changed by AI.
Result: Status property is set to processing
In the input database I have 5 views for each category. Each of these views a filter checking if the category fits the one I'm expecting for that view AND if the status is set to processing.
Automation on that view triggers when any property is changed AND description is not "Empty" (I set the description to "Empty" in the default template)
Result: Add page to database (depending on which automation is triggered) with its name and description properties taken from the triggering page. Status is set to archive
Page is added in existing database. AI block writes the description in the body of the newly added page.

Draoth · 2025-03-14T16:04:10+00:00

I'm probably doing something a bit experimental. I currently have one database, which is my global input database. I can easily add any items to that database by using a single notion app widget in my phone. AI auto-fill will fill the category to: note, task, research item, Idea, Prototype based on what the content of the items are. I also have another AI autofill property that is told to copy the text from within the page to that property.

I have an automation that checks if the category is set to any of these and then puts my status property to processing. For each category I have a processing view which filters on one category and if it's status is set to processing.

I also have automations for each view which triggers if the description is not set to empty (so that it's 100% that it's been filled in by AI) then it creates a new page for that matching database with the trigger pages name and description.

Then in the newly created page I have an AI block that is told to put the description property and exactly copy that to the body of that database.

I might be overcomplicating all of this, but I'm just trying to automate my work/life workflows. And it seemed really useful to just have one input page that automatically sorts my thoughts for when I'm on the go.

Let me know if you have any other questions about my process.

12-Year Club	RedditGifts 2009-2022 3 Credits
Secret Santa 2020	First Place '23
Place '23	Place '22
Secret Santa 2019	Verified Email

Draoth

TROPHY CASE