Alias 2024 Issues - Including Math differences

Alias 2024 Issues - Including Math differences

amandaallsion.lila
Advocate Advocate
1,156 Views
2 Replies
Message 1 of 3

Alias 2024 Issues - Including Math differences

amandaallsion.lila
Advocate
Advocate

Hi, I have noticed several things that have really impacted my work flow in the latest Alias version - currently 2024.1. Most of them are disruptions to the smooth operation of tools, which knocks me out of flow. But I've also noticed a difference in the math of certain surfaces which I cannot find an explanation for, and can only assume this is a fundamental difference in the way surfaces are calculated and created.

 

I did a test between 2024.1 and 2022 Update 2.1  and am clearly seeing that 2022 will produce a 5 degree single span surface from the same projected 5 degree single span COS or trim edge, whereas 2024.1 creates a 5 degree, 5 span in 2024. This is using the Skin tool. Construction settings are exactly the same between both. Rebuilds are on in the skin tool in both versions. But, even if I turn rebuilds OFF in 2022, it still builds a clean surface there. This is what I've been experiencing regularly in 2024, and it requires me to rebuild/reduce spans on each surface manually after it's made, and sometimes, it even WARPS the surface when it rebuilds. (I don't have an example of the warping in this post, but it's something I have experienced with great frustration.)

 

I build very clean bezier math in general and have been using Alias almost exclusively in my career for nearly 27 years, so please trust me when I say something is very different. This isn't just user error, or me not knowing how to build properly. 

 

I looked for others commenting on this and was surprised to not see a mention of this on the forum. Perhaps it could be something about my specific construction settings, but I did try to reduce the tightness/tolerance of the trim curve fit, thinking perhaps that would resolve it, but it doesn't seem to have an impact.

 

I will be happy to work with the developers to send a sample file if this is helpful.

 

Otherwise, there are some general frustrations I have experienced which I have listed here. These have disrupted my workflow and I feel are messing with the beauty of Alias, which is the ability to move very quickly and intuitively, and not have to confirm function executions. Not only have there been changes in this regard to require confirmations on certain functions, but they may not even accept a space bar. This may not seem like a big deal to some people, but it really can be highly disruptive to flow. And if this is what Alias excels at, then it shouldn't be messed with. It should be an OPTION - and not made the default workflow.

 

I've listed below some things I've noted, and whether they seem like a disruption, or a bug:

 

Disruption to Design:

-Extend and Trim - require YES click to do if COS is not going to create a solid trim. EXTREMELY annoying and disruptive to flow. (Does not even respond to a space bar YES)

 

-Tool Dialog windows sometimes these pop up right in the way of work when activated - such as TRIM - I go to select an area to keep and the dialog box pops up right in the way of the cursor.

 

-When clicking in a text field, it is harder to click to a specific number to change. It requires a click, a pause, and another click, since a single click, or a double click highlights the entire number. It seems this was redesigned to easily select the FULL number, but it's consequently made it more difficult to easily adjust decimal points numbers.

 

Bug or Design disruption:

-Proportional Move tool shows blend of 1 upon first use after startup, but is actually functionally set at 0. Requires moving slider away and back to 1 to reset every time Alias opens. Also is set to be unlocked between U and V, so requires a click to lock before adjusting. That seems counter-intuitive. Attempts to save preferences with this set to 1 and locked have not saved.

 

Bugs:

-Pick Objects on Layer, followed by Delete Active:
Have noticed when attempting this sometimes, the objects highlight as picked, and then when delete is selected, they deactivate, and Alias says no objects were active to delete. Alias requires a restart to function properly.

 

-Undo does not always work for Extend. I may extend a surface an undesirable amount and then go to undo and it won't undo

 

-Build differences? Perhaps related to the surfacing change I discussed above:

COS are more sensitive, and extend with distortions much more often, and extend much less often to enclose a trim area in the trim tool.

 

And as noted above, surfaces built from trim edges or COS are often much heavier than what it builds in previous versions, and I do not yet understand why. Construction settings and build settings are exactly the same.

 

 

0 Likes
Accepted solutions (1)
1,157 Views
2 Replies
Replies (2)
Message 2 of 3

Michael-GG
Alumni
Alumni
Accepted solution

@amandaallsion.lila thanks a lot for your very detailed, long and structured analysis here! I truly appreciate the time you have put into this post. I will send you my email address in a PN, so you can share your data with me.

I will try to address every single point you have made in your post above. Could you be available for a screen sharing session, to minimize my effort to ensure I do see (and therefore can log) exactly the issues you describe above? If not, that's fine, but it would be very helpful!

Thanks a lot,

GG



Michael G.-G.
Manager Quality Assurance Automotive
Message 3 of 3

amandaallsion.lila
Advocate
Advocate

Thank you, Michael. I appreciate your help looking into these things! I'll respond to your DM.

0 Likes