-
-
Notifications
You must be signed in to change notification settings - Fork 723
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
RatRig V-Core 4 Profiles #5932
Comments
I'm not seeing much difference from the profiles in #5660, is there something I'm missing? |
We also based the profiles in PrusaSlicer and did a few tests in-house for the different machine variants, trying to optimize as best as possible for now, while keeping the file structure organized with our developers, ensuring future updates and iterations simpler. (Hopefully!). Unfortunately I wasn't aware of your PR, is it already on OrcaSlicer? I couldn't see it in my local installation |
It should be in the latest version as it was included in v2.1 RC and shows up in my installation of v2.1.1 UPDATE: I'm currently adding the given profiles with the names changed to what is currently in Orca Slicer so that any custom profiles that have been made shouldn't become broken from this update. |
I noticed that some values like |
fdm_process_ratrig_common.json |
Is there an existing issue for this feature request?
Is your feature request related to a problem?
Hi! I'm here submitting the new V-Core 4 Profiles by RatRig! This is the first iteration of the profiles so all the feedback from the users is welcomed and will be taken into consideration for future updates!
I've attached the RatRig.Json file as well as the RatRig Folder, everything was tested and in proper working condition!
RatRig Profiles 29July2024.zip
Which printers will be beneficial to this feature?
Klipper
Describe the solution you'd like
RatRig V-Core 4 profiles! This might not be the right place to submit them. If so, sorry in advance and I will publish them in the right place.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: