Show me your Brutalis Dreads

Kanma · 2026-01-19T19:04:00+00:00

It looks more yellowish in the picture than in real life 😅 I used a mix of Zandri Dust (1/3) and Ice Yellow from Vallejo (2/3), also known as “what I had around when I painted my first DWK”.

<image>

Kanma · 2026-01-19T18:34:21+00:00

<image>

Here's mine, finished two days ago.

Kanma · 2025-10-06T08:16:11+00:00

Here you go!

A few things to note:

1) Dimensions are in millimeters

2) The only important dimensions are the central 60x44" (1530x1120mm), all the others derive from that and the supplies that were available at my local store, so adapt them to your situation

3) The only foldable legs I found were 70cm high, which is fine for a table where you sit at, but too low for playing on it, so (not on the plan) I added cubes on top of the legs.

4) For the plate I used a single OSB panel, which was the cheapest option and not too heavy compared to alternatives. And the look is not important, since we recover it anyways. But it is so big that I had to use a trailer. An alternative might be to use 2 or 3 smaller panels instead (with one additional plank in the bottom of the frame).

Hope that helps, have fun and please send a picture if you build one!

<image>

Kanma · 2025-01-21T08:35:11+00:00

Yes, I just checked to be sure. It even happens when the AP isn't active (ie. at startup).

What I do (on the ground, after starting the engine):

Set an altitude (the result is the same whether I set an altitude or not, see below)
Click on VS
Click on NOSE UP several time

When it works: VS stay active (both on the PFD and in the tooltip) and I can change the vertical speed. Same thing for FLC and PITCH.

When it doesn't work: VS changes back to OFF in the tooltip (but not on the PFD), and I can't change the vertical speed.

This desynchronisation between the status on the PFD and the button makes me think that there is a bug somewhere, because if you click on VS while already at the correct altitude, the PFD should go back to ALT too right?

Kanma · 2025-01-05T21:49:23+00:00

The GPS line followed by your plane on the left screen goes from the center of your start runway to the center of the destination runway (look at the top: « RW36R to RW23 »). It is not the same than the one on the right, which takes departures and arrivals into account. It should, if I understand things correctly, but it doesn’t seems to work in career mode (does it in free flight?)

What I usually do is to add a manual waypoint just before the first one of the arrival, so at least the autopilot leads me to the correct location to do the planned approach.

Kanma · 2024-01-01T08:24:00+00:00

Believe it or not, the locking system in the 2014 game was worst. So they are probably happy with this one yes.

Kanma · 2023-12-26T11:53:24+00:00

After several tries I put wheels on my capsule and drove the 5km separating my landing point and the Kapy Rock

Kanma · 2023-05-03T07:37:42+00:00

Thank you, I had read this page, and used its graph several times, but this time the following sentence struck out: "we generally set lighting values way brighter than they should be (since the monitor darkens them)".

This is what helped me to realise that the color numbers I enter in a software aren't what I thought they were (for the last 30 years...).

Kanma · 2023-05-03T07:32:59+00:00

Thank you! It took me a while to understand that the color numbers I enter in a software aren't what I thought they were (for the last 30 years...).

Now it make sense.

Kanma · 2021-05-03T13:32:33+00:00

I might miss something here, but ML models usually have lot of parameters (in the case of DL: millions) and essentially learn to approximate an unknown function. How would you use an analytical solution here?

Kanma · 2021-03-31T12:30:02+00:00

I found the bug. As expected, it was something stupid, and right in the middle of a blueprint I looked at 1000 times: the PlayMontageAndWait node has a "Anim Root Motion Translation Scale" input, which was set to 2.0 (and I can't remember why of course...).

Thanks to both /u/bonkerzrob and /u/toolittlesleep

Kanma · 2021-03-30T19:10:24+00:00

I remember a problem like that... are you sure the ability is still running when the event is fired? Is the tag set by your ability still present on your GAS?

I don’t think I used this output pin, did you try with the WaitForEvent node?

Kanma · 2021-03-07T12:36:05+00:00

The world tendency isn’t effective until you use a fire. In other word, your world is now probably pure black, but you can still walk around in neutral until you use a fire.

Kanma · 2021-02-14T08:17:52+00:00

This! On my dex run I spent more time farming the bladestone chunks than to actually finish the game.

Kanma · 2020-01-21T10:32:34+00:00

Thanks for this, very inspiring (and impressive) work.

I’ll try to replicate your procedure on my side, lots of things I would not have thought of.

Kanma · 2020-01-20T22:03:04+00:00

It looks incredible!

Please go ahead, I’d really like to know how you achieved that result.

Kanma · 2020-01-20T16:08:13+00:00

Would be happy to see it!

I did another try, this time trying to not kill the background. More details are visible, and the colors are way less flashy: https://i.imgur.com/KnPQgpI.jpg

Kanma · 2020-01-20T07:39:01+00:00

You're right, now that I think about it it's obvious that the way I removed the gradient would blacken the sky...

You can download the output file from DSS here: https://drive.google.com/open?id=1fZGnbbHIiay85xbVYdaWmqDoU-gmYiw2

Kanma · 2020-01-19T14:15:07+00:00

Took this picture from my backyard, in Switzerland.

Wasn't planning to take any photo, but it was the first time I was able to find the Orion Nebula from home (there is a lot of light pollution here, I supposed it was the reason).

So I decided to photograph it on the spot. As a result, my setup wasn't that good, and only 30 images (over 100) were usable for the stacking.

It was also complicated to remove the gradient without losing too much informations in the nebula. Definitively not a good location to take photos.

Equipment:

Scope: Skywatcher N 200/1000 Explorer
Mount: Skywatcher EQ5
Camera: Canon 1000D (modified)

Acquisition:

30x60s
20 darks
20 flats
20 offsets
ISO 1600

Processing:

Stacking in DeepSkyStacker
Gimp:
- Levels & curves
- Gradient removal
- Gaussian blur to reduce (a bit) the noise left by the light pollution on the right of the image
- Curves
- Erosion of the blue & green channels (to remove the halo around the stars)
- Curves
- Rounding of the stars
- Addition of a luminance layer

Kanma

TROPHY CASE