#217 Default compatibility level not reflected in compat. menu

[Fabian Greffrath]

Hello,

sorry for the misleading subject line, but this is really a bit tricky to explain in one sentence.

When I change the "Default compatibility level" in Options/General to something different than "default", then I expect this setting to have an impact on the fine-grained compatibility options in the Options/Setup/Doom Compatibility menu. However, independent of the set default compatibility level, the settings in this menu are all set to "no".

In Zandronum, for example, the fine-grained settings are updated live as I change the compatibility level, which I find far more intuitive.

- Fabian

[Fabian Greffrath]

> In Zandronum, for example, the fine-grained settings are updated live as I change the compatibility level, which I find far more intuitive.

This even work so in plain ZDoom.

[Nobody/Anonymous]

Hey There. I found your blog using msn. This is a very well written article. Ill make sure to bookmark it and come back to read more of your useful info. Thanks for the post. Ill definitely return. Burberry Bags http://burberrybags.v5s7.com

[Tirsa Poppins]

How do you propose this should work? Those options are supposed to be applicable only with mbf_compatibility and higher, and to take effect immediately; default_compatibility_level takes effect only after G_DoLoadLevel.

If a user sets DCL to a vanilla complevel, changes one of the compat menu options then restarts the program, should the change be lost? If it's kept, there's a discrepancy between it and DCL. Should DCL be changed then, and to what?

I find your idea interesting, but it may be pretty complex to implement. The current system badly needs an overhaul in any case: it's confusing, contradictory and unintuitive. Having to take demo recording into account makes it even more messy.

I like Zdoom's approach too, but I don't think it would be easy to incorporate into the current tangled system.

BTW, these options don't seem to be applied to demos except with best_compatibility. Is this intended behavior?

[Fabian Greffrath]

I wasn't aware of the sheer complexity of the demo compatibility settings in PrBoom+ when I filed this request. However, I understand now that this is a very complicated and fragile code path and I am fine as long as it works as it does.

The current system badly needs an overhaul in any case: it's confusing, contradictory and unintuitive.

This!

[Fabian Greffrath]

I wasn't aware of the sheer complexity of the demo compatibility settings in PrBoom+ when I filed this request.

I should add that I believed back then that each of the "-complevel" levels corresponded to a specific combination of switches in the Options->Setup->Doom Compatibility menu. I wasn't aware of the fact that these only revealed the tip of the iceberg.