Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

I might have just figured out how to integrate Web Workers with TanStack Table V9... So... multi-threaded TanStack Table coming soon? This would theoretically unlock huge UI performance wins for specific large tables that use heavy client-side computations for filtering, sorting, aggregation, etc. In a normal setup, the UI... show more

Kevin Thomas Van Cott

3,214 subscribers

44,178 görüntüleme • 3 ay önce •via X (Twitter)

Eğitim Haberler & Politika Bilim & Teknoloji

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

JUST IN: President Trump tells Maria Bartiromo that an end to the conflict in Iran could come very soon. "If they're going to have a nuclear weapon, we'll be living with them for a little while. But I don't know how much longer they can survive."

JUST IN: President Trump tells Maria Bartiromo that an end to the conflict in Iran could come very soon. "If they're going to have a nuclear weapon, we'll be living with them for a little while. But I don't know how much longer they can survive."

Fox News

274,466 görüntüleme • 5 ay önce

One of my favourite things about building Superlogical is that we all care, a disproportionate amount, about the little conveniences, performance gains and UI treats that most rational people just don’t. I'm currently working on our scrollback search UI. You basically have two common choices as a designer: a) insert a toolbar into the view or b) float a search bar over the view For terminals, any intrinsic size change causes a reflow - which is jarring for the user to see and potentially pushes offscreen something you were looking at. This means option A sucks. For option B though, the problem is that you’re potentially obscuring matched words that fall under the search UI since it floats over them. (Every app I tried makes this mistake which is kinda nuts) So what's the solution? Give our search UI a gentle nudge out the way when it's over something you're trying to see.

One of my favourite things about building Superlogical is that we all care, a disproportionate amount, about the little conveniences, performance gains and UI treats that most rational people just don’t. I'm currently working on our scrollback search UI. You basically have two common choices as a designer: a) insert a toolbar into the view or b) float a search bar over the view For terminals, any intrinsic size change causes a reflow - which is jarring for the user to see and potentially pushes offscreen something you were looking at. This means option A sucks. For option B though, the problem is that you’re potentially obscuring matched words that fall under the search UI since it floats over them. (Every app I tried makes this mistake which is kinda nuts) So what's the solution? Give our search UI a gentle nudge out the way when it's over something you're trying to see.

almonk

40,539 görüntüleme • 1 ay önce

loadoutlibrary Many questioned why anyone would stick a screwdriver between the slide and frame in my last video. So this time, I tried it with something much more likely to be carried near a firearm. Many people, including law enforcement and armed citizens, carry keys on their belt or near their holster. The odds of a key going into that slot seem small, but not impossible, especially for law enforcement. I’m not taking sides for or against Sig. I just don’t want to see anyone have an accident if there’s something that deserves a closer look. Is this a non-issue, or is it a valid topic for discussion?

loadoutlibrary Many questioned why anyone would stick a screwdriver between the slide and frame in my last video. So this time, I tried it with something much more likely to be carried near a firearm. Many people, including law enforcement and armed citizens, carry keys on their belt or near their holster. The odds of a key going into that slot seem small, but not impossible, especially for law enforcement. I’m not taking sides for or against Sig. I just don’t want to see anyone have an accident if there’s something that deserves a closer look. Is this a non-issue, or is it a valid topic for discussion?

Daily Gun Dose

137,430 görüntüleme • 1 ay önce

designers love to hate on raw, unfinished things. redesigning the whole ios/watchos/macos/... ui after a decade is a brutal challenge for any design team! almost impossible to satisfy the expectation. most haters around here have never designed in a large organization like apple and are not aware of challenges such as politcs, opiniated stakeholder, impossible deadlines, the list goes on... i empathise with the ui designers in apple. yes! os26 and liquid glass feels rough at the moment! so did the ios7 at launch. it evolved. this will too. i appreciate the brave direction apple has taken with this liquid glass ui. yes it comes with challenges including readability, compatibility and more... let's stop b*tching about it and contribute to solutionise these challenges.

