Huge space, manual shifting, the car is more agile (more nimble), better road holding, less calculations.
The program works for about 1 minute when it starts, but it saves the generated track (which is almost 1GB), so the next time you start it, it takes less time to load.
If you roll over, you don't have to start over, with the K-key you give a lift to the front wheels, and thus the car can be tilted back.
There is also a 'game' mode. if you press the G-key, you will see 5 balls on the radar. You have to catch these.
I added mouse control. since steering in real life is an analog thing, it cannot be solved precisely with buttons. (either I steer left or right ??? this is stupid in real life) You can also control it with the keyboard, in the traditional way, or you can steer by moving the mouse left and right. left button forward, right button maybe. both buttons = handbrake.
The control requires skill and speed, I recommend manual shifting, so you can immediately control the torque if the car wants to slide off the road.
If you want to roll over, smaller wheelbase. If you want to go stably on hills, larger wheelbase. The physics is implemented on the screen with approximate accuracy.
Track editing works the same way. The BLUE channel is the depth data. If the RED channel =255, so it is red on the map image, the program covers it with asphalt.
It can be easily edited with an image editor. Any image. If we want a smoother surface ? 'blur'. If we want to shift and scale the level differences ? 'bright/contrast'. Do we want a lot of potholes ? 'add noise'.
I hid the QB64 logo in one part of the map.
If you want to experiment with your video card's capabilities, try this: at the beginning of the source code you will find: MapDat(1) = 2000. It is currently set to 2000. This means that the entire map has 2000x2000 depth data. The higher you set the value, the higher the resolution it works at. I think this is already a huge resolution.
Important! The game can be enjoyed if the physics are 27,28,29,30FPS. This can be seen above. On a slower computer it may be less, but unfortunately then the game will not provide the experience I calibrated it for.
hsiangch_ong:
Thanks for your answer. The civic in the game is a very underscaled, dumbed-down model. If you want the original (with wheels, in high resolution, complete), I will be happy to send it to you. I don't have Linux, I can't test it. Are the physics good? I didn't answer in detail because I rewrote a lot of things, so I hope that the errors you noticed have been corrected. I hope you try this too, and now you can compare it to what.
An afterthought.
This is an exciting area of flexible body physics. It is very easy to model the operation of any structure. But unlike rigid body physics, it requires a lot of calculations. I spent a lot of time just calibrating it. This car game is a very deceptive and simplified pseudo-physics. Inaccurate physics. The relationship between flexible points can describe the structure of a cube, a car, a clockwork, anything that moves, has an axis, can be attached to something. Here, the most accurate result would have been if I had given the movement from the engine crankshaft all the way through the differential, to the axle of the wheels. This is conceivable, but it's crazy. And a lot of calculations. Currently, the torque is applied to the outer surface of the driven wheels. And since there is no counter-force, the car does not rise. In the game, it rises, but I achieved it by cheating. It would be very nice to implement the dynamics of a complex structure someday, but for now I want to finish this car game.
https://drive.google.com/file/d/1JUOWDKN...drive_link
The program works for about 1 minute when it starts, but it saves the generated track (which is almost 1GB), so the next time you start it, it takes less time to load.
If you roll over, you don't have to start over, with the K-key you give a lift to the front wheels, and thus the car can be tilted back.
There is also a 'game' mode. if you press the G-key, you will see 5 balls on the radar. You have to catch these.
I added mouse control. since steering in real life is an analog thing, it cannot be solved precisely with buttons. (either I steer left or right ??? this is stupid in real life) You can also control it with the keyboard, in the traditional way, or you can steer by moving the mouse left and right. left button forward, right button maybe. both buttons = handbrake.
The control requires skill and speed, I recommend manual shifting, so you can immediately control the torque if the car wants to slide off the road.
If you want to roll over, smaller wheelbase. If you want to go stably on hills, larger wheelbase. The physics is implemented on the screen with approximate accuracy.
Track editing works the same way. The BLUE channel is the depth data. If the RED channel =255, so it is red on the map image, the program covers it with asphalt.
It can be easily edited with an image editor. Any image. If we want a smoother surface ? 'blur'. If we want to shift and scale the level differences ? 'bright/contrast'. Do we want a lot of potholes ? 'add noise'.
I hid the QB64 logo in one part of the map.
If you want to experiment with your video card's capabilities, try this: at the beginning of the source code you will find: MapDat(1) = 2000. It is currently set to 2000. This means that the entire map has 2000x2000 depth data. The higher you set the value, the higher the resolution it works at. I think this is already a huge resolution.
Important! The game can be enjoyed if the physics are 27,28,29,30FPS. This can be seen above. On a slower computer it may be less, but unfortunately then the game will not provide the experience I calibrated it for.
hsiangch_ong:
Thanks for your answer. The civic in the game is a very underscaled, dumbed-down model. If you want the original (with wheels, in high resolution, complete), I will be happy to send it to you. I don't have Linux, I can't test it. Are the physics good? I didn't answer in detail because I rewrote a lot of things, so I hope that the errors you noticed have been corrected. I hope you try this too, and now you can compare it to what.
An afterthought.
This is an exciting area of flexible body physics. It is very easy to model the operation of any structure. But unlike rigid body physics, it requires a lot of calculations. I spent a lot of time just calibrating it. This car game is a very deceptive and simplified pseudo-physics. Inaccurate physics. The relationship between flexible points can describe the structure of a cube, a car, a clockwork, anything that moves, has an axis, can be attached to something. Here, the most accurate result would have been if I had given the movement from the engine crankshaft all the way through the differential, to the axle of the wheels. This is conceivable, but it's crazy. And a lot of calculations. Currently, the torque is applied to the outer surface of the driven wheels. And since there is no counter-force, the car does not rise. In the game, it rises, but I achieved it by cheating. It would be very nice to implement the dynamics of a complex structure someday, but for now I want to finish this car game.
https://drive.google.com/file/d/1JUOWDKN...drive_link