why point and line size is relative using the latest PeasyCam ?

oatcracker

why point and line size is relative using the latest PeasyCam ?

in Contributed Library Questions • 6 months ago

I found that after updating the latest PeasyCam library, the size of point/line as shown in 3D scene is always relative rather than absolute. i.e. the size of a point/line as shown on screen is always the same no matter you zoom in or out.

Is it related to the update of Processing (2.0b8) or PeasyCam?

How can we show the point by its absolute size?

Thanks!

Replies(8)

oatcracker

Re: why point size is relative using the latest PeasyCam ?

6 months ago

I think it's caused by the latest Processing 2.0b8 because 2.0b6 don't have this problem.

Again, may I ask how to show point in 3D scene by its absolute size?

Thanks!

oatcracker

Re: why point and line size is relative using the latest PeasyCam ?

6 months ago

any suggestion on how to show real point size when zoom in/out in Processing 2.0b8?

Thanks again!

rbrauer

Re: why point and line size is relative using the latest PeasyCam ?

6 months ago

I think it might be hint(ENABLE_STROKE_PERSPECTIVE);

oatcracker

Re: why point and line size is relative using the latest PeasyCam ?

6 months ago

yes, the "hint" does the trick.

Thank you very much, rbrauer!

oatcracker

Re: why point and line size is relative using the latest PeasyCam ?

6 months ago

BTW, is the "hint" function a Processing thing or a Java thing? Where can I find its reference? Thanks!

GoToLoop

Re: why point and line size is relative using the latest PeasyCam ?

6 months ago

Name

hint()

Examples

void setup() {
  size(400, 400, OPENGL);
  // Enable 4x oversampling (if supported)
  hint(ENABLE_OPENGL_4X_SMOOTH);
}

Description

Set various hints and hacks for the renderer. This is used to handle obscure rendering features that cannot be implemented in a consistent manner across renderers. Many options will often graduate to standard features instead of hints over time.

hint(ENABLE_OPENGL_4X_SMOOTH) - Enable 4x anti-aliasing for OpenGL. This can help force anti-aliasing if it has not been enabled by the user. On some graphics cards, this can also be set by the graphics driver's control panel, however not all cards make this available. This hint must be called immediately after the size() command because it resets the renderer, obliterating any settings and anything drawn (and like size(), re-running the code that came before it again).

hint(DISABLE_OPENGL_2X_SMOOTH) - In Processing 1.0, Processing always enables 2x smoothing when the OpenGL renderer is used. This hint disables the default 2x smoothing and returns the smoothing behavior found in earlier releases, where smooth() and noSmooth() could be used to enable and disable smoothing, though the quality was inferior.

hint(ENABLE_NATIVE_FONTS) - Use the native version fonts when they are installed, rather than the bitmapped version from a .vlw file. This is useful with the default (or JAVA2D) renderer setting, as it will improve font rendering speed. This is not enabled by default, because it can be misleading while testing because the type will look great on your machine (because you have the font installed) but lousy on others' machines if the identical font is unavailable. This option can only be set per-sketch, and must be called before any use of textFont().

hint(DISABLE_DEPTH_TEST) - Disable the zbuffer, allowing you to draw on top of everything at will. When depth testing is disabled, items will be drawn to the screen sequentially, like a painting. This hint is most often used to draw in 3D, then draw in 2D on top of it (for instance, to draw GUI controls in 2D on top of a 3D interface). Starting in release 0149, this will also clear the depth buffer. Restore the default with hint(ENABLE_DEPTH_TEST), but note that with the depth buffer cleared, any 3D drawing that happens later in draw() will ignore existing shapes on the screen.

hint(ENABLE_DEPTH_SORT) - Enable primitive z-sorting of triangles and lines in P3D and OPENGL. This can slow performance considerably, and the algorithm is not yet perfect. Restore the default with hint(DISABLE_DEPTH_SORT).

hint(DISABLE_OPENGL_ERROR_REPORT) - Speeds up the OPENGL renderer setting by not checking for errors while running. Undo with hint(ENABLE_OPENGL_ERROR_REPORT).

As of release 0149, unhint() has been removed in favor of adding additional ENABLE/DISABLE constants to reset the default behavior. This prevents the double negatives, and also reinforces which hints can be enabled or disabled.

Syntax

hint(item)

Parameters

item	constant: name of the hint to be enabled or disabled

Returns

None

Usage

Web & Application

PGraphics
createGraphics()
size()

Updated on August 30, 2010 04:29:39pm EDT

GoToLoop

Re: why point and line size is relative using the latest PeasyCam ?

6 months ago

Found that in Processing v1.5.1 reference! As it's censorshipped, gonna get chopped off soon as well!

oatcracker

Re: why point and line size is relative using the latest PeasyCam ?

6 months ago

noted with thanks!

Top Reply