Results 1 to 4 of 4

Thread: Fprime "bug"? hypervoxel temperamental rendering

  1. #1
    Registered User
    Join Date
    Jun 2012
    Location
    brighton uk
    Posts
    21

    Fprime "bug"? hypervoxel temperamental rendering

    Hi all,

    Running into an issue with Fprime which others may know a way around.
    Fprime v3.5, Lightwave 11.5, 3.3ghz hex core AMD, 32gb ram, 64bit, win7, GTX 580 lightning extreme

    The issue is with hypervoxel rendering. I realise that fprime is better suited to older versions of lightwave.
    If I open the fprime live preview window I can see my hypervoxels, however as soon as I move to the next, previous, or any other frame the voxels disapear from fprime's preview window, although they are still there and can be seen in lightwave's preview windows without issue.

    I've also noticed that I can render out a specific frame in fprime by dragging to that frame, saving the scene, closing and re-opening, and as if by magic fprime will be working with voxels on that frame again, although if I try to move to another frame I'm back to square one.

    There was a point in my workflow in which fprime suddenly "corrected" itself and allowed me to drag and render any frame or sequence of frames I wanted to, then the following day it started acting up again.

    I don't know why it's having issues. Hitting fpriume's refresh button doesnt make any difference, or closing/opening render windows. My hypervoxels have motion, pre-saved .pfx motion.

    Any help or suggestions would be greatly appriciated. I've spent the last 48 hours trying to search online for any similar issues, but as you might expect I'm getting a lot of returned results for older versions of fprime which didn't support hypervoxels at all.

    Thanks folks

  2. #2
    You could try emailing Worley. I've found he's pretty good at responding.

    No guarantee there's a fix as I don't believe he's still developing for LightWave. (I hope I'm wrong about that though)
    My opinions and comments do not represent those of my employer.
    www.ernestpchan.com
    www.zazzle.com/gopuggo

  3. #3
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    7,122
    You could also try with 11.6.2 and see if that fixes the issue. There was an HV SDK fix in particular that might help fPrime function better.

    Otherwise, yeah, best to contact Worley. Consider yourself lucky, us Mac UB folks haven't had working Worley plugs since 9.6.x/v10.
    John W.
    LW2015.3UB/2019.1.5 on MacPro(12C/24T/10.13.6),64GB RAM, NV 980ti

  4. #4
    Super Member Snosrap's Avatar
    Join Date
    Aug 2004
    Location
    Ohio, USA
    Posts
    4,925
    sounds silly, but make sure auto key is on.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •