• Posts 8
  • Reputation 0
  • Member Since
  • Last Active
Email
All Posts Topics Started Likes
project a curve on surface

Thanks for the super helpful info Jeremy.

I had it connected this way (as you instructed here above) before but for some stupid reason didn't notice that my "projected result" curve had transforms on it (moving the resulting curve to some strange place space) ...so I just assumed I had this connected wrong somehow - stupid me...I should have double checked.

Going over it again with your notes and just redoing the setup, it's working beautifully now and not flipping out like Maya's curve projection feature does. - SoUP to the rescue once more :D

Thanks again,

cheers!

0 0
project a curve on surface

Hey all,

I'm hoping one of you soup ninja's can help me out with a super noob problem.

I'm trying to figure out how to project (using rayproject node ...I guess) a curve onto a surface. For some reason I just can't figure this out myself (stupid I guess :D ). Is there anyone out there that could help me out with a simple sample scene? I know there's plenty of scenes in the old examples folder ...but those deal only with polys and particles not curves.

I know there's a "project curve to poly" feature already in Maya but in my case that doesn't seem to work as I hoped.

sampleSnap.jpg 

The problem is that I have a deforming surface (ocean) and I need an object (boat) to travel across the surface using a motion path that represents the deformed ocean surface. If I project a curve to the surface (using Maya's built in feature) it looks just fine, but the problem arises when the surface starts deforming (waves)... then Maya can't figure out what the 'start' and 'end' of the curve actually is ...so the motion path keeps "flipping" out, which is not good.

That's why I'm wondering if SoUP could provide me with some control/method of doing this that would not "flip" on me.

Perhaps even a way to "force lock" the start and end of a "rebuilt" curve.

Any ideas/help/suggestions to solve this would be much appreciated.

thanks.

-M

0 0
Regarding Scatter node density on scaled surface

aaaaawwlright, now were talking - I knew there was something going on with that rayProject node ;)

Anyways, this gives me something to play with, a good starting point. Thanks dude.

I'll get back to you with what I manage to Frankenstein together, hopefully I'll find some time in the next few days.

 

thanks again for all the help - cheers!

-M

0 0
Regarding Scatter node density on scaled surface

Thanks for the tip - not sure how I could've overlooked the camera frustum clipping option ...I'll check that again, thanks

Regarding the example scene "cinemaProjectorOnSmokeScreen":

This may sound stupid, but could you in just a few words explain what I'm supposed to see in that scene?
I open it and hit play. All I see is a few particles being emitted and a moving (up and down) polyplane with a rotating textureplacement node - That's it. One doesn not appear to be affecting the other. So I'm not really sure what I'm supposed to be searching for, result wise?

As I mentioned I'm starting to think there's something not right with scenes that use the "rayProject" node. For example if I open up the "rayproject_3" example scene, I know I'm supposed to see a "projected" shadow of the character on the wall, but that's not what I see. It appears as if the "shadow geometry" is intersecting with the character geometry. (see attached screenshots).

I'm running Maya 2016 SP6+EXT1 Linux and SOuP 2016_04_20.

Thanks again for all the help.
cheers!

Click image for larger version - Name: rayscreen.jpg, Views: 10, Size: 22.80 KB Click image for larger version - Name: cinSmokeScreen.jpg, Views: 10, Size: 98.72 KB
0 0
Regarding Scatter node density on scaled surface
pretty late reply here...busy weekend.

Thanks for your input.

but...


The problem with adjusting the point density is that, the larger the surface I'm trying to project on, the more points I need to genereate, making the whole thing super slow.

...and in this case I'm not going for instances.


To explain a bit better what I'm going for here. I'm trying to set up a camera that gives an artist a visual feedback of the region it coveres/sees. This is extremely handy when it comes to dmp and texturing setups/pipelines. Being able to generate a texure map that shows exactly the area needed for texturing. ...or scattering objects on surface etc.
Often those scenes are quite heavy, geometry wise, and the target objects in question are often pretty high poly so getting a responsive setup is quite difficult. Hence I'm trying to set this up without using the "deleteComponent" node - I'd like to "query" the target surface as litle as possible and this setup shouldn't be dependant on the input surface size or resolution.


