Hi, I tried the current unstable build and on skippy the wheels are pretty strange: tire and rim can be separated with the convergence setting of the nVidia 3d function settings. My system: - projector benq set up as acer h5360 dlp 120Hz due to requirements of 3d vision - 3dvision 2 set - trackir-5 - gtx 780 - amd 8350 @ 4.4 Ghz - 8GB RAM - Windows 7 64 Bit If I set the convergence so that it fits the view best, the rims and tyres on AI skippies are separated. I installed the current unstable build 483 simply over the old stable 382 one. Regards Michael
I can confirm this issue also with 3DTV Play. Tyres are always at screen depth (as well as being completely disconnected) Its the same with all open wheelers. Actually....its all tyres on all cars. Tyres are now at screen depth only and as a result look disconnected from hubs. It effects player car and AI cars and transparent trainer, ie all tyres. This build isn't really playable in 3DVision. I also installed over the top of a duplicate 382 build.
Sad to hear that cause I played in 3D Vision also - hopefully that won`t carried over to the stable build.
Yeah, 494 is likely the same as 493 in every regard. Hopefully the stuff they held for this build will go well in internal testing and the next unstable -> stable comes fairly soon, and they can fix this as well.
So this 493 unstable is now becoming 494 for release and thats it? Its not playable for me so what is the point of unstable releases if problems aren't going to be fixed before stable release anyway or have I misinterpreted something?
Seems as good a place as any to ask this... is the unstable phase working well for this sort of thing? I know if there's some serious issues that haven't been found an unstable gives a chance to find that out without breaking the game while it's fixed, but assuming this tyre depth thing is a quite simple bug/oversight you'd think it could be fixed as a 495, quickly checked basically to make sure the game still runs, and then we get 496 (so what we had in 493, with a very quick bugfix or two) I'm guessing development doesn't stop when an unstable is released, and the issue might be having to fix the 493 code as well as putting the same fix into the ongoing dev version? Is there a way to better manage this sort of thing? Depth-less tyres isn't a showstopper, but it's going to suck for 3d users until the next build comes along...
I guess I was comparing it to a consistent rF2 crash bug, or something similar You can still play the game... it'll just be really irritating in 3D.
Which makes playing it a pointless exercise. Will have to stick with 382 I guess. I thought the whole point of unstable releases was to get general feedback for a little while, not just a matter of hours. Still, what do I know, only been a software engineer for 30+ years.