Unwanted face overrides in VW 2022

[Kaare Baekgaard]

When I use an existing textured object to create a new object - by shelling or using boolean operations – and then give the new object textures by changing its class – I get unwanted texture overrides. Leftovers from its earlier incarnations so to say, that I then have to delete.

 

This is a bug.

[Guest Shengxi Wu]

Hi @Kaare Baekgaard, thanks for the feedback. I am trying to reproduce the bug and it seems that those unwanted texture overrides will appear as soon as you perform a boolean operation among two textured objects. This is a bug for sure. I will submit a bug report to document this behavior.

 

I am not sure how the latter part of your description ("give the new object textures by changing its class") would affect this, please see the video attached below and let me know if I've missed anything.

 

[Andy Broomell]

The result does seem odd when the texture on the two original objects is the same texture, but if those two textures were different to begin with, the fact that the resulting Solid Addition could still display both textures is actually a useful new feature of 2022 that I didn't realize existed. So perhaps the only change should be that *if* all textures in the operation are the same, then all faces are assigned to "Overall" and there are no overrides.

 

Interesting results too when doing solid subtractions of different textures. Cool!

 

 

 

Edited September 24, 2021 by Andy Broomell

[Kaare Baekgaard]

On 9/24/2021 at 4:13 PM, Andy Broomell said:

The result does seem odd when the texture on the two original objects is the same texture, but if those two textures were different to begin with, the fact that the resulting Solid Addition could still display both textures is actually a useful new feature of 2022 that I didn't realize existed. So perhaps the only change should be that *if* all textures in the operation are the same, then all faces are assigned to "Overall" and there are no overrides.

 

Interesting results too when doing solid subtractions of different textures. Cool!

 

 

 

Cool? Sure in a novelty kind of way. Useful? Not really.

[Kaare Baekgaard]

On 9/24/2021 at 3:47 PM, Shengxi Wu said:

Hi @Kaare Baekgaard, thanks for the feedback. I am trying to reproduce the bug and it seems that those unwanted texture overrides will appear as soon as you perform a boolean operation among two textured objects. This is a bug for sure. I will submit a bug report to document this behavior.

 

I am not sure how the latter part of your description ("give the new object textures by changing its class") would affect this, please see the video attached below and let me know if I've missed anything.

 

By default all new objects, that I make, have their texture assigned by class. I think most users work this way. So when I change the class of an object, I change its textures. Preferably all of them (always!). I may assign an override on purpose after that, but never before.

[Kaare Baekgaard]

I must have deleted close to 1000 unwanted texture overrides today.

 

Can you put this on a priority list, please

[Kaare Baekgaard]

Yes, no? Anyone from VW?

 

This is not an idle claim, guys.

 

There are unwanted relic texture overides all over the construction tree of every effing level of every effing boolean object.

 

Please tell me it is on a to-do list somewhere...

 

[Guest Shengxi Wu]

7 hours ago, Kaare Baekgaard said:

Yes, no? Anyone from VW?

 

This is not an idle claim, guys.

 

There are unwanted relic texture overides all over the construction tree of every effing level of every effing boolean object.

 

Please tell me it is on a to-do list somewhere...

 

Hi @Kaare Baekgaard, sorry for the late reply. We were swamped with different tasks recently so we might not have a chance to revisit the Texture task in a moment.  I'll bring this up with our engineers, and see if there is an easy fix for this.

 

Just to clarify: rather than having the behavior shown in @Andy Broomell's post, you think it makes more sense for new faces resulting from boolean operation to either

• have no texture (if the original object has no overall texture), or
• have overall texture

Is that correct?

[Andy Broomell]

@Kaare Baekgaard - In your case, are your original objects all using the SAME texture or are they DIFFERENT textures?

 

@Shengxi Wu - At the very least, if the original objects are using the SAME texture, the resulting boolean should not have any face overrides - it should simply be the one OVERALL texture, i.e. the same texture that the original objects had. I assume this is what Kaare is experiencing.

[Guest Shengxi Wu]

1 hour ago, Andy Broomell said:

 

 

@Shengxi Wu - At the very least, if the original objects are using the SAME texture, the resulting boolean should not have any face overrides - it should simply be the one OVERALL texture, i.e. the same texture that the original objects had. I assume this is what Kaare is experiencing.

 

For the case where the two original objects are using the same texture, I believe we've fixed this in VW2022 SP2.

 

The behavior shown in your screenshot, where the two objects are using different texture, still remain. I am wondering if that is what Kaare would not prefer.

[Kaare Baekgaard]

On 11/11/2021 at 11:11 PM, Shengxi Wu said:

am wondering if that is what Kaare would not prefer.

 

 

Nooooooo!!!!!!!

 

no

 

 

[Kaare Baekgaard]

 

 

[Guest Shengxi Wu]

8 hours ago, Kaare Baekgaard said:

 

 

 

Hi @Kaare Baekgaard, I am sorry that we haven't addressed your concern in time.

Just want to confirm, would it be helpful if we enable the "Remove Texture Override" command from the context menu at a group level?

[Andy Broomell]

16 minutes ago, Shengxi Wu said:

Just want to confirm, would it be helpful if we enable the "Remove Texture Override" command from the context menu at a group level?

 

In general it seems odd that nothing can be done at the group level. I would find this handy, in addition to other commands at the group level such as selecting a texture.

 

 

--------

 

Another thing related to this thread... When using the Split tool to slice a 3D solid, the sliced edge shouldn't end up with a Face Override. It should just be the Overall texture.

 

 

(I'm not even sure where it's pulling the override Texture from... It must be the most recently added texture or something so it's the one that gets used by default)

[Guest Shengxi Wu]

2 hours ago, Andy Broomell said:

 

In general it seems odd that nothing can be done at the group level. I would find this handy, in addition to other commands at the group level such as selecting a texture.

--------

I believe operation at group level was proposed in the original design for batch processing. For some reason (probably because of the minimum viable product requirements, or might be technical challenges), we decided to not go with it. Anyway, we will investigate if that is possible in case that resolves Kaare's concern.

 

2 hours ago, Andy Broomell said:

 

(I'm not even sure where it's pulling the override Texture from... It must be the most recently added texture or something so it's the one that gets used by default)

I can't reproduce it. Could you attach a sample file so we can look into that? Thanks Andy.

[Bas Vellekoop]

On 1/14/2022 at 7:55 PM, Guest Shengxi Wu said:

I believe operation at group level was proposed in the original design for batch processing. For some reason (probably because of the minimum viable product requirements, or might be technical challenges), we decided to not go with it. Anyway, we will investigate if that is possible in case that resolves Kaare's concern.

 

I can't reproduce it. Could you attach a sample file so we can look into that? Thanks Andy.

 Any change that this still gets implemented on grouplevel? Would be very handy indeed 🙂