It isn't any thicker. Look at the actual extrusion amounts from the E-commands. It's the same thickness as the others, it's just raised due to your raft separation distance setting.
I registered to take part in this discussion --> first post, hey there.
I use S3D with a first generation Ultimaker and have recently been able to add a second extruder. Now I am happily dual-extruding away, but have quickly encounterd the same issue as the OP.
I can confirm all of the remarks, the first layer is shown dangerously green in the build preview (printing speed).
As of now I helped myself by overriding the printing speed at the end of the top raft layer, reducing printing speed to 50%. At a base speed of 55 mm/s (give or take 5, depending on the printer's mood of the day) this seems to work reasonably well. However this requires me babysitting the printer through the first 10 minutes of each print.
Hi, I'm also having this issue. I see there's no solution, yet, but I want to keep this thread active. I'm new to 3d printing, and Simplify is the only program I've used, so pardon me, if I don't know all the tricks, yet.
I'm not afraid to learn some g-code. I've figured out some of the basics, already (editing the start sequence, for example,) but if I have to edit the individual part's g-code, every time I export a different model, I'll pull my hair out. Can I edit the layer change script to only slow down the print speed for the layer after the raft, and then resume the model, as usual?
has anyone solved this problem as this is a pretty much software killer for me, i don't mind doing 2 processes but how do you set a process for raft and process for object as they are set due to layer height. would you set it to a minus figure say. and if so would you set it to the number of layers multiplied by the layer height ? as not sure if layer height for raft is set at a standard or weather its the same as the object.
well any help would be great other wise this software is useless to me as i have to print to raft every time.
I didn't solve the issue yet. Using two processes doesn't work for me because the start and stop heights doesn't seem to include the raft. I really don't know why the developers don't address the problem. I think my future solution would be a small program editing the g-code before printing. I'll try that end of may, when i hopefully have some time.
I've run into the same problem - first part layer on top of the raft goes full blast. I also couldn't easily get 2 processes lined up properly to go super slow with the raft to work around the issue; the layers just didn't match up right. It wasn't worth my time to try to get it lined up right as post-processing is far more straight-forward.
As to the thickness issue, I don't see that. There's supposed to be a gap between the first part layer and the raft, so maybe that's making it look thicker?
My issue is the print head moving far faster than it should be with no cooling overrides or anything applied; the g-code comments indicate that it's treating the whole first layer above the raft as inner perimeter. After printing the first layer at 60mms the cooling overrides kick in for subsequent layers making the speed about 16mms for part layers 2+ on a print I did this morning (a vertical tube). Thankfully the print came out okay.
I have found the only true solution to this first layer problem is to edit the G-Code.
You will find that the first layer is set at 100% speed in mm/minute.
it's layer 5 with raft layers set to 1.
I save the G-Code to a special folder and from there I open with notepad. under edit I use find F6000 for example. this tends to get me quickly to the 5th layer.
I then change the innner and outer to F1500. Just check for the following:
A good indicator is the fact that an extrusion value is listed. Just make sure you scroll through the code and look for these lines. once you reached Layer 6 you're done, then save and either press play and select the file of do a send to and select the SD drive.
I'm having this same problem. I can't believe there isn't a solution to this in the software yet without having to get into the GCode and manipulate it.