designers love to hate on raw, unfinished things. redesigning the whole ios/watchos/macos/... ui after a decade is a brutal challenge for any design team! almost impossible to satisfy the expectation. most haters around here have never designed in a large organization like apple and are not aware of challenges such as politcs, opiniated stakeholder, impossible deadlines, the list goes on... i empathise with the ui designers in apple. yes! os26 and liquid glass feels rough at the moment! so did the ios7 at launch. it evolved. this will too. i appreciate the brave direction apple has taken with this liquid glass ui. yes it comes with challenges including readability, compatibility and more... let's stop b*tching about it and contribute to solutionise these challenges.

Oykun

347,970 görüntüleme • 1 yıl önce

While working on a new video with solutions to the previous one, I found ChatGPT's new UI struggles even more with concurrent updates: entries lose state and stick around for too long (see video). If this was a LiveView app, we would be getting so much flak.😅 --- I believe part of the problem here is having separate mutate and fetch requests on every deletion. The first fetch is cancelled when the second one comes up, causing items to stick around for longer. Many said yesterday that you could do the mutation and fetch as a single request, but that leads to other problems, such zombie entries. For example, imagine you delete link1 and link2 within a brief period of time. There is no guarantee the deletion order in the database will match the order the client receives the response, so you may end up with this: 1. (client) request to delete link1 sent 2. (client) request to delete link2 sent 3. (server) deletes link1 and loads a new list (includes link2) 4. (server) deletes link2 and loads a new list (no link1 or link2) 5. (client) receives link2 response 6. (client) receives link1 response So if you choose to use the latest response (link1), you brought link2 back to life. If you say you will use the response from the last request, events 3-4 can be swapped, and now you bring link1 back to life. Another way to solve this is by basically not allowing concurrent requests at all but that can affect the user experience drastically in other ways. Next week I should publish a video explaining how LiveView tackles this. Stay tuned!

While working on a new video with solutions to the previous one, I found ChatGPT's new UI struggles even more with concurrent updates: entries lose state and stick around for too long (see video). If this was a LiveView app, we would be getting so much flak.😅 --- I believe part of the problem here is having separate mutate and fetch requests on every deletion. The first fetch is cancelled when the second one comes up, causing items to stick around for longer. Many said yesterday that you could do the mutation and fetch as a single request, but that leads to other problems, such zombie entries. For example, imagine you delete link1 and link2 within a brief period of time. There is no guarantee the deletion order in the database will match the order the client receives the response, so you may end up with this: 1. (client) request to delete link1 sent 2. (client) request to delete link2 sent 3. (server) deletes link1 and loads a new list (includes link2) 4. (server) deletes link2 and loads a new list (no link1 or link2) 5. (client) receives link2 response 6. (client) receives link1 response So if you choose to use the latest response (link1), you brought link2 back to life. If you say you will use the response from the last request, events 3-4 can be swapped, and now you bring link1 back to life. Another way to solve this is by basically not allowing concurrent requests at all but that can affect the user experience drastically in other ways. Next week I should publish a video explaining how LiveView tackles this. Stay tuned!

José Valim

23,050 görüntüleme • 2 yıl önce

LangGraph. CrewAI. Agno. Which one to pick? The good news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.

LangGraph. CrewAI. Agno. Which one to pick? The good news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.

Avi Chawla

31,074 görüntüleme • 10 ay önce

SplitPaneKit This is something I've wanted to componentize for a while. We've seen this pattern appear in a few apps now, I even use it at Abode. It has a couple "gotcha" moments with performance and optimisation while animating separate or child views with the drag and translation of the split views, handling breakpoints etc, I thought I'd put it into a nice package. I actually made quite a few optimisations from how I handle this with Abode in this package. So might need to implement it over there😅 As before, right now its UIKit only, but SwiftUI host will likely come over the next few days as I make improvements and final changes to the initial API from feedback. - Draggable split-pane interface - Custom breakpoints or built-in presets - Scroll view integration - drag from content or handle - Coordinated animations with pan-effecting views - UIKit

