Great news ...
Thanks Michael.
eric

Phantastic.

Can we hear what will be the innovations in the next beta.

Hi Rudl, well there are a lot of various bug fixes, it will take me a while to collect up all the information so I'll do that after it's ready.

But hopefully it will be a turning point where I'll be able to focus mostly on brand new features after this release.

- Michael

Hello Michael!

When you can start to work on "new things", please add this little but very very useful feature :

The chance to capture Moi's viewport, like already Moi does, but with the addition of a flag or a scripting variable, to get a transparent background.
This feature would be perfect for everyone like me is often engaged in creation of 2D/3D image composition in print quality resolution.

Thanks a lot!

Hi Marco,

re:
> The chance to capture Moi's viewport, like already Moi does, but with the addition of a
> flag or a scripting variable, to get a transparent background.

I actually looked into that when you mentioned a month or so ago, but unfortunately I found that it is not a simple matter to incorporate that into MoI's current viewport display engine. Curve drawing is the part that makes it difficult - the display engine is expecting to blend the curves against a colored background and it's problematic for curves to write alpha values.

It's more straightforward with something that draws shaded polygons and not curves, and you can get that type of image out of MoI currently by exporting to .ai format, if you turn on the Shaded background image option a companion PNG file will be generated along with the .ai file.

- Michael

@You : "...It's more straightforward with something that draws shaded polygons and not curves, and you can get that type of image out of MoI currently by exporting to .ai format, if you turn on the Shaded background image option a companion PNG file will be generated along with the .ai file."

Ok Michael. I forgot this chance :)

I will try and let you know if it's good for what I want to do (image composition in very high resolution).

Thanks.

Hi Michael!

I've tested and exported in AI in order to get hires images and the procedure is almost OK! :) Thanks for reminder.

But...I have only a final problem. What can we do to solve it ?

The problem is I need very very high resolution images (up to 16Kx16K) because actually Moi doesn't apply any kind of antialiasing to the generated images,
and I have to use the "trick" to have a very big image that I can scale down to about 4K or 2K in order to "blur" its edges and make, in this way, a sort of "manual antialiasing".

The problem is that in Moi, even if I specify a canvas resolution of 110 megapixel, the generated image file can reach a max resolution of 11039 x 6795, that is absolutely not 110 megapixel :)

You can see this behavior in these images :

I stay tuned. Thanks!





Marco (mkdm)

And using this plugin ? You can put any resolution (following your hard memory avaible)


script: /* Print screen to the Clipboard */ var prev_background = moi.view.viewportBackgroundColor; moi.view.viewportBackgroundColor = 0x000000; moi.view.lineWidth = 4; moi.grid.display = false; moi.grid.showXYAxes = false; moi.ui.getActiveViewport().renderToClipboard( 2560, 2560 ); moi.view.lineWidth = 1; moi.grid.display = true; moi.grid.showXYAxes = true; moi.view.viewportBackgroundColor = prev_background;

Ok.

But...I'm sorry Pilou...I already know these things and they works very well but I was talking about the chance of having
the "viewport" captures not only in super hires but also with transparent background, and that feature is available only
in export to AI, but it seem that that command can't generate images grater than 110396 x 6795 and I need more.

Ciao!

Hi Marco,

re: 11039 x 6795 not adding up to 110 megapixels - I'll take a look at the calculation it's probably related to the aspect ratio of the image.

But if you need such a high resolution you'll probably need to use a rendering program to get it rather than using this feature in MoI.

- Michael

@You : "But if you need such a high resolution you'll probably need to use a rendering program to get it rather than using this feature in MoI."

No Michael.
I need exactly Moi for this, because I don't need to have a photorealistic rendering nor any other kind of rendering,
because any kind of "rendering" in so high resolution takes ages, also with very fast computer.

No, I need exactly what I usually do with Moi or Rocket 3F/NVIL.
That is, produce super fast viewport capture at very high resolution.
I'm currently using this kind of graphic to produce a kind of "digital art" not so obvious or common.
Or, at least, this is my actual aim.

I need those kind of hires images to create image composition of 2D/3D/digital painting/image processing.

