BeamNG: Personal Micro Blog(s) - Feburary 2015

If you mean the negative x, I am almost positive they are directly under the positive so they can save space and automatically mirror it to the other side. Don't quote me on that

 

The official vehicles map both sides of the car to one texture. It saves space, but on the downside it means you cannot have mirrored decals (i.e writing) on the side of the car. It isn't really a problem at all, as you could just use alpha map decals to overcome this problem.

Very nice! i like how you can fit the whole car's mapping into one image, and make very good use of the space available.

 

Both sides of the car overlap. Like on the rest of the default vehicles. (didn't even see post above me when I hit reply, oops!)

 

umm headlights?
also when do you think we will start seeing adaptive textures for stuff like dirt and scratches?

 

The headlights and glass also have their own maps.

This could really turn into a great guide if you keep posting the progress step by step I really dig it!

 

Tdev, would it be possible to get a brief description of how and why the cache system is in place? Thanks!

 

What's the FPS of the 200BX at the moment? Would the current answer be representative of the final product?

 

+1, also how would you go around doing this? With two texture layers or what?

 

Something like that. There would be two seperate uv textures. One would be the base map (vehicle color) and the other would be the outer layer map (dirt texture) which would slowly fade in whe the vehicle goes off road.
To acheive this though, beamng devs need to assign areas to where the dirt layer would fade in (eg. Grass area) they would then need to set a timer to which the vehicles outer map is fading in and save that specific time for when the vehicle goes back on road. This all takes up valuble memory space and I can imagine we wont see thos for a while as there are many other priorities for the devs to work on.

 

I'm not tdev but I can explain it. Since DAE models are in an XML-like format, they take a long time to load versus a binary format. The cache saves a DTS (Dynamix Three Space) model into your documents, which is a binary copy of the DAE file. It is much smaller, and faster to load.

 

XML theoretically aids support for dae across multiple different softwares. In practise... Not always the case.
Binary files can have issues with endianess etc when moved between seperwte operating systems and architectures. And other issues too.

Plus for a while, XML was (is?) The in thing to be used in computing

Impossible to give an fps value as it depends on machine. Appears it may result in similar to covet performance (although I can only speculate based on the size of the vehicle compared against others and the number of doors etc

 

i actually asked gabe about performance earlier in the thread:

 

In the earlier versions i encountered that the game crashed when i loaded too many textures in the editor, but then again, i run linux and use wine, which takes a fair bit of the CPU for itself.
Except for that, when i loaded a few hundred textures at once, it did not crash (that is good). +I only have 3gb ram

 

Where did gabester say that especially YOUR mods crash the game? He only said that the default game content (namely content by gabester himself and LJFHutch) crash the game.

And why should they want to delete fine modding content from the forums? If it won't work people won't use it anyways. And for those it works they'll be happy.

 

I am not a professional, but is that a limitation of torque or something? The way I understood it anything that would be put in the VRAM past 2GB would just go into system RAM, not crash the game. I also don't think I've seen the game use over 2GB at 1080p with AA maxed out. Also, wouldn't that make it nearly unplayable on 1GB cards like the 650ti?