SplitPaneKit This is something I've wanted to componentize for a while. We've seen this pattern appear in a few apps now, I even use it at Abode. It has a couple "gotcha" moments with performance and optimisation while animating separate or child views with the drag and translation of the split views, handling breakpoints etc, I thought I'd put it into a nice package. I actually made quite a few optimisations from how I handle this with Abode in this package. So might need to implement it over there😅 As before, right now its UIKit only, but SwiftUI host will likely come over the next few days as I make improvements and final changes to the initial API from feedback. - Draggable split-pane interface - Custom breakpoints or built-in presets - Scroll view integration - drag from content or handle - Coordinated animations with pan-effecting views - UIKit

Joseph Smith

23,654 görüntüleme • 1 yıl önce

This might be the most cursed thing I tried in Battlefield 6 😂😂😂 VSSM 10x scope on full auto... For all those who think I use cronus or any cheating device you might want to check out this video on my YouTube channel There is 0% chance anyone can control the recoil on this thing 🤣 Lowkey was fun trying to get a gameplay with this though. I lowkey miss messing around with builds like this just for the memes.

This might be the most cursed thing I tried in Battlefield 6 😂😂😂 VSSM 10x scope on full auto... For all those who think I use cronus or any cheating device you might want to check out this video on my YouTube channel There is 0% chance anyone can control the recoil on this thing 🤣 Lowkey was fun trying to get a gameplay with this though. I lowkey miss messing around with builds like this just for the memes.

Maxiq

36,483 görüntüleme • 2 ay önce

Medics say that its near on impossible for a women to have sex with that many men in a 12 hour timeline The downstairs department would look like a puffer fish with tumours. Ain't northing going in or out of that.... Unless, it wasn't a naturally made vagina which god gave you! If this IS TRUE. I would imange the men having sex with it and didnt know they were Fuc**ng another "Man " would want to "delete " themselves.. Theres a " the Moral of the story here somewhere.....

Sensitive content

Medics say that its near on impossible for a women to have sex with that many men in a 12 hour timeline The downstairs department would look like a puffer fish with tumours. Ain't northing going in or out of that.... Unless, it wasn't a naturally made vagina which god gave you! If this IS TRUE. I would imange the men having sex with it and didnt know they were Fuc**ng another "Man " would want to "delete " themselves.. Theres a " the Moral of the story here somewhere.....

Queen Gurty

1,004,726 görüntüleme • 1 ay önce

So often when discussing training / dryfire / shooting its like we are speaking 2 different languages. There are key concepts that some people are either unaware of, or choose to ignore that preclude having a productive discussion. For example if I were to say "slapping or smashing your trigger is perfectly fine for most shots" a bunch of people would be up in arms, talking about slowly working to the wall, letting the shot surprise you, etc. Experienced, performance-focused shooters will know that with a good grip or mount, I am right, and that how you mechanically move the trigger isnt super important. When you get to low %, or distance shots, you are increasing your level of confirmation of your dot or sights, and the trigger pull is maybe 10-15% slower. This is a video of me, absolutely smashing the trigger with 2-3x the force needed. Its not as stable as i would like, but im also having to straddle 2 tripods to get this shot lined up...🤣

So often when discussing training / dryfire / shooting its like we are speaking 2 different languages. There are key concepts that some people are either unaware of, or choose to ignore that preclude having a productive discussion. For example if I were to say "slapping or smashing your trigger is perfectly fine for most shots" a bunch of people would be up in arms, talking about slowly working to the wall, letting the shot surprise you, etc. Experienced, performance-focused shooters will know that with a good grip or mount, I am right, and that how you mechanically move the trigger isnt super important. When you get to low %, or distance shots, you are increasing your level of confirmation of your dot or sights, and the trigger pull is maybe 10-15% slower. This is a video of me, absolutely smashing the trigger with 2-3x the force needed. Its not as stable as i would like, but im also having to straddle 2 tripods to get this shot lined up...🤣

