PrusaControl 0.9.4_415_beta (Not Responding)

[StephanJlx]

Hi Guys

I recently became the proud new owner of the MK2 and I am dying to use it but I am having issues with PrusaControl. It opens up etc, but as soon as I bring the part in, big or small, it crashes. It goes into a white none responsive state and I have to force close. I have uninstalled it twice and the fresh install does the same thing. Anybody else having this issue?

Thanks

[prusa3d-bb]

Hello,

Do you have this issue with Sli3cer Prusa Edition as well?

Best regards,

Jennes De Schutter Customer Support

PRUSA Research

+420 222 263 718

+421 220 570 305

Partyzánská 188/7a, 17000, Prague

shop.prusa3D.com

--- original message --- On Tue, Dec 5, 2017 at 07:16 am, [email protected] StephanJlx wrote:

Hi Guys

I recently became the proud new owner of the MK2 and I am dying to use it but I am having issues with PrusaControl. It opens up etc, but as soon as I bring the part in, big or small, it crashes. It goes into a white none responsive state and I have to force close. I have uninstalled it twice and the fresh install does the same thing. Anybody else having this issue?

Thanks

—

You are receiving this because you are subscribed to this thread.

Reply to this email directly, view it on GitHub, or mute the thread. --- end of original message ---

[StephanJlx]

Hi

No, I don't have an issue with slic3r prusa edition. It works fine but I don't like it. Only PrusaControl doesn't work on my PC.

I have managed to get it to work on my slower and older laptop, but this means I have to work on a cloud based storage to transfer between computers. Not ideal.

I think the issue might be the graphics cards but the PC actually has a better CAD graphics card.

Regards

Stephan Le Roux

On 05 Dec 2017 17:34, "prusa3d-bb" [email protected] wrote:

Hello,

Do you have this issue with Sli3cer Prusa Edition as well?

Best regards,

Jennes De Schutter Customer Support

PRUSA Research

+420 222 263 718 <+420%20222%20263%20718>

+421 220 570 305

Partyzánská 188/7a, 17000, Prague

shop.prusa3D.com

--- original message --- On Tue, Dec 5, 2017 at 07:16 am, [email protected] StephanJlx wrote:

Hi Guys

I recently became the proud new owner of the MK2 and I am dying to use it but I am having issues with PrusaControl. It opens up etc, but as soon as I bring the part in, big or small, it crashes. It goes into a white none responsive state and I have to force close. I have uninstalled it twice and the fresh install does the same thing. Anybody else having this issue?

Thanks

—

You are receiving this because you are subscribed to this thread.

Reply to this email directly, view it on GitHub, or mute the thread. --- end of original message ---

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaControl/issues/64#issuecomment-349340536, or mute the thread https://github.com/notifications/unsubscribe-auth/AgrPv77fahLwMSpVdAbAKtXG20UddznVks5s9WJ0gaJpZM4Q1ylE .

[prusa3d-bb]

Hello Stephan,

this might be a problem with the software. I'll report it as a bug.

Best regards,

Jennes De Schutter Customer Support

PRUSA Research

+420 222 263 718

+421 220 570 305

Partyzánská 188/7a, 17000, Prague

shop.prusa3D.com

--- original message --- On Tue, Dec 5, 2017 at 04:43 pm, [email protected] StephanJlx wrote:

Hi

No, I don't have an issue with slic3r prusa edition. It works fine but I don't like it. Only PrusaControl doesn't work on my PC.

I have managed to get it to work on my slower and older laptop, but this means I have to work on a cloud based storage to transfer between computers. Not ideal.

I think the issue might be the graphics cards but the PC actually has a better CAD graphics card.

Regards

Stephan Le Roux

On 05 Dec 2017 17:34, "prusa3d-bb" [email protected] wrote:

Hello,

Do you have this issue with Sli3cer Prusa Edition as well?

Best regards,

Jennes De Schutter Customer Support

PRUSA Research

+420 222 263 718 <+420%20222%20263%20718>

+421 220 570 305

Partyzánská 188/7a, 17000, Prague

shop.prusa3D.com

--- original message --- On Tue, Dec 5, 2017 at 07:16 am, [email protected] StephanJlx wrote:

Hi Guys

I recently became the proud new owner of the MK2 and I am dying to use it but I am having issues with PrusaControl. It opens up etc, but as soon as I bring the part in, big or small, it crashes. It goes into a white none responsive state and I have to force close. I have uninstalled it twice and the fresh install does the same thing. Anybody else having this issue?

Thanks

—

You are receiving this because you are subscribed to this thread.

Reply to this email directly, view it on GitHub, or mute the thread. --- end of original message ---

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/prusa3d/PrusaControl/issues/64#issuecomment-349340536, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgrPv77fahLwMSpVdAbAKtXG20UddznVks5s9WJ0gaJpZM4Q1ylE .

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub, or mute the thread. --- end of original message ---

[lf-]

I'm also experiencing this issue on Windows 7 with 0.9.4_415. Where are the log files I can send you so you can find out what the issue is?

[StephanJlx]

Thanks!

