Our plan will make a permanent impact on Decentraland as we are proposing an open source reusable car racing/driving system for the community to use in future projects. The game code, the cars and the Race Track environment will be open source.
The launch of the Racetrack will mark the first chapter of the Metaverse Motor Show.
We are developing a modular game and racetrack system that will allow new racetrack based car games to be more easily created and will be highly optimised for the game engine to allow various techniques to be used to get the best performance for driving in Decentraland.
The modular racetrack setup will facilitate advanced racetrack designs such as ramps/inclines and different ground contours such as banked bends as well as other aspects that affect car behaviours.
This a project that contains numerous benefits and opportunities:
Enhances the profile of Decentraland, by showcasing what is possible using SDK7.
Supports and grows the Community by creating a game with wide appeal that will attract new users to join the community.
Supports Community Developers, who will be able to use what we create as a jumping off point for new driving games and experiences.
Provides a more sophisticated motor/driving gamification. We will open source all of the driving game libraries that we are developing for this game so they can be used by less experienced game developers to create similar experiences after the Metaverse Motorshow.
A competitive game that will not only engage users during the Metaverse Motorshow, but will remain playable afterwards.
The racetrack and the games on it will be the centrepiece of Februaryās event. Players will be able to pick from different cars and race them on the racetrack. Each of the car brands, be it web3 or web2 will get their own custom pit stop with some of their latest models displayed.
Deliverables:
Base set of modular racetrack parts/tiles and associated Blender Scripts required for Export
3D asset pack (e.g. ready to use tiles)
Racetrack area formed using 3d assets and additional environmental assets.
Several open source car models
Open source library with complex car mechanics with working examples
@dogman@Shiny for sure.
We have a experimental track scene, its not exactly the same version as you can see in the video which was focused on car entry and interior. We are currently prototyping 3rd person view of the car and experimenting with controlling the car. The current incarnation moves the steering wheel with your mouse with the keyboard just used for accelerate and brake.
I will get it published tomorrow to peertest, the moment its in Vegas City on a private catalyst and the track was deployed pretty randomly in terms of location so need to check that we are ok pushing to peertest in itās current coords or whether we deploy it somewhere else.
(In what we publish tomorrow you still get to click on the McClaren and see the door open, itās just that it then puts you in the view you see in this screen grab)
Could we get a video to understand the mechanics a little better? If the ādrivingā feels good this could be a great system for DCL to implement at the client level across the world.
Any consideration for interop specs on the models? I know OMI is working on a vehicle spec and it would be great if these assets could be implemented into any scene w/ module for testing and expanding DCLs technology for cars along the right interop pathways. ([DAO:c7d1bf9] Should DCL work with and adopt OMI standards for Vehicles & Seats?)
hey @Morph we are spiking a whole variety of approaches to shape the way forwards.
I will post a public demo link as per my previous comments asap. But itās a bleeding edge version and as we experiment we introduce glitches etc that we donāt want to expose people to.
But the signs are promising for example, here is a test we were doing a couple of weeks ago to investigate ramps/inclines.
I am really up for OMI standards adoption where possible and at very least staying tethered somehow to the vehicle spec as it evolves. At the really basic level making sure the models are broken up in a similar way makes a tonne of sense. I havenāt been able to find much information on this on their site or in the Github - but will continue to investigate.
Will post more videos asap and once there is a demo link that I am able to share I will do.
Finding the optimum way to handle driving in DCL is definitely something Iād love to see evolve into the client and we are here for the long term to participate in that to what ever extent we can.
Hey @theankou, our core team is from the automotive industry and weāve created just about anything from high poly production ready cars to game ready cars. Cryptomotors, our Web3 project is mainly focused in bringing digital cars in as many virtual worlds as possible, from millions of polygons of NURBS data to just a couple thousand, Decentraland ready models. Weāve brought our cars to many different virtual worlds so far, like Decentraland, Voxels, Somnium Space, Revv Racing, Sandbox and even created our own game. We are really confident that the car models that we will create will strike a balance between detail and performance for the smoothest experience. I am attaching here some pictures for reference. LetĀ“s take this car that I personally worked on for example:
Thank you for answer @George_VA. Your car models is great and your team did a great job on creating them.
However, this cars (from DCL screenshot) seems very high detailed for Decentraland. Do you know that tris limitation is 10k per parcel? As it seems, one car from your screenshot have much more triangles than the whole parcel limit (maybe iām wrong, but it looks like around 30-70k with all this bevels and smooth corners.). Imagine there is bunch of this cars, for example - 10 on 3-4 parcels, this is a huge amount of triangles, especially on Web DCL, players will have less than 30FPS (Ohh this flashbacks from MABā¦). (However, FYI - on DCL Desktop FPS will be stable and smooth)
I know that many scenes dont follow guidelines, but i hope, in worst way, there will be annotation with recommendation to play on PC will be added somewhere.
@theankou , totally agree, and I remember when we first started testing car models in DCL 2 years ago, so I totally get your concern with performance. But with a lot of testing, we found a good technique that worked well: all of the Decentraland car models that we created were between 5 and 10k polygons (depending if they had interior or not). We had a Cryptomotors dealership in the Crypto Valley where we had a couple of these cars, around 4 of them, and it was running smoothly on a Macbook Air Web client. We never went over the 10k limit poly count. I think this particular one sits at around 10k poly. The way we did it and the reason the car looks like this because we baked the high poly model texture on the low poly one.
I would also like to add that in addition to Voxel Architects great skills and experience in modelling cars for different 3D engines, both teams have a lot of experience in optimising scenes for best performance in Decentraland. So for example, in terms of the game we can use lodding and culling techniques to make sure we get the best performance out of the game engine by only displaying things when they are needed and when we do, we display a level of detail needed. So cars in the distance can be a very low tri count, but ones very close to you will be at the appropriate level of detail to look good. If you are an interior view we donāt need a high level of detail on the exterior of the car you a driving, and if you are in 3rd person view, the interior is largely not needed.
Over the past few years we have evolved many optimisation techniques in DCL for performant big scenes like The Australian Open, LaLigaLand, The Flamingos and Jose Cuervo Metadistillery, so we will be able to use our experience with a priority of ensuring this works in both the browser client as well as the desktop, and to get the cars looking as best they possibly can in DCL. And to that end we can use the getPlatform() method to control which sets of assets are used in Desktop and which are used in Browser - so if necessary we can use lower poly models in the browser version to get a playable FPS.
Hey @SugarClub , sure thing. I am attaching here an image of a model with the mesh and 3D wheels. So the body itself is 4144 tris, model converted and downsized from the original NURBS model. The wheels in this particular model are what adds 4000 extra tris, but we can optimise that further by making the wheels as cylinders and texturing them, which will keep us under 6k tris.
I originally voted no, but after reviewing the comments and community discussion & responses from the team, I am able to see the benefit for this attraction for future users, developers, and overall platform appeal.
I hope this becomes the F1 scene of the Metaverse and attracts the car gaming network.
Best of luck and I look forward to the updates on this as it progresses.
Today, we had our monthly meeting with Ersin Bactisa and Anna S. from Motorshow, and we reached an agreement on the final version of their Roadmap to make it public to the community. This version is slightly different from the original one presented in their proposal, but itās designed to be easier to read and reflects better due dates for each development.
We also agreed to extend the vesting contract by one more month, adding flexibility to finish the game and accommodate the main event. Additionally, we decided to schedule a Testing Tuesday session at the end of January or in early February. We will confirm the details in our next monthly check-in.
Regarding metrics, I will request the numbers of commits to track progress, as well as metrics for the events once they occur. We also discussed the process of posting GovApp updates and updating their Public roadmap with evidence on each card before each monthly check-in with GSS. I will create a Discord channel for them and post the public roadmap.
Thanks for this meeting, happy to meet you and hope we can have a great process together. Best regards, FIFI
After a thorough review of this project during the onboarding process, the Squad recommends extending the current vesting contract from 3 months to 4 months.
The Grant Support Squad, in agreement with @JamesA@George_VA , Anna and Ersin, has decided to extend the duration by one additional month. During the roadmap review meeting with the grantee, it was determined that the extra month would allow them to deliver better.
Therefore, we recommend that the DAO Committee (@HPrivakos@Tobik@rizk) modify the vesting contract with the following details:
Hi @fifitango, thank you for the update. This is not directed at you however why does this keep happening that grants are revoked for reasons that should be avoided beforehand. I can think of multiple without much thought such as wrong category. Perhaps the GSS can include as part of their duties some sort of pre grant request meetings/info sessions/feedback/guidanceā¦etcā¦
I think you are doing a fantastic job and that you are a great fit for your position. This is simply āa want to better understandā.