Havoc 2-1

35,672 görüntüleme • 1 yıl önce

Honestly, I don't get why Vgen still doesn't have basic price sorting or filters in 2026 😩 You're telling me I have to click into every single commission listing just to find out the price... and half the time it's way out of my budget? To solve this: I developed VGENUnlocked. It fixes the BS: 1. Prices show automatically as you scroll through commissions 2. Hover over "mature" images → they unhide instantly 3. Set a min/max price range and everything outside it gets filtered out automatically 4. Sort by price, rating, or review count. Actual useful controls. If you hunt for commissions on Vgen, this is about to make your life 10x easier.

Honestly, I don't get why Vgen still doesn't have basic price sorting or filters in 2026 😩 You're telling me I have to click into every single commission listing just to find out the price... and half the time it's way out of my budget? To solve this: I developed VGENUnlocked. It fixes the BS: 1. Prices show automatically as you scroll through commissions 2. Hover over "mature" images → they unhide instantly 3. Set a min/max price range and everything outside it gets filtered out automatically 4. Sort by price, rating, or review count. Actual useful controls. If you hunt for commissions on Vgen, this is about to make your life 10x easier.

✨ 𝗗𝗔𝗥𝗞 ✨ Shitposter Detective

254,639 görüntüleme • 4 ay önce

(Yes i know the movement is exaggerated, its just to show the motion, it also doeant move like jello when in vr) -Left is before, Right is after- Ok wall of text time for the nerds Literally everything is the same on both sides except the position of 1 bone (made sure that even after adjusting, the collider would still be in the same spot) The reason for this change is because she wanted to be able to clap her ass in vr, and last time i did this all i did was add a toggle for a hidden bone that moved, and its angle would trigger the sound. Which was because that with my previous position, the cheeks could never really meet in the middle when in motion unless you just pushed them together with your hands, and i wanted to just have the sound actually be triggered by them colliding with each other This is also the first time ive used endbones to help drive the movement, so now thanks to that and all my previous experimenting with squishing as well, I can now get bones to move exactly how i want them to move when in natural motion. And i know a lot of people are gonna ask me to teach them how or explain my thought process but i literally just go off feeling lmao. Like, i just kinda visualize in my head how i want the motion to look, and then i just kinda know where to put everything, so im not even sure how to even start explaining rip. I have the things that artist want where they can just make the shit in their head exactly how they envisioned it lol I have a few more ideas i want to try, so we'll see if theyre good enough to get a tweet lol Thank you for coming to my ted talk

(Yes i know the movement is exaggerated, its just to show the motion, it also doeant move like jello when in vr) -Left is before, Right is after- Ok wall of text time for the nerds Literally everything is the same on both sides except the position of 1 bone (made sure that even after adjusting, the collider would still be in the same spot) The reason for this change is because she wanted to be able to clap her ass in vr, and last time i did this all i did was add a toggle for a hidden bone that moved, and its angle would trigger the sound. Which was because that with my previous position, the cheeks could never really meet in the middle when in motion unless you just pushed them together with your hands, and i wanted to just have the sound actually be triggered by them colliding with each other This is also the first time ive used endbones to help drive the movement, so now thanks to that and all my previous experimenting with squishing as well, I can now get bones to move exactly how i want them to move when in natural motion. And i know a lot of people are gonna ask me to teach them how or explain my thought process but i literally just go off feeling lmao. Like, i just kinda visualize in my head how i want the motion to look, and then i just kinda know where to put everything, so im not even sure how to even start explaining rip. I have the things that artist want where they can just make the shit in their head exactly how they envisioned it lol I have a few more ideas i want to try, so we'll see if theyre good enough to get a tweet lol Thank you for coming to my ted talk

Pixel

27,240 görüntüleme • 1 yıl önce

