Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

garf

Members
  • Content count

    26
  • Joined

  • Last visited

Community Reputation

3 Neutral

About garf

  • Rank
    Peon

Personal Information

  • Name
    Garf

Recent Profile Visitors

1,296 profile views
  1. Thanks chaps, I'll take a look at this. I haven't had a chance to go any further with looking in to this problem but one difference is that one camera is alembic imported and the other is created natively. It's a non-issue at the moment as my shot cams will be alembic imported but I was curious.
  2. I'm clearly being an idiot here. Can someone explain to me why if I render a pyro sim from two different cameras it looks totally different - even the alpha is different? One is wide and far the other is close up. One directional light, mantra. Is this a scattering issue within the shader? I'm using the stock pyro material but I've removed the flame colour bits and thrown in a heat>fit>ramp into the emitcolor instead.
  3. I wasn't totally sure where to post this. Has anyone come across the houdinifx.exe, houdini.exe etc staying within the processes list on Windows after Houdini has been quit? It appears to be only happening on this machine, I've not had a problem on others. Houdini 15.0.416 Windows 7 I've currently got a batch script to kill all instances of it - but it's not ideal when some processes are hogging many Gigs of Memory.....
  4. That's the point. You cant import Houdini particles into Maya with Alembic. It seems that every other DCC on the planet has this ability but not Maya....... Even dead software like XSI can handle this. Autodesk are a shambles.
  5. Is this really still an issue? https://forums.autodesk.com/t5/maya-forum/alambic-importing-partical-erro-error-line-1-particleshape1/td-p/7040953
  6. Ayup! How do you evaluate a parameter to determine it's contents 'type' - e.g. expression/string - 'type' method is currently crossed out in the docs http://www.sidefx.com/docs/houdini/hom/hou/Parm import hou sel = hou.selectedNodes() for i in range(len(sel)): for p in range(0, len(sel[0].parms())): sel[1].parms()[p].set(sel[0].parms()[p].eval()) print str(sel[0]) + ' = ' + str(sel[0].parms()[p].eval()) print str(sel[1]) + ' = ' + str(sel[1].parms()[p].eval())
  7. thanks - this was implemented in h16, right? I'm on 15 right now - so not currently an option.
  8. Anyone know how/if it's possible to maximise the viewport in python? cheers
  9. thanks - it's way overkill for what I need but it's good to know it's do-able
  10. I'm not convinced they are pasted to 0,0 ideally I'd like to lookup where in the coordinate system the network viewer is currently showing and just bung them somewhere in there. I'm liking the moveNodesTo() idea though - I might give that a go
  11. Anyone know how houdini decides where to paste these in the network view? They often end up pasted miles away from the working area.....
  12. Heya, I've written a little python expression to scale geo dependent on through which camera is being viewed. It works but does not recognise when the viewport has changed - is there an event trigger I can use to get it to recognise this change? import hou desktop = hou.ui.curDesktop() scene_viewer = desktop.paneTabOfType(hou.paneTabType.SceneViewer) viewport = scene_viewer.curViewport() camera = hou.GeometryViewport.camera(viewport) if 'preview' in str(camera): return 0.01 print 'preview cam' else: return 1
  13. This is what you need. http://www.sidefx.com/docs/houdini/hom/locations
  14. You can using houdini scripted UIs (selectFile is what you want) https://www.sidefx.com/docs/houdini/hom/hou/ui From the docs: selectFile(start_directory=None, title=None, collapse_sequences=False, file_type=hou.fileType.None, pattern=None, default_value=None, multiple_select=False, image_chooser=False, chooser_mode=hou.fileChooserMode.ReadAndWrite) → str So for example: dialog = hou.ui.selectFile(start_directory=hou.hscriptExpression("$JOB"), title='Select your file', file_type=hou.fileType.Image) You can make start_directory a $VARIABLE or something more explicit like "/my_folder/images/"
  15. Thanks for the response, Mark. It's good to know I'm not being a total plonker!