Yes, it gives exactly the same output. I would be happy to send you my python script but I'm unfortunatly not allowed to do this for confidentiality reasons.
I will see if I can reproduce the same behaviour with another dataset/script that I could share. Thanks a lot ! Lionel ________________________________________ De : Cory Quammen <cory.quam...@kitware.com> Envoyé : mardi 8 août 2017 20:44 À : Wilhelm Lionel Cc : Paraview@paraview.org Objet : Re: [Paraview] Screenshot resolution and 2D actors size > Regarding the pvbatch issue, do you have any hint? That is odd. I'm not sure what is going on exactly. Have you tried running your script with pvpython? Thanks, Cory > Kindly, > > Lionel > ________________________________________ > De : Cory Quammen [cory.quam...@kitware.com] > Envoyé : mardi 8 août 2017 16:44 > À : Wilhelm Lionel > Cc : paraview@paraview.org > Objet : Re: [Paraview] Screenshot resolution and 2D actors size > > Hi Lionel, > > This is a bug [1] that will be fixed in ParaView 5.4.1, coming out in > the next week or so. In fact, it is fixed in the latest 5.4.1 release > candidate, which you can get from www.paraview.org/download. > > HTH, > Cory > > [1] https://gitlab.kitware.com/paraview/paraview/issues/17603 > > On Tue, Aug 8, 2017 at 10:29 AM, Wilhelm Lionel <lionel.wilh...@epfl.ch> > wrote: >> Dear Paraview community, >> >> >> I created a full layout with 5 different views and would like to save a >> screenshot. The paraview GUI looks exactly like the image I want to save so >> I just use File -> Save Screenshot and keep the default resolution. The >> settings and the generated image are attached as "settings_test1" and >> "test1" (everything works fine). >> >> >> If I change the resolution of one pixel in one of the dimensions (width for >> example), the resulting image shows huge scalar bars. Here are also attached >> the screenshot settings and the resulting image ( as "settings_test2" and >> "test2" ). I have to mention that the small numbers on the views are in fact >> 3D Text objects. >> >> >> The entire visualization is produced by a Python script that I launch in the >> following way : Tools -> Python Shell -> Run Script. In order to avoid >> resolution problems, I also tried to run the script with pvbatch and at the >> end save the screenshot with the following settings : >> >> >> SaveScreenshot(OutputImageName,layout, SaveAllViews=1, >> ImageResolution=UsrImageRes, >> FontScaling="Scale fonts proportionally", >> SeparatorWidth=1, >> SeparatorColor=(1,1,1), >> ImageQuality=100 >> ) >> >> >> These settings are the same as the ones presented in the "settings_test*" >> images. The result attached as "test3.png". >> >> >> Is this a bug or this behaviour should be expected ? Does anybody has an >> idea ? Are the problems with pvbatch and the GUI related or not ? >> >> >> I'm using Paraview 5.4.0 with MPI enabled when I use the GUI. >> >> >> Kindly, >> >> >> Lionel Wilhelm >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Search the list archives at: http://markmail.org/search/?q=ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/paraview >> > > > > -- > Cory Quammen > Staff R&D Engineer > Kitware, Inc. -- Cory Quammen Staff R&D Engineer Kitware, Inc. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview