Alright word. If you try and play the demo on the new 0.15 update, you will get something that looks like this. I believe there is something wrong with the "isRenderEnabled" function because when I press the checkbox nothing happens. @Nadeox1 Could you look at this?
Texture format has changed, new something something (BC7?) format supported (see the notes on changelog), but older texture format support is more deprecated. You likely have texture formats that won't work anymore. There's programs that can batch-change them or you can change them 1 by 1. I have had this issue in the past, and right now I've got two murdered maps (Nevada Interstate & Tail of The Dragon/Deal's Gap are both TOAST and CTD the game), so my plate is full. See the log, likely issues with can't use textures. EDIT: Oddly enough it looks like it's trying to render the invisible ever-tall collision walls preventing you from leaving the course in the normal game.
I did this but now my object doesn't have collision. I've been using collision outside of the actual shape itself. Yeah basically, except it's just one whole model instead of a ton of separate ones
The optimization does not support that 'RenderDisable' thing atm. If you don't need those part to show up, why you don't remove them from the model? Or assign them to a completely invisible material?
as a border to prevent players going to unfinished area though normal car means. Usually you have to teleport by hitting f7 while in free cam to get pass the wall and back --- Post updated --- as for transparent walls, aesthetic and practical reasons, better than a bunch of trees on an unfinished mountain area or easy to pass construction work. It also doesn't ruin the map by being transparent.
as for transparent walls, astethic reasons, better than a bunch of trees on an unfinished mountain area or easy to pass co the other purpose is easy, to avoid your car falling into space when you reach the edge of a map
