RMR1
@Simberia
And THAT was a hard case...There’s also been a claim on this or the AC forum that uninstalling bitdefender made cars in AC drive better...
And THAT was a hard case...There’s also been a claim on this or the AC forum that uninstalling bitdefender made cars in AC drive better...
Nice, you've noticed. I hope I kept maximum error in xy below 20 cm (possible by using insane orthophotos (pixel size = 10cm) and LiDAR data(Accuracy XY = 15cm) ). Z accuracy may be some cm. Its hard to say after noise suppression. Here you can compare the 2016 stage, if you want (it was the same in 2015):
BTW: I have no clue, why some systems need that much RAM, yet. I thought it may correlate with old CPUs, but sure not in your case. Did you install the 2017 c++ redist packs?
After watching this video I was impressed at how accurate your track is, wow !
:'( Maybe you are right about these moveable objects... I am sorry, it doesn't work out for everybody. For now just use my 'fix' (find it in first post). But i've not given up already. How many moveable objects we should try in next test? In last test version it was about 300 cuboids (and i already know it was risky)Yeah just fix the track please. It has potencial and is accurate enough.
Physic objects are not AC friends. Unfortunately this ain't wreckfest nor Grid.
Past comments from the devs states no more than 15 movable objects per track is the recommended number. The game was simply not meant for knocking down street signs.:'( Maybe you are right about these moveable objects... I am sorry, it doesn't work out for everybody. For now just use my 'fix' (find it in first post). But i've not given up already. How many moveable objects we should try in next test? In last test version it was about 300 cuboids (and i already know it was risky)
even your fix doesn't work, only Actakkut's fix work, though the track eats up to 4gb ram (don't know if it's fine or too much, but other mountain tracks eat less than 2gb):'( Maybe you are right about these moveable objects... I am sorry, it doesn't work out for everybody. For now just use my 'fix' (find it in first post). But i've not given up already. How many moveable objects we should try in next test? In last test version it was about 300 cuboids (and i already know it was risky)
Wait! What? This doesn't work for you? http://www.mediafire.com/file/z6ktkulsyyc5a8d/landsbergWP1_09_prefix.7z/fileeven your fix doesn't work, only Actakkut's fix work, though the track eats up to 4gb ram (don't know if it's fine or too much, but other mountain tracks eat less than 2gb)
but that would be optimization I guess
oO You mean it may be caused by replay settings? All movable objects are displaced a little in the replays also. Something is going on there...Oh, one other thing to keep in mind with movable is they're storing iirc 12 bytes per frame to the replay file (position + rotation), so 300 movables > 100kB/sec on high quality replays. You might try disabling replay storage entirely and see what that gets you.
I am the modder. I want to know it! Why you can't understand this? I thought you are here to help. So do it!What’s going on is that you are way above the recommended number listed above, turning off replay won’t fix anything.
I think people ARE trying to help.I am the modder. I want to know it! Why you can't understand this? I thought you are here to help. So do it!
Kunos nutzt nicht mehr als zwei Dutzend (oder 15 wie die anderen schreiben) bewegliche Objekte pro Strecke, dementsprechend ist die Engine auch nicht für mehr ausgelegt. So sieht es aus. Mach die Leitpfosten unbeweglich und lass nur ausgewählte Objekte beweglich. Andernfalls wird es nie auf jedem Rechner laufen.I am the modder. I want to know it! Why you can't understand this? I thought you are here to help. So do it!
That's cause replays store movables at relatively low accuracy. I believe 16 bit floats instead of 32 bit floats for their position.oO You mean it may be caused by replay settings? All movable objects are displaced a little in the replays also. Something is going on there...