Jump to content

Recommended Posts

Posted

Another one in the Procedural Texture Menu, scroling on any of the number value inputs inside the variables changes the number but doesn't update the Procedural Texture

Posted

Im unsure what we see in your video. Can you please write down a numbered list of your exact steps:

  • what you did (keyboard or mouse input / UI actions)
  • what you expected to happen
  • what happened

There a Numerus issues and bugs open in that area, but from the video alone I’m unable to identify what you described as too much is going on. Show one instance of the issue, not multiple will help to stay focused.

one issue I can see:

if you change the name of a variable, you need to finish by enter from keyboard before the change is registered. Leaving the variable name by mouse and your name change is gone. This would be easier to spot if by using o and x as names, as a and g look too similar on my screen (old eyes).

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected.

 

Posted

I’m seeing a similar problem with Photo 2.1.0.1799 on Windows 10.

When I create a Procedural Texture Live Filter, select a preset – e.g. Chequered – and change a variable value – e.g. the Square Count – via mouse scrolling, nothing happens to the result; the value changes but the effect doesn’t.
However, if I change the value via the keyboard the effect changes.

I’ve tried a few different texture presets and they all seem to have the same problem.

See attached video.

Posted

I agree this is different than in previous versions. I just tested this against V1.10. You can scroll the numbers and the change is immediate, in V2.1 it is not. Which would be considered the bug, or the correct by design way?

Affinity Photo 2.5..; Affinity Designer 2.5..; Affinity Publisher 2.5..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD

  • Staff
Posted
On 5/28/2023 at 8:52 AM, GarryP said:

I can’t see how the current situation in V2, as I described above, could be considered as anything other than the result of a bug.

I agree this is a bug.  I've replicate this and will get it logged with the Dev Team :) 

@EzbazeThanks for reporting this :) 

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.