Borgloh - the most northern hill climb track in Germany
I am happy to announce my first track for assetto corsa.
It's the location of the annual Bergrennen Osnabrück at Borgloh. The most northern hill climb in Germany.
I tried to be as precise as possible without having LIDA or laserscan technology.
Big thanks to the AC modding community all over the internet especially at assettocorsamods.net
I waited years for proper hillclimb like this, but even if my computer holding 60-70 fps, cpu dying from the start with 99% occupancy. Unplayable for me, but well done.
POWER CLASS INDEX
ks_maserati_mc12_gt1: 297.5
REPLAY QUALITY AT 16.666667 Hz
MAX SIZE MB 750.000000
ReplayManager MAX FRAMES COUNT 2757353 WHICH IS 2757.353000 MINS
Autosave replay options min frame: 500
"cpu dying from the start with 99% occupancy"
Same here unfortunately (I don't have a very powerful CPU, so it happens to me with some tracks, usually when I run a race with at least 20 cars; but I have never experienced it during a practice session without any AI cars on a track).
The track looks stunning, the comaprison video is really impressive but would be awsome if you could optimize it a bit better.
In my case it doesn't help, still crash to the desktop
My hardware is not like many other have - Mac Pro Late 2013 with 12 Gb RAM and 2 AMD FirePro D300 graphic cards 2Gb VRAM each (Win 10 Pro 64x via Bootcamp), but i have problem only with this track. Even Luca Ring with HiRes textures runing without problem
I can't load it either, PC locks up in the AC start up procedure so that I need to restart it via reset button. No log file either this way.
Big issue someone on discord pointed out is that every object has collision on. All of it.
Nochmal auf deutsch, ist vielleicht einfacher zu verstehen: Du hast alles an Mesh und Objekten so benannt das es aktive Kollisionserkennung hat, das führt dazu das es bei den anderen zu 99% CPU Warnungen kommt. Aus irgendeinem anderen Grund kann ich die Strecke überhaupt nicht laden, der PC hängt sich im AC Ladebildschirm auf, die Festplatte rödelt wir verrückt, musste zweimal mit Reset neustarten. Das ist mir bisher nur bei einer anderen Mod strecke passiert (einer 42 kilometer Race Track Builder Strecke), nirgens sonst, also muss irgendwas mächtig schief gehen.
Der Content Manager Showroom kann es sogar laden, sieht auch alles in Ordnung aus (Meshdichte etc), aber ingame geht es weiterhin nicht
good job here, but I'm going to be critical. it looks good, but there still a lot of work to do. all these 3d objects that are being used under "wall" for collision data need separate meshes, invisible meshes and lower poly to manage all collision data. just like the physical road being invisible, all collision data needs handled that way and as low poly as possible. even the house the car would never touch is titled as physical wall.
Ks grass should be used for 3d upright grass, not the flat terrain grass.
far to much 3d grass in grass kn5. at its thickest it should be about 0.5m - 0.7m between grass pieces. half that volume if you can.
road layout is quite good, however the visual version can be even lower polygon if you want to save more.
many people having issues with the track, including me, it crashes my AC. but I have to say its lovely looking at first glances, and then its too much for some peoples pc`s.
The track doesn't load for me as well, but I could catch it before it hung my PC. I was trying to load a practice session with the Praga R1. In the task manager the acs.exe was sitting using ~12GB RAM (and growing) if I read that correctly.
Hi again,
I hope this fix will get us any further.
I have done 2 major things:
I renamed many objects (tire walls, etc..) so at the moment you can't collide with them anymore
I disabled the reflector posts along the track which are all movable objects.
If this help and the track loads correct, can you please test what will happen, if you uncomment MODEL_4 in models_layout_a.ini. This is for the reflector posts.
thanks!
In the earlier version (which worked fine for me on all points), when I hit a reflector post, it comes loose and flies in a very believeable way. So in the new version that does not happen any more ? (have not replaced it yet).
In the new version (if you leave the included ini file untouched) all the reflector post are not loaded any more. So if this solves the problems I will see how to implement them again.
In the new version (if you leave the included ini file untouched) all the reflector post are not loaded any more. So if this solves the problems I will see how to implement them again.