Don't know if you have a suggestion box? I would like to see PrusaControl have a gcode editor too. Unless I am missing it? An even better idea is to build another feature into the Gcode preview toolbar where you can add color changes. Instead of just being able to add color changes you should also be able to show where to start or stop printing. That means that you would have almost flawless print restarts after failures due to power outs etc. And it can be as simple as picking points on a line with visual representation.

I am into my second batch of prints and I love my machine. It does crazy overhangs with zero support...black magic!

On 05 Dec 2017 17:47, "prusa3d-bb" [email protected] wrote:

Hello Stephan,

this might be a problem with the software. I'll report it as a bug.

Best regards,

Jennes De Schutter Customer Support

PRUSA Research

+420 222 263 718 <+420%20222%20263%20718>

+421 220 570 305

Partyzánská 188/7a, 17000, Prague

shop.prusa3D.com

--- original message --- On Tue, Dec 5, 2017 at 04:43 pm, [email protected] StephanJlx wrote:

Hi

No, I don't have an issue with slic3r prusa edition. It works fine but I don't like it. Only PrusaControl doesn't work on my PC.

I have managed to get it to work on my slower and older laptop, but this means I have to work on a cloud based storage to transfer between computers. Not ideal.

I think the issue might be the graphics cards but the PC actually has a better CAD graphics card.

Regards

Stephan Le Roux

On 05 Dec 2017 17:34, "prusa3d-bb" [email protected] wrote:

Hello,

Do you have this issue with Sli3cer Prusa Edition as well?

Best regards,

Jennes De Schutter Customer Support

PRUSA Research

+420 222 263 718 <+420%20222%20263%20718> <+420%20222%20263%20718>

+421 220 570 305

Partyzánská 188/7a, 17000, Prague

shop.prusa3D.com

--- original message --- On Tue, Dec 5, 2017 at 07:16 am, [email protected] StephanJlx wrote:

Hi Guys

I recently became the proud new owner of the MK2 and I am dying to use it but I am having issues with PrusaControl. It opens up etc, but as soon as I bring the part in, big or small, it crashes. It goes into a white none responsive state and I have to force close. I have uninstalled it twice and the fresh install does the same thing. Anybody else having this issue?

Thanks

—

You are receiving this because you are subscribed to this thread.

Reply to this email directly, view it on GitHub, or mute the thread. --- end of original message ---

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <<https://github.com/prusa3d/PrusaControl/issues/64#issuecomment-349340536

, or mute the thread <<https://github.com/notifications/unsubscribe-auth/ AgrPv77fahLwMSpVdAbAKtXG20UddznVks5s9WJ0gaJpZM4Q1ylE> .

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub, or mute the thread. --- end of original message ---

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaControl/issues/64#issuecomment-349345180, or mute the thread https://github.com/notifications/unsubscribe-auth/AgrPv7Nv-W-SUU7PbTQiyTZfqO-usxPAks5s9WV6gaJpZM4Q1ylE .

[prusa3d-bb]

Hello,

Since your comment is in here, it should be noted. Thank you very much. We'll see if your suggestions could be used.

We do not implement any gcode editing since we want Prusa Control to be as fool proof as possible.

Best regards,

Jennes De Schutter Customer Support

PRUSA Research

+420 222 263 718

+421 220 570 305

Partyzánská 188/7a, 17000, Prague

shop.prusa3D.com

--- original message --- On Wed, Dec 6, 2017 at 08:21 am, [email protected] StephanJlx wrote:

Thanks!

Don't know if you have a suggestion box? I would like to see PrusaControl have a gcode editor too. Unless I am missing it? An even better idea is to build another feature into the Gcode preview toolbar where you can add color changes. Instead of just being able to add color changes you should also be able to show where to start or stop printing. That means that you would have almost flawless print restarts after failures due to power outs etc. And it can be as simple as picking points on a line with visual representation.

I am into my second batch of prints and I love my machine. It does crazy overhangs with zero support...black magic!

On 05 Dec 2017 17:47, "prusa3d-bb" [email protected] wrote:

Hello Stephan,

this might be a problem with the software. I'll report it as a bug.

Best regards,

Jennes De Schutter Customer Support

PRUSA Research

+420 222 263 718 <+420%20222%20263%20718>

+421 220 570 305

Partyzánská 188/7a, 17000, Prague

shop.prusa3D.com

--- original message --- On Tue, Dec 5, 2017 at 04:43 pm, [email protected] StephanJlx wrote:

Hi

No, I don't have an issue with slic3r prusa edition. It works fine but I don't like it. Only PrusaControl doesn't work on my PC.

I have managed to get it to work on my slower and older laptop, but this means I have to work on a cloud based storage to transfer between computers. Not ideal.

I think the issue might be the graphics cards but the PC actually has a better CAD graphics card.

Regards

Stephan Le Roux

On 05 Dec 2017 17:34, "prusa3d-bb" [email protected] wrote:

Hello,

Do you have this issue with Sli3cer Prusa Edition as well?

Best regards,

Jennes De Schutter Customer Support

PRUSA Research

+420 222 263 718 <+420%20222%20263%20718> <+420%20222%20263%20718>

+421 220 570 305

