robcat2075

Since you have the problem in v19, you can put in a bug report. Do the screen capture that shows the missing menu item in v19 and include that in your report.

For our contest medals Ken is using the 3D print to create a mold in clay, then pouring molten metal into the negative space.

Are you permanently on v18? Just to try... if you have time to kill... no promises... you might try installing an earlier version to see if it is any different. Earlier versions of v18 are on the ftp site also

It should be between View and Properties I don't use a Mac but you might try Help>Reset Settings, then reboot.

Creature from the White Lagoon 7 hours? I would have just crazy-glued it back on.

Here is the ftp dir for OSX... ftp://ftp.hash.com/pub/updates/osx/

For a while, it was going to be Planes, Trains, Automobiles... and Flying Saucers! FlyingSaucers1000.mp4 Someone asked me if the Image Contest winners had been announced yet. No! I am tediously slow at getting the announcement video done. Hopefully real soon now...

That looks very cool , Paul! How long is the print time for that 2"? I guess eventually you paint it, right?

It can't be any worse than those loops hanging off his face.

Isn't there software that will figure out additional supports automatically? There is no way to model or turn a sphinx shape so there are no over hangs.

There are still flipped patches. I see some problem at the top of the headdress where it all converges also. I think it might be good to make the headdress a separate mesh from the body. It would be easier to diagnose what is in and out if they were separate. clip4702MoreFlipping.mp4

Here is a quickstart on fixing normals... clip4702FlippingNormals.mp4

I took a quick look and, indeed, there are patches with normals not facing out. Tools to help you fix that... Shift 1 will toggle Show Normals ON/OFF f will flip the Normal of a selected patches Shift 6 will toggle Show Back-Facing Normals ON/OFF to make backward patches easier to spot. Shift p will turn on "Patch Group Mode" which lets you just click on the middle of a patch to select it, without having to select all the CPs.

I wonder how many MacOS programs are going to bother to make the jump to ARM.

How about if Steffen had a Mac to test running A:M on Windows on a Mac?

Ouch...

What are the parameters we would look for in a Mac that will be able to stay current for the reasonable future? I guess these are the required elements...

That's a lot of fixin'! Thanks, Steffen! Thanks, Jason!

That was very amusing! And very elaborate! Good work!

Hi Heiner, The significant change is from "Newton" to "Bullet" for simulations. Bullet has support for soft bodies that Newton did not. The rendering is also faster. Most of the work on A:M for v19 has been bug fixes. You can read the long lists of bug fixes and feature enhancements in Latest Info... https://forums.hash.com/forum/2-latest-info/ note that there is a separate post for each release: v19.0... v19.0b...v19.0c...

Here is a first look at the "Summer Memories" medals, cast by Ken Citron (AKA pixelplucker)... 3D print in resin... Clay mold... Pewter casts...

I'm sorry it's been such hassle. Don't get all disappointed yet. I don't think your v18 is the problem right now. I think trying something very basic and small would be useful to test out their pipeline. Just a little lathed torus or vase, maybe. If you could post your model sphinx , there are some 3D printing gurus here who might be able to diagnose it.

There is definitely something wrong with 256 export. Don't use it.

By doing a simple object that you know has no faults you can at least confirm that the pipeline works. the numbers are how many polygons the A:M patches are subdivided into. 64 is one patch into 8x8 polygons, 256 is 16x16 1024 is 32x32 Currently there is a problem with 256. It makes bad polygons. If 256 doesn't work, try 64.

When they say "too large" did they mean in physical dimensions or size of the data in the file? You might try something exceedingly simple and small to start with like a vase.