CURA DOESN'T OPEN

[johnnywawsher 0]

There have been atleast 3 threads about this and NONE of the devs have a fix to such a stupid bug?

When you click on cura it just loads and doesnt respond

[nallath 1,120]

Well, none of the devs can reproduce this stupid bug. If we can't reproduce it, it's almost impossible for us to debug it (and also know if we actually fixed it).

Getting angry or typing in caps, although I guess it's probably nice to get it off your chest, isn't going to change any of those things, unfortunately.

[Guest]

My suggestion would be to include a verbose logging option in Cura, so you don't have to tell your users that you are helpless.. Clearly, without doubt, you don't have enough.  Also, don't ever try to write files to the "Program Files" directory after you are finished installing.  Most users won't have access to do that and it's not how Windows programs are meant to work.

[ahoeben 1,948]

58 minutes ago, Jason9 said:

Also, don't ever try to write files to the "Program Files" directory after you are finished installing.

 

What makes you think Cura tries to do that? It doesn't. Never did.

[Guest]

Did you search for *.* in the Cura installation directory and sort by date descending?  There's heaps of .qmlc files that have their dates updated each time you start Cura.  Bad, bad, not good.  May not be the problem here, but.. bad.

[ahoeben 1,948]

You run Cura as Administrator. Bad, bad, not good.

[Guest]

:)

 

Yeah, the machine I'm talking to you on is actually connected to the Internet.  None of my other ones (which I use to print) are.

 

Keep trying though.

[nallath 1,120]

Uh. Those are just cached / compiled files. We could disable that, but then Cura would run a whole lot slower.

 

Also, there is quite a bit of logging in Cura already, but although logging helps, it isn't some magic tool that miraculously enables us to fix all issues. If only that were the case.

[Guest]

Sure, but if you enabled entry/exit logging, it would probably help with hangs.

[nallath 1,120]

You are aware that entry/exit logging is for crashes (and thus, does absolutely nothing when the software hangs), right?

[Guest]

As a 50 year old professional software developer, no, endless loops are generally shown to be within an entry point that never exits.

[nallath 1,120]

To be honest, I still don't understand what you mean or how this would solve any of the aforementioned issues. But feel free to have a look at the codebase and suggest how it can be changed. I think that will have more actual results than popping generic advice that may or may not be applicable to the situation.

[Guest]

Right.  It's late where I am so I'm leaving the forum, but as a team-lead in a software development team for a large government department, I suggest.. talk to your lead and/or business-owner.  He/She will have good advice for you and your team.  But I feel for the OP, I think the caps were justified now.  I don't think my advice here was obscure.

[nallath 1,120]

For what it's worth I talked to my lead (although it was a bit awkward to talk to myself like that...)

[spudgunman 0]

I am totally new to this, haven't even got my printer working.. I installed cura3.6.0 opened a stl and it was there I could see my thing and what not.

 

I just added plugin for Auto Slicer, Auto Orientation, Backups, Repetier, Z offset

 

after this I cant open any STL files, I do but nothing happens looks like same issue. looks like the app has serious issues

 

uninstalled all the plugins, no change.

uninstalled the whole app config files and all config files

still not working

Microsoft Windows [Version 10.0.17763.253]

 

really not kidding, I found this as silly as the guy arguing in this thread, but I get his frustration.. 3.6.0 and it works like a 0.0.1 code.

 

 

Edited January 29, 2019 by spudgunman

[JLemmens 0]

Same problem.

Cura opens ONCE when I open it as long as the computer hasnt been on for a while. Then it locks up opening any file after which I can't open it anymore. Sometimes it just doesn't open at all but it is active in the "processes".

 

It's pretty annoying that I have to use a Mac *shudder* to use this.

[nallath 1,120]

I can share a bit of good news; We managed to get some machines that exhibited the problem and implement fixes that work on those machines. The fixes have been merged, so they are in the next release (4.5). If all goes well, it will be released within 2 weeks.

[ahoeben 1,948]

41 minutes ago, nallath said:

If all goes well, it will be released within 2 weeks.

 

Will that be a beta, or is the "final" release scheduled in two weeks?

[nallath 1,120]

Beta (which is always the case as far as the Cura team is concerned; We really, really, really like having a beta before a "real" release, because it makes the real one more stable)