Partyzánská 188/7a, 17000, Prague

shop.prusa3D.com

--- original message --- On Tue, Dec 5, 2017 at 07:16 am, [email protected] StephanJlx wrote:

Hi Guys

I recently became the proud new owner of the MK2 and I am dying to use it but I am having issues with PrusaControl. It opens up etc, but as soon as I bring the part in, big or small, it crashes. It goes into a white none responsive state and I have to force close. I have uninstalled it twice and the fresh install does the same thing. Anybody else having this issue?

Thanks

—

You are receiving this because you are subscribed to this thread.

Reply to this email directly, view it on GitHub, or mute the thread. --- end of original message ---

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <<https://github.com/prusa3d/PrusaControl/issues/64#issuecomment-349340536

, or mute the thread <<https://github.com/notifications/unsubscribe-auth/ AgrPv77fahLwMSpVdAbAKtXG20UddznVks5s9WJ0gaJpZM4Q1ylE> .

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub, or mute the thread. --- end of original message ---

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/prusa3d/PrusaControl/issues/64#issuecomment-349345180, or mute the thread <https://github.com/notifications/unsubscribe-auth/AgrPv7Nv-W-SUU7PbTQiyTZfqO-usxPAks5s9WV6gaJpZM4Q1ylE .

—

You are receiving this because you commented.

Reply to this email directly, view it on GitHub, or mute the thread. --- end of original message ---

[pc4life0427]

I am having trouble with newest version of Prusa Control as well...It wont even open on my Mac...it always asks for a Font...different one each time..I have tried to download all over again and 3 times it does the same thing.

[tibor-vavra]

@pc4life0427 Hi, thank you for your report. Please create new issue with screenshot and log file prusacontrol.log (from your home directory).

Tibor

[ottensmeyer]

Running 0.9.4_415_beta. If I open a gcode file generated separately (i.e. Prusa3D Slic3r MK2 Multi Material), the path is correctly displayed, however when trying to load an STL (filenames have only ASCII characters), PrusaControl locks immediately after clicking Open. Any suggestions or additional information that would be necessary for diagnosis? Have tried starting normally, also using Run as administrator, same result. Apologies for multiple postings.

The description of StephaneJlx matches what I observe - Prusa3d Slic3r MK2 Multi Material works fine, but doesn't support 0.1mm layer thickness, hence the need for PrusaControl.

prusacontrol.log is empty (0 byte file)

Thanks, Mark

[FredBluggs]

I too have the same problem.

Open PrusaControl, and import an stl file, and PrusaControl becomes non responsive, utilizing 80+% of CPU time.

Open the same stl file in Slic3r PE and behaviour is as expected, without issue.

Windows 10 Pro ver 1703 Slic3r PE version 1.38.6-prusa3d-win64 PrusaControl 0.9.4_415_beta. STL file used is castle.stl from C:\Users\Public\Documents\Prusa3D\Objects 213\MK3 prusacontrol.log is a zero byte file.

Regards, Fred

[neilgroulx]

I'm also having this same problem. Files open up fine in Slic3r Prusa edition. PrusaControl starts up OK, but as soon as I load a file it becomes non-responsive and I have to force kill it. Completely unusable!

[lonepinetech]

I was using Prusa Control with no issues for many prints. I then upgraded my GPU from the integrated gpu on my gigabyte h27dm-ds3h motherboard to a quadro k620 dedicated gpu. Prusa Control now goes not responsive upon import of an .stl. I will miss it!

[suremicro]

Possible workaround - I also found PrusaControl locking with high CPU usage when loading a model and ran the Windows compatibility checker which seemed to resolve the issue:

Find the executable (for example C:\Program Files\PrusaControl\PrusaControl.exe), right click and choose the Compatibility tab. Check 'Run this program in compatibility mode for:' and select Windows 8 then OK.

Alternatively run the compatibility troubleshooter and following the instructions.

[payala]

I had the same issue, I also have an nVidia Quadro graphics card, and the workaround of @suremicro worked perfectly for me.

[lf-]

@suremicro Interesting! I was reproducing this issue with a Quadro on Win7.

[VHCEngineering]

Any news on this? I too am having an issue on Windows 7 with quadro Graphics card.

[lf-]

Check your driver is up to date. I know on the machine I reproduced it on had a prehistoric driver installed.

On Jul 25, 2018 9:38 AM, "VHCEngineering" [email protected] wrote:

Any news on this? I too am having an issue on Windows 7 with quadro Graphics card.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/prusa3d/PrusaControl/issues/64#issuecomment-407798594, or mute the thread https://github.com/notifications/unsubscribe-auth/AGWDqEVVAoqAgYsewVoKgdKNjKS0FC83ks5uKJDggaJpZM4Q1ylE .

[VHCEngineering]

The graphics card driver is up to date

[beeb]

Can reproduce the issue on my computer with Windows 10 and a Nvidia Quadro graphics card. Program becomes unresponsive upon loading of STL. Workaround is to use compatibility mode Windows 8, it solves it for me.

[throb]

Confirmed here also with Quadro 5000 on Windows 10 with latest NVidia Drivers. Win8 Compatibility mode also solves the issue.