Jump to content

momposina

Members
  • Content count

    10
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

2 Neutral

About momposina

  • Rank
    Peon

Contact Methods

  • Website URL
    https://www.egmontas.xyz

Personal Information

  • Name
    Egmontas Geras
  • Location
    London
  1. Vellum Pressure

    Hi, I wanted to ask about some of the hidden intricacies of vellum pressure. In particular I recently found out about the @pressuregradient attribute that determines the direction in which the object expands as pressure is applied. I wonder: How is it determined? I suspect something to do with Normals, but then when I visualise the attribute it tends to always have a rough relationship with {0,0,0} - why? This leads to strange inflation especially if an object is off-center and then it trends away from the origin, as opposed to away from its center of mass... Can it be manipulated in the solver? It would be nice to procedurally predetermine the inflate direction, although I'm not sure how to access or manipulate this attribute. Can it be manipulated per frame? If I have multiple objects that start in a rest position and their inflations happen one after another - one ball moves other balls out of rest position for example... Then once the ball that has already been moved starts to inflate, is it computing on the pressure attribute given at the start of the solve, or the one at it's current frame number? I could probably word these questions better and I do apologise, but at the moment it seems I have run out of places/videos to read/listen to. Thanks a lot for your help! Cheers.
  2. Nekiya

    Thanks! Pretty much all is raw render, I composited in After Effects but have done almost no post-production, was just about sequencing the shots. Lighting and materials repeat themselves through the scenes, I think that is how the 'character' is maintained? Will keep going!
  3. Nekiya

    Hello, I'd like to share a shortfilm that I've been working on for the last few months. It is set up and rendered entirely in Houdini; whilst some 3d models are drawn in other bits of software, the majority is procedurally drawn and the outliers also tend to undergo transformations. Strictly no 2d effects, everything is simulated spatially within the scenes (this is part of an ongoing practice ethos of trying to understand all geometry in 3d and render a fully composited shot). I am very excited to continue to develop and unpack a lot of the systems that have been built for this project. It would be great to get some feedback, thoughts and criticisms from this community. I hope you enjoy. LINK: https://vimeo.com/446918887 Cheers, Egmontas Description: Nekiya is a short film that constructs a spirit realm as a reflection on the naive hypothesis for the existence of ghosts. Who has seen the spirits? Neither I, nor you. But when the invisible weighs upon your chest, the spirits are reaching through. Let the spirits emerge and let Spookiness be true. As Spookiness has an overwhelming desire to meet Soba, she anxiously struggles to determine her place in this delicate world full of occurrences at the edge of her perception and control. Soba begins to doubt the verity of not only her constructed memories, her tears, but the seemingly indeterminate nature of her body itself. Spirits emerge as three-dimensional entities with embedded spatial, material and behavioural data that characterises their potential and inherent constructional capacity within what we can now determine as our multiple realities. These spirits are a consequence of procedural logics that inform both simulation and translation in a digitally pliable universe. Nekiya is the hypothesis of a haunted space of spectrality; it is an episode in the search for a practice of digital poetics.
  4. Digisoup

    wow! that's brilliant, thank you.
  5. Digisoup

    Hello, I thought that I would share a side-project I started this last month because I lost a bit of steam (no pun) and thought that it would be curious to receive some feedback. The Digisoup began as an idea to create a procedural recipe that creates and fills a bowl of soup with various ingredients. The initial to do: bowl, stock, dumplings, veg, seasoning, steam, etc. The bowl or vessel was modelled independently but used as a source object for the other ingredients. Spring onion, spices, chilli, dumplings, eggs and noodles have all been drawn within a procedural framework - I intend to do posts explaining each ingredient if anyone is interested. The stock (liquid of the soup) is primarily a shading exercise, and on that note all of the shaders are also procedural and do not utilise bitmaps or external references. The intention with that was to be able to control 'fattiness' or 'richness' of the soup we are about to enjoy. I haven't yet documented the entire process but here are some of the shots I've managed to salvage while working in progress. At some point the project began to evolve into figuring out the context around the bowl with some embedded procedural tricks - I will expand on this later! Would love to hear your thoughts! Cheers.
  6. Procedural Robots

    These are great! Very interesting stuff - got me thinking how...
  7. Growth Systems

    Thanks! This project got so messy - I will begin working on a concise, "clean" version however, which I would very much like to share
  8. Growth Systems

    I originally made a post in in the WIP section, but have finalised a selection of images that demonstrate the extent of the project at this particular time. Hope to get some tips, speculation and direction . The work started with an idea of looking into systems of growth and the procedural simulation of that growth. The question of landscape surveillance and 'fertility' arose - can a landscape (or object) topology be evaluated for growth? In this case the landscape would be a scanned model of a terrain, converted from pointcloud to mesh data and thus reinterpreted as a topology of points and primitives with certain inherent attributes: Position (vector), Normals (vector), and curvature (scalar) predominantly. The simulation can then search for 'flatness' and eliminate areas of surface beyond a limit of acceptability. The surface is then displaced whilst maintaining ties to the remainder, this seemed to mirror a process not too dissimilar to inflation (although much more noisy and undefined), always using the retopologised mesh (and thus recalculated attributes) as a driver for the next frame of growth. Generated or grown form is evaluated through a series of spatial explorations with particular functional characteristics in mind. Much like a single-surface-landscape produces the massing for proposed architectural volumes, these volumes are then reinterpreted as single-surface forms that morph into a typology of architecture defined by certain rules. The primary purpose of the interior volume is to house the program of an architecture. The height of the form is predetermined in the procedural algorithm of massing to produce volumes within a range of heights (for example between 3 and 20 meters). The nature of the form suggests an architectural language of evaluated skin as a means of facilitating architectural space. This is then differentiated to provide for the various requirements of a space of production - for example: how can the floor surface serve as a platform for plant growth; how can the side envelope serve as a mediator of thermal comfort; etc? A. There is a desired differentiation between roof and side envelope - key factors to be considered are the issues of transparency in form for light to enter the space below and the capacity to drain rainwater or melting snow. B. An impression of uniformly distributed structural frames is suggested as a method of holding up a dressing of skin not too dissimilar to ideas of bone to muscle tissue connections. C. The form is interpreted as a skin multi-functional, multi-material character. There is a desire for a thermal envelope mixed with porous characteristics that allow for breathability within the interior environment, light, and mediation from the harsh external environment. The following images are all excerpts of a fully procedural exercise; all grown; but in various stages of development of the same system.
  9. Explorations in Growth Simulation

    Here are a few more images of objects that underwent some sort of early 'growth logic' - I was primarily concerned with using the external mesh skin to grow both inwards to create an interior, and outwards to create perforations...
  10. I started using Houdini about 2 years ago, recently I have felt a desire to not only share but, hopefully to open up a discussion about the explorations undertaken in the work. The first post is therefore a look at how it began. The work started with an idea of looking into systems of growth and the procedural simulation of that growth. The question of landscape surveillance and 'fertility' arose - can a landscape (or object) topology be evaluated for growth? In this case the landscape would be a scanned model of a terrain, converted from pointcloud to mesh data and thus reinterpreted as a topology of points and primitives with certain inherent attributes: Position (vector), Normals (vector), and curvature (scalar) predominantly. The simulation can then search for 'flatness' and eliminate areas of surface beyond a limit of acceptability. The surface is then displaced whilst maintaining ties to the remainder, this seemed to mirror a process not too dissimilar to inflation (although much more noisy and undefined), always using the retopologised mesh (and thus recalculated attributes) as a driver for the next frame of growth. The video and images below are examples of the earliest explorations (and failures) of this theme, first applied to a modelled object, with the video then moving onto a landscape: https://vimeo.com/376861116
×