Jump to content
SandervG

Welcome to Ultimaker Cura 3.2 | Stable

Recommended Posts

Posted · Welcome to Ultimaker Cura 3.2 | Stable

The nasty scrambled-font-problem is there again with Cura 3.2 on my MacOS 10.13.3 version.

 

Share this post


Link to post
Share on other sites
Posted (edited) · Welcome to Ultimaker Cura 3.2 | Stable

Hi guys.

In "layer view" i just see "compatibility mode" instead of previous color scheme with 3 options, feedrate, material color, and line type.

I seen a flag in general settings about the "compatibility mode". It's referred to that (in this case it's not functioning.

 

Second question: where to find a manual (or an upgrade of manual) with the new functions?

 

Thanks in advance to anyone will help.

Herman

Edited by erman58
nowi try to restart the system after installation to see if the situation it's the same...

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable

I just want to report that on Cura 3.2 on MacBook I do not have proper letters, see attached screenshot.

I have this only on 3.2. 

5a7b45ca15463_Bildschirmfoto2018-02-07um19_25_55.thumb.png.ffa2721f18c56e6e4f477a1391bda8be.png

Any suggestion what to do?

Thank you.

 

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable

... no change restarting computer.

Another: no plugins version upgrade 3.1 to 3.2. Why? (win version)

 

Are you sure that it's all ok?

Suggestions?

Thank you

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable

How are you installing the plugin? It works for me using the Plugins -> Browse Plugins.

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable
6 minutes ago, ahoeben said:

How are you installing the plugin? It works for me using the Plugins -> Browse Plugins.

I did it that way. I also have installed it directly from github to the plugin folder and, although the installation is made (as version 3.1 not 3.2), it actually does not work. It does not print when pushing "Print to octoprint" button

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable
50 minutes ago, osmunda said:

I also have installed it directly from github to the plugin folder and, although the installation is made (as version 3.1 not 3.2), it actually does not work. It does not print when pushing "Print to octoprint" button

 

That is the exact symptom you get when you install the 3.1 version of the plugin in Cura 3.2. I have only just come around to switching the github page to the 3.2 branch by default; before just now the default download would get you the 3.1 version of the plugin which is not compatible with Cura 3.2 (due to changes in the API between Cura 3.1 and Cura 3.2). Having said that, the official way to get the plugin is through the Plugin Browser or using a .curaplugin file.

 

Please remove all versions of the plugin from your configuration folder (including any versions you have manually installed), and restart Cura. Then use the Plugin Browser to install the plugin and restart Cura. If that does not work, please upload your cura.log somewhere (dropbox, google drive, etc) so I can have a look.

 

If you manually install the OctoPrintPlugin from git, chances are you end up with the plugin in a different folder than the plugin browser expects it, and it is possible that if you install an updated version with the plugin browser you end up with multiple versions of the plugin that fight eachother.

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable

@mrSEADEMON and @erman58: In the General preference page, is the option "Force layer view compatibility mode (restart required)" checked? If so, uncheck it and restart Cura.

 

If that does not solve it, that means that your graphics driver tells Cura it does not support the features needed to show the "non-compatiblity-mode" version of layerview, and Cura can only display simplified layerview.

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable
Just now, ahoeben said:

@mrSEADEMON and @erman58: In the General preference page, is the option "Force layer view compatibility mode (restart required)" checked? If so, uncheck it and restart Cura.

 

If that does not solve it, that means that your graphics driver tells Cura it does not support the features needed to show the "non-compatiblity-mode" version of layerview, and Cura can only display simplified layerview.

thanks. I add start cura with Nvidia card and all work

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable
18 hours ago, ahoeben said:

 

That is the exact symptom you get when you install the 3.1 version of the plugin in Cura 3.2. I have only just come around to switching the github page to the 3.2 branch by default; before just now the default download would get you the 3.1 version of the plugin which is not compatible with Cura 3.2 (due to changes in the API between Cura 3.1 and Cura 3.2). Having said that, the official way to get the plugin is through the Plugin Browser or using a .curaplugin file.

 

Please remove all versions of the plugin from your configuration folder (including any versions you have manually installed), and restart Cura. Then use the Plugin Browser to install the plugin and restart Cura. If that does not work, please upload your cura.log somewhere (dropbox, google drive, etc) so I can have a look.

 

If you manually install the OctoPrintPlugin from git, chances are you end up with the plugin in a different folder than the plugin browser expects it, and it is possible that if you install an updated version with the plugin browser you end up with multiple versions of the plugin that fight eachother.

I have removed the octoprint plugin folder but I have the same errror when installing it from Plugin Browser. In fact, There is no Octoprint archive or folder for this plugin in the installation folder neither at github branch (https://github.com/Ultimaker/Cura).
I am sorry but I can't find the requested cura.log. Please, where I can find it?

Thanks for your support

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable

You should not need to download anything from github. Forget github for now.

 

To find the log file, launch Cura and go to Help -> Show configuration folder. There's a file named cura.log in that folder.

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable

Could you tell me what files are inside C:\Users\Eladio\AppData\Roaming\cura\3.2\plugins\OctoPrintPlugin\ ?

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable

The following ones:

 

DiscoverOctoPrintAction.qml
LICENSE
OctoPrintComponents.qml
OctoPrintOutputDevice.py
OctoPrintOutputDevicePlugin.py
README.md
__pycache__
OctoPrintPlugin
.gitignore
__init__.py
CMakeLists.txt
DiscoverOctoPrintAction.py

 

I thought that I have removed that folder but I did it from tin installation folder at C:\Program Files\Ultimaker Cura 3.2. Maybe I should remove them from this location also?

 

 

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable

Yes, that's what I've been trying to have you do ;-)

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable

