HI Albert - how did you get on with the test?
LOOOOOOOOOOOOOOOOOOLhey, i got clearly less fps, the cpu load is bigger, plus no diference from the phys mesh felt the same to me
DO NOT be afraid of too high of a poly count on the physical. I have done tests between a 40k and 600k poly mesh and found ZERO loss in FPS. The only thing I saw is it may add some time to your loading time. But be reasonable with your numbers. For example Kunos Monza is exactly 400k triangles and the Nordschleife is around 730k triangles. The key is to make sure you set the renderable setting in the editor to false. Also obviously the the physical model should be called 01ROAD and the visual can be anything else.
The reason this is important is if the physical layer is low count like the visual you get this "notchy" feel to your track. If you have a hill instead of driving smoothly over it you are essentially driving over one flat plane after another.
How do you fins nurburgring gp? is it find to drive for you?something must have gone very wrong then as kunos meshes are high resolution and work fine, and i assume bridgehampton works for you too, that probably has more tris in its mesh than scanned nordschleife.
its alright. its bumpy, and lower resolution than all the other scanned tracks, but it has at least 4 tris the spanning the width of it vs the 1 tri on this trackHow do you fins nurburgring gp? is it find to drive for you?
hey guys i messed the starting cameras, they have incorrect blur/dof
overwrite the file with this one.
https://mega.nz/#!8B1AzKTC!qIjkDIBuSpjFz1pggXd_IgMOH1z1GIsQX76AnmFTtmQ
sure https://mega.nz/#!dUlEDahR!n4zoJ5Jsu6lSGqM9zpzxLgsaTP7CPI-Us9IjF1rt_O8Hello Albert,
please, could you reupload it?
BTW it's a good rF conversion, light on CPU and AMD friendly (smooth with the 38 cars full grid, minimal dithering), thanks!
Only the AI would need some tweaks at the start because many cars crash on the pit wall...