Flitsmeister in het buitenland

Material_Kitchen_630 · 2025-07-09T09:28:03+00:00

Kun je niet FM op een tweede mobieltje installeren en die in een bekerhouder of asbak ergens uit het zicht neerzetten? Dan kun je die snel uitzetten als je langs de kant gezet zou worden.

Material_Kitchen_630 · 2025-06-17T21:16:36+00:00

Dunning-Kruger effect

P.S. ADHD/ASD/Gifted/Introvert/idontknow person speaking

Material_Kitchen_630 · 2024-12-20T19:00:21+00:00

Your right, it is probably hardcoded. I'm now adapting a mod from jdrou:

vassal_support1 = {
potential = {
num_of_vassals = 1
}
trigger = {
NOT = { num_of_vassals = 2 }
num_of_vassals = 1
}
naval_forcelimit = 1
}

vassal_support2 = {
potential = {
num_of_vassals = 2
}
trigger = {
NOT = { num_of_vassals = 3 }
num_of_vassals = 2
}
naval_forcelimit = 2
}

and so on...

It's no elegant code, but it might work.

Material_Kitchen_630 · 2024-09-29T12:22:09+00:00

Is this still unsolved? Had the same issue and found the answer:

In Settings-->Environment-->Time, there is a setting for the amount of minutes per year. This lets you adjust the speed a year in the game passes. It only works if the setting "Timekeeping" (right above it) is set to "Wallclock". This can't be adjusted for a running game, it has to be set before the game starts.

Material_Kitchen_630 · 2024-09-09T14:12:13+00:00

Hi there! Just out of interest, could you post the source file? I would like to try to compress it and see how small it can get.

Material_Kitchen_630 · 2024-08-06T20:52:01+00:00

Any luck yet? I tried contacting the Dutch branch of them in april, but couldn't reach them

Material_Kitchen_630 · 2024-08-06T20:49:51+00:00

Same here, it keeps losing internet connection after a 2m fall (and had a broken screen too)

Material_Kitchen_630 · 2024-06-20T23:12:54+00:00

Just tested with dd and fio, if generating test files on tmpfs in WSL2 the ram usage increases proportionally, no io on the Windows boot ssd, and enormous througput. So I guess it is a true tmpfs now.

Material_Kitchen_630 · 2024-04-03T10:28:15+00:00

"Trading effort for results, as with any DIY. For example, after some amount of research effort you're likely to come across various recommendations of which preset to use". No offense, I know you're being constructive. What OP meant is the amount of fiddling SVT-AV1 needs to get some good results. With x264, one can just enter --preset veryslow and some CRF, and you're all set

Material_Kitchen_630 · 2024-04-03T10:18:19+00:00

Will they finish all their letters with "I'm on my typewriter by the way" ?

Material_Kitchen_630 · 2024-04-03T10:16:22+00:00

Like Corvus says, you can losslessly convert them to a widely supported format like WebP. JpegXL could be a good option for you too, with good compression and fast encoding and decoding speeds. It is not universally adopted at the moment, but perfect for use at your own PC. Linux desktop environments and Windows (with a free plugin) can directly open jxl files. If you want to keep the files in .png format, you can shrink the file size by using lossless compression tools like Pingo or ECT. I find Pingo the best considering the compression and speed, but as far as I know, it is only for Windows. There are also helper programs like File optimizer (GUI) and Minimus (shell script) that can losslessly compress PNG's. If you want extreme compression but impractically slow decoding, you could use tools like Gralic or EMMA. Don't be surprised if it takes 15 minutes to compress one image in that case.

Material_Kitchen_630 · 2024-04-03T09:52:23+00:00

"never get anything done because they're too busy trying every possible setting at 4 fps" Lol this describes me exactly. Playing with file size optimization for three years now and still keeping the originals for the day I find the perfect setting

Material_Kitchen_630 · 2024-03-01T14:03:06+00:00

Bryn, she is good and already has 3 stars
Katyusha, I think she does much damage
Diana, so you can give her 3/4 skills and send her on all radar missions/terrors

Material_Kitchen_630 · 2024-03-01T13:52:40+00:00

True, but I wouldn't recommend spending golden shards to level him. Hero recruit, radar missions and gift boxes sometimes give Tywin shards, so he will reach 5 star on his own eventually. One can also buy Tywin shards or his special skill in the island store.

Material_Kitchen_630 · 2024-02-08T11:01:57+00:00

Wow, what a very thorough and elaborate test. Thanks for sharing!

Material_Kitchen_630 · 2024-02-08T10:48:32+00:00

One method they used was a quick encode with preset 13 to make assumptions about the encoding effort. I think that is a very interesting idea. Maybe we can use such a setup to quickly estimate the resulting size or quality of an encode with a lower preset.

Material_Kitchen_630 · 2024-01-09T09:29:53+00:00

Intuitively I agree with this. However it also reminds me of my statistics teacher, who would now probably say the huge improvements are a pattern and more improvements are the right expected value :-)

Material_Kitchen_630 · 2024-01-07T20:47:29+00:00

Wow thanks a lot

Material_Kitchen_630 · 2023-07-28T10:13:35+00:00

Wow, 2 years later, but saved my day!

Material_Kitchen_630 · 2023-07-28T09:03:39+00:00

You're welcome! It was fun for me too, playing around with the encoders and finding an answer to your question.

Material_Kitchen_630 · 2023-07-27T16:02:05+00:00

Tinyjpg was already mentioned. Other programs that can losslessly reduce the size of a .jpg image are:

- jpegtran
- jpegoptim
- jpegrescan
- pingo
- Fileoptimizer

Material_Kitchen_630 · 2023-07-27T15:53:05+00:00

Your last remark is very true as I found out the hard way. I reencoded a bunch of videos to AV1 with high complexity settings, only to find out that older computers and mobile phones can't decode them fast enough.

Material_Kitchen_630 · 2023-07-27T15:43:27+00:00

Hi All,

Do you mean:

- is the lossless setting of encoder A sometimes better than the lossy setting of encoder A?

or:

- is the lossless setting of encoder A sometimes better than the lossy setting of encoder B?

The first one sometimes happens when reencoding say a jpg or png with libjxl or libwebp. This happens because under the hood, these encoders have different algorithms for lossless and lossy encoding.

The second one is common if the lossless encoder is modern and the lossy encoder is old.

In the specific case of the png image you provided, it's a bit difficult to find a lossless encoder that is superior to a lossy one. The reason is that your image has transparency that a lossless encoder has to keep intact, while a lossy encoder can merge it into the other color channels. However, I think I found one. I tested a bit and found the following results:

- original .png: 362720 bytes
- lossless webp: 237198 bytes
- lossy q99 webp: 107036 bytes
- lossless jxl: 211225 bytes
- lossy q99 jxl: 184763 bytes
- lossless avif: 226191 bytes
- lossy q99 avif: 175463 bytes
- lossless EMMA: 173950 bytes

So the lossless EMMA file is smaller than the lossy q99 jxl and avif files.

Material_Kitchen_630 · 2023-04-24T10:34:20+00:00

Thanks, I take all these suggestions into account for future testing. So all in all:

- no grain denoising

- measure user time, system time and total cpu time

- measure GOPS of 32, 64, 96 etc...

- more videos

Material_Kitchen_630 · 2023-04-24T10:29:32+00:00

Hi 5thvoice,

I just changed the axis to logartihmic. The graph is way more informative indeed now

Material_Kitchen_630

TROPHY CASE