The Eye of God C automatic parking is too cautious. It waits immobile when encountering scenes of people and vehicles. At night, it mistook a distant power pole as an obstacle, causing the user to alm

The automatic parking function of Eye of God C is too cautious. Especially in places where pedestrians or vehicles are coming and going, it will stop and wait, often waiting endlessly.

Those people or cars were always moving. Just when it felt there was a space and wanted to move forward, another person or car appeared. It had no time to react, and it just stuck there without moving.

As a result, the user gets tired of waiting because it just refuses to continue.

Something went wrong when I used it at night. Later that day, there was clearly a telegraph pole in the distance. It was so far away, but it suddenly stopped and refused to move again. Maybe it thought the pole was something alive. If it really thought it was an obstacle, it stands to reason that it should just stop the entire parking process and then exit. But it didn't do that and just waited there.

I thought it was almost healed and the time had almost passed, so I walked forward and almost walked out of the parking lot. When I turned around, I saw it was still stuck there. During the day, its operation is quite smooth and effortless.

This over-caution made the whole process drag out. For example, last time in the parking lot, there were not many people, but there were always one or two people walking by, and it would stop immediately and wait until they were completely gone before it dared to move. Even if the space is large enough, it has to confirm it several times for fear of running into something. Users stand aside and look at it, feeling that time is wasted.

If only I could be a little bolder and react faster. But as it is now, it would rather wait than take risks, which has led to many people using it and getting started on their own.

Let’s talk about the electric pole at night. The light was low that day and the parking lot was a bit dark. It glanced at the thing from the rearview mirror or sensor and misunderstood it. The pole was dead and wouldn't move, but it seemed to think it was potential trouble, so it stopped. Normally, when the system detects a fixed obstacle, it should give a sound reminder or directly cancel the parking mode.

But it chose to wait. Perhaps the algorithm felt uncertain and would rather play it safe. As a result, I walked out for several steps before I realized something was wrong and quickly came back to check. Fortunately, nothing serious happened, but this incident made me cautious about using it at night.

Although this overly cautious design is for safety, it is quite troublesome to use in practice. Especially in busy parking lots, where people and cars are mixed, it can easily get stuck. It can be done smoothly when the sun is good during the day and everything is clear. But at night, or in places with poor lighting, the sensors are prone to errors and regard distant shadows as threats. Users have to be patient or be prepared to take over manually at any time. If the software could be optimized to distinguish between living and dead obstacles, the experience would be perfect.

I have tried it several times myself, and every time I encounter a similar situation, I have to wait for a long time. For example, last week in the underground garage of the shopping mall, a car happened to back out from the side, and it immediately paused. After the car had completely driven away, it had to wait a while to ensure that no one came back. It's doing that right, but it's a little too slow.

The example at night was even more exaggerated. The pole was at least five or six meters away from the front of the car, but it stopped as if it had seen a ghost. It may be that the camera resolution is not high, or the algorithm is too sensitive. Anyway, since then, I have been paying more attention when parking my car at night and not relying entirely on it.

It reacts more slowly when it encounters children or pets running around. Those little things moved so fast that they didn't have time to judge, so they simply didn't move. The user looks on anxiously, but cannot give random instructions. As a result, the entire parking process, from start to finish, took twice as long as usual. Safety is the first priority, but the balance must be found.

It would be nice if a manual override button could be added to allow the user to accelerate safely. But it is very strict and waits until it is confirmed to be correct before moving.

Thinking back on when I used it during the day, it was really reliable. Once the space is empty, it pushes forward steadily, at a precise angle and at a uniform speed. There are no unnecessary pauses, everything falls into place. But when it comes to complex scenes, the secret is revealed. The parking lot where people and cars move around is already chaotic, and being so cautious makes it even worse. It is even more typical to misidentify electric poles at night.

The iron thing in the distance stood quietly, but it was panicked. The user almost walked away before discovering the problem. Fortunately, the parking lot was not far away, so I came back quickly, but I was really stuck.

This problem is not an isolated case, many users have reported similar things. The system is too conservative, resulting in low efficiency. Smooth during the day, laggy at night, unlimited activity areas, etc. After optimization, I hope it will be smarter and be able to distinguish real threats. Only the user experience can go up. As it is now, I feel like cursing people when I use it, but safety comes first, so there is nothing I can say.