Here’s my first try at implementing damage to the car. It’s working for the body mesh but not the bumper because I still need to combine the sub-meshes. This was just a test to see if the Impact Deformable Component could work in my project. Now I need to add some sort of smoke/sparks effect and disable/hinder the car once it takes enough damage.
Also, I’m switching to Unity’s universal rendering pipeline for improved visuals. I was using the built-in renderer which supposedly does not have the features that the new pipelines do. The first thing I’m attempting to implement with it is some basic anti-aliasing but I haven’t figured that out yet. Thanks for reading!
I flattened the terrain “walls” that prevented players from driving off the edge of the world, but I never liked the look of it. I think a better design is shutting the car off when the player drives outside the test area (with a fence around the perimeter maybe). I imported a free skybox asset and I am happy with the results. Technically, this does not count against my feature freeze as one of my cards is “TestTown Improvements,” so I can throw this work in that bin.
I’m giving myself a hard deadline of the end of the year to release this game. It’s going out in whatever state it’s in so I can move on to the next project. I can’t stop thinking of new things I want to implement, which, naturally, increases the difficulty of finishing this thing exponentially. Most software companies deal with this by implementing a product-wide feature freeze which means nothing new gets added until everything they’ve already committed to doing is tested and ready for public consumption… but I just had a really good idea that I think is important enough to include! Occupants! Self-driving cars are pretty useless if they don’t drive people around, so, I want to take the ragdolls and stick them in the car by attaching their hands and feet to the steering wheels with some basic collision detection to determine if the occupants were harmed. This also helps with the scoring system as some companies will value their occupants more than others ;).
The other idea I had was using some sort of soft body/destrictible mesh for the cars and the props in TestTown because I think people will have a lot of fun knocking stuff down and it’s a good way to determine the amount of property damage the player has incurred. However, this could take a long time to implement if I can’t find an existing system that does a good enough job.
I’m going to add these two features to the board and stop there. Honestly, if I can ship this game with just the prototypes of these features I’ll be happy. Thanks for reading!
I had to model the LiDAR unit on the Fuber (blue volvo-ish) car. The NoMo car looks a bit small and thin here, so I might change it, but the problem so far has been the Teslow car. It’s too blocky, and I haven’t found a good substitute that isn’t published under an editorial license. I’m going to try importing the prefab’s model into Blender and using a subdividing modifier on the larger meshes, starting with the wheels to see if I can increase the level of detail.
Also, something I didn’t showcase in my last post was that I changed the game’s title scene to this absurdity:
Not sure if this will end up in the final cut as it is 😉
Motivation sucks. For every bit of it that I get, there seems to be an equal and opposite amount of apathy. Despite that, I guess it still technically produces something positive because during the manic depressive high I get a few things done. I had been contributing to my project at least an hour every business day and then taking the weekends off, but the last two days I just played video games instead of the hour I should have spent working on CarCoder. I guess that’s not bad considering I did work for a few weeks like that. I want to share some screenshots of everything that I did to see if that helps me, and also talk a bit about why I don’t want to work on the project anymore.
1. You can no longer make the car fall off the edge of the world:
3. Intersections with “working” lights!
4. Improved resolution of TestTown’s town square backdrop and added more props:
5. Improved look of the “auxiliary” TestTown buildings:
6. Added a four-way intersection with stop signs:
7. CCTV camera models:
8. CCTV shaders:
9. You can adjust the time of each instruction as well as remove them:
Things that are broke now that were not before
No more car sounds.. after adding additional cars for the car selection scene (more on this in a moment) my car controller would do very odd things like cause the wheels to just float away and other oddities that I just took out the sounds and animations to get the new cars working.
Reordering an instruction can break the new adjustment UI changes (I think)
The biggest change I have made so far is the car selection scene, or what I’m calling the job selection scene. I had this idea that the player could choose who they wanted to work for since there are several companies, and that would give them a different car with different capabilities/specifications (speed, handling, etc) and a completely different scoring mechanism depending on that companies safety rating. So, while one car manufacturer might value safety above everything else, another might value the speed at which you completed objectives above everything else. I set out to create a new scene that appears after you select a level, and here’s how it looks so far:
You can see the new cars, sure, and it all works, but let’s just admit that it needs a lot of polish, to say the least. The new scoring system complicates things as well, but I felt it was necessary to make the game more interesting and give it some replayability. It didn’t seem like much fun without the chance to get things wrong, and this way, less, um, cautious players can progress but still be challenged. This has also meant tasks of tedium like searching the internet for appropriate yet affordable 3D models, and then getting those models to work (and look) correctly. My goal now is to make all the levels I possibly can and get everything working. Then, a feature freeze to get it polished up for the release.