Being pretty new to SOuP, I'm sure there are a number of ways to achive this. But this is what I got so far (see attached files):


scene v001

Bounding object is a "cube shape", parented to the camera, and its size/width controlled by the camera lens attributes.

- Problem 1: bounding object will always be a full cube, and can't be deformed to represent the true camera frustum (volume). Meaning the closer the camera is to the surface, the bounding object will always affect the "largest" available bbox area, instead of drawing a more narrow line on the surface.
Also, using a "input geometry" shaped as the camera frustum, only produces the component points of the input geo and not the full volume - doesn't produce an accurate enough result and pretty unintuative to control.

- Problem 2: ArrayToTexture2D node gets quite slow, the higher the poly count is. At least the setup is quite responsive up until the point one needs to bake out the texture. Not ideal but acceptable.


scene v004

Here I'm scattering points onto the target surface and using a projectionPlane to define the area of where the scattered points are by the cameras FOV ( note: projection plane is offset slightly from the full far-clipping plane). Then using those points as "input geometry" to influence the target surface.

- Problem 1: as with "v001" , points are not projected based on the camera frustum shape.

- Problem 2: number of scattered points is dependant on the target surface size - the larger the surface, the more points are needed to generate. Meaning if the geometry is large, say huge landscape scene, the slower the setup becomes - near unusable.

- Problem 3: I disconnected the ArrayToTexture2D node at some point for more scene responsiveness (as the node doesn't have and enable/disable feature/check box). Now I can't reconnect the node without Maya crashing instantly.


Now, I fully understand that getting a setup like this to be super responsive in all scenarios may not be possible to do, but right now I'm just at the concept level trying to figure out if it's possible to do or not.
Also, I have the feeling that using the rayProject node somehow would simplify this tremendously, but that's one node I haven't figured out how works (plus all rayProject sample scenes I've opened don't seem to work in Maya 2016, so not really helping either).


Any tips or thoughts you may have regarding this kind of setup would be greatly appreciated.

Thanks again,
- M.
0 0
Regarding Scatter node density on scaled surface

right, yes that is what I'm observing.

I guess the question is ... Is it possible to have the projectors not act as post-modifiers and project the desired amount of points onto a surface/geometry.
Perhaps you know of other means within Soup to do this?

0 0
Regarding Scatter node density on scaled surface

That's the way I had it connected. Even so the amount of "scatter points" seems relative to the size of the projected surface/geometry. The scatter node does not maintain the number of scatter points within the projection area/ray.
e.g. if I'm projecting 200 points onto a surface... and then replace the geometry with another geo of different size/polycount ... I won't get 200 points.

0 0
Regarding Scatter node density on scaled surface

Hi all,

I've got a noob problem, I'm hoping someone here can please shed a light on.

So, I have a simple polygon plain surface and I'm using a projection plane from the scatter node to "project" some points onto my surface - much like the example scene "scatter_textureBasedDistribution1.ma". All very well .. basic enough.

Now, can someone please explain to me why, if I scale up my polygon surface, my number of scattered points decreases?
I bet there is a super simple explaination for this, but for the life of me I can't figure out how to set up the scatter node (network) so that it maintains the same amount of points on the projected part of the surface.

what am I missing here?

(note - you can try this yourselves by opening up the example scene "catter_textureBasedDistribution1.ma", unchecking the "contained" on one of the projection plains, set the scatter node to "surface". then select the sphere and scale it up.

...this happens also within a volume ... if one were to scale up a shape the amount of points within the projected "path" get reduced.


cheers,
- M.

Click image for larger version - Name: scatter1.jpg, Views: 16, Size: 62.44 KB Click image for larger version - Name: scatter2.jpg, Views: 15, Size: 82.54 KB
0 0
count post selected

Add a Website Forum to your website.