dosmax wrote on Today, 08:47:Quick 2.6.8 feedback: […]
Show full quote
Quick 2.6.8 feedback:
I think the removal of the default values settings page was not a good decision. Even with the DFendX's goal of supporting modern DosBox flavors out of the box, it is still useful for (at least) two reasons:
1. Some settings (like e.g. resolutions, cycles, shaders etc.) still benefit from being user-configurable even with full support for a given DosBox flavor.
2. At some point DFendX development wil inevitably cease too, at which point any removed customization option becomes not just an inconvenience but a potential problem.
--
Sidenote: not sure whether that is just an isolated issue here or an actual bug, but with DosBox Staging as my default DosBox, the Glide page seems to be incomplete/wrong. Everything besides 'Activate Glide' and 'Glide Emulation' is greyed out. Staging does not have a 'Glide emulation' 'emu' setting I think, but it does have voodoo_memsize, voodoo_threads and voodoo_bilinear_filtering, which are all greyed out for me.
Hi,
Thanks for the feedback. I'll address some of your points:
1. As for the removal of the default values settings frame, this was a necessary completion of something that should have already happened, as the underlying feature that it related to (customizing confo box lists) was removed long ago, for a range of reasons.
- First and foremost, supporting multiple DOSBoxes means many of the confo now have different lists depending on the DOSBox kind. The value editor only supported the concept of a single custom user list per confo, meaning the whole point of switching DOSBox kinds is lost. The complexity cost of having more than one use custom list per confo outweighed their value, especially when considering other drawbacks.
- The default value list override could result in a bad user experience after program update - as after a user has changed the default value for one list, they will not see updates to the default list after a program update. So they might be unaware of new dosbox features that would have otherwise appeared. Having to reload the default list, then edit it again, after every upgrade, is a poor user experience IMO.
- DFendX had more complex combo boxes that D-Fend Reloaded - some (like shaders/presets) are dynamically loaded from scanning files on disk at load time, other combos interact with each other, i.e. the values in combo B might depend on which value is chosen in combo A, and these more complex interactions coexist very poorly with custom user values in lists.
- There exists a perfectly good solution to custom user values in conf overrides - i.e. "Custom settings" in the "DOSBox settings" frame, as well in the "more settings for this DOSBox installation" form. These simply override whatever gets generated automatically before DOSBox loads, survive program updates, can apply at a profile or installation level, coexist nicely with any kind of complex combo interactions that might exist, and are the better approach for users to target custom conf values DFendX doesn't (yet) support.
- If DFendX is not supported at some time, custom conf lists will only get you so far. There will eventually be something else that breaks that changing these lists won't fix, either in one of the DOSBoxes or Windows itself. I.e. software needs to be maintained or it will rust eventually.
2. Glide settings for Staging. When I have Staging selected for a profile, I see memory size/bi-linear filtering/threads combos all active. Are you sure the profile itself was set to Staging, not just the program default? I did spend quite a bit of time comparing the different glide support offered by the three DOSBoxes, and I hoped the combos reflected that, but if I missed something I will fix it in the next release.
Cheers