Did a quick test too. Simple scene. Two cubes close to the camera, and two cubes around 200m away.
Left side using C4D bitmaps and right side Corona bitmaps.
The only thing that changes is the focal length of the camera. With a focal length of 35, the texture is blurry. With a focal length of 235, both have the same sharpness.
Hi
Interesting. So also blurry with Corona Bitmap. You are not using any DOF in the camera settings, right ?
So this could mean it is somehow connected with the focal length in general ?
A
What do you mean with “also blurry with Corona Bitmap”? Only Corona Bitmap is blurry, native C4D bitmap is sharp. (Keep in mind, there is a bit jpg compression visible)
And I think this issue is only with Corona bitmaps, I haven’t seen this with C4D bitmaps…
/// EDIT
I made a better scene. Left side is native C4D bitmap. Right side is Corona bitmap. Again, please keep in mind that there is jpg compression, and my texture is not perfectly sharp.
Focal length is 15, 36, and 80mm.
Are these IR or viewport previews or are they final renders in the VFB?
These are final renders in VFB. But it’s the same in IR. (didn’t check viewport rendering)
Thank you for the tests. These are great examples !
It would be interesting if there are changes in render-times as well between rendering all with Native-Bitmaps, Corona-Bitmaps or Corona-Bitmaps with -100% Blur-Scale.
Best
A
Not sure why there is a long discussion about scene scale, cm/ mm, -100 blur-scale.. etc
The corona team knows about this problem for a long time and didn’t forget about it!
https://forum.corona-renderer.com/ Corona bitmap render blurry c4d native bitmap not #msg176403
It’s one of many corona bitmap issues and the only solution for now: Use native c4d bitmap.
-100 blur-scale is brutal and NOT the solution!
I wouldn’t normally care, but the fact that most cosmos assets use corona bitmap makes cosmos “unusable”.
Hello
Thank you for making us aware !
You are completely right. Totally agree with you. This obviously remains the exact same problem since about three years.
I do care a lot, as the Bitmap-topic seems connected with the recent rendertime-issue using Apple M-systems.
Best
A
i just tested and if the texture is far away the bitmap is really extremely unusable, like super strong dof on the surface!
this is really bad i must say. i hope 11 brings a fix for that(i read some in max forum in 11 daily that could be related to that)
it not happens if objects are near, but if the scene scale is big the mip mapping goes completely wrong in corona bitmap.
if the corona team wants an extreme example i can forward you one(a wood floor texture, in corona bitmap you see not even the lines anymore)
manually editing all bitmaps to blur scale -100% isnt a workflow thats possible in complex scenes. the corona team should at least set the default to what blurscale -100% does. nobody ever needs such blurry textures, in so scene case i can imagine that to be ok(even if this means a speed loss)
to me it seems like something is wrong with scale by a factor of 100x or even 1000% in regard of blur and blur offset.
-100% is what i consider 0%, the blur offset value is unusable as even at 1 or 0.1% it completely blurs the surface to one solid color, starting at 0.001 it does what is expected(adding a minimal blur in far away party).
so i think maybe the corona bitmap takes the c4d units by a wrong factor multiplied? or it doesnt take the c4d document settings into account(scene scale from small to huge etc)
after testing i found the setting blur -100% AND the blur offset of 0.002% does give a nice result, similar to c4d bitmap but actually even a bit better for me (not getting artifacts as the bluroffset 0). this even more let me thing corona bitmap interprets the scene scale wrong
Just a suggestion, as the problem has already been 3 years, and if it is not possible to resolve It soon… Maybe the Corona team could add in the new Lister a tab for the Corona bitmaps so they all can be changed in one go.
Not a perfect solution but would be great already as a walkaround soon.
Best
L.
We have addressed the issue 
This has been resolved in the last daily build. If you have a moment to test it and let us know, that would be great!
Hello
As far as I can tell it works with the latest build. Great job ! Thx.
Asimo
That’s great, thanks for testing and letting us know
