Sign in to follow this  
jpnascim

OpenGL OpenGL printing: getting too thin lines and too small points

Recommended Posts

jpnascim    100
Hello, I am trying to output my OpenGL scene to a bitmap and a printer using code that is very similar to the one contained here: http://www.codeguru.com/cpp/g-m/opengl/printing/article.php/c5585 It executes fine, except for one thing: in the output, lines appear very thin and points appear very small when using high resolution printing(say 600 dpi). Output to smaller resolutions yields correct results. Calls to glLineWidth() and glPointSize() appear to have no effect or little effect for values higher than 2. To summarize: * When generating BMP files with 75 or 96 dpi, everything is rendered correctly. Lines and Points follow screen appearance. * When printing to a PDF or Laser Printer (which, by default, uses 600 dpi) lines and points appear as 1 pixel width/size. The DPI values retrieved from printer influence size of memory bitmap to where I render. Does anybody now if bitmap size influences how lines and points are rasterized? Thanks in advance. João Pedro

Share this post


Link to post
Share on other sites
SimonForsman    7642
Quote:
Original post by jpnascim
Hello,

I am trying to output my OpenGL scene to a bitmap and a printer using code that is very similar to the one contained here:

http://www.codeguru.com/cpp/g-m/opengl/printing/article.php/c5585

It executes fine, except for one thing: in the output, lines appear very thin and points appear very small when using high resolution printing(say 600 dpi). Output to smaller resolutions yields correct results. Calls to glLineWidth() and glPointSize() appear to have no effect or little effect for values higher than 2.

To summarize:

* When generating BMP files with 75 or 96 dpi, everything is rendered correctly. Lines and Points follow screen appearance.

* When printing to a PDF or Laser Printer (which, by default, uses 600 dpi) lines and points appear as 1 pixel width/size.

The DPI values retrieved from printer influence size of memory bitmap to where I render. Does anybody now if bitmap size influences how lines and points are rasterized?

Thanks in advance.

João Pedro


in opengl a line normally doesn't have a width so when rasterized it becomes as thin as possible, a higher resolution means the line gets thinner, the recommended resolution in windows is 96 dpi (1280x960 for a 16.7" 4:3 monitor) which is why 96 dpi rasterizations match what you see.

http://www.khronos.org/opengles/sdk/docs/man/glLineWidth.xml

The only linewidth that is guaranteed to be supported is 1 , the rest is implementation specific, use glGet to see what range your implementation supports.

Share this post


Link to post
Share on other sites
samster581    120
Quote:

* When generating BMP files with 75 or 96 dpi, everything is rendered correctly. Lines and Points follow screen appearance.

* When printing to a PDF or Laser Printer (which, by default, uses 600 dpi) lines and points appear as 1 pixel width/size.


A line that is 1 pixel wide at 77/96 dpi is not 1 pixel wide at 600 dpi.
You need to scale up glLineWidth() accordingly. Use GetDeviceCaps() to get the ppi for you device.

Share this post


Link to post
Share on other sites
jpnascim    100
Hello,

Sorry for not getting back sooner. Thank you for the replies.

Quote:
Original post by SimonForsman
The only linewidth that is guaranteed to be supported is 1 , the rest is implementation specific, use glGet to see what range your implementation supports.


Ok, I see. By calling glGetIntegerv(GL_LINE_WIDTH_RANGE, range) when render context is the memory bitmap, I get min=1 and max=10.

Quote:
Original post by samster581
A line that is 1 pixel wide at 77/96 dpi is not 1 pixel wide at 600 dpi.
You need to scale up glLineWidth() accordingly. Use GetDeviceCaps() to get the ppi for you device.


Right. In fact that's what I was doing. I get device DPI for the PDF printer I am using, in this case, 600 dpi. With DPI and page size, I determine bitmap render size, like this:

const unsigned X_DPI = GetDeviceCaps(PrinterDialog.hDC, LOGPIXELSX);
const unsigned Y_DPI = GetDeviceCaps(PrinterDialog.hDC, LOGPIXELSY);

// Define the size of the image that will be created
bitmapWidthOnPage = pageWidthInches * X_DPI;
bitmapHeightOnPage = pageHeightInches * Y_DPI;



Then I build the bitmap, device context, rendering context and activate everything:


