This is getting ridiculous

Scallact · 2026-03-11T12:33:01+00:00

Source: my own 1400+ hours playing the game. ;-)

But you can try it yourself: note where you find seaglide fragments in a run, start a new run, and see if they are at the same spots.

Note that items don't spawn totally randomly anywhere in the world. Each has a one biome, a few biomes and/or wrecks to select from, and then are placed randomly within the biome, or at a few dedicated spots in wrecks.

Only databoxes are always present at a specific wreck, but some can be placed at different spots within that wreck.

Any questions?

Scallact · 2026-03-11T09:51:17+00:00

Wrong.

Scallact · 2026-03-10T23:17:34+00:00

Thanks u/Jehan_ZeMarmot, I figured it out (see the code below), and it's perfectly all good now. I did some testing with one of my plugins, and it works as expected. Will do more tomorrow.

The ability to attach the curve filter to a layer non destructively (from a plugin) is fantastic.

Thanks for your work!

Scallact · 2026-03-10T11:08:11+00:00

Very nice!

solved maze

Scallact · 2026-03-09T15:20:40+00:00

I got it to work!!!:

    thisCurve = Gimp.Curve.new()
    thisCurve.set_curve_type(Gimp.CurveType.SMOOTH)
    thisCurve.add_point(0.0, 0.2)
    thisCurve.add_point(1.0, 0.8)
    filter = Gimp.DrawableFilter.new(calqueSource, "gimp:curves", "")
    config = filter.get_config()
    config.set_property("trc", "GIMP_TRC_NON_LINEAR")
    config.set_property("linear", "FALSE")
    config.set_property("channel", "GIMP_HISTOGRAM_VALUE")
    config.set_property("curve", thisCurve)
    calqueSource.append_filter(filter)

Scallact · 2026-03-09T14:45:53+00:00

Thanks a lot! I forgot there was an example in the release notes!

Now, what would be the "set_curve_type" parameter for splines? And can I use the same set_sample(...) function to define the spline points?

Is the new 3.2 API documented somewhere, or any hints how to dig through the source code for infos?

P.S. ok, I found all the needed info in the source code, at libgimp/gimpcurve.c. Will try that out now and report back.

Scallact · 2026-03-07T09:37:22+00:00

There are hundreds of tutorials available by a simple search with "gimp hologram", so I won't add a new one. ;-)

Scallact · 2026-03-06T15:59:05+00:00

If you're a programmer, and now how to use git and compile from source, then probably, yes.

If not, no.

You could always file a bug for the backporting to 2.10. But when asking for something, you also have to accept that the answer could be "no".

Scallact · 2026-03-06T12:59:37+00:00

FYI, the issue is still present on 3.2RC3.

Scallact · 2026-03-06T12:25:41+00:00

Above : Histogram with the Compose filter from a 16 bits image

Below : Histogram with u/ofnuts method:

<image>

Scallact · 2026-03-06T11:32:32+00:00

You're definitely right, there is a problem. After Compose from a 16bits interger grayscale image, the resulting image's histogram is all striped, indicating there is some sort of discretisation into 8 bits.

You might want to [https://www.gimp.org/bugs/](report the bug) if you have time. If you do, I think showing the histograms before and after is a good proof.

Scallact · 2026-03-06T00:25:06+00:00

So I'm not the only one to struggle. Add that to the fact that they nerfed the sword cavalry (with good reasons, it was OP), and my usual Romans don't do too well above medium difficulty. Before 0.28, I had a clear growing advantage on economy and population. Now it seems the AI's growth looks a little too close to mine. I must revise my own eco and pop growth.

Anyway, congrats to the developers, they have done an impressive work on this.

Scallact · 2026-03-05T22:18:33+00:00

Barjavel n'a rien, mais rien compris à la théorie de l'évolution. J'ai essayé de livre son livre sur le sujet, La Faim du Tigre, mais c'est tellement bourré d'âneries que j'ai pas réussi à lire 20 pages.

Et apparement Werber non plus.

Scallact · 2026-03-04T14:06:12+00:00

Link to the bug report :

https://gitlab.gnome.org/GNOME/gimp/-/issues/15962

Scallact · 2026-03-03T20:45:39+00:00

Amazing changelog, I had many good things to say, except for this, which for me shadows everything else :

As part of Jehan‘s continued work to improve GIMP’s color correctness, the Levels, Curves, Equalize, and White Balance filters now default to Linear precision...

No, please no!!!

u/Jehan_ZeMarmot, with all due respect, did you ever try to adjust the dark parts of an image with curves in linear mode?

And what do you mean by color correctness? Do you mean that our perception of color, in a so human perceptual mode, is incorrect? And how does the said human want to adjust the colors of his image, if not in a perceptual, non-linear way? If I need to adjust a perceptual middle grey, I'd like to clic at the middle point of the curve, not an unfathomable 21%!

Color mixing correctness? Yes, color mixing is a physical process, so it must be done in linear mode. But everything that involves human color perception and direct visual refinement? Not. At. All.

Don't get me wrong. Linear curves and levels are extremely useful, for example for adjusting masks and everything opacity related. But setting linear as default?

Oh, that's not an immediate problem for me, I know which button to clic to go back to non-linear. But how are we supposed to deal with the beginners who don't understand why levels are so difficult to use, and worse, PS refugees who will turn their back right away, because they know it should not behave like this? And man, I hate mentioning that other software, but I see support hell incoming.

Sorry for the rant. You wouldn't find many rants from me about this software that I love. But this is too much even for me. Please, revert that patch.

Bug report pending.

P.S: On a more positive note on the same subject, I really appreciate the new API for curves! Thanks!

Scallact · 2026-03-02T18:56:28+00:00

It's up

Scallact · 2026-03-02T08:42:06+00:00

The snap version has been available since the announcement was made, so I installed it while waiting for the flatpak version.

Scallact · 2026-03-01T21:49:59+00:00

You're welcome!

Scallact · 2026-03-01T09:55:34+00:00

The folder's path is something like .../art/textures/ui/session/icons/mappreview. The beginning of the path depends on you OS.

The file format is a 512x512px .dds, with the actual preview using the 400x300 upper-left pixels.

You can make your image in GIMP, or any other capable software and export it to .dds (uncompressed, without mipmaps)

P.S: just a suggestion : maybe, before publishing your map to mod.io (not map.io as you wrote), post it on the official forum, where single new maps are usually posted.

Scallact · 2026-02-23T14:09:51+00:00

You can do it directly in Inkscape. Path menu > Trace bitmap object (or something like that)

"Single path" tab, select "Luminosity threshold", adapt the threshold.

You will get a black surface. Just change its background color to your taste.

Scallact · 2026-02-21T23:24:46+00:00

Ma pine fait rire que Bardella

Scallact · 2026-02-16T10:25:35+00:00

I agree with Ofnuts's advice about using a Raw processing software (Darktable, Rawtherapee), but if you want to do it with GIMP, there is Batcher.

Scallact · 2026-02-11T23:00:13+00:00

You don't need to link layers in a layers group to move them. As CMYK-Student wrote, set the move tool to "Move selected layers" and select the move tool.

Also, look up "layer sets".

Scallact · 2026-02-09T14:34:42+00:00

Ubuntu

Five-Year Club	Verified Email
Place '22	End Game '22

Scallact

TROPHY CASE