G-Code Viewing - to ascertain X - Y - Z dimensions ons sliced stl file from Thingiverse  

RE:

Are you sure they used Prusa Slicer to generate the gcode ?  Bad Allocation is usually a problem with memory.  Is the file large ?  Large files with lots of small lines to preview (such as produced using Gyroid infill for example) means using a LOT of computer memory.  

Besides that if all you wanted to do is a filament change to a different colour at a particular height then you could just open the gcode file in a text editor (as long as its not bgcode) and then manually insert a M600 command at the start of the correct layer.  You wouldn't have to reslice.

Also one other thing if you open up Prusa Slicer and use File>Import>Import Config and then select a gcode file it will load in all the settings used for the actual slice.  It wont however help with what the original part was scaled to as it just loads the profile settings in as they are stored at the end of the gcode file.

Although also examining the gcode manually in a text editor will include the maximum layer height its printing at so you could use that info to scale the part to the same height.

RE: G-Code Viewing - to ascertain X - Y - Z dimensions ons sliced stl file from Thingiverse

The artist decided after the bgcode was created by the Prusa Slicer ( I used) they wanted some of the design to be 1 color and the rest of the object to be another color.

I selected File > Import Config and found that bgcode file and clicked Open but that object never opened in the Prusa Slicer.

I then selected File > Import Config from Project but ti didn't find that bgcode file.

I finally selected File > Import Config Bundle bit it too didn't reveal that file or load it.

I'm trying to learn what the best practices are once you slice the gcode in the Prusa Slicer to then add colors?

Joan and others have shared how to add color(s) with the slider but can I somehow load the bgcode and then add colors via the slider?

I would start from scratch and add colors but the artist wanted the object a certain size and I'm still trying to read bgcode (seems hard than tea leaves!)

Thank you so much for this brainstorming!

RE: G-Code Viewing - to ascertain X - Y - Z dimensions ons sliced stl file from Thingiverse

Would you mind posting the file you tried to load the config from ?   I'd like to see if I can figure out why you can't load the settings from it.  You will need to zip it up first for the forum to accept it.  Otherwise the forum will silently drop it. 

btw it wont load the Object/geometry,  its not supposed to.  It loads the SETTINGS in for use with whatever CURRENT objects you are working with.
You also cant use 'import settings from a project' as its gcode and not a project.  That option is for loading the settings from a PS .3mf file into your currently open slicer session.  Same with config bundle as its not a .ini file that contains pre-packaged bundles of settings.  

gcode/bgcode is the 'finished' form.  You cant re-slice it or really do anything with it in the slicer.  You can look at the raw text of the file and edit it in any text editor though (for gcode, you cant do that with bgcode as its been converted to binary).

This is why saving a project file for everything you do in PS is a good habit to get into.

Normally you save profiles for commonly used settings, which are what the basic ones are anyway.  However if you are working on something and think 'I want to use the custom settings I used on xxx' and you didn't happen to save a proper profile for them then you can use the import config option to import most of them from a saved project.