Jump to content

GeoGem

Members
  • Content count

    7
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About GeoGem

  • Rank
    Peon

Personal Information

  • Name
    Geo Gem
  • Location
    VANCITY
  1. Point Age/Frame Born in SOPs

    much appreciated, thank you I ended up figuring out a cheat by using good old AttribTransfer with a timeShift. Though im not sure of any downsides of doing it this way, id still like to learn how to implement an @age without using dops. ill look thru the links you shared.
  2. Point Age/Frame Born in SOPs

    Ive followed Entagma's tutorial to make a the custom snowflake growth solver, everything is working great. Ive added an ID point attrib to keep a constant point id. What I am now trying to do is to create an emitter from the latest points 'created' in the past 3 or so frames. I fully understand that I can import into a popnet and use all the age/life/birth/jitter options to get the effect im thinking of.... the problem here is that all points from the start of the snowflake growth sim, exists on every frame, which reads into the POPsource, not giving me the effect of NEW points making a trailing emitter. so ive been trying to do something as simple as using a SOPsolver IN SOPs(not dops/pops), to fade @Cd.r=1 every frame to black, then just using a blast or removepoint in wrangle to delete a threshold of points below a certain chf('threshold').....but i cant get it to act on the newly created points of the snowflake solver.... my second attempt has been: int prev = pointattrib(1, 'id', @ptnum, 1); if(@Frame > 1){ if (@id == prev){ @Cd.r=1; } else{ @Cd.r=0; } } [ NOTE: Im using colour to just automatically visualize this before swapping to removepoint or using a blast node w/ threshold ] So, wiring the stream from the snowflake sim, into a timeshift( $F-1 ), then into opinput1 of my pointwrangle, so i can read the id point attribute from the previous frame, compare it to opinput0, in which....logically in my head, should colour the current frame points to be RED, and the PREV frame points matching CURRENT frame points to be BLACK.... even if this worked, id be slightly lost on how to blend it with the past few/N # of frames.... to dumb my question down to the most basic, im needing to add an manual AGE attrib based on the per point creation frame or even just a time/seconds float.... keep in mind, this is not set up in dops/POPnet as of right now. im probably missing something fairly simple, unfortunately a search of odforce, cgwiki and sidefx forums havent provided me with a solution. THANK YOU!
  3. ah yes! great, a few extra nodes to use. very important to specify Cd as darker than the desired color first, but preferably black. everything has to be set Prim attribs and it works great, thank you for specifying. i find myself using this quite a bit to avoid manual selection blasts. Ive included the hip as an attachment(using Crag) for whoever else comes across this thread, full credit to the help from @anim of course. fullyConnected_byPartialBbox.hipnc
  4. got around to playing with this. the wrangle for loop method works great until theres too many primitives, long cook time. using the detail promote method, the Piece Attribute checkbox is disabled when Original Class is set to detail. I tried fiddling with using 'class' in the original name and adjusting some things, but it seems i need to stick to the for each method. thank you though.
  5. hmm i tried your code in a wrangle running thru both prim and points, couldnt get it working. I use a group node before the wrangle to use its bounding function like i first specified or just select some points? those two functions seem quite useful though, i did not know of them till now. I dug thru my instructors old files and found a little trick he did by running a Cd attrib through PRIM to DETAIL attribpromote with a MAXIMUM method then reverse it again DETAIL to PRIM in a for each loop, and it somehow it tells the Cd value to envelope the whole connected piece. super fascinating, hip file attached. grpbound_partial_fullconnectivity.hipnc
  6. The simple example: using the bounding region option in the group sop, if the bound was to select a partial amount or even a single point/prim of an "island"/piece geo, is there a way to extend the group to cover the whole of the connectivity. another example: a wheel that has a rim, hubcap and lugnuts as part of one imported model, would like to tell my group node, or wrangle to select whatever is in the top 10% of the bbox, then extend the partial selection to just the tire piece/name/class. if the bound were to select the top 30%, it would be both the whole tire and rim, minus the lugnuts and hubcap being 40% from the outer diameter. The idea is to create a connected pieces group, procedurally, without addressing a name/class that could possibly change if the input were transformed or changed topology. H18 i feel i could accomplish this easily with the group expand by surface, but unfortunately im unable to use H18 for a while. Im fairly good at wrapping my head around vex scripting, no hesitation to trying to coding this if im not missing an easier technique. Thanks!
  7. Houdini 19 Wishlist

    whats with the eh? it was only the last month or two that i found out right clicking the title bar and deselecting Always on top solved much of my frustrations of constantly moving it out of the way.... but yea its seems like a no brainer to make it a dockable panel. My request, a simple function to rotate node inputs and outputs from vertical connection to horizontal connection so we can have the option to work laterally like in vops. hotkey would just switch the input and output dots to the sides of the node, the title and comments to top and bottom, as well as orange dependency links . im aware of shift+A+drag will nicely lay them out laterally, but the wiring in both normal wire and S curve format is rather "messy". this option could be set PER node under the Flags menu. + Drag and drop images into vops, shop or mat view and have a menu appear (like 3ds max) to select whether to drop them as color maps, or mantra/redshift/other render texture nodes. other simple network view layout things, within the display options: + ability to adjust the default distance, in pixels, to which a new node is placed when shift+enter is used to drop a node on a wire or from existing selected node. (and/or snap the new node to the closest grid line when grid is active.) + the above feature would also be amazing without the grid active. as we all operate on various node view spacing workflows. + ability to adjust the magnet strength of all network view snapping + a function to clamp the zoom range of the network view. currently zooming out to infinity and zooming in to gigantic node size seems impractical. (im sure theres probably already a way to alter this with a python script or something) + the ability to add user color set presets in the right click menu of the network color swatches.
×