robcat2075

Oops... I think I see one tiny bit of patch weirdness where the horizontal and vertical window dividers meet.

Looks good. What is the roof intended to be?

I think Jason, the keeper of the A:M registrations, is at a convention right now so an immediate turn-around is unlikely.

I'm not sure about the sequence vs. single question but... 2554pixels x 410 pixels x 24bits per pixel / 8bits per byte = 3.1 MB if you have an alpha channel in the TGA it's 32 bits per pixel and makes for 4.1 MB I believe the size that A:M reports once an image is imported into the Images folder is the full uncompressed size of the image.

What formats does it play?

The effector could work for a stationary floating object but not for a boat that moved forward and turned, leaving a curved wake behind it. Something I was experimenting with was using particles ejected horizontally from a moving shape to build a displacement map for the wave that is created as a boat moves forward and turns. boatwake.mov

I'm looking at it. Need to remember all the stuff.

Converting a video to an image sequence is also a useful work around.

If your CPU doesn't support SSE4 (mine doesn't) then the option will not appear. But it would be a box to check during installation.

After updating my NVidia driver i get slightly better behavior. A:M survives the switch to Bones Mode but crashes when do (T)urn. Now the computer doesn't need to be rebooted anymore, either, so that's progress!

Interesting. i can reliably create a freeze that way.

OK, I've discovered that the freeze happens if you are using OpenGL rather than OpenGL3. Try that.

I get a complete freeze when i do that. i have to press the hard reboot button on my PC.

Someone try this in v18d and tell me what happens.... -restart your computer -start A:M v18d -start a new Object window -Lathe a vase in the normal fashion -ctrl-a to select all -ctrl-c to Copy -ctrl-v to Paste -drag the still-selected copy a bit to the left -click in the background to deselect all -Press the Bones Mode button

Nice to see you back, John!

And the problem is that Steffen doesn't have a Mac with an NVidia card? that will make it harder. Is there a previous version of A:M that works correctly in these things?

I think yours are clearly new bugs and when you have time make a report on them.

Just to try... any or all of these -Options>Global switch the real-time driver. (may need restart) -Options>OpenGL switch "inverse sort order" (may need restart) -do Reset All Settings (will need restart) If those don't help then a bug report is in order. Until that can be fixed revert to the last version that worked appropriately.

If you need to get an AO appearance on bump-mapped surfaces there is a way to add it in

Here's a test Object I made in v17 with all normals facing out. When i load it in v18 it still looks right. normalsOutTest.mdl

Can you post that object (not re-saved in v18)?

v18d just went up. Try that. That's what I'm testing and i don't get a delay.

Can you post a sample model where the next step causes this lock up for you, or post a model and describe the steps that do it? I'm still not sure what the maneuver is to try it.

Fuchur, is it fixed in v18c? I can't reproduce the problem but I'm not quite sure what it looks like and I'm not on v18b

I've been meaning to do it. If anyone else has it done already, speak soon.