I'm sure having thirteen LOD's will
Last edited:
I'm sure having thirteen LOD's will
Use http://racesimstudio.com/contact to contact RSS.I'm sure having thirteen LOD's will be great and all, but a word from David about the physics errors would be great to hear.
Use http://racesimstudio.com/contact to contact RSS.
Either way ingame the drawcalls and fps are insane,IMHO, you're not understanding the CPU reading. That % it's how much time your cpu spends on its part relative to the whole frame time (cpu stuff +gpu render). If your GPU is processing something heavier making the combined frame time longer (lower fps), but the CPU time on a frame will remain almost the same, then the CPU % on the benchmark will be lower. But it doesn't mean the CPU occupancy is lower (on the contrary, its probably taking just a bit more of frame time due to the extra graphics overhead to feed your GPU), that's just relative to the whole frame time.
Take a close look next time you close the official launcher, there are numerous names there that might be familiar.Do you know who does cars for Kunos? I'm sure there are more developers
CPU value is for the graphics thread. It shows the relationship between the time spent in the application (CPU) and the time spent to complete a frame (FRAME TIME). Values of CPU near 100% indicate a CPU-bound system graphically.
EX... if a frame took 16ms to complete and CPU is 50% it means that AC was able to prepare the frame in 8ms.. and the GPU took 16ms to render it. (GPU bound).. if CPU is 100% then it took the CPU 16ms to prepare the frame and the GPU is probably capable to go faster (CPU bound).
No relationship whatsoever with the value read in task manager.
PHY is relative to the physics thread, values above 100% indicates that the system is not able to calculate the physics in time (3ms per step) and that the game is now running slower than realtime (slowmo). Practically means there are too many AI and the CPU is not able to handle it.
Sorry should not use my phone at RD must have happen when scrolling - removed it!@MeMyselfAndI , I've noticed you've left a a disagree on my previous post. Just look at a previous Stefano post if you still have any doubt (original link). The CPU value on the benchmark result is just the average of the value described bellow (cpu time in proportion to total frame time):
Lord Kunos said:
Mudbox?Throwing down some dust here its dirty work but someone has to do it
No Quixel photoshop, I find I have 3ds max and photoshop open 12-14hrs a day minimum 7 days a week,Mudbox?
Make sure that central mirror is sorted before releaseAnyone want some bonnet clips
maybe play the mp4
https://i.gyazo.com/df59fbdfe8307f1501289dc98b9ae414.mp4
I changed it 4 times good spot, I will see whats going on now with the shadersMake sure that central mirror is sorted before release
issues with the mirrors is that until I made these 6xLOD and closer LOD the distance I never realized the mirrors only work in the main LOD_A the rest is reflections, like damaged glass, only works with 1 x LOD zoom out slightly and the glass is brand new again so was playing with it a few times the mirrors, 4-5 times trying to get them correct either I missed it again good stuffMake sure that central mirror is sorted before release