So it would have to be a back to back, tiny race style test to have PD3 first and then PD4 second, could be an interesting test if you want to go through the trouble of setting it up. I’m not sure it is needed, I think we will be able to tell the difference.
On the same course, same length, to make everything except PD equal.
2 x races around Crit City seems a good race test.
It would be very advantages if Zwift could leverage the multicore possibilities of CPU’s.
I can only see 1 or sometimes 2 logical processors busy with zwifting.
The other 14 are hanging around and begging me for work.
Some calculations can’t be parallelized (done at the same time on many cores). Of course, some performance gains can be made with low-level API when it comes to graphics etc., but you can’t do simultaneously calculations that are chronologically dependent on each other. The performance gain talked here would be advantageous for low end machines because more computing would be done server side.
A post was merged into an existing topic: Pack Dynamics Test Events (December 2022)
2 votes have been moved.
Thanks for the feedback!
Overall it was a good test, but the changes are big. People will need time to get used to it and weaker riders in a bunch won’t like it. I don’t think PD4 would be received well in group rides.
Please don’t assume this is a done deal and won’t be changed. It’s still a work in progress
Let’s move the feedback to this thread here (https://forums.zwift.com/t/pack-dynamics-test-events-december-2022) please. This one is already too big.