I always wondered "What if I port my three.js game to Rust? Will it improve performance?" I finally ported it to both Rust Desktop and Rust WASM (that runs on the browser) Comparing the three.js version with the Rust desktop I had a clear winner: Rust desktop. But now I took the time to port it to the web using Web Assembly (WASM) And my conclusion is... A tie! Both versions averaged 42FPS (60FPS if running one at a time) So if your goal is to ship a web game, it doesn't even matter the tech you use. (Three.js is recommended because the ecossystem is huge though) As long you optmize well (Web workers, reduce triangles, draw calls, etc) you should be good to go. But in the event you want to ship a native game to publish on Steam a system language (Rust, C++, etc) will be better for you. Now I want to port the three.js game to Desktop using Electron and see the results. I'll let you know. Btw, I'm open to new freelance projects. If you have anything for me, my DMs are open!

I always wondered "What if I port my three.js game to Rust? Will it improve performance?" I finally ported it to both Rust Desktop and Rust WASM (that runs on the browser) Comparing the three.js version with the Rust desktop I had a clear winner: Rust desktop. But now I took the time to port it to the web using Web Assembly (WASM) And my conclusion is... A tie! Both versions averaged 42FPS (60FPS if running one at a time) So if your goal is to ship a web game, it doesn't even matter the tech you use. (Three.js is recommended because the ecossystem is huge though) As long you optmize well (Web workers, reduce triangles, draw calls, etc) you should be good to go. But in the event you want to ship a native game to publish on Steam a system language (Rust, C++, etc) will be better for you. Now I want to port the three.js game to Desktop using Electron and see the results. I'll let you know. Btw, I'm open to new freelance projects. If you have anything for me, my DMs are open!

André → andreelias.dev

19,531 görüntüleme • 4 ay önce

Rumor has it I’m still swimming… 😂 Lol, but hey, I’m about to get real for a second. There have been many moments recently where I’ve felt like the currents have been too tough to swim through… All I wanted to do was throw in the towel and come up for air. But it’s in moments like this where I remind myself that I CAN swim… and I’m actually a damn strong swimmer at that! I may have to hold my breath for a little longer, or paddle a bit harder, but I always make it to the other side. So this is your reminder to just keep swimming. If I can do it, so can you. Whatever it is, you’ve got this ❤️ #mentalhealth

Rumor has it I’m still swimming… 😂 Lol, but hey, I’m about to get real for a second. There have been many moments recently where I’ve felt like the currents have been too tough to swim through… All I wanted to do was throw in the towel and come up for air. But it’s in moments like this where I remind myself that I CAN swim… and I’m actually a damn strong swimmer at that! I may have to hold my breath for a little longer, or paddle a bit harder, but I always make it to the other side. So this is your reminder to just keep swimming. If I can do it, so can you. Whatever it is, you’ve got this ❤️ #mentalhealth

Janna Breslin

35,598 görüntüleme • 3 yıl önce

Sharing some more UI previews for Superlogical, this time the "tab peek." If you three-finger swipe down, you can "peek" at the other session tabs. These are live-updating, metal-rendered previews including splits. If you keep dragging, you enter a "mission control" style mode. This is one of those UI patterns that once you get used to, you mindlessly find yourself doing it ALL THE TIME. It's a great way to quickly take a look at everything thats going on. You aren't reading the mini text of course, but the shape of it tells you a lot about where things are. The peek pushes the terminal down off screen, it doesn't resize it, so it doesn't force any weird reflow or anything either. There's a lot more to talk about, especially about how this interacts with how we expose what needs attention so you can easily find the terminals/sessions/etc. that require your attention. Of course, you'll be able to drive this with the keyboard too. :) As always, a disclaimer: this is all early work subject to change, just trying to share some of what we're building in public. A lot of the UI experiential design is almonk so follow him for more updates too!