If you let me use Moi to generate viewport capture up to 16k x 16k or at least 12k x 12k I'm happy :)


Please, let me know.

Thanks for your support.

Hi Marco, I'm sorry but no the focus of MoI is not currently on generating super high resolution bitmap images. That's the job that a rendering program is focused on.

MoI is able to generate images for you with a few different methods as you know, but it's for quick and simple jobs. Your need to do a super high resolution 16k x 16k image is not a simple job, so it's not something you should expect to get from MoI's current image generating toolset. At some point I do expect to have some more rendering tools built in though.

- Michael

Ok Michael. No problem :)

But...just a final question about this matter before concluding this conversation.

Given that Moi is already capable with the AI export to generate the bitmap representation of the viewport, up to 11039x6795, what is the difficulty to create the same image up to 16k x 16k or at least 12k x 12k ?

I'm not asking you to build a new algorithm or use a new library but only to tune it up to increase the resolution.
(Anyway, I don't know how this request can impact the current Moi's code)

Thanks again for your kind support :)

Ciao.

Marco (mkdm)

Hi Marco, I did some testing here and it might be a limit in Windows - do you see any difference if you set a large paging file for the OS ?

- Michael

Hi Marco, also check if you have set a memory limit in moi.ini under:

[Settings]
MaxProcessMemoryUseGB=


I just tested here and was able to make a 20322 x 12303 image. It will consume quite a large amount of memory though.

- Michael

Hi Michael and thank you very much for your kind support! Much appreciated as usual.

20322 x 12303 THIS WOULD BE PERFECT!!!!

Well...

@You : "...Hi Marco, I did some testing here and it might be a limit in Windows - do you see any difference if you set a large paging file for the OS ?..."

I have to check and I will let you know (tomorrow I hope)

@You : "Hi Marco, also check if you have set a memory limit in moi.ini under:
[Settings]
MaxProcessMemoryUseGB=
I just tested here and was able to make a 20322 x 12303 image. It will consume quite a large amount of memory though."

Ok. I've checked my .ini file and I have these settings, so I assume that is OK.
MaxProcessMemoryUseGB=

So, if I understood well, the thing that I have to try is only to set a large paging file.

I have actually 32 Gb ram on Windows 10 Pro. How I can set up the page file to make a good test ?
What's your paging file size ?
Also...changing the file paging size will affect the overall performance of my PC ?

I will read your response and I will try all these things tomorrow :)

Thank you again!!


P.S. You are doing these test with V3 or V4. I have used always V3.

Marco (mkdm)

P.S. Are you doing these test with V3 or V4 ? I have used always V3.

Hi Marco, you have to use V4, images of these sizes will very easily exceed the 32-bit memory limit that V3 has.

Once you use V4 you should find that you can increase the "Canvas megapixel resolution" by quite a bit. I got 20322 x 12303 by using 250 for that value and that was pretty much the limit on my 16GB system and there was some swapping.

You probably won't need to mess with your paging file with 32GB memory, and yes MaxProcessMemoryUseGB= (just blank) is correct. That's the default and means no limit set for memory use.

Don't increase the Canvas megapixel resolution by too much in one step because if you set it high enough to consume all your system memory your system can become pretty sluggish. Increase it in steps of say 50 at a time until you reach the size you want.

But definitely you'll need V4 for doing this. V3 actually has an internal limit of 75.0 for the Canvas resolution.

- Michael

Do the Mac retina displays, or Windows 7 with 4K displays permit higher resolution "screensaves"? Or is it not screensaves that are desired in higher resolution?

- Brian

https://graphicdesign.stackexchange.com/questions/27946/is-it-possible-to-take-high-quality-screen-captures

https://graphicdesign.stackexchange.com/questions/13292/how-can-i-preserve-vector-file-size-and-quality-when-exporting-to-png-format-wit

Hi Brian, the max resolution of viewport.renderToClipboard() or viewport.render() will be determined by the video card, it's an image generated by the GPU it doesn't really have anything to do with the monitor resolution.

The image generated by saving to .ai format is generated by the CPU, not the GPU so it's only limited by available system RAM (in v4 since it's 64-bit, v3 being 32-bit will have a lower limit).

- Michael