//Create Bitmap here
memset(&BitmapInfo, 0, sizeof(BITMAPINFO));
BitmapInfo.bmiHeader.biSize = sizeof(BITMAPINFOHEADER);
BitmapInfo.bmiHeader.biWidth = bitmapWidthOnPage;
BitmapInfo.bmiHeader.biHeight = bitmapHeightOnPage;
BitmapInfo.bmiHeader.biPlanes = 1;
BitmapInfo.bmiHeader.biBitCount = 24;
BitmapInfo.bmiHeader.biCompression = BI_RGB;
BitmapInfo.bmiHeader.biSizeImage = ((width * 3) + complement) * height;

// Create DIB
DibNew = CreateDIBSection(NULL, &BitmapInfo, DIB_RGB_COLORS, &BitmapBits, NULL, (DWORD)0);
//Create Device Context
HDC_MemoryBitmap = CreateCompatibleDC(NULL);
//...
//Create Rendering Context
HRC_MemoryBitmap = wglCreateContext(HDC_MemoryBitmap);
//...
//Make it current
wglMakeCurrent(HDC_MemoryBitmap, HRC_MemoryBitmap);
//...


Then I render the scene to the bitmap taking care to set lineWidth to the maximum value of 10 obtained earlier(as a test). Still, rendered line is thin.

Any other ideas?

Thank you very much,

Joao Pedro

[Edited by - jpnascim on May 3, 2010 8:50:46 AM]

Share this post


Link to post
Share on other sites
samster581    120
OpenGL only knows about pixels, it doesn't know anything about ppi or device resolution (as far as I know).
As long as you're setting up a thick line width using glLineWidth(), then the line should look thicker, provided it's supported
by your graphics card.

So, open up your 600 ppi bitmap and measure the pixel width of your line. If you say you set its width to 10, then your lines
should be 10 pixels wide. There's your proof.

If you want bigger lines than 10, then you'll have to come up with a new way to render OpenGL lines. Like, drawing them as
thick polygon rectangles. That will support lines of any thickness.

Share this post


Link to post
Share on other sites
jpnascim    100
Well, problem solved.

Before the correction, I was generating a bitmap with a size dependent on output device DPI. For example, if page size is A4(8.27 X 11.69 inches) and printer's DPI is 600 I was trying to render a bitmap with size:

horizontal = 8.27 x 600 = 4962 pixels
vertical = 11.69 x 600 = 7014 pixels

When rendering to this bitmap lines appeared thin, no matter the values I've passed to glLineWidth(). The reason I was doing this was because I thought I would loose image quality in a high DPI device if I rendered to a smaller bitmap and called StretchDIBits() (Win32 API).

Well, it turned out that if I generate my bitmap considering 96 dpi:

horizontal = 8.27 x 96 dpi = 794 pixels
vertical = 11.69 x 96 dpi = 1122 pixels

and make a call to StretchDIBits() with the parameters:

nDestWidth = 4962 (paper width in pixels)
nDestHeight = 7014 (paper height in pixels)

nSrcWidth = 794 (rendered bitmap width in pixels)
nSrcHeight = 1122 (rendered bitmap height in pixels)

With these values, results are correct. Lines and Points appear with programmed thickness. Also, print quality is excellent with no loss of resolution due to bitmap scale up operation.

Thanks for the help,

