Hello! Can someone help me with the templates for this car? whatever I do, all the cars turn white. am i wrong converting .psd to .dds? Thanks a lot! has small adjustments in the handling and I changed the sound!
Then there’s no reason for the mod to not work with unpacked data... try removing the ACD?
Update: Baku 2019 1.0 by PatrikPAT
is it normal that exporting the FBX from blender is twice as large as the version from RTB while not adding anything but only modifying some mesh?
the problem: importing the modified FBX with blender on KSeditor gives me the result in the picture:
Depends on what "modifying some mesh" means, a single subdivide will double mesh size instantly.
Suspect the RTB exported file is a customised export that does not include anything absolutely neccesary for kseditor (example no backface as kseditor cannot use them etc) , because the fbx it exports does not load properly for me in Rhino/Maya or 3dsimed, in the case of rhino it actually tells me it is "fixing" it, maya/rhino both export a file roughly double the size as well. if you open with hex editor yuo will also see the textures etc directy references INSIDE the larger size fbx, and the ini will reference a LOT more objects, suspect instancing is not being respected, however all a mute point, no matter what size fbx you have the outcome KN5 is alwasy the same size from any source
below is 3dsimed trying to open the pure rtb export which includes an AC ini file.
View attachment 981082
and here is after a simple import/export through blender.
View attachment 981083
if you "explode" geometry to move its points you can induce flipped normals, always double check before you export that you fixed normals or use the "make doublesided" function in 3dsimed.
3dsimed is the very last tool I use and only if I really have to, it can induce a lot of issues with it import/export and handling of textures, (I actually only use it now for porting tracks from other games), generally I only use to use RTB for sattelite imagery and height data until I found out I can grab that in a better fashion with BlenderGIS anyhow as a bit of poking with the scripts allows you to grab gistorical sattelite imagery from google earth as well, and you dont need to jump through all the hoops of signing up for googleapi etc. (and it supports real ACS data as well, the google height data is very incorrect and compared to DEM files I have found it to be out by as much as 20m in some cases.
pratically all the trees have 1 face...
the google height data is very incorrect and compared to DEM files I have found it to be out by as much as 20m in some cases.
Some Major Updates to my take on an Apricot Hill + Mid-Field combo. I hope to get some AI sorted then you can all have a go on the newest version!
View attachment 981101 View attachment 981102 View attachment 981103 View attachment 981104 View attachment 981105 View attachment 981106 View attachment 981107 View attachment 981108 View attachment 981109 View attachment 981110 View attachment 981111 View attachment 981112 View attachment 981113 View attachment 981114 View attachment 981115 View attachment 981116
Does anyone have a better optimised version of Montlhery or an update to the Racedepartment version that they can share?
This one seems to be very CPU intensive
I never knew Mid Field was always connected to Apricot Hill
That's looking really good. Normally I don't like when tracks have been merged together, but I think this combo will be great.
I may have missed it, but are there going to be additional layouts, and will there be versions where you just stay on one track? I think I'd enjoy the quality of your tracks if I'm on one or the other, and the combined version as well.
yeah, their Toyota TS050 is pretty useless for me, as on the controller I'm not shifting manually and the upshift revs is 7650 but the limiter is at 7100, and I can change nothing...it's by ACSFK the model is encrypted just to warn you (and you can download on their discord)
RTB and if you use the GIS basic google data then yes, especially over tile seams in the data, google height data is only meant to be an indication and is between 30-100m sample points often, and I think trees also screw it up, but BlenderGIS allows you to use real DEM data instead, If you watch the Z numbers in here and reference the overlay of 2m dem versus RTB, about 10m in some place, but it goes wrong up and down. RTB is "ok" for make believe tracks, but if you trying to grab real nuance, then you need to go at DEM "bare earth" 2m or better 0.5m which is available for a few locations in Australia as well. Still not true laser scan but 1m error is heaps better than a 10-30m error.
Due to the seasons adjustments function, the hill in the background turns white, but the trees and grass stays green. Looks very odd (not a big deal to me, just want to mention it). Furthermore, why didn´t you include some realistic billboards instead of the Kunos ones? At least I recommend to use these ones from our fellow PeperoniAC: