@Ryan_Carlyle None of that sounded rude and I agree with all of that except the last sentence. I’ve noticed visible differences in each slicer I have tried with the same part and it all depends on the part. Unfortunately you can’t tell very well which slicer is best for a part until you try each one for every part which can be extremely wasteful. The Autodesk software might not show a visible difference but we can’t really speculate without testing.
Is the 3D Print Utility of a similar codebase?
http://blog.123dapp.com/2013/07/introducing-the-autodesk-3d-print-utility
@Nick_Kloski Both are from Autodesk so I would expect the codebase to be similar but the version integrated into Spark will probably be more refined and more powerful. Of course I’m just speculating based on reason. You could look at the source files on Github (link posted in comments above) but I doubt you will have a full answer until commercial release at the end of the beta.
@Nick_Kloski There is some of the same functionality but Print Studio and Spark are new.
There seems to be some confusion about what Spark is and does. It’s a platform. A set of APIs with a data and processing backend (cloud). While those in the dev program can get a standalone Print Studio, the beta group is aimed a devs to start making apps or integrating services and machines to the platform. Those that wish software to test will be disappointed. Unless of course they can make the software themselves. 
Same settings? 99% of print settings are in the slicer, looks like Slic3r could do with more (or maybe less) slowdown in cooling.
Looks like you need flexible couplers and to make sure you have the proper step/mm for the x and y axes
Downloaded this jewel. Installed it. Looks nice. What, you can’t set the temperature? ok. Slicing went well. Save and print with repetier…Preview… Nooo. That can’t be good. It looks it’s skipping every other layer. Tried a simpeler model… Oh, well let’s ust print and see what it does. Prints the first layer… And stops. Sends the bed way down.
Nah, typical Autodesk program. Looks nice, doesn’t do nice.
Sorry, Cura engine is 10 times better, and so is slic3r.
@Rien_Stouten It sounds like it thinks your printer is an SLA machine the way it keeps moving the bed. I’m curious though how did you get a download?
Z-Wobble isn’t such a great issue as the photo and lighting brings out very small defects. I’m also using a legacy Mendel so theoretically z-wobble should be nonexistent.
Also I printed a modified version of this with Slic3r at a different angle. @Ryan_Carlyle (All overhangs and curves are at the same angle.) ill post photos of that later today also. Print Studio has a sensible slicing algorithm. @Adam_Steinmark I have been using Slic3r for a time and I am using the latest version. I have easily hit at least 80 hours with slic3r.
When I get home Ill update this with the link to the Print Studio files!
@Rien_Stouten It’s a beta version meant for developers, not end users… It’s not meant to be a standalone slicer for any printer. It’s meant to be part of a bigger platform where this is an example of how to use it in the context of Spark. Were you using it in the manner intended you would understand the issue of which you complain.
The temps and other parameters are set from profiles developed by the printer manufacturer to use in conjucntion with a pre defined set of materials. It’s similar to someone like Printrbot giving you the ini file for a slicer or getting an S3D profile from a printer manufacturer.
Does print studio work for DLP printers? I would think so, if it is driving Ember…it would be GREAT to have more options out there for DLP resin printing besides Creation Workshop.
Or, another way of asking…it probably odes support DLP, but since Autodesk does not manufacture any FDM printer themselves (yet), does it support FDM?
@dstevens_lv Oh, excuse me for my tremendous stupidity, oh mighty one.
We all should know by now that Autodesk developers don’t develop for mere mortals.
Please do forgive me. Tomorrow I shall sell all my autodesk stock, so that the omnipotent autodesk developers will never have to deal which such a stupid nincompoop like me, okay?
But seriously, when a slicer program is promoted in a user group like this one, it is only fair that you get an honest review based on experiences with mentioned software and the hardware that is often used by said users.
If you have a problem with that Sir, bugger of.
(Yes, that’s right, I don’t like to be called stupid or ignorant. Silly me.)
@Nick_Kloski Print Manager works with both SLA and FDM processes. Print Studio is a standalone preview of what you can do with Print Manager and the API. If you have an Ember you use Spark to print right now. The Ember process is production release quality though does not yet incorporate all of the potential features of Spark, it has all the basics, print prep, healing, printing and cloud storage.
@Rien_Stouten It’s not being promoted here, a user mentioned it. You downloaded a closed beta from an unauthorized source without the supporting docs and notes. That’s on you. You then jumped to conclusions about what it is supposed to be without being fully knowledgable as to what the software is about.
It’s not just Autodesk devs that can work on it. It’s anyone that is accepted into the program now. (which is most anyone that applies) It will be open to all devs when they get it to a point where it’s ready for public consumption. That’s why it’s a closed program right now, it’s not yet ready for wide consumption.
Spark is no more of an end user tool than Xcode, a C complier or an iOS API. You are taking the use out of context and are using it to support your agenda of ranting against “the man”. That’s a weak argument.
@dstevens_lv
Dear mr. Stevens, I don’t like your tone, and your arguments suck and contradict each other. I get the impression that you are an employee with Autodesk, because I recognise the condescending tone in your replies. As a daily user of Autodesk products, and a beta-tester for some of them, I can only be confirmed in my opinion that Autodesk inc. is on the way out, since companies that don’t listen to users are dead, or soon will be. As they should. Wake up mr. Stevens, take a deep breath, and smell the internet.
Oh, and don’t start the stupid discussion about closed sources. If you don’t want your appalling program all over the internet ( I woudn’t I’d be too ashamed), do something to prevent it. It took me one search on google, and the third link was the jackpot.
The first two were only corporate yadahyadah-pages with no real info by Autodesk, as usual.
And that is the last I’m gonna say about it. Print studio is not worth the trouble.
@Rien_Stouten I don’t work for Autodesk. I am using the platform as a prototype. For a Reprap I think a better solution is something like Octoprint though at the moment it doesn’t have the depth Spark does. It could though with a few more plug ins, specficially healing. From a technical perspective a lot of Spark is pretty cool though I still don’t think having the backend host all the processing is the best use of resources.
Well that escalated quickly.
@Joe_Spanier @dstevens_lv @Rien_Stouten I have posted a link to the Spark github. Check it out on the community software page.
@Aaron_Spaulding I posted the link a bit earlier in the thread. I’ve had access to the program for a while. There’s more to it than the Github, though it can give a good idea of what it’s about. Once you have access to the platform you can test against a dev environment, submit a machine type to be included in the platform and other things. There are some interesting (to me, anyway) tech demos for various ways of working with meshes. The API is pretty well documented and there is sample code for most popular languages.