View Issue Details

IDProjectCategoryView StatusLast Update
0005702DarkRadiantGUIpublic02.04.2022 05:55
ReporterBrendonChung Assigned Toorbweaver  
Status closedResolutionfixed 
PlatformWindows 10 
Product Version2.13.0 
Fixed in Version2.14.0 
Summary0005702: Fit Texture fields do not allow values below 1.0
DescriptionIn the Surface Inspector, the two numerical Fit Texture fields currently do not allow values below 1.0
Steps To Reproduce1. Open Surface Inspector
2. In the Fit Texture fields, input 0.5
3. Click on another field. Notice the Fit Texture field clamps the value to 1.0
TagsNo tags attached.




11.08.2021 17:37

administrator   ~0014281

@orbweaver, is this related to the changes in 0005684?


11.08.2021 20:33

developer   ~0014282

Yes it almost certainly is. I guess we need to use wxSpinCtrlDouble to preserve the ability to use fractional values.


12.08.2021 16:05

developer   ~0014285

To be honest I'm not quite sure of the use case or expected behaviour of fitting 0.5 texture images to a brush. When you fit a whole number of images you are aligning the boundaries of the texture to the brush, but what happens when it's just half an image? Is the edge of the image supposed to align with the left, right, top or bottom edge of the brush face, or is it just a zoomed-in portion of the center of the texture? Under what circumstances would it be important to fit exactly half a texture image, rather than adjusting the scale and offset visually?


15.08.2021 04:24

reporter   ~0014299

Hi! Regarding use cases, my crew and I found the "less-than-1.0 fit" frequently-used and helpful in our workflow. Some examples:

1. For patches (i.e. pipes), we find manually adjusting the scale can be fairly time-consuming, but having them snap to 0.5 or a fractional value oftentimes gets the job done instantly for some materials.
2. For materials that include lines/portions, it's helpful to be able to quickly fill an irregularly-sized brush face.

Regarding the expected alignment, we thought the default behavior for the less-than-1.0 fit in version 2.12.0 worked great.


20.08.2021 20:14

reporter   ~0014306

Last edited: 21.08.2021 09:45

I second Brendon's comment, that and you could always have values lower than 1.0 in previous versions of DR.


20.08.2021 21:21

developer   ~0014307

One application for sub-1.0 fits is when working with a texture atlas, since you have many small images assembled into one large image for performance reasons.


24.08.2021 19:31

developer   ~0014313

Fixed in 9ede3773ad8da98b7f36950d89e696fdd277726f

Issue History

Date Modified Username Field Change
10.08.2021 16:55 BrendonChung New Issue
11.08.2021 17:37 greebo Note Added: 0014281
11.08.2021 17:37 greebo Status new => acknowledged
11.08.2021 20:33 orbweaver Note Added: 0014282
12.08.2021 16:05 orbweaver Note Added: 0014285
15.08.2021 04:24 BrendonChung Note Added: 0014299
20.08.2021 20:14 Bikerdude Note Added: 0014306
20.08.2021 21:21 Dragofer Note Added: 0014307
21.08.2021 09:45 Bikerdude Note Edited: 0014306
24.08.2021 19:31 orbweaver Assigned To => orbweaver
24.08.2021 19:31 orbweaver Status acknowledged => assigned
24.08.2021 19:31 orbweaver Status assigned => resolved
24.08.2021 19:31 orbweaver Resolution open => fixed
24.08.2021 19:31 orbweaver Fixed in Version => 2.14.0
24.08.2021 19:31 orbweaver Note Added: 0014313
02.04.2022 05:55 greebo Status resolved => closed