Jump to content
Hash, Inc. Forums

Search the Community

Showing results for tags 'netrender'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Discussion
    • * Latest Info *
    • Open Forum
  • Animation:Master
    • Animation:Master
    • Featured
    • Community Projects
  • Animation:Master Users
    • New Users
    • A:M Users Groups
  • Learning Animation:Master
    • TaoA:M Online
    • A:M Rigging
    • A:M Rendering
    • A:M Tutorials & Demos
    • Benchmarks
  • Quick Links
    • Hash Inc Store (Direct Link)
    • New Users!
    • Manuals (Download)
    • TaoA:M Videos (Exercises)
    • Quick Start Videos (Intro to A:M)
    • A:M Stills
    • A:M Films
    • A:M FAQ
    • A:M on Facebook
    • Hash Inc FTP Site
    • The Hash Inc Store (Subscribe to A:M for only $79!)
  • A:M Users's A:M User Club Banner
  • Animation:Master's General Discussion
  • Animation:Master's Releases
  • Animation:Master's Topics
  • Live Answer Time's Themes and Notifications

Calendars

  • Community Calendar
  • Hash, Inc Trade Shows & Event
  • Hash, Inc Notes, Important Dates

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Name


Location


Interests


System Description


Short Term Goals


Mid Term Goals


Long Term Goals


Contests Won


Additional Information


FACEBOOK


TWITTER


SKYPE


YOUTUBE


GOOGLEPLUS

Found 1 result

  1. Before I begin trying to find the source of this bug I'd like some opinions as to what might be happening. Attached are two "versions" of four sequential TIF files (545 through 548) from an on-going Netrender job. If there is a "b" (for bad) in the filename it is the first frame rendered by any one of the my four cores. If there is a "g" (for good) it was either not a Netrender first frame or it could be any frame rendered within A:M itself. I've numbered the files so you can sequentially show them bad, good, bad, etc. When I cycle through them on my monitor, the bad ones seem a bit darker and noisier but nothing that says "obviously this is what's wrong"; they're just poorer quality. All subsequent Netrender images are totally fine. The work-around is trivial but wastes some render time. Debug will take stripping down the choreography until this stops happening but I'm open to suggestions as what to change/remove first. 01_b0545.tif 02_g0545.tif 03_b0546.tif 04_g0546.tif 05_b0547.tif 06_g0547.tif 07_b0548.tif 08_g0548.tif
×
×
  • Create New...