#Model tracking is heavily delayed

1 messages · Page 1 of 1 (latest)

thorny vigil
#

Hello, here because the Live2D discord wasn't able to help me. My tracking for this specific model is delayed by about half a second. My other models track fine, but for some reason this one is the only one that's delayed so much. Augmented physics are not the issue as we confirmed in the Live2D discord.

nocturne nebula
#

This looks okay, it is how the rigger did it, augmented/physics angles delay the model slighty you can reduce the smoothing on the parameters to have more snapiness

thorny vigil
#

Augmented physics aren't the issue, I confirmed that in the Live2D discord with someone else. The tracking itself is heavily delayed.

#

Smoothing also isn't the issue, I turned that down to zero and it's still delayed.

nocturne nebula
#

Please jsut the FPS because it could have some important info in the log if you screenshot that

thorny vigil
#

It averages around 30fps

nocturne nebula
#

Since you said you are having problems with this single model, does the other models also run at 30fps ?

thorny vigil
#

Oh yeah, other models have around 60fps. This model is also really big.

nocturne nebula
#

Did you put this to 60 and what are your mask settings

#
  • the physics settings you have it on match app fps right ?
thorny vigil
#

Both are set to 60fps and smoothed masks are off

nocturne nebula
#

could you put match app FPS on the physics ones and your mask config waht value are you using ? (Please a photo of it would be ideal)

#

Big models needs big optimizations! (or things like this can happen KatouSweat )

#

Usually the lag you encounter it is because they abused automeshing on high density/too detailed, and your model it works the same as a game, it is lagging everything else (icnluding the tracking that is why the delay it seems) but lets see if what i said improves the tracking

thorny vigil
#

I have match app fps off because it seriously screws with my physics. I can mess with the meshes cause I totally abused automeshing on high density lol, I was the one to rig the model

nocturne nebula
#

Okay since you rigged it

#

if it breaks the match app fps then you are rigging with it at 30 fps in physics settings!?

#

Usually with my L2D peeps im the person that is strict with optimization because these types of problems KatouLUL

#

If you can show me

#

For example this si a big model with 6 outfits

thorny vigil
#

Yeah, this is my first time working on a model this stupidly big LOL. give me one second

nocturne nebula
#

also on your physics settings if you can show me this number KatouDet

thorny vigil
#

ough yeah, we got. a lot of big meshes.

nocturne nebula
#

Weird that the match app fps produces problems

thorny vigil
#

I'll adjust the meshes and optimize it and see if that doesn't help.

nocturne nebula
#

not too many masks seems okay

#

abused a lil bit of interpolation but not that much

#

But yes you abused way too much automesh >_ <! that lags everything

#

also when exporting idk if you haev this on, the erratic physics as well seems like part of the model lagging as well

#

Okay last thing! what cpu+gpu are you running

#

I know it will sound insane but models, big models needs beefy's pc's as well KatouNOOO

thorny vigil
#

I'm working on bringing it down now :3 I'm running intel i5 and nvidia rtx 3060ti

nocturne nebula
#

Probably no one told you that

thorny vigil
#

No, I know that

nocturne nebula
#

oof yeah probably your cpu is suffering

thorny vigil
#

Ooo guess I gotta get a new cpu

nocturne nebula
#

if you go to performance

#

im 100% sure you will see some of the graphs peaking at 100%

#

Also one thing dont use 16k x 16k textures like never, use multiple 4k x 4k, (like 20+ can be no problem)

thorny vigil
#

ooo yeah she's struggling a bit

#

oh yeah i know, i've been using 4kx4k

nocturne nebula
#

And like one 8k x 8k for like really big textures that doens't fit 4k x 4k

#

oh okay great KatouNod

thorny vigil
#

lol i turned my meta shit off and my cpu usage went down to like 63%

nocturne nebula
#

Extended interpolation don't use 5, use 3 or 2 in the value that shoudl help as well KatouNodders but right now you have too many poligons in your model it is why i think the lag is happening, im like 80% sure that is what generates the rest of your problems/delays

thorny vigil
#

yeah i'm working on that right now

nocturne nebula
thorny vigil
#

I slashed the polygon count over a third in size and it's running a lot better but Ithe tracking issue hasn't changed at all, still lagging about half a second behind.

thorny vigil
#

Okay, I restarted vtube studio and the delay has decreased substantially

#

Still a lil bit of delay but this is so much better