CM0

The most data gathered in another sense is vision. Models trained on video data have also demonstrated they are unable to make sense of that data as well. We already have machines that can experience their environment with LLM models at the core, but they still are unable to reason. True humanlike reasoning is going to require new innovations. Scaling LLMs does not seem to be the path to get there.

I just linked to a test that any human would pass, but all AI's fail. Additionally, humans outperform LLMs in reasoning with a fraction of the data that LLMs require. Current LLMs have already nearly consumed all text data that exists.

Current AI systems are mostly representations of the data on which they are trained. Once you move outside the distribution curve it gets everything terribly wrong. Complex relationships of data and its ability to create permutations out of that creates a convincing intelligence mimic. But it actually understands none of it. Very simple tests can expose the failures, such as LLM's don't know what they know and don't know.

Awesome, glad to see this is finally addressed. Will lower the temperature on my laptop. Note, as pointed out in this thread, the ruler also causes this problem. Hopefully that is addressed as well?

Of course I can manually fix it, but I have hundreds of these. It should be migrated as part of the update.

Opened in 2.4.2 Opened in 2.5.0 Windows 10. Font Bahnschrift. Font alignment.afdesign

Could you post a link, I can't find the page either. I need the older version as well, all my older document fonts are now misaligned.

Yes, this is a positive change in concept as it allows you to gather feedback quicker and iterate on those changes before development progress too far. I was pushing for more iterative development long time ago, so I see it as much positive potential. However, if you don't iterate on those changes it is mostly moot. Lots of feedback from the other betas has been ignored. This all could easily be addressed with simple acknowledgements of intent. Furthermore, sometimes a feature simply isn't ready. You are not required to release it. We did this often for companies I worked at. Just because a feature was in beta wasn't a guarantee we would make it available in that release. We shipped features that were ready and held others for next release to keep iterating if lots of feedback indicated more work is required.

Affinity seems to have closed their eyes to all the feedback on this feature as if that makes it all go away. I've never understood their policy of "we don't talk about or acknowledge difficult issues". Significant demotivator for continuing to participate in these betas.

Many glitches when using this with brushes. 2024-05-22 21-28-23.mp4

Curves are not curves, they are segments.

2024-05-17 13-28-47.mp4 Once it goes to 0, the application freezes, I can't click on anything. Then the window closes.

I'm using the stroke width tool. Yes, I'm on windows. I'll post a video shortly.

I recreated it. While doing so I found another bug. The triangle object will crash Affinity if you grab the wide point and reduce it to 0 width. Expand Stroke Bug Beta.afdesign

I have a lot of feedback I will pass your way so you can get it acknowledged :-P Over the many years, zero of all the bugs I've submitted have been fixed. There is a reason for some level of pessimism.