View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0031433||2.x IDE Bugs||Configurations||Public||2019-10-14 11:25||2020-03-27 14:33|
|Reporter||Patrick Roche||Assigned To||Steven Campbell|
|Priority||High||Severity||B - Major||Reproducibility||100%|
|Platform||OS||Windows 10||OS Version|
|Target Version||2.3.0||Fixed in Version||2.3.0|
|Summary||0031433: Configurations: Parent configs are inheriting settings from child configs|
|Description||Parent configs are inheriting asset group-use information from their child configurations when the user restarts the IDE. This means that a texture group that's in a child configuration of the default configuration can change the default configuration. Parent configurations should never inherit properties from their children.|
|Steps To Reproduce||1 - Launch IDE|
2 - Tools > Texture Groups
3 - Click Add New
4 - Set the new texture groups name to something memorable (testTex1 for example)
5 - Close the texture groups menu.
6 - Expand Configurations in Resources Window
7 - Create a new Configuration named testConf1
8 - Switch to the newly created testConfig by clicking the target button in the top right.
9 - Open texture groups and select testTex1
10 - Uncheck everything in 'Use Group on' and close the menu
11 - Save and close IDE. Relaunch IDE.
12 - Switch to default config using the target in the top right
13 - Open texture groups
14 - Switch to testTex1
15 - Notice all options are unchecked
|Tags||No tags attached.|
|2.x IDE Found In||126.96.36.1990|
|2.x Runtime Found In||188.8.131.527|
|2.x IDE Verified In|
|2.x Runtime Verified In|
||I don't think this is the issue, it is just that texture groups and audio groups cannot be different in each configuration so when changed they are changed in ALL configurations.|
||Check as per Russ's comment|
Indeed - as per Russell's comment - texture and audio groups cannot be different for each configuration (which is different from the documentation for both configs and texture/audio groups).
However, I believe some of the confusion is stemming from the fact that during a session, you can change the Use Group On... settings per config, and it will show different values of what config you are in. It is not until you close and open GMS that all configs get the Use Group On... values of the last active config.
||2.3.0 is a big change for the project format, so we will address this as part of this work.|
||Will say CB5, as that's when this was resolved, but really all CBs so far...|