the body element is already full width so just doing "width: 100%" always works. and yeah chatgpt is good at coding but it is not good at CSS at all for some reason..
Liking the new format, Kevin! No logo splash, faster intro, going straight to the juicy content. Hope it doesn't hurt your channel's metrics! Thank you for giving it a go ❤️
I used to do full-stack dev but quit back when IE7 support was still a thing that people sometimes had to do. I enjoy how much better things have gotten with decent html5 and css features, but my "oldschool" brain sometimes has trouble with the stuff we could never really use like this. It is great to have videos like this that distill the quirks down into manageable chunks without hours of experimentation.
@@ongke3655 support these days is completely unnecessary. But this was coming from back in the day when it still had 10%-20% market share. Not supporting that was basically just bad business back then.
Are you using something like Nvidia's Eye Contact feature? Around 1:40 your eyes suddenly change and it stood out to me. I appreciate the content either way! Thanks for uploading.
I JUST WANNA SAY... I LOVE YOU......... IVE BEEN SEEKING FOR THE SOLUTION OF THIS PROBLEM FOR A LONG TIME WHEN I SAW YOUR VIDEO AND BAMM!!! SOLVED!!! THANK YOU!!!!!
I've started web dev this year (through the Odin Project, which is how I found your channel incidentally!) and Issue 2 was the bane of my life last week. What's worse is that most Google results don't include svh at all - I had to *really* look to find it. But wow is it a great unit to use.
Now, haven't been excited about a CSS topic probably since CSS grid came up - since when have 'svh' units been a thing?! (Also, how could I ever miss this?!) This LITERALLY IS a gamechanger - developing for those collapsing addressbars has always been SUCH a nuisance - thanks Kevin! 👍
It’s so sad that there’s still no real solution for 100vh on mobile. svh also doesn’t seem supported by iPhone Safari which is what our clients complain about the most.
@@thedigitalceo It works on 15.4 onwards according to CanIUse, so you could set it to 100svh and then also declare 100vh as a fallback if it isn't supported by the browser (with a padding hack as well)
This exact header 100vh issue on mobile. arghhhh. I think i asked about it like 6 months back on your discord channel. There was so little info on web about the new units. Was super happy to see this video. Now its way more clear how to make use of the new units. Truely appreciate your work, thanks in behalf of the whole world :D
Earlier today I was wondering how to fix a problem with an element not showing properly on mobile because of the 100vh differences between devices. Thank you very much Kevin!
wow, i've never known anything about that "svh" unity, it's an incredible solution for a lot of projects that could have problems like the showed on the video, thx kevin!
Couldn't fall back to sleep so I've been flipping back and forth between you and Web Dev Simplified. You guys make great videos. I'll definitely have to come back to this one when I'm working on my projects.
So far I have only used viewport units on pages that fill the viewport exactly on regular screens, either landscape or portrait. For that use-case it works pretty well. For other use-cases I have never considered them, not because of the problems it may cause, but because the alternatives I did use came more natural. min/max/clamp are so good. And combining them with container-query-units is awesome.
Damn! You always teach me fascinating things, and make me want to tinker and play. Thank you for giving such clear ideas about how the various rules work. You're so awesome at this.
I thought this was a contradictory post from one of your contents, glad to learn this was kind of a continuation about dynamic viewports. I stopped using viewports and started using dynamic viewports because of your videos.
wow man, this video was exactly what I was looking for. My last project was almost 100% made with view port units. In this project it was`t a huge problem, because the target of the web site is PC/Laptops but I`m really excited to watch your course and learn the best practices. Doing layouts/UI/UX is the sort of thing that I`ve to do every day but hate every time I`m doing, and these type of video are really great to learn boring things with a dynamic explanation. thanks man =)
Thanks for the video. Subbed. I used to do a lot of web design, but haven't in ages. While things have definitely improved since those days, it's a little crazy to see the struggles with the same old problems on new tech. Will use your channel to get back up to speed. Appreciate your approach/method/sharing/pace/explanation/allthethings.
omg thank you so much for the "100svh" tip. In my case it's a sidebar which must have the exact same height as the viewport but on tablets it was having that same issue.
That 100vh part was very useful because I want the comment section on videos on my site to be off screen until scrolled so the comments don’t need to be loaded unless a user scrolls to see them
Regarding the 100vw producing scrollbar - I think it's not because the vw does not take into the account the scrollbar, but because (in case of body) there is already some margin applied on it. The scrollbar disappears when the margin is removed
Yeah, this. Exactly this. When sizing elements, the default behavior is to apply the sizing only to the content area, which only includes the content itself and ignores padding, borders, and margins. You can include the padding and borders in your element sizing by declaring "box-sizing: border-box;" but then that still leaves the margins left over. You have to also set "margin: 0;" and then things should work.
This is only true for mobile browser/devices. Desktop 100vw DOES produce a scrollbar as of 2023. Chrome is in the works to provide a solution for that, it had a custom flag to enable overlay scrollbar until a few time ago. There's one hacky solution though: "width: calc(100vw - (100vw - 100%))", but I can see a case where you would want a 100vw instead of 100% through parent-child elements.
I literally just put this into my code, alt tabbed and saw this thumbnail, went back to my code and deleted it, then pressed play and said to myself, "don't worry, Kev, i'd never."
I build with a mix of units and than run a PX to REM convertor before running final checks on my responsiveness. I've found that's working for me as I get more involved with Accessibility and working with multiple developers.
Great video as always! QQ - do you use any software for eye contact? There are some weird artifacts in the video ~1:36 and ~1:42 where your pupils shift noticeably.
Without it zooming wouldn't work. 1rem is the unit that gets increased or decreased when zooming, so without it your font size would have been just clamped 5vw
@@noctemcat_ Thanks! But testing here with clamp(5rem, 10vw + 3rem, 10rem) or clamp(5rem, 10vw, 10rem), the zoom works the same in both cases. :/ Testing without clamp really is a problem, but when using clamp, doesn't matter if I use +rem or not. edit: I realized the zoom works, but doesn't works properly... so we have to use +rem. Thank you!
@kevinpowell although the footer is not sticky "stays at the bottom" I use flex: 0 auto in the first div bellow the body, then once the content inside goes beyond the height it can initially display the footer will be at the bottom of the content. to me it's not good design to keep a footer in view, as it's taking up space all the time. Always appreciate your work Kevin.
thanks Kevin for another great video. Good to know you're telling people about your courses here too now. More people should learn from you, I feel like there's no one better in this field than you
@@pelly5742 learn to use height:100% properly and youll never have to worry. old web dev is better for a reason. this guy seems scared of it, must not fully understand it ... 'little issues' means even he doesnt fully understand what hes doing
I always set my body elements to flexbox column with a min-height: 100vh, then align my footer to the bottom with the content area set as flex grow. Seems to work well.
This was a roller coaster of emotions for me. “Yeah this thing has problems but you can use this to fix it. But actually it has problems too so maybe try this. And actually…” 😂
Sidenote: What's up with your camera? Check 0:31-0:38. There is a strange eye distortion going on where it almost looks like one of those Nvidia eye tracking demos gone wrong
I use vh to make objects dead center. Like if I want to center a login form in a login page I use height: 100vh for the body of the page. Is there any better way to center objects?
Hello Professor KP! 😇 I am studying UX Design. Longtime artist trying to figure out front-end development. I liked your videos right away as soon as I noticed have you kept your profile in a circle frame. Plus you kept looking back towards the camera. You must be a writer. Funny thing. I watched/listened to a couple of your videos on 1.5 and 2 playback speed.
I do use a utility class to make panels restricted to a container look like they are full viewport width (width: 100vw; margin-left: calc(50% - 50vw). I got it from an Andy Bell tutorial. I've not seen any horizontal scroll issues though. Could just put overflow-x: hidden on parent of course. Will have to chck this, but there's no other way to do this one really.
I pretty much only use viewport units for dashboards that could be displayed on large tv's, or for setting 100% height on the page container. for the 100vw issue, you could just do overflow-x: hidden if u really needed to use it.
8:34 - I have seen this vw font size/padding/margin thing too many times. I can't understand this, you can see all the problems when shrinking window to 300px width already, how can they keep doing this? Also you can see on wide screen how it is broken too, but for this you need wide screen or 2 screens to test at least. What bothers me the most is that if someone uses vw units it means they probably know modern CSS and it shows that they care about responsive design. So how in the world they are building websites like this? Using clamp for font sizes is usually enough, you can easily do websites that work from 200px to your max container width (on bigger screens browser zoom works great, at the same time makes website usable on ultrawide screens). Using vw units without clamp or min for anything is a bad idea. Using media queries is not a bad thing, no matter what you do, it almost never takes more than 3 media queries to make it work perfectly on every screen size and usually it is 1-2 queries. It works like that even if your container is 100% width (so for every screen size it will take exact same px width value as screen offers) which i like to do, so there is never empty space on sides on mobile devices. Mostly it comes from bootstrap css where containers are like 400px, 600px, 800px... fixed and nothing in between.
I'm glad I started playing around with HTML and whatnot after svh became a thing in the standards... Learned using them from day one. And I probably use them too much
Hey, great video! What about using: html, body { max-width: 100vw; overflow-x: hidden } I understand the vh can be problematic, but the vw on that use case is something I always use to avoid that some elements that are outside the window width make the horizontal scrollbar visible. I was wondering if there's another solution to that.
But they are already full width, no reason to add that line in there. You could just have the `overflow-x: hidden` if you really need it, without the max-width.
I didn't know why that annoying horizontal scroll appeared, I don't know what I'd do without your videos, thank you Kevin!!!!
Wow, I was just the other night ranting about the vw units causing horizontal scroll and ChatGPT being unable to help me. Thank you!
you can use overflow-x: hidden; or width: 100%; instead
the body element is already full width so just doing "width: 100%" always works. and yeah chatgpt is good at coding but it is not good at CSS at all for some reason..
Liking the new format, Kevin! No logo splash, faster intro, going straight to the juicy content. Hope it doesn't hurt your channel's metrics! Thank you for giving it a go ❤️
Devs watch TH-cam on 2x speed, angrily scrolling until they find the code that fixes their bug, I'm /sure/ this is helping😂
@@bobwilkinsonguitar6142 😆me rn
100vh has been problematic for me! never had to use 100vw, but it's good to see that dvh and svh are getting support! Thanks for covering this! :D
I used to do full-stack dev but quit back when IE7 support was still a thing that people sometimes had to do. I enjoy how much better things have gotten with decent html5 and css features, but my "oldschool" brain sometimes has trouble with the stuff we could never really use like this. It is great to have videos like this that distill the quirks down into manageable chunks without hours of experimentation.
Same!!
IE should be excluded from the world. Even IE10 or 11
@@ongke3655 support these days is completely unnecessary. But this was coming from back in the day when it still had 10%-20% market share. Not supporting that was basically just bad business back then.
Are you using something like Nvidia's Eye Contact feature? Around 1:40 your eyes suddenly change and it stood out to me.
I appreciate the content either way! Thanks for uploading.
i also spot that weirdness
That was scary as shit!
reptilian kevin
I JUST WANNA SAY... I LOVE YOU......... IVE BEEN SEEKING FOR THE SOLUTION OF THIS PROBLEM FOR A LONG TIME WHEN I SAW YOUR VIDEO AND BAMM!!! SOLVED!!! THANK YOU!!!!!
Man, these were the most productive 13 minutes I've been into since so long!
Thank you so much!
I've started web dev this year (through the Odin Project, which is how I found your channel incidentally!) and Issue 2 was the bane of my life last week. What's worse is that most Google results don't include svh at all - I had to *really* look to find it. But wow is it a great unit to use.
Now, haven't been excited about a CSS topic probably since CSS grid came up - since when have 'svh' units been a thing?! (Also, how could I ever miss this?!)
This LITERALLY IS a gamechanger - developing for those collapsing addressbars has always been SUCH a nuisance - thanks Kevin! 👍
They're relatively new, so do keep an eye on browser support, though it is pretty decent!
Thank you TH-cam algorithm for bringing me to this amazingly useful channel 👏👏
And thanks Kevin 👏
oops though that was a top-level comment. oh well
It’s so sad that there’s still no real solution for 100vh on mobile. svh also doesn’t seem supported by iPhone Safari which is what our clients complain about the most.
@@thedigitalceo It works on 15.4 onwards according to CanIUse, so you could set it to 100svh and then also declare 100vh as a fallback if it isn't supported by the browser (with a padding hack as well)
This exact header 100vh issue on mobile. arghhhh. I think i asked about it like 6 months back on your discord channel. There was so little info on web about the new units. Was super happy to see this video. Now its way more clear how to make use of the new units. Truely appreciate your work, thanks in behalf of the whole world :D
I've faced many of these problems. A lot has been clarified in this video. Thank you, Kevin!
Great! I have just enrolled for the free course. I learn so much from your videos and I just love playing with CSS, so fun!
Thank you kevin, I spent a lot of time to know the reason why I am getting that scroll bar even I used 100vw, yet you saved my time in the future.
This is the first video I watch from your channel and I can say, with absolutely no doubt, that I just became your fan, man! Thanks!
Earlier today I was wondering how to fix a problem with an element not showing properly on mobile because of the 100vh differences between devices. Thank you very much Kevin!
I don't use vw for everything but sometimes I see people doing so. Now I'll give these people the link to this video :) Thanks Kevin!
wow, i've never known anything about that "svh" unity, it's an incredible solution for a lot of projects that could have problems like the showed on the video, thx kevin!
Couldn't fall back to sleep so I've been flipping back and forth between you and Web Dev Simplified. You guys make great videos. I'll definitely have to come back to this one when I'm working on my projects.
Thank you! Love your professionalism
So far I have only used viewport units on pages that fill the viewport exactly on regular screens, either landscape or portrait. For that use-case it works pretty well. For other use-cases I have never considered them, not because of the problems it may cause, but because the alternatives I did use came more natural.
min/max/clamp are so good. And combining them with container-query-units is awesome.
Thank you for sharing about container query units, i study responsive design right now and i had no idea those even existed...
Wow 2 days back i was searching for this !!! 😂❤️ Great one
Damn! You always teach me fascinating things, and make me want to tinker and play. Thank you for giving such clear ideas about how the various rules work. You're so awesome at this.
I was wrestling with this the other days, so happy to hear this because now it makes sense.
Perfect timing for this, thank you, as always
Kevin, you are a golden find
Hey Kevin , thanks for the detailed information about View ports 😊
By the way can please explain the clamp() function in detail in a video ?
Already have one :D - th-cam.com/video/U9VF-4euyRo/w-d-xo.html
What clamp() does, I used to do with calc() combined with css variables for min and max.
This is awesome. Good job Kevin. I'm very grateful for all of your excellent content!
Exactly what I needed! Thanks for this video, it’s the best
I thought this was a contradictory post from one of your contents, glad to learn this was kind of a continuation about dynamic viewports. I stopped using viewports and started using dynamic viewports because of your videos.
Hi kevin , its really amazing that I have a problem in my code and in the NEXT DAY you make a video about my problem, happened already like 7 times
Thanks to Kevin, now everything I say or do has 'awesome' in it.
wow man, this video was exactly what I was looking for. My last project was almost 100% made with view port units. In this project it was`t a huge problem, because the target of the web site is PC/Laptops but I`m really excited to watch your course and learn the best practices. Doing layouts/UI/UX is the sort of thing that I`ve to do every day but hate every time I`m doing, and these type of video are really great to learn boring things with a dynamic explanation. thanks man =)
Hey Kevin! Nice shirt 😁🤘 just wanted to say thanks for the clearness of your videos, always find myself learning new things every time.
Thanks for the video. Subbed. I used to do a lot of web design, but haven't in ages. While things have definitely improved since those days, it's a little crazy to see the struggles with the same old problems on new tech. Will use your channel to get back up to speed. Appreciate your approach/method/sharing/pace/explanation/allthethings.
Man this was extremely informative. I definitely have used view port values a lot in the past..
omg thank you so much for the "100svh" tip. In my case it's a sidebar which must have the exact same height as the viewport but on tablets it was having that same issue.
Are you using the AI tool for eye contact?
Haha I looked for this comment - had the same feeling xD
Was testing it out, but I've stopped cause it's a bit glitchy :D
Now that u said it, it's so uncanny and I can't unsee it anymore 😭
It was distracting me a lot
You are number 1 and my best teacher!
👍
Love the video 👍 A good summary of the issues and solutions that everyone should be aware of
Straight to the point and well presented - perfect 👌
Do you use some software for your eyes? What was that at 1:40?
That 100vh part was very useful because I want the comment section on videos on my site to be off screen until scrolled so the comments don’t need to be loaded unless a user scrolls to see them
Regarding the 100vw producing scrollbar - I think it's not because the vw does not take into the account the scrollbar, but because (in case of body) there is already some margin applied on it. The scrollbar disappears when the margin is removed
This exactly too.
Yeah, this. Exactly this. When sizing elements, the default behavior is to apply the sizing only to the content area, which only includes the content itself and ignores padding, borders, and margins. You can include the padding and borders in your element sizing by declaring "box-sizing: border-box;" but then that still leaves the margins left over. You have to also set "margin: 0;" and then things should work.
You're right, i used to follow and i got better results.
This is only true for mobile browser/devices. Desktop 100vw DOES produce a scrollbar as of 2023. Chrome is in the works to provide a solution for that, it had a custom flag to enable overlay scrollbar until a few time ago. There's one hacky solution though: "width: calc(100vw - (100vw - 100%))", but I can see a case where you would want a 100vw instead of 100% through parent-child elements.
Your videos are always very helpful. 👍
I literally just put this into my code, alt tabbed and saw this thumbnail, went back to my code and deleted it, then pressed play and said to myself, "don't worry, Kev, i'd never."
I build with a mix of units and than run a PX to REM convertor before running final checks on my responsiveness. I've found that's working for me as I get more involved with Accessibility and working with multiple developers.
Great video. I'm investigating CSS functions now. Thanks.
Pretty on point. I liked this style
I can see the NVIDIA Broadcast! Amazing content by the way. I do web design on the side and you have helped me so much! Thanks alot
For a moment I thought I was going crazy 😅
Thanks, I didn't know about dvh or svh. It's scary that Google/TH-cam knew I needed to see this video...
Great video as always! QQ - do you use any software for eye contact? There are some weird artifacts in the video ~1:36 and ~1:42 where your pupils shift noticeably.
1:41 there is an eye glitch on Kevin face. Pretty interesting times we live in :)
Once again bringing accessibility issues. Thank you so much for this.
Respect + 🤟🏻
Hello! Why do I need to do "5vw + 1rem" instead of just "5vw"? 10:35
I didn't understand :(
Without it zooming wouldn't work. 1rem is the unit that gets increased or decreased when zooming, so without it your font size would have been just clamped 5vw
@@noctemcat_ Thanks! But testing here with clamp(5rem, 10vw + 3rem, 10rem) or clamp(5rem, 10vw, 10rem), the zoom works the same in both cases. :/
Testing without clamp really is a problem, but when using clamp, doesn't matter if I use +rem or not.
edit: I realized the zoom works, but doesn't works properly... so we have to use +rem. Thank you!
Oh using AI eye tracking are we? 😆
Great content as always!
1:40?
Super helpful. Great channel!
Absolutely game changing!
@kevinpowell although the footer is not sticky "stays at the bottom" I use flex: 0 auto in the first div bellow the body, then once the content inside goes beyond the height it can initially display the footer will be at the bottom of the content. to me it's not good design to keep a footer in view, as it's taking up space all the time. Always appreciate your work Kevin.
thanks Kevin for another great video. Good to know you're telling people about your courses here too now. More people should learn from you, I feel like there's no one better in this field than you
for how widespread and common those problems are, it is kind of shocking that there is still no easy way to overcome those.
well height is broken since the beginning, that's why align items vertically basically doesn't work without flexbox or grid
Right? It's so baffling to me that native UI elements of the browser aren't taken into account when calculating the viewport.. it just makes no sense.
@@pelly5742 learn to use height:100% properly and youll never have to worry. old web dev is better for a reason. this guy seems scared of it, must not fully understand it ... 'little issues' means even he doesnt fully understand what hes doing
@@pelly5742because every browser has different native elements
Loving the Nathan Barry shirt! 👕
Very good video ! Thanks for your always great work
Very helpful tips especially with 100vw. One of the points I tackle through with every project...
TH-cam recommend me this today. And I can't stop my finger to subscribe him.
I always set my body elements to flexbox column with a min-height: 100vh, then align my footer to the bottom with the content area set as flex grow. Seems to work well.
This was a roller coaster of emotions for me.
“Yeah this thing has problems but you can use this to fix it. But actually it has problems too so maybe try this. And actually…”
😂
Sidenote: What's up with your camera? Check 0:31-0:38. There is a strange eye distortion going on where it almost looks like one of those Nvidia eye tracking demos gone wrong
Hella good video. Subscribed.
Oh wow, you only just uploaded. Great video!
I use vh to make objects dead center. Like if I want to center a login form in a login page I use height: 100vh for the body of the page. Is there any better way to center objects?
MY CSS GURU!!! THANK YOU!
Thanks man! dvh saved my life
THANKS. I think I just found a great problem in my project
omg thank you so much, I have the problem with 100vh height in my project and the svh is probably gonna fix it!! Thank you!
0:18 are u using some software in your eyes ? your eyes take some jumps through the entire video =s
Did anyone else see the strange flickering in his eyes at 1:35 ??
Genuinely confuses tf out of me
Hello Professor KP! 😇 I am studying UX Design. Longtime artist trying to figure out front-end development. I liked your videos right away as soon as I noticed have you kept your profile in a circle frame. Plus you kept looking back towards the camera. You must be a writer. Funny thing. I watched/listened to a couple of your videos on 1.5 and 2 playback speed.
Thank you sir for the SVH value trick 👌🏻😊
Can't you stare at us without AI, Kevin? lol @ 1:43
But thanks for the video!
This was amazing to learn about, I've just been using the h-full (100%) trick, will try out the svh way! Thanks
Wait, are you using that NVIDIA Eye Contact thing (or something comparable) that makes your eyes look at the camera? Something's weird...
Are you using something to fix eye contact on your videos or are you AI? Great video!
I do use a utility class to make panels restricted to a container look like they are full viewport width (width: 100vw; margin-left: calc(50% - 50vw).
I got it from an Andy Bell tutorial. I've not seen any horizontal scroll issues though. Could just put overflow-x: hidden on parent of course. Will have to chck this, but there's no other way to do this one really.
good tip
Excellent. I always want to know some solution to this problems
Thanks a lot! As usual I found your video awesome. (Gone to remove all 100vh from style.css files) :)
Could someone explain me why he adds + 1rem in the middle of clamp? 10:18
Are you using Nvidia's face correction or eye tracking program?
1:40
Awesome video. Thank you.
Hi Kevin, You now have around 600k more subscribers since writing the sign up page for the course 👍. Thanks for the relatable, real world content.
I pretty much only use viewport units for dashboards that could be displayed on large tv's, or for setting 100% height on the page container. for the 100vw issue, you could just do overflow-x: hidden if u really needed to use it.
8:34 - I have seen this vw font size/padding/margin thing too many times. I can't understand this, you can see all the problems when shrinking window to 300px width already, how can they keep doing this? Also you can see on wide screen how it is broken too, but for this you need wide screen or 2 screens to test at least.
What bothers me the most is that if someone uses vw units it means they probably know modern CSS and it shows that they care about responsive design. So how in the world they are building websites like this? Using clamp for font sizes is usually enough, you can easily do websites that work from 200px to your max container width (on bigger screens browser zoom works great, at the same time makes website usable on ultrawide screens). Using vw units without clamp or min for anything is a bad idea. Using media queries is not a bad thing, no matter what you do, it almost never takes more than 3 media queries to make it work perfectly on every screen size and usually it is 1-2 queries.
It works like that even if your container is 100% width (so for every screen size it will take exact same px width value as screen offers) which i like to do, so there is never empty space on sides on mobile devices. Mostly it comes from bootstrap css where containers are like 400px, 600px, 800px... fixed and nothing in between.
Thank you!!!
Also your eyes creep me out, at 1:40 they're sketchy...
Haha, I'd be testing something, but I've since stopped using it 😅
Nice mate, keep it up.
I'm glad I started playing around with HTML and whatnot after svh became a thing in the standards... Learned using them from day one. And I probably use them too much
Thx for another usefull info :)
Kevin my friend, u don't need to add those strange eye filters @0:40 @1:19
You look good as you are
svh's problem is, in android, virtual keyboard will also change the height... and this is inconsistent with iOS Safari's behavior
Hey, great video!
What about using:
html, body {
max-width: 100vw;
overflow-x: hidden
}
I understand the vh can be problematic, but the vw on that use case is something I always use to avoid that some elements that are outside the window width make the horizontal scrollbar visible.
I was wondering if there's another solution to that.
But they are already full width, no reason to add that line in there. You could just have the `overflow-x: hidden` if you really need it, without the max-width.
Hey Kevin.
Are you using Nvidea's Eye Contact, right? Or some variant of AI eye to camera focus
Cheers!
I think he is.. Glitched on 1:40-1:43
Yeah, thought the same
It looks a bit scary if u ask me
Haha, yeah, but I've stopped for new content, too many glitches