Sharing some more UI previews for Superlogical, this time the "tab peek." If you three-finger swipe down, you can "peek" at the other session tabs. These are live-updating, metal-rendered previews including splits. If you keep dragging, you enter a "mission control" style mode. This is one of those UI patterns that once you get used to, you mindlessly find yourself doing it ALL THE TIME. It's a great way to quickly take a look at everything thats going on. You aren't reading the mini text of course, but the shape of it tells you a lot about where things are. The peek pushes the terminal down off screen, it doesn't resize it, so it doesn't force any weird reflow or anything either. There's a lot more to talk about, especially about how this interacts with how we expose what needs attention so you can easily find the terminals/sessions/etc. that require your attention. Of course, you'll be able to drive this with the keyboard too. :) As always, a disclaimer: this is all early work subject to change, just trying to share some of what we're building in public. A lot of the UI experiential design is almonk so follow him for more updates too!

Mitchell Hashimoto

351,482 görüntüleme • 1 ay önce

In light of the Cybercab event this week, here are my expectations: Of course the first official Robotaxi rides in a Cybercab will happen. Good chance it's limited to a certain portion of the geofence, especially for the launch event to avoid any edge cases I think Elon will say a few words. Likely nothing we don't already know - thanking the teams and explaining the importance of and vision for Cybercab Frankly though what happens at the event doesn't matter. It's what the Cybercab service looks like the following day. I think best case scenario would be Tesla having ~25 active Cybercabs operating in Austin for a majority of the operating hours (6A - 10P). I think we all need to be prepared for somehwere around ~5-10 Cybercabs to be active for a week or so after the event and then a slow build from there While we don't know how many active Robotaxis Tesla has in Austin, we can guess it's ~50-75 on any given day. I think increasing that fleet by up to 50% is the most we should be hoping for. I think the survey going around where ~50% of people are expecting > 100 Cybercabs to be deployed is overly optimistic. Not that it can't happen, and I'd love to be wrong, it would just be a stark departure from everything we've seen/heard so far This event shouldn't be viewed as a scaling announcement, but rather a beginning of operations and celebration of the Cybercab. I know Elon said over the weekend Tesla is "about to" flood Austin with Cybercabs, but in his mind that could mean later this year with V15, not this week Given Ashok's recent commentary about why they're going broad instead of deep (more different cities instead of higher fleet volume in each), I'd be more impressed with Cybercab starting operations in the other active Robotaxi cities in the following week or two after the event. To me, that would be a great signal that the validation is going well with Cybercab more generally, not just in the Austin geofence where Tesla has extensive data So while this is a huge milestone (no wheel, no pedals, purpose built for autonomy, cost profile, attention-grabbing design etc.), I'm still not expecting to see hundreds of Robotaxis in Austin or other cities until later this year or early '27 $TSLA

Dillon Loomis

127,399 görüntüleme • 1 ay önce

Hello artists, I have a problem! I'm looking for a way to fix this issue in Clip Studio Paint: As you can see in the video, my shadow layer is clipped to my base color layer, but it's still stretching the color to the edges of the base color. I've tried looking for an option or something to fix this, but haven't found anything. I've changed my brush settings, created a new brush, etc., but nothing works. I went back to Paint Tool SAI and saw that when I make a selection, it doesn't do this in Paint Tool SAI. So I tried it in Clip Studio Paint, and unfortunately, the problem persists. It spreads the color to the selection edges where Paint Tool SAI doesn't. If anyone has a solution, a better-programmed brush, an add-on, or anything that can fix this problem, I would be very grateful!

Hello artists, I have a problem! I'm looking for a way to fix this issue in Clip Studio Paint: As you can see in the video, my shadow layer is clipped to my base color layer, but it's still stretching the color to the edges of the base color. I've tried looking for an option or something to fix this, but haven't found anything. I've changed my brush settings, created a new brush, etc., but nothing works. I went back to Paint Tool SAI and saw that when I make a selection, it doesn't do this in Paint Tool SAI. So I tried it in Clip Studio Paint, and unfortunately, the problem persists. It spreads the color to the selection edges where Paint Tool SAI doesn't. If anyone has a solution, a better-programmed brush, an add-on, or anything that can fix this problem, I would be very grateful!

Aniu

51,316 görüntüleme • 10 ay önce