Hello!
I cant get Corona Bitmap to increase in pixel quality in viewport, when changing the px value in native “Configure ViewPorts (texture map)”.
It works fine with 3ds max bitmap.
I sometimes use this for drawings and quick sketches.
BR/
Hello!
I cant get Corona Bitmap to increase in pixel quality in viewport, when changing the px value in native “Configure ViewPorts (texture map)”.
It works fine with 3ds max bitmap.
I sometimes use this for drawings and quick sketches.
BR/
Hi,
Which version of Corona and Max are you using?
This seems to be working fine for me in Max 2020 with the latest Corona daily build (2019-08-07)
Thanks,
Rowan
Yep same, max 2018.
So frustrating, something so basic.
Super easy to reproduce on my part, regardless of what viewport resolution is set (even 8k or 16k!) following happens on my 3dsMax 2016, Corona 5 installation:
Interestingly, if NativeBitmap is put under CoronaColorCorrect (or maybe other nodes too?) same happens, viewport shading is blurry.
Here is quick screenshot, I didn’t do anything special, same map loaded into their respective bitmap loaders and the results show it all.
Hi Juraj,
I still can’t reproduce this, can you send me a screenshot of your viewport configuration → display performance tab please?
Thanks,
Rowan
Why would it apply differently between Native and Corona Bitmap loaders?
Since my GPU Driver settings are stock I would place the fault on Corona.
It’s interesting though, I’ll go test it as well.
I tried it on max 2016 with default Nitrous direct3d 11 driver, texture map resolution in display performance settings is set to 4096 - the difference between bitmap and Corona bitmap can be seen, but it’s very marginal, visible only when you zoom in close to 1:1 magnification. Interestingly enough, difference almost completely dissapears when i set interpolation to nearest neighbour, but then texture shifts very slightly in the viewport. Tested on JPG, PNG, TIFF, all 4096x4096 - no difference between formats.
Edit: GPU Nvidia 1060, drivers heavily outdated.
Same settings as Marus has in GeForce driver.
Do you guys have 4K or other HighDPi monitor, do you have scaling in Windows on?
This is not scene dependent, I opened empty scene. And it happens to native bitmap as well if I put it under CoronaCC node, but CoronaMix for example is ok.
This will be Corona related, not my windows setup. Max Native works well.
Hi,
I have a 4k monitor with Windows scaling set to 150%.. Do you have a similar setup?
Rowan
can’t contribute anything other then we have been having the same issue since forever and working around it by using max bitmap also.
Max 2016.
I am afraid we will need a scene file from someone who is experiencing this. The uploader is in my signature. Let me know once the upload is done and what is the file name.
Also attaching my “rig” that can be used to test this.
(Internal ID=421751111)
So after meddling a little bit too, refreshing the coronabitmap and re-enabling the Show Shaded Material fixed it for me, also worth noting after setting view-port texture map resolution to 8k, I’ve set view-port settings to “Show Realistic Materials with Maps”, except the CCC one the rest seem fine.
1920x1080 reso, 100% Windows Scaling, Nvidia 2060 Super latest drivers.
Hi. Having the same problem with 3ds Max 2016, as you can see in the attached screenshot.
No matter how much I meddle, reset, reload, restart etc.etc., it doesn’t get better.
Please go to your view-port settings, change your baked procedural maps resolution to be exactly the same as your texture/environment, re-apply the corona bitmap and please share your results. For 3ds max 2020 it’s how it fixes the issue for me. (see picture)
Also please consider enabling realistic maps with textures on your view-port rollout. (see pic no2)
Hi @Corona_GK, thanks for your input.
As I said before, I’ve already enabled maps for both Realistic and Shaded, so trying that again didn’t change anything. BUT changing the resolution for Baked Procedural Maps, had never crossed my mind, since this isn’t procedural maps. However it actually did fix the problem - but only after saving the max-file, and then reopen it.
So for everyone with this problem: There’s no immediate change in the viewports when changing the procedural resolution. You need to reload either the bitmaps or the max-file.
Thanks ![]()