Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Printer profile settings not registering #17

Open
Asterchades opened this issue May 2, 2021 · 4 comments
Open

Printer profile settings not registering #17

Asterchades opened this issue May 2, 2021 · 4 comments
Labels
enhancement New feature or request not a bug

Comments

@Asterchades
Copy link

I've created a complete custom printer profile for my use which defines a number of settings that I use globally - many of which are formulaic, which is why I don't just use the internal Cura print profile feature. Two of the options I set in this profile are "arcwelder_enable" (true) and "arcwelder_g90_influences_extruder" (also true). However, neither of these settings are "taking" when using the base printer profile, instead reverting to their default values (false for both). This is the same whether I reassign the "value" or "default_value", or both, in the printer profile.

All other options are functioning as I have specified.

The specific declarations I use are:

				"arcwelder_enable": { "value": true },
				"arcwelder_g90_influences_extruder": { "value": true }

No trailing comma as that is the final entry in the profile.

In case it is relevant, I am using SmartAvionics' master builds of Cura, last updated April 20th (just after the 4.9 release). Plugin is v3.5.1 from the Cura Marketplace.

@fieldOfView
Copy link
Owner

Specifying values in the .def.json file is going to be hard to impossible to support in this plugin, because the .def.json is loaded and parsed before the plugin adds its own settings to Cura. In doing so it replaces the settings you made.

Just in case though, could you zip up your .def.json files so I can see exactly how you are trying to do this?

@Asterchades
Copy link
Author

Thalyn_FDM.def.zip

Pretty much exactly as stated. I use two profiles so I can separate out the things that I don't want across all Cura installs (like disabling Wipe for Arachne at present) or printers.

@fieldOfView fieldOfView added enhancement New feature or request not a bug labels May 9, 2021
@fieldOfView
Copy link
Owner

fieldOfView commented May 9, 2021

I'm considering this as "not a bug", but I'll keep the issue open as an "enhancement"/feature request. I never intended the plugin values to be set in the printer definition (.def.json). You can set them in profiles (.inst.cfg) and even in xml material profiles if you wish.

@Asterchades
Copy link
Author

Sounds good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request not a bug
Projects
None yet
Development

No branches or pull requests

2 participants