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

2.4.58.1/2.4.58.2 Crash on startup #2620

Closed
lordIcocain opened this issue Apr 2, 2022 · 12 comments
Closed

2.4.58.1/2.4.58.2 Crash on startup #2620

lordIcocain opened this issue Apr 2, 2022 · 12 comments
Labels
bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build

Comments

@lordIcocain
Copy link

lordIcocain commented Apr 2, 2022

What happened?

Got crash on startup in last two version of 2.4
2.4.58.0 working
2.4.58.1 can start only when AppData/SuperSlicer empty
2.4.58.2 crash in any case (still creating files in AppData/SuperSlicer)
image

Also, my windows user name contains Cyrillic characters, in the console it is written with weird characters.(on screenshot below)

Project file & How to reproduce

image

Version

2.4.58.1, 2.4.58.2

Operating system

win10

Printer model

Any

@supermerill supermerill added bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build labels Apr 2, 2022
supermerill added a commit that referenced this issue Apr 2, 2022
Fix Script can't open file with utf characters (hopefully)
#2620
@lordIcocain
Copy link
Author

Hello, just tested night build, no problem with startup. Thank you.
Still get some errors, but not saw any problems in work.
image

@supermerill
Copy link
Owner

can you help me to debug these errors?
As long as they're here, you won't have quick settings and some settings will be missing.

can you try to add a "configuration" directory next to your superslicer.exe file, and report if it still fail?

@lordIcocain
Copy link
Author

image

@lordIcocain
Copy link
Author

lordIcocain commented Apr 3, 2022

Last night build with folder "configuration"
image
and without
image
UPD
in folders \ui_layout\default and \ui_layout\example just no have this files.
I run 2.4.58.2 with folder "configuration", no crusher and no errors. Also not have files what required on screenshot upper.
UPD
I run Night build what was before build "Fix wipetower temp&fan, script error on startup" and there no errors. Only about "Error in a Vendor Config Bundle".
I hope that might help.

supermerill added a commit that referenced this issue Apr 4, 2022
@lordIcocain
Copy link
Author

lordIcocain commented Apr 5, 2022

image

@supermerill
Copy link
Owner

supermerill commented Apr 6, 2022

Does it still error out for script & quick settings?

@lordIcocain
Copy link
Author

Seems like it trying load ui_script files what actually does not exist.
filament.as
sla_material.as
printer.as
These files were not required in previous versions, they were not in the settings directory and there were no errors that these files were not found.
The program began to request these files in a nightly update that fixed bugs with Cyrillic(UTF) path.

@supermerill
Copy link
Owner

Seems like it trying load ui_script files what actually does not exist.

I know, and it's indenteded. There is currently no scripted widget on these tab, and so i didn't created the scripted file,n as they aren't needed. You can see that now that I added logs, but it's completly harmless.

do you still don't have the quick setting on the platter tab?

@lordIcocain
Copy link
Author

I'm confused. I dont get any problems in program working. The quick settings window opens and works as it should.

@supermerill
Copy link
Owner

The quick settings window opens

the "quick settings" are the three widgets here
image
and if the script fail, you can only have the "infill" one (as it's the only one that isn't scripted)

@lordIcocain
Copy link
Author

image
it ok too

@supermerill
Copy link
Owner

great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build
Projects
None yet
Development

No branches or pull requests

2 participants