#47 unwanted raytracer->Size changes

Lode Leroy

(I filed an RFE for this, but some more testing makes
it look like a bug...)

When changing the item "Size" in the Raytrace dialog,
and then clicking on some other window (or widget)
the "Size" is reset to the window size.

For me, this actually happens sometimes at the same
time as starting the raytracer, which ends up tracing
at the previously selected size, but the wireframe is
scaled to full screen.

E.g: Select Size = 256 then change Color -> size=768x768
Select Size = 512, then click "Raytrace" then the raytracer
renders 512x512 but the wireframe overlay renders in

(btw most likely in rt.tcl)


  • Lee Butler

    Lee Butler - 2006-01-12

    Logged In: YES

    If the geometry window is an even multiple of the size you are raytracing,
    then the image will get "zoomed" to match the geometry. So a 512x512
    window will have the wireframe "filled" when you select a 256x256 rendering.
    A 512x480 geometry window will have the 256x256 raytrace image
    unzoomed (though panned), causing the rendering to look small compared to
    the wireframe.

    The merger of the geometry and framebuffer windows builds the user
    expectation of the two views being co-registered. The fact that the 256
    render gets zoomed in the 512 window re-inforces this expectation. Alas,
    the notion is incomplete. There was no design intent to always match the
    rendering (at resolutions other than the one of the geometry window) with
    the wireframe display. The expected behavior is that the user would render
    at the resolution of the geometry window. It would be an interesting feature
    to add to register renderings to the geometry window regardless of relative
    resolution. Probably tricky, definitely time consuming, and (arguably) limited

  • Lee Butler

    Lee Butler - 2006-01-12
    • priority: 5 --> 1
  • Sean Morrison

    Sean Morrison - 2008-05-07
    • labels: --> Geometry Editing
    • milestone: 387263 --> other bug / workaround
    • assigned_to: nobody --> lbutler
    • status: open --> closed-wont-fix

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks