Search found 37 matches

Go to advanced search

by smeagollum
Wed Dec 13, 2017 5:09 am
Forum: General Discussion and Tips
Topic: v4.0.1 is out......
Replies: 9
Views: 2763

Re: v4.0.1 is out......

Unfortunately there are graphics issues on Win 10 also. Not sure the performance is worse, but the print preview looks horrible compared to v4.0.0. The moire patterns are really bad. Here's an example: s3d_401_moire.jpg This is the Moon City model , sliced at 0.2 mm layer height. The pattern varies ...
by smeagollum
Wed Dec 06, 2017 5:16 am
Forum: General Discussion and Tips
Topic: Why can't S3D do this properly? Or can it?
Replies: 18
Views: 3548

Re: Why can't S3D do this properly? Or can it?

A continuous printed 50% infill is stronger than a peg only sitting on perhaps 3 or 4 top layers because the affiliation is deaper instead only bonding by the layers. Closing the surface makes sence when you want to seal the part belowe. That's a fair point, I guess. However, surface quality (the s...
by smeagollum
Tue Dec 05, 2017 7:24 pm
Forum: General Discussion and Tips
Topic: Why can't S3D do this properly? Or can it?
Replies: 18
Views: 3548

Re: Why can't S3D do this properly? Or can it?

@horst.w: I disagree. Not that I don't want the process splitting (which is a good thing), but that doesn't mean there shouldn't be any automatic functions for issues like this. It is cumbersome to split many times, and adjusting the split points after the fact entails editing each of the processes ...
by smeagollum
Tue Dec 05, 2017 8:50 am
Forum: General Discussion and Tips
Topic: Why can't S3D do this properly? Or can it?
Replies: 18
Views: 3548

Re: Why can't S3D do this properly? Or can it?

@horst.w: Splitting into multiple objects is of course a possibility, but it is a bit cumbersome. @brian442: Thanks a bunch, that method works, even if it gives me even more solid layers under the peg. Fine-tuning the splitting positions can fix this, though (reducing the total height of the middle ...
by smeagollum
Tue Dec 05, 2017 6:12 am
Forum: General Discussion and Tips
Topic: Why can't S3D do this properly? Or can it?
Replies: 18
Views: 3548

Re: Why can't S3D do this properly? Or can it?

I agree that it would be wasteful in the example with the cubes, but I think the user should be able to choose. It could also have been an option to have a setting for an area where S3D should use solid layers instead of holes. This could be similar to the area setting for bridges, and for small are...
by smeagollum
Mon Dec 04, 2017 7:50 pm
Forum: General Discussion and Tips
Topic: Why can't S3D do this properly? Or can it?
Replies: 18
Views: 3548

Why can't S3D do this properly? Or can it?

S3D is a very fine slicer, but it has some quirks and annoyances, and this one is particularly irritating. Instead of many words, here's a picture: s3d_issue.jpg This is just a simple plate where there are some pegs protruding upwards. The issue is that S3D insists on breaking up the top layer with ...
by smeagollum
Thu Nov 30, 2017 3:37 am
Forum: General Discussion and Tips
Topic: Modifying the Gcode, then creating x3g
Replies: 3
Views: 1080

Re: Modifying the Gcode, then creating x3g

S3D doesn't really have built-in functionality for generating x3g. It ships with a open-source executable called GPX which it calls in the background to do the conversion from gcode to x3g. In other words, you can just do this conversion yourself, after editing the gcode file. You need to figure out...
by smeagollum
Sat Nov 25, 2017 7:11 pm
Forum: Troubleshooting and Bug Reports
Topic: broken gcode generated with size of 65536 kByte = 64 MByte
Replies: 4
Views: 1266

Re: broken gcode generated with size of 65536 kByte = 64 MBy

I think most customers would agree on this, but the update frequency is what it is.
As for a bug list, this is a user forum, and it isn't actively used by the developers. It is monitored by them, but they don't engage in any discussions.
by smeagollum
Fri Nov 24, 2017 7:12 pm
Forum: Troubleshooting and Bug Reports
Topic: broken gcode generated with size of 65536 kByte = 64 MByte
Replies: 4
Views: 1266

Re: broken gcode generated with size of 65536 kByte = 64 MBy

This is a known issue in v4, there are other posts about it as well. It should of course have been fixed, but S3D seldom releases updates to the software. It will probably be fixed some time next year, I guess.
by smeagollum
Sun Oct 15, 2017 1:05 pm
Forum: Troubleshooting and Bug Reports
Topic: [FIXED] 64MB bug with Factory file when using big STL files
Replies: 8
Views: 4697

Re: v4 64MB bug with Factory file when using big STL files

I did a quick test myself now, and chose a model that would generate a very large g-code file. The g-code file ended up at 163 MB, but as Jacotheron says, it is padded with a lot of null bytes. In fact, after removing those, the file is reduced to 133 MB, so there was around 30 MB of junk null bytes...

Go to advanced search