Great. Now it works. I don't know what was the initial problem but after removing that folders and installing it from Plugin Browser (and activate the plugin plus restart the program), it works.

Thank you very much for your support and your effort

 

Share this post


Link to post
Share on other sites
Posted (edited) · Welcome to Ultimaker Cura 3.2 | Stable

This is not stable at all.

I installed it 6 times now. Each time it crashes some of my various higher end 3d software, or simply won't launch due to the same error I got for EVERY Cura version after like 2.1 or 2.3 and up until 3.1 ( which worked fine.. until now.. ) The error is related to win updates and service packs informing me that AGAIN, I need MORE service packs to run Cura 3.2 

YOu cats need to understand some of us out there simply can NOT keep adding service packs etc and altering our pipeline.. they often have compatibility issues with other 3d software. This can not keep being the answer for you guys. I can't keep ruining my career software so I can 3d print. This is obviously a prob with 3.2 as when I re-install 3.1 I have no issues.  Thoughts?

Edited by VULCAN

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable
On 2/6/2018 at 7:51 AM, kmanstudios said:

Oddly all my Avast installation did was to run a scan for malware, report it was safe and then say "It was a rare file and will be sent to HQ for further testing" and then let me install with no issues. The last time I installed with Avast I did get a pop up saying that the file was fine and added to Avast's clean list. Or, whatever they called it. But I did not have to create any exceptions.

 

Edit, oh yeah, also, nothing popped up regarding arduino or anything else.

Lose AVast for starters. It is garbage. No high end IT people use it at all. Mcaffee, avast, norton, all garbage and basically a virus in themselves. And they sell your info. Kapersky is the only true secure hold out. They won't sell their code to the US OR Russia where they are from. Most IT guys in my industry that requires an insane amount of legitimate system security use Kapersky for anti virus. 

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable

The thought I have is that you are doing a rather poor job describing what your problem is, making it very hard to help you. This is your first post here, and I have no idea what you mean with "the same error I got with EVERY Cura version after like 2.1 or 2.3".

 

I do share a house with a cat, but I am - in fact - human.

Share this post


Link to post
Share on other sites
Posted (edited) · Welcome to Ultimaker Cura 3.2 | Stable

typicall UM team response.. read it again.. and not my first post. QC better. If you want to help, help. 

did you miss this?

The error is related to win updates and service packs informing me that AGAIN, I need MORE service packs to run Cura 3.2 

 

Edited by VULCAN

Share this post


Link to post
Share on other sites
Posted · Welcome to Ultimaker Cura 3.2 | Stable

All you say is " The error is related to win updates and service packs informing me that AGAIN, I need MORE service packs to run Cura 3.2 ". I am sorry, that does not ring a bell for me. Unless you take a breath and take some time to be a bit more descriptive, I can not help you. If you just came to vent, and don't want my help, that's fine with me as well.

 

I do spend a lot of time working on Cura, but I am - in fact - not part of the UM team.

Share this post


Link to post
Share on other sites
Posted (edited) · Welcome to Ultimaker Cura 3.2 | Stable

So why are you replying if you can't help? What is hard to understand about what I said?  What is descriptive?  I sent the error to UM.. what else? If you don't get that, you obviously didn't see what was happening with prev versions.. the same issues,,. what do you want ? Just to chime in? Ask me a question if you want to help...  Just telling me you don't like the way I talk isn't helping. When you need a product to work and you have spent thousands on it and the dev team keeps fixing things that aren't broken and breaking things that work, then maybe you can tell me to take a breath. I on the other hand have a job to do and don't have time for garb like this when it is billed as STABLE. 

Edited by VULCAN

Share this post


Link to post
Share on other sites
Posted (edited) · Welcome to Ultimaker Cura 3.2 | Stable

Is this descriptive enough? I had to do this thing called research to figure out that it was referring to wanting me to update to another OS or use more Service Packs.. I had to research that error just to find out that info.. so how much more descriptive would you like it hot shot since this is the only error I get? ( It doesn't let me view the "detailed crash report" ) before you ask.. 

 

 

 

 

Cura32Error.jpg

Edited by VULCAN

Share this post


Link to post
Share on other sites
Posted (edited) · Welcome to Ultimaker Cura 3.2 | Stable

Anyhow. I'll fix it myself like I have done with every UM and Cura problem so far. No sense in trying to get help. 

Edited by VULCAN

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • Ultimaker Cura 4.0 | Stable available!
      Ultimaker Cura 4.0 is mainly focused on the improved user interface and cloud integration.
      As always, we want to collect your user feedback for this release. If there are any improvements you can think of, feel free to mention it here and help us to shape the next release.
      • 96 replies
×
×
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!