Hi to everyone! Here are the developers of City Car Driving 2 speaking.
We have taken into account the criticism that watching videos without sound is boring and makes little sense.

And in log # 25, we are sharing the progress in the mechanics of cargo transportation and construction. Now we are approaching the key object in the game: this is a sawmill where resources are stored.

In this building and other similar objects in the game world, we will be able to take various supplies, their list has not been approved, but all resources will be logical, only what passenger cars can transport.

It is very important to note that the UI is now in working order: this is debugging information for us, the developers. This will definitely not happen in the game, it is important to show the mechanics here.
Each resource has its own weight; they are gradually loaded into the vehicle and automatically stored in boxes. All this changes the physics of the car while driving: the car’s handling will obviously become more difficult, and it will grow noticeably heavier.

After reloading the resources, you can select any building on the map that requires construction.
As an example, we chose a paint workshop building, you may notice “objects flying in the air”: this happened after we changed the coordinates of the entire map to adjust the traffic.
In the workshop building, we do the same as in the sawmill – independently reload the supplies, and then we press the “construct” button.

After this, through a standard loading screen with tips and history of the city, we finish the construction of the object. The key detail of this mechanic is that in the game world, there will be objects that only change their model, but there will also be buildings that are fully functional. For example, as you might guess, in this object, we will be able to paint our vehicles.

This is a rather short diary, and this is still not the promised “DevMP4” section. Instead of the usual log in text, we are experimenting with the format of presenting the information about the progress of the development. Have your say, we equally accept wishes for success, criticism, and negative feedback.

Thank you for your interest in the project and feedback.
Developer logs are published every two weeks, don’t miss them.

All the videos in the log are from our archived bug fixing tasks. The video shows half an hour of the tester’s work accelerated a thousand times: they test each model to be included in the game. They check textures, LOD, and physics: so that the model looks good, both up close and at a distance, and does not let going through it.
If defects are found, for example, “gaps” between the top of the model and its base, then tasks are assigned to the artists who must correct the mistake. We have quite a lot of independent 3D assets, so each model must be tested. In addition to models, our QA team also test other areas of the game. For example, the behavior of pedestrians and traffic at the location. In the first video, you can see that pedestrians do not see any obstacles on their route and endlessly walk into the obstacle without stopping. The same video shows how strangely the minibus turns: the “brains” of this vehicle did not correlate its weight and speed for the correct turn. And the truck crane in the background did not “see” that there were already other vehicles in front of it and crashed into them at full speed. The second video shows the same situation with a truck. So far this is not the smartest vehicle in our volume of traffic. Now the listed problems, of course, are already being corrected.
We have repeatedly shown the car wash: this is one of our oldest mechanics. At the beginning, it happened due to incorrect reading of the vehicle position. This kind of bug is quite a common situation when any games are developed: the player loses control of the character | vehicle, after which the object of interaction “pulls” it into itself.

We carefully look for bugs, fix everything promptly, and care about the technical condition of the game. The videos and explanations in this log are only a small part of the QA work.

We tried to select the most interesting and already fixed points, so that, as we wrote at the beginning, we could show you defects and bugs not from the position of “a cheerful selection of bugs” but to share a little portion of the work process. At the end of the log, we add a small bonus: this has practically nothing to do with CCD 2.0, but in UE, you can literally turn on the destruction (of course, unrealistic) of any object with one click. This action destroys any optimization, but we couldn’t help but experiment. Developer logs are published every two weeks. Don’t miss them