The result is multiple versions of Chief sharing a single settings file. This means the 3DConnexion software creates a settings file for Chief based on the ID Chief provides when registering for 3D mouse events. Applications have the option to create their own 3DConnexion settings file but Chief relies on the 3DConnexion software to do this for it. The root cause is due to the way Chief lets the 3DConnexion driver store its settings and identifies itself with the same ID string "ChiefArchitect" for every major release. ![]() Technically this is a bug / limitation in the way Chief registers/configures itself with the 3DConnexion software but given how few people this probably affects I've not reported it as its less important than others and importantly there is a workaround. ![]() If you use a 3DConnexion mouse in multiple versions of Chief Architect and notice it loses any custom settings/speeds when running one version then another (on Windows at least) then read on.īackground (for the interested, otherwise jump to the workaround)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |