So Impressions

[Lord Futzi Voldemort]

So here's another one that made it in the new release. I know this one for some time but i didn't report it, because I thought, this is so obvious, someone else has already seen and reported it:

[wmv]http://www.canned-planet.com/media/retime.wmv[/wmv]

You can see clearly, that some random curves are ignored when rippling. Sometimes some curves are only scaled or rippled with a tiny delay, almost unnoticeable, but it can screw up an entire animation. As a workaround you have to use at least 3 retime markers and move the two rightmost together. If you don't know that and a lot of keys are outside the visible range it is easy to create a real mess.

[Rork]

Ppl,

When posting your 'bugs', please3 write how to repo them. Than people can check if it is you, or indeed a bug......

If so, maybe people reading this thread, and are on the beta list, can log these bugs.

Complaining without a repo doesn't help bughunting, does it? ;)

[Lord Futzi Voldemort]

I added a video showing the steps? Isn't it visible for all?

Ah, about complaining:

The "send to" function, doesn't seem to work here at all, neither from or to maya nor from or to mudbox. Can anyone confirm?

[Hirazi Blue]

@Rork - Generally speaking: Agree about the necessity of clear repro steps...

If so, maybe people reading this thread, and are on the beta list, can log these bugs.

This, however makes it sound, if bug reporting is something only people on the beta list can do, while you can also do through the Subscription Center and through this web form (although it hasn't been updated to include Softimage 2014 yet)

[Rork]

yeah.. sorry, missed the vid ;)

with the send to... options, that's from within the 2014 applications, right?
because you cannot send to... from different versions. e.g. no 2013<>2014 etc.

[Rork]

This, however makes it sound, if bug reporting is something only people on the beta list can do,

no, but might the faster track......

[Lord Futzi Voldemort]

@Rork - Generally speaking: Agree about the necessity of clear repro steps...

If so, maybe people reading this thread, and are on the beta list, can log these bugs.

This, however makes it sound, if bug reporting is something only people on the beta list can do, while you can also do through the Subscription Center and through this web form (although it hasn't been updated to include Softimage 2014 yet)

I also thought beta was over with the release? Oh, I forgot, it's Autodesk...

[Lord Futzi Voldemort]

yeah.. sorry, missed the vid ;)

with the send to... options, that's from within the 2014 applications, right?
because you cannot send to... from different versions. e.g. no 2013<>2014 etc.

Absolutely.

Edit: the send to function actually opens the right application, but nothing is transferred.

[xsisupport]

yeah.. sorry, missed the vid ;)

with the send to... options, that's from within the 2014 applications, right?
because you cannot send to... from different versions. e.g. no 2013<>2014 etc.

Absolutely.

Edit: the send to function actually opens the right application, but nothing is transferred.

I've seen that sometimes when sending to Maya...and then I clicked in Maya and that seemed to wake things up and the Send finished. It's like it was paused or something. I don't do Send a lot so I cannot be more specific.

[Bellsey]

@Rork - Generally speaking: Agree about the necessity of clear repro steps...

If so, maybe people reading this thread, and are on the beta list, can log these bugs.

This, however makes it sound, if bug reporting is something only people on the beta list can do, while you can also do through the Subscription Center and through this web form (although it hasn't been updated to include Softimage 2014 yet)

I also thought beta was over with the release? Oh, I forgot, it's Autodesk...

In the past it was like that, but now as part of the overall feedback community, 'Beta' is a kinda constant ongoing project with preview release builds being dropped on a regular basis (sometimes monthly).

On the 'Send To' function, I have also experienced the oddity of the pause. I haven't been able to figure out why this happens when sending from Softimage to Maya. Usually when there's a lag/pause and nothing appears to be happening, I've just clicked on the File Menu and as Stephen says, it wakes up and works.

[Eugen]

Regarding that pivot bug:
The only case I have encountered the pivot being definitely wrong is with subcurves, which I reported in the 2014 beta (no fix yet).

Did you change the temporary tool pivot?

[csaez]

Regarding that pivot bug:
The only case I have encountered the pivot being definitely wrong is with subcurves, which I reported in the 2014 beta (no fix yet).

Did you change the temporary tool pivot?

The loops in the screenshot are not uniformly distributed over its surface, so the point position average is not at the center of its bounding box.

[Lord Futzi Voldemort]

Regarding that pivot bug:
The only case I have encountered the pivot being definitely wrong is with subcurves, which I reported in the 2014 beta (no fix yet).

Did you change the temporary tool pivot?

The loops in the screenshot are not uniformly distributed over its surface, so the point position average is not at the center of its bounding box.

Yes they are uniformly distributed. You can try it out.

[Lord Futzi Voldemort]

yeah.. sorry, missed the vid ;)

with the send to... options, that's from within the 2014 applications, right?
because you cannot send to... from different versions. e.g. no 2013<>2014 etc.

Absolutely.

Edit: the send to function actually opens the right application, but nothing is transferred.

I've seen that sometimes when sending to Maya...and then I clicked in Maya and that seemed to wake things up and the Send finished. It's like it was paused or something. I don't do Send a lot so I cannot be more specific.

I know it was like that (nothing to be proud of either). At first I thought that was the problem. But as I said in my post: Nothing gets transferred - not from soft to maya, not from maya to soft, not from soft to mudbox, not from maya to mudbox. There is also not "connected to maya" button in the ui. And anyway: Why in all the world does the send to function still change my viewmanager layout for no obvious reason? That is soooo annoying.

[Lord Futzi Voldemort]

Regarding that pivot bug:
The only case I have encountered the pivot being definitely wrong is with subcurves, which I reported in the 2014 beta (no fix yet).

Did you change the temporary tool pivot?

I fact, I had a problem once, where the temporary pivot was not reset, after deselecting the object. That was a different issue and is not related to the confirmed COG bug. Just try it: create a cube, add 3 edgeloops select the point and watch.

Here a re a few other interesting experiments:

Create a grid, select all points and play around with the references, COG, Obj, Local etc. - The Gizmo will always be in the right place. Now connect two of the points somewhere in the grid. The COG is immediately off. So I thought, well it is calculated based on Polygon numbers and position, not based on point numbers and position as you would expect.
In the image the xform gizmo is in local mode and offset!

cog_wrong.jpg

But then I switched to rotate, and surprise, the gizmo is right where it should be in object mode.

cog_right.jpg

But in COG or Local mode it is off center, so no it can't be the number of polygons.

cog_local_wrong.jpg

[Lord Futzi Voldemort]

In the past it was like that, but now as part of the overall feedback community, 'Beta' is a kinda constant ongoing project with preview release builds being dropped on a regular basis (sometimes monthly).

.

So were buying in fact an unfinished product. Well, in that respect, nothing much has changed anyway.

I don't understand why you don't release monthly or bimonthly builds, so we can benefit from that "beta" work. Instead we wait a whole year, only to find out, that our reports are ignored. Good way to make unhappy customers.

apologizer.png