cameraV2's set camera direction to is a bit weird

[fg133266]

This is my building block

This is the effect I need

QQ202539-21162.mp4

But the actual effect is like this, I'm not sure if I did something wrong;-;

[fg133266]

What I said may be strange because I used translation software. I'm sorry ;-;

[SharkPool-SP]

the issue is with the way you use thread variables itself, the value changes way to fast and too largely. Which causes it to look like its rotating. You get the effect you want when you use something like the timer:

[WAYLIVES]

Hi! Just check the box in the add-ons to ensure that the pen is in high quality and nothing more! Everything will work)

[WAYLIVES]

the issue is with the way you use thread variables itself, the value changes way to fast and too largely. Which causes it to look like its rotating. You get the effect you want when you use something like the timer:

This is a problem with this extension. Sprites start jumping if the pen is in poor quality...

[SharkPool-SP]

@WAYLIVES the problem is not really a thing the extension can control. As mentioned in the turbowarp setting, its a rounding error. Which is why high-quality pen works.

[WAYLIVES]

@WAYLIVES the problem is not really a thing the extension can control. As mentioned in the turbowarp setting, its a rounding error. Which is why high-quality pen works.

Yes, yes... The pen is drawn in high quality because there is no rounding in the x and y position.

[SharkPool-SP]

I'm gonna close this as the issue is unrelated. I'll make a separate issue

[GarboMuffin]

Changing camera properties sounds like the kind of thing that should request a redraw so that the original project does actually work

[SharkPool-SP]

Changing camera properties sounds like the kind of thing that should request a redraw so that the original project does actually work

Which it will in the new issue? This is not a issue with setting direction as the title displayes

[GarboMuffin]

#2025 is unrelated to what I was talking about in that comment

What I mean is adding vm.runtime.requestRedraw() when changing camera properties so that the VM knows it shouldn't run the loops 1000000x per second. Camera V1 has been doing that for years

[GarboMuffin]

If indeed the original bug in this issue is caused by "the value changes way to fast and too largely" then requesting redraw to limit the loop to run once per frame would fix it

[GarboMuffin]

It also doesn't really make sense for big directions to cause issues... the extension should know that 36000 degrees actually means 0 degrees for example

[SharkPool-SP]

I'll test it out when I make the pr