SC2Mapster

I have something like

        while(1)
	{
		facing = UnitGetFacing(gv_hero);
		CameraSetValue(1, c_cameraValueYaw, facing, 0.0625, 100, 10);
		TriggerDebugOutput(1, FixedToText(facing, 5), true);
		Wait(0.03125, c_timeGame);
	}

into an map initialization trigger, its pretty smooth camera until it reachs 90 or - 90 degrees and gets very buggy, anyone know a solution?

edit 1: bugy to buggy.

edit 2: Worked with

	while(1)
	{
		facing = UnitGetFacing(gv_hero);
		CameraSetValue(1, c_cameraValueYaw, facing, 0.0625, 0, 0);
		TriggerDebugOutput(1, FixedToText(facing, 5), true);
		Wait(0.03125, c_timeGame);
	}
	return true;

I dont know exactly, what the problem is, but Wait(0.03125, c_timeGame) does not work as you might expect. A wait with 0 seconds time runs every 0.03125 seconds. Any value > 0 will make it run at 0.0625 seconds instead, even if it is <= 0.03125. Also, it is not 100% confirmed yet, that an interval < 0.0625 would make any difference at all.

However, I noticed some problems with said angles as well, when comparing angles with each other. If both of them are very close to 90 or -90 degrees, the difference becomes absurdly high.

€ Maybe your velocity is too fast, try something like 1

If I'm not mistaken I faced a similar problem sometime back.. Camera angles not displaying properly. Could swear one of the patch notes said it was fixed though... Apparently not?

When you say buggy, do you mean jittery? In my scenario the camera just swung to a 0 degree angle and got stuck there as I recall.

@FuzzYD: Go

The patch did fix it. However if you have unacceptable settings you will also receive weird glitches with the camera. These unacceptable settings being (100, 10) in your case.

The problem I see in your first script is the speed you used with the velocity and deceleration values. I suggest using initial velocity almost 100% of the time.