Queries Regarding VectorStyler 1.3
-
@monsterfox Object -> Convert Shape
-
@VectorStyler
Actually, having such an AI format export function would be sufficient for me. I frequently export files to AI format in my work—if I had to repeatedly export to PDF first and then rename the file extension to AI, it would be too cumbersome. I understand you might be more rigorous and consider this not a standard AI format, but it would meet the needs of most users. Adding this format would greatly convenience users. Please consider my suggestion. -
@VectorStyler Recently, I encountered such a halftone effect in my work, which took me a lot of time to deal with. Can the current repeater achieve this effect?
-
@monsterfox said in Queries Regarding VectorStyler 1.3:
@VectorStyler Recently, I encountered such a halftone effect in my work, which took me a lot of time to deal with. Can the current repeater achieve this effect?
It is not clear form this image resolution, but I would say yes: a regularly spaced varying shape halftone can be created with the Regular halftone type.
If the shape (not just the size) is changing based on the backdrop intensity, the this can be achieved with blended shapes (a bit complicated).
If you send me a higher resolution image, I can try to replicate it
-
@VectorStyler Do you think this image works? If not, I’ll create a high-resolution one when I’m at work.
0_1764086938319_Image_1764086517678.zip -
@monsterfox Cannot be done with the current options.
-
@VectorStyler Is the multi-voice feature still underdeveloped and not yet available? After installing version 1.3, the default voice isn’t still the native language.
-
@monsterfox said in Queries Regarding VectorStyler 1.3:
After installing version 1.3, the default voice isn’t still the native language
The default is English , but it can be selected in Settings -> Application
-
@VectorStyler 0_1764167822028_HF.vstyler
There are too many restrictions on uploading high-definition images. Here is the file for your reference. Additionally, please create an operational demonstration using the 1.3 Repeater. Thank you. -
@monsterfox said in Queries Regarding VectorStyler 1.3:
@VectorStyler 0_1764167822028_HF.vstyler
Additionally, please create an operational demonstration using the 1.3 Repeater.I will try to improve the repeater in the near future, but at this time this is a difficult case.
-
@VectorStyler If the Repeater could edit samples independently and perform transformation operations, it would be much easier to implement this case.
-
@VectorStyler It took roughly two years to move from version 1.2 to 1.3. Will we have to wait just as long for every update after version 1.4? The wait feels extremely lengthy.
-
@monsterfox said in Queries Regarding VectorStyler 1.3:
Will we have to wait just as long for every update after version 1.4?
It depends on the content of 1.4 and what bugs are in the way.
Bugs, stability and performance are always a priority.
-
@monsterfox I can relate to you in that no one wants to wait years for updates to any product. The value of VS is clear, the direction is promising, and the potential is significant. Many of us have invested time in using and testing the software, offering feedback, and suggesting improvements. Your contributions have been substantial, and the anticipation around the 1.3 release has been shared by many, including me.
It is also important to acknowledge the steady effort that went into the 1.2 builds while development on 1.3 was underway. Every week or two, like clockwork, there was a new 1.2 build with added fixes and tool improvements. These updates were part of the same ongoing development process that ultimately led to 1.3.
Several features introduced in 1.3 clearly required extensive time and attention. It is reasonable to assume that many of them demanded more effort than initially estimated.
Your question about the expected timeframe for version 1.4 is completely understandable. The improvements in 1.3 naturally lead to interest in what the next stage may hold. I'm enjoying the new 1.3 updates and all the while thinking through what features would be great in 1.4!
My goal is simply to keep the broader context in view. The progress achieved over the past two years, and the continued development, reflect a remarkable level of dedication and skill. What @VectorStyler has accomplished and is continuing to build upon is inspiring and superhuman.
I share this view in the hope that it adds clarity to the discussion. Given the pace and quality of development so far, I’m optimistic about what lies ahead for VS.
-
@Boldline very well said
-
@Boldline Thanks for your perspective. I just want to note that it took 4 years to move from version 1.1 to 1.3, and the updates have been as amazing as expected. However, if the updates continue at this pace, it will take 20 years to reach version 2.0—by then, many of us will have already ended our professional careers, which is really regrettable. That’s why I’ve been feeling a bit anxious, and I might have expressed my emotions inappropriately. I apologize to everyone for that.
-
Where i miss the relation a bit.
We're talking about a program that costs $95, not one
with a monthly subscription fee.All previous bug fixes and improvements until now have been free.
Without wanting to do anyone wrong, I see no real reason to
complain about the length of the development process. -
@monsterfox Thank you for expressing your concerns. I get it. Nobody wants to wait twenty years for progress. I confess I still hope we see a companion pixel editor and desktop publishing tool that works alongside VS well before the 20 year mark! Some of the groundwork already in VS might even speed that up. Either way, I am glad VS exists and that it delivers a stronger and more powerful vector editing experience than what I started with years ago.
I do not have inside info, but based on how fast bugs were fixed and roadmap features were shipped, it feels possible we may not see long strings of versions like 1.7 or 1.8. By the time we hit 1.5 or 1.6, the core features might be finished and the next logical move could be 2.0. At some point everyone needs to decide when VS feels complete enough for full professional use. For me, most of what I need is already in place or can be handled through outside tools. I get almost all my daily work done in 1.3, which is a massive leap from the 2020 beta where I started.
That said, I still have a list of needs and nice to haves that would make the app even stronger. I am sure you do too. Hopefully the current feature set already covers most of what you rely on. Keeping some perspective, VS is already well ahead of Affinity and plenty of people use Affinity as their main tool!
I cannot guess how difficult or time consuming the remaining roadmap tasks are, but I hope the updates continue with the same momentum. Without pushing the developer into commitments he does not want to make, and while still leaving room for surprises and his willingness to respond to user requests, it might be worth having more focused conversations soon about which tools and features we see as the top priorities for 1.4. That way @VectorStyler can make his final decisions knowing where we as the community are coming from. As @Subpath mentioned, we've been given so much value already in VS and less has been expected from us. I don't want to look a gift horse in the mouth! I know we're all so grateful to @VectorStyler for his contributions to our vector design careers.
-
@VectorStyler Will a halftone effect with dot merging be added to the halftone panel in the future?
-
@monsterfox said in Queries Regarding VectorStyler 1.3:
@VectorStyler Will a halftone effect with dot merging be added to the halftone panel in the future?
In the case of the first image of this thread:
The problem is not with dot merging, but with the shape of the halftone. Those halftones (first image) are created in postscript as images. So this exact case will not be added to the halftone panel.The second image from this thread might be possible, I have this in the backlog and will try to add it as soon as possible.
