PrusaSlicer with better RRF time estimates.
-
@pcr Very nice! Thank you!
Where is the .ini settings file saved? is it /users/user/Library/Application Support/PrusaSlicer-n8/ ? Or is it in a folder named just PrusaSlicer? This is important to keep the n8 version separate form the stock version.
Also, the PrusaSlicer.desktop file might not be configured correctly. I don't even know what it's for really. Does the correct name and icon appear for the app in your desktop environment?
Please don't hesitate to let me know of any issues you encounter I'd be happy to hear about them. I've never had it running on linux! Linux looks nice. What desktop environment you using?
-
@pcr I ended up making a PR anyway, so feel free to comment with any desired changes or problems:
-
@bot when will you merge upstream ;)))) hehe beta 2 is out
-
@pcr there is really not much added since I compiled this. Mine is basically beta2, except a few tiny bug fixes. If you need anything specific let me know. I have a beta2 branch that you can compile:
n8-240b2 -
@bot thankk you. Really like your improvements
-
Off topic, but people on here are are familiar with Prusaslicer and it's useful for anyone else starting with it:
How the *$%£^!! do you get it to select a tool/extruder??
I have three tools defined.As it is, the GCode has
M104 S240 ; set temperaturebefore the start gcode or any tool selection.
For a multi-tool machine it needs the appropriate tool / extruder selection before any related settings, but I cannot find how to do that?
It looks really good; I grabbed it last night and have spent a few hours going through the settings & trying to figure out all the appropriate options, and done a lot of searching, but just cannot find this info.
Up to now, I've only ever used Cura, an old version originally specified for use with my Overlord pro delta printer.
It's always worked fine for that, but is rather restricted for the Duet-based machine.
In that, I've been setting the correct tool in the start gcode; nothing is sent before the start sequence. -
@rjenkinsgb you have to put it in your start g-code. Also, select "RepRapFirmware" g-code flavor.
-
I definitely released the n8 version of 2.4.0-beta2.
It is... colourful.
-
Spammmming my own thread
-
@bot That is really good!
-
@pcr Thank you! Let me know how you feel after a few days.
At first, I was reluctant about the colours but I went with what seemed to be best practices. I have since fallen in love with the colours. Dat sequential magma spectrum...
*not actually a robot
-
@bot will do.
Just have to adjust the hash of a file....
See my PR on upstream
https://github.com/prusa3d/PrusaSlicer/pull/7380
closed Update Hash of wxWidgets #7380
-
I did my first print using your slicer version yesterday afternoon/evening.
The time estimate was spot on.
And, the print quality is vastly better than the old Cura slicer I use with my Overlord Pro and initially used for the Duet machine!
The item sides have no noticeable layer lines or ripples, just a really good result.Thanks!
-
-
@pcr Very nice!! Thank you.
I saw that it's somewhat easy to do: use an existing app image, replace all the files. (Don't forget the resources folder! That's where the opengl shaders are located)
I wonder if this process is possible to do on macOS? I would hate to have to bug you every time to make an appimage for me! lol.
*not actually a robot
-
@pcr Hey hey hey would you like to make an appimage for this latest release? Make sure you include the
Resourcesfolder from this release, because that is where the shaders are... and that is the main improvement!https://github.com/n8bot/PrusaSlicer/releases/tag/version_2.4.0-beta2-release2-n8
-
@bot here ya go
https://anonfiles.com/56F150Ybu3/PrusaSlicer_n8_beta2_release2-x86_64_AppImage
and yes i am repacking the original prusa slicer appimage
thats faaaarrr easier -
@pcr Wow thank you so much!
Do you have any suggestions for improvements in the source code to make building/deploying on linux easier? I've never done it, but there are some potential improvements that could be made to the PrusaSlicer.desktop and gcodeviewer.desktop files. Do you have any idea what is best for them?
-
Sorry, but these new shaders are out of this world:
-
@bot thats true! look so good. Thats why i "reopend" the PS github talk about this
But honestly i dont think they will do a change. Mainly because they had to adjust the docs.the build process of the PS is pretty simple. Once you have all deps. But you can link them. So you dont have to compile them each time. The PS compile time is pretty quick, at least with 16 cores
The crazy thing is that if you compile the deps and PS the size of the folder is over 5GB.....They implemented a special options to add the desktop files in the menu bar. So now its easy.
I am using PopOS (Debian Based) with Gnome DE. PopOS is great for getting a machine running quick and without hiccups. Its not the most "linuxy" distro out there. But for end users who have not the time to dig deep into the linux multiverse its great. Plus it handles the drivers pretty good. Including the switching of Laptop GPU´s (Nvidia->Intel).