João Pedro

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
    • By markshaw001
      Hi i am new to this forum  i wanted to ask for help from all of you i want to generate real time terrain using a 32 bit heightmap i am good at c++ and have started learning Opengl as i am very interested in making landscapes in opengl i have looked around the internet for help about this topic but i am not getting the hang of the concepts and what they are doing can some here suggests me some good resources for making terrain engine please for example like tutorials,books etc so that i can understand the whole concept of terrain generation.
       
    • By KarimIO
      Hey guys. I'm trying to get my application to work on my Nvidia GTX 970 desktop. It currently works on my Intel HD 3000 laptop, but on the desktop, every bind textures specifically from framebuffers, I get half a second of lag. This is done 4 times as I have three RGBA textures and one depth 32F buffer. I tried to use debugging software for the first time - RenderDoc only shows SwapBuffers() and no OGL calls, while Nvidia Nsight crashes upon execution, so neither are helpful. Without binding it runs regularly. This does not happen with non-framebuffer binds.
      GLFramebuffer::GLFramebuffer(FramebufferCreateInfo createInfo) { glGenFramebuffers(1, &fbo); glBindFramebuffer(GL_FRAMEBUFFER, fbo); textures = new GLuint[createInfo.numColorTargets]; glGenTextures(createInfo.numColorTargets, textures); GLenum *DrawBuffers = new GLenum[createInfo.numColorTargets]; for (uint32_t i = 0; i < createInfo.numColorTargets; i++) { glBindTexture(GL_TEXTURE_2D, textures[i]); GLint internalFormat; GLenum format; TranslateFormats(createInfo.colorFormats[i], format, internalFormat); // returns GL_RGBA and GL_RGBA glTexImage2D(GL_TEXTURE_2D, 0, internalFormat, createInfo.width, createInfo.height, 0, format, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); DrawBuffers[i] = GL_COLOR_ATTACHMENT0 + i; glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + i, textures[i], 0); } if (createInfo.depthFormat != FORMAT_DEPTH_NONE) { GLenum depthFormat; switch (createInfo.depthFormat) { case FORMAT_DEPTH_16: depthFormat = GL_DEPTH_COMPONENT16; break; case FORMAT_DEPTH_24: depthFormat = GL_DEPTH_COMPONENT24; break; case FORMAT_DEPTH_32: depthFormat = GL_DEPTH_COMPONENT32; break; case FORMAT_DEPTH_24_STENCIL_8: depthFormat = GL_DEPTH24_STENCIL8; break; case FORMAT_DEPTH_32_STENCIL_8: depthFormat = GL_DEPTH32F_STENCIL8; break; } glGenTextures(1, &depthrenderbuffer); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); glTexImage2D(GL_TEXTURE_2D, 0, depthFormat, createInfo.width, createInfo.height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, depthrenderbuffer, 0); } if (createInfo.numColorTargets > 0) glDrawBuffers(createInfo.numColorTargets, DrawBuffers); else glDrawBuffer(GL_NONE); if (glCheckFramebufferStatus(GL_FRAMEBUFFER) != GL_FRAMEBUFFER_COMPLETE) std::cout << "Framebuffer Incomplete\n"; glBindFramebuffer(GL_FRAMEBUFFER, 0); width = createInfo.width; height = createInfo.height; } // ... // FBO Creation FramebufferCreateInfo gbufferCI; gbufferCI.colorFormats = gbufferCFs.data(); gbufferCI.depthFormat = FORMAT_DEPTH_32; gbufferCI.numColorTargets = gbufferCFs.size(); gbufferCI.width = engine.settings.resolutionX; gbufferCI.height = engine.settings.resolutionY; gbufferCI.renderPass = nullptr; gbuffer = graphicsWrapper->CreateFramebuffer(gbufferCI); // Bind glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo); // Draw here... // Bind to textures glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, textures[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, textures[1]); glActiveTexture(GL_TEXTURE2); glBindTexture(GL_TEXTURE_2D, textures[2]); glActiveTexture(GL_TEXTURE3); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); Here is an extract of my code. I can't think of anything else to include. I've really been butting my head into a wall trying to think of a reason but I can think of none and all my research yields nothing. Thanks in advance!
    • By Adrianensis
      Hi everyone, I've shared my 2D Game Engine source code. It's the result of 4 years working on it (and I still continue improving features ) and I want to share with the community. You can see some videos on youtube and some demo gifs on my twitter account.
      This Engine has been developed as End-of-Degree Project and it is coded in Javascript, WebGL and GLSL. The engine is written from scratch.
      This is not a professional engine but it's for learning purposes, so anyone can review the code an learn basis about graphics, physics or game engine architecture. Source code on this GitHub repository.
      I'm available for a good conversation about Game Engine / Graphics Programming
    • By C0dR
      I would like to introduce the first version of my physically based camera rendering library, written in C++, called PhysiCam.
      Physicam is an open source OpenGL C++ library, which provides physically based camera rendering and parameters. It is based on OpenGL and designed to be used as either static library or dynamic library and can be integrated in existing applications.
       
      The following features are implemented:
      Physically based sensor and focal length calculation Autoexposure Manual exposure Lense distortion Bloom (influenced by ISO, Shutter Speed, Sensor type etc.) Bokeh (influenced by Aperture, Sensor type and focal length) Tonemapping  
      You can find the repository at https://github.com/0x2A/physicam
       
      I would be happy about feedback, suggestions or contributions.

  • Popular Now