Lines Width on technical pdf scripting

i wrote a script to export layouts at an automatic place, with an automatic name: the script is like this:

{
            var pdf = FilePdf.Create();
            
            foreach (var layoutName in selected)
            {
                var pageview = pageviews.FirstOrDefault(p => p.PageName == layoutName);
                if (pageview == null)
                    continue;

                // Dimensions papier en pouces
                double inchW = pageview.PageWidth / 25.4;
                double inchH = pageview.PageHeight / 25.4;

                SD.Size size = new SD.Size(
                    (int)(inchW * dpi),
                    (int)(inchH * dpi)
                );

                var settings = new ViewCaptureSettings(pageview, size, dpi)
                {
                    RasterMode = true,
                    OutputColor = ViewCaptureSettings.ColorMode.DisplayColor
                };

                pdf.AddPage(settings);
            }

            pdf.Write(finalPdf);

            
            Process.Start(new ProcessStartInfo(finalPdf) { UseShellExecute = true });
        }

the output is a raster pdf, and it not take the value of the midth line print of the layer when the display mode of the view is “technical”, do you know why?

Hi,

Can you manually print in vector mode, if so the script needs tweaking.
However my understanding is that technical mode, although representing lines, is pixel based and as such your pdf will be image based (raster) as well.
I expect all geometry you add to the layouts like the block or annotations will be in vector.

Does this make sense?
-Willem

I thought it was the opposite @Willem , Technical is vector based. Other modes like rendered are raster based.

Hi @michaelvollrath

You are right, my bad, technical can indeed be printed to PDF as vector.
Thanks for the correction

-Willem

Hi @onlyforpeace

I was too quick to reply.

I see in your code that you set

What if you set that to False?

-Willem

I don’t understand… I thought I had tested this line of code, but apparently not, since it works now. That’s what happens when you work on several things at the same time.

thank you @will