I have replicated your test on my PC and I also do see a increased lag in the polygon selection compared to R20.
Navigation itself is smooth in both versions (over 100 fps) but the selection tools look indeed a bit more sluggish when compared side by side with the previous version. I don’t think it’s placebo, but I’d have to record the screen to measure the delay.
And I’m not in 4K on either versions.
to contribute to the actual issue: i get this, too, but really only with high poly counts… well, probably also with lower poly counts, but it’s not really noticeable under 1 million polys… around 2.5 million it starts to get annoying, where r20 takes around 1 second to select connected r21 takes 2, at 5 million it’s 2 seconds r20 compared to 4 in r21. tested on a 2016 mbp…
Beta testers go out of their way to test software that is not ready for release. Filing bug reports, working and talking with developers to iron out workflows and make sure everything works. They will never, and should never, use the beta on a real world project until its actually released. So for a beta tester to make a video showing what they have done is awesome. They most likely testing this over and over and over for a year until it all worked perfectly, then they recorded this same workflow again so everyone else can see how its done. No beta tester is making any hard core dosh from these videos. Instead it helps them be in a position to help improve the software, voice all your concerns that everyone mentions here on the forums, and make the software better. Beta testers don’t get paid. They do it in the free time that they have simply to help make the software better. You should be thanking them for their time, not insinuating they are taking advantage of anyone for simply making a video, and sharing their knowledge, on YouTube. These people all have families, kids and work a full time job and usually test C4D in the few precious minutes in the day they have spare. Respect people.
Calm down Kent. I think most of us understand the transactional nature of being a beta tester.
Never having to pay for C4D, having advanced notice of features to make training courses and plugins is payment enough for a few evenings tinkering with beta software.
I’ve been beta testing Redshit for the last 2 years but the difference is I’ve been paying for that privilege, I wish I’d been given it free.
Just me giving my respect to the beta testers. Since they helped me a lot. And generally all of the ones I know are also paying customers. I just don’t like wild accusations being thrown around where people reading here might not know how it works. If you’re a beta tester and you’re not contributing to the actual benefit of the program, you get booted from the beta, then you have no software. But as I mentioned, they usually all own C4D and are paying customers, experts in their fields.
Many of the people i invited to become betatesters i recruited from here and other forums because they were helpful and investigative. I am not surprised that some choose to extend on this by sharing what they learned during beta, be it on youtube, on forums or when presenting for Maxon.
We love our betatesters. Given the stuff they have to cope with, especially early in beta or if we don’t do what they want, i sometimes wonder why they don’t run away screaming 
One of the downsides of being a Maxon beta tester is that sometimes they put a camera on you and it’s stored on youtube in perpetuity.
Unfortunately not.
I tried everything at my end.
I unplugged my 4K monitor and switched the other 2k monitor from an rtx 2060 to a 2080Ti but no luck.
I also installed R21 on a 2012 iMac which only has a 2k resolution and have the same problem there.
This has to be a bug.
Still rocken R20 and wont be moving until this is fixed.
so I was testing the new pro render feature
I have to say i was impress… the performance with my shitti video card was outstanding… on AO or difuse and hard surface modeling wireframe view…
really really nice… but then… cinema goes an pull something like this… you know the NODE system?? the material node system everyone is so in love with. even my self… well… yeah… is not supported by the pro render feature…
or I am missing a click somewhere that let me use node material on the prerender set up? any ideas guys?
You have to switch the node space to pro render before you create the new material. It’s next to the layout dropdown menu in the main interface.
thanks found it. another way is to turn on the prorender feature and create a node material…
but if you have a scene already created there is no way to turn on the pro render feature all the nodes shaders show error on the preview window.
@Cian: The selection being slower with millions of polys is confirmed, however the viewport being slower when navigating isn’t. We’re talking up to an extra second in this modeling operation compared to R20 - which is noticable (but not “unworkable” in my book).
Best regards,
Wilfried
Hi Wilfried.
Thanks for your reply.
It’s only the selection I have a problem with. I know the title of this tread says Viewport but that’s because I find it’s a viewport issue.
I have no problem with navigation.
The problem I have with the selection speed is unworkable for me as I work with large files on a daily basis.
I want to to move to R21 but I can’t until this is resolved.
Cian.
