GZDoom 4.9.0 released

[shaodoomkahn]

how do i change save and screenshot folder location

[Hirogen2]

Actually, /proc/cpuinfo is a pseudo-file provided by the kernel, itself. And yes it is quite well expected that on Linux you use /proc information - virtually all Linux tools that matter do so, anyhow.

Your expection is quite wrong; the format of /proc/cpuinfo varies wildly between processor architectures, which does not lend itself very well to parsing. /sys is the authoritative source, and that is what lscpu uses.

[Doomguy 2000]

Is it just me or does the startup music function not work properly?

[Blzut3]

Your expection is quite wrong; the format of /proc/cpuinfo varies wildly between processor architectures, which does not lend itself very well to parsing. /sys is the authoritative source, and that is what lscpu uses.

Actually it does. That said, you're not completely wrong in that it does use /sys for some things, and that's probably a better place to get the topology info if you need it.

[brick]

I just noticed that the patch notes for 4.9.0 have this change:

carry over the tiling flag from the finished to the entering screen

Unfortunately this seems to revert a bugfix that was introduced in 4.8.2:

fixed background tiling for summary screen.

As a result 4.9.0 now has reintroduced a bug that was present in 4.8.1 and that was fixed in 4.8.2, where Heretic intermission maps tile when they should not.

I think I understand the reason for wanting the tiling to carry over (if the entering screen also uses a flat like the finished screen), but maybe the best solution would be to have the script differentiate between flats to tile and images to not tile (it seems to already know how to deal with Doom maps - those are not being tiled and are centered as they should be)

[Graf Zahl]

This has already been fixed.

Also, please don't post bug reports on the news thread. Can't you read the BIG RED NOTE on the news post?

[yum13241]

Proof that big red warnings don't always work. Some just don't read or are willfully ignoring.

[Rachael]

Doesn't mean they're bad.

A lot of problems are the sole problem of the person themself. You can lead a horse to water but you can't force it to drink. But for serial offenders we can revoke posting privileges selectively, and that's not entirely unheard of for us. I just don't think this particular instance qualifies as needing to go that far.

[yum13241]

Doesn't mean they're bad.

Very true.

I just don't think this particular instance qualifies as needing to go that far.

I also agree (not like my opinion matters about this)

I hope the "news" gets across: News is for News! Not "I found a bug!".

[combolynch]

RIP Using separate gzdoom profiles for specific tc's and mods

[Rachael]

-config <custom.ini> is still perfectly valid for that use, and it will work.

[Graf Zahl]

Portable installs are as well. Even older GZDoom's only had one INI per installation folder.

For god's sake, is it this hard to read an announcement to process all information...

[KynikossDragonn]

For god's sake, is it this hard to read an announcement to process all information...

Considering I unfortunately come across people that pull the "too long didn't read" card on me then wonder why something isn't working, yes it apparently is too hard to read.

I can understand if someone has a form of attention deficit syndrome, but it feels more like rude spite most of the time.

[combolynch]

Portable installs are as well. Even older GZDoom's only had one INI per installation folder.

For god's sake, is it this hard to read an announcement to process all information...

what is portable install, I read the topic for info but I didn't understand it. Is it like installer something?
But yeah I figured out that I will stick to creating custom ini's for the mod. Then I will copy it to the ini folder when I play the true mod for it.

[Graf Zahl]

A portable install is one where the ini is kept locally. All you need to do is naming it gzdoom_portable.ini.