CM0

I don't know . But seriously, larger LLMs and "reasoning" llms do perform better at some tasks. But all of the machines are essentially probability machines. That doesn't mean they are useless, but it does place limits on their capabilities. They require immense training data for any capability you want to produce. The AI Labs are selling us mostly hype when they talk about "reasoning" and AGI. They have to keep the money flowing for these expensive machines that still are not profitable. They can become really good at some tasks, but the tendency for them to make strange and unexplainable errors, hallucinations, is not going away. Hallucinations are simply the result of a machine that doesn't have true understanding and is only constructing its output from probabilities of text patterns.

ChatGPT doesn't know what it is talking about. It is just making stuff up. Nonetheless, it is partially true. In order to be very good, it will need many human examples. However, considering the base language is javascript and there are plenty of examples of coding in javascript. If you feed the model the API documentation it will probably do somewhat ok. But you can't ask the model what it can do. Models do not know. FYI, I write extensively on this topic. For anyone interested, BTW all illustrations done with Affinity - Explanation of the lack of reasoning in LLMs

Affinity v2.6.3, Windows 10 When using paint mixer or smudge, if you turn on size jitter you will get square artifacts in your brush stroke. The following is with jitter about 50% and mixer strength 60% using Basic round brush. It seems to occur with all brushes, but the basic round makes it more noticeable. I also discovered it often occurs if using sub brushes, you get these odd square artifacts as well. Brush settings:

It is in the picture. It is rendering outside of the ArtBoard. It should be clipped to the ArtBoard layer.

When you have an effect like motion blur combined with curves adjustment, contents outside the bounding area of the artboard are rendered on screen. Affinity 2.6.3, Windows 10. draw outside artboard.afpub

Any updates on this issue?

I have addressed this substantially in the past. I have logged a substantial number. Each one often becomes a battle with the mods or others on the forum to even understand the issue, which I'm certain would be immediately understand by a dev. It is time consuming and exhaustive. Furthermore, Affinity has no priority system. They have no idea what is the most important items to fix. You cannot properly extract this information from a public forum. You need a proper customer facing tracking system. FWIW, development processes was part of my day job, so yes I'm opinionated here. If I have a hundred bugs, Affinity has no idea which ones are the most important to me. Since the likelihood of any ever being fixed is already nearly zero, if I submit them all then then chances of the most important ones being fixed first is even less likely. Therefore, I started only just mentioning the absolutely most painful. Start fixing the ones I've already submitted is the best way to fix this. Then you have ensured it is worth my time to submit the rest.

I have a log of so many bugs I've never even reported because I lost faith in them ever being fixed.

Any updates on this?

So, implying that Illustrator seemed to handle it ok? BTW Inkscape uses Python for scripting. Not sure if you have tried that.

I want a high performant scripting language that uses JIT. Affinity has always prioritized performance. I've never considered the Affinity app as intended to be scientific level of accuracy or any other application in its class. What is the end user use case? Does Illustrator support the use case(it uses JS)?

It is the Python Decimal module. However, it is still done in software. So it's performance is slow in comparison. It is not useful in general for graphic applications. This kind of accuracy is for mostly scientific purposes.

Spline runs in the browser - https://spline.design/#features Graphite runs in the browser - https://graphite.rs/ Modyfi runs in the browser - https://www.modyfi.com/ Don't worry, this is not an issue.

I just checked and this still is not fixed in RC1. It is very disappointing that af-399 was marked fixed, but in reality it was only a partial fix. All that needs to happen is the same fix applied for erase mode. I fear it will never be fixed if not addressed while we had attention on this issue.

I couldn't agree more. There are so many bugs that don't even have work arounds. Fixing bugs is like getting new features. You can do things you couldn't do before.