make sure you have checked the checkbox from the pattern utility node that enables the pattern. if you can't get it working send me a hipfile, and I will gladly take a look houdinielement@gmail.com
Found it. You have to dive inside the building_from_patterns hda and in end of points output, on a Set_orient node, on the cleanup tab, add module_name as a point attribute to keep.
Does anyone else have problems with the HDA? I don't know why but it keeps crushing my Unreal, and when I create or save the HDA in houdini an error shows up telling me that I have references to nodes outside the subnet or references that use absolute paths to operators inside the subnet.
Excellent Tutorial dude, thanks a lot. Just two questions or problems I'm having right now: 1. How would you implement the convex corner here?. 2. To be honest I badly made my concave corners work, in fact I had even to scale them to make them match with the rest of the walls/windows and I don't know why exactly, if you have any idea why would that happen I would love to know. Thanks again for your work man :D
Concave corners would basically also be done with identifying concave points from building node point cloud. I have made concave corners for other buildings, and at the basis it would converting each floor into a polyline and putting down a labs node, I'm not sure what its called, but its takes polyline and figures out convex and concave points. After that you would transfer the concave group to the building point cloud and you can rename those points to concave module names. For the corners, i remember someone else asked me about corners not lining. I don't exactly remember the solution. I know it was something about module scaling. To help you out, write me an email, you can send me a file so I can take a look. My email should be in my channel description.
ive had the same problem, what fixed it for me was to double check that my transform node inside the for-loop does not have any pivot or pre transforms and to set the match size - justify X to None. the other two are set to Min. Recache the for-loop as well if that doesn't work. might simply be a bug.
@@viktors_anfimovs Hey I am having the same issue and also another one, where I am using a more difficult blockout geometry, and when I have more than 4 sides the whole roof don't work as well as some of the corners, I guess because it cannot select half of the geometry for the procedural module selection and other issues. Have you tried to use a procedural more complex blockout and still worked? And if so, would you mind sharing what did you have to modify? Thanks!
Im on 19.5. Try to look where does megascans put its package folder. Make sure houdini picks it up. I think, bu default it should be in your documents-houdini19.5 folder
Had same problem, Bridge simply didn't create the necessary folder. Here is the solution: Create "packages" folder in your Houdini installation folder c:\Users\YOURNAME\Documents\houdini19.5\packages\ Manually create there a text file MegascansPlugin.json Edit the file to put there the path to your Megascans (using my path here): { "path": "d:\\MEGASCANS_LIB\\support\\plugins\\houdini\\4.6\\MSLiveLink" } Save this and run Houdini, you should be fine.
This is an excellent tutorial. Really nicely done. Clears up a lot of information on the megascans. For some reason I am having trouble at 1:11:25, I am using 19.5 bu it says the syntax is incorrect for 0-`npoints`(0)/2. Any ideas? I have set the group type to points, it is the base group and I can see the group name appearing in the spreadsheet. this is the message: Warning Bad pattern specified 0-npoints(0)/2. Possible problems: Number out of range or a syntax error. Valid Syntax: [!]start[-end][:step][,increment] examples: !1-10:2,3 1-10:2 * 0-5 1
I have hit another issue, on the attribute wrangle at 1:17:15 I get an error saying ; Invalid source /obj/megascans_building/attribwrangle2/attribvop1 Error: Read-only expression on left side of assignment (2,37). I have checked the code as it was done in the tutorial but not sure what is causing the issue int gable_tp_num = npoints(1); for (int i = 0; i < gable_tp_num; ++1){ vector gable_pt_pos = point(1, "P", i); vector gable_scale = point(0, "scale", i); float offset; int new_pt; if(v@N.x ==0){ offset = gable_pt_pos.x; new_pt = addpoint(0, set(offset, v@P.y, v@P.z)); } }
@@viktors_anfimovs Thank you. That solved everything and I now have a complete HDA. The only thing I am seeing in the viewport is a normal problem with the edge of one roof. Is that just the viewport or should I be putting in a normal node along the way somewhere?
@@DonquijoteDC You can try to turn on flat shaded geometry in viewport. Also maybe viewport is acting up, from labs tools you can from main toolbar, go Labs-Reset Viewport. Look at geometry that you are importing, if the single piece looks correct. Normals should be correct for the megascans assets. Sometimes they do not look right. Hope this helps!
The corners meshes for me aren't aligning at all. In match size I made sure to have X none and Y & Z to min. I don't understand what I am doing wrong here.
Does anyone know how to use the variation parameter in the building utility node in the floor description? I would like to have different expanded forms per facade face basically. Anything I add there takes too long to compute and make me abort whatever its trying to do.
If I remember correctly, create new modules without variation and then reference them in a new utility node as a variation and control its weight. In a pattern reference the module with variations on it, and it should randomly select the variations.
@@viktors_anfimovs No luck. I think I have to come up with facade side variations on my own, this video is the only documentation that exists about how the node works.
I made a quick hip file to show a little bit of using variations. Maybe this will set you on the right track. drive.google.com/file/d/1-0SPnwAPRmkO8AkJVwzFC60FhFiapeGo/view?usp=sharing
Great lesson
My points from building from patterns are coming out without module name attribute, so the blast for corner setup does not work. Any ideas?
make sure you have checked the checkbox from the pattern utility node that enables the pattern.
if you can't get it working send me a hipfile, and I will gladly take a look
houdinielement@gmail.com
Found it. You have to dive inside the building_from_patterns hda and in end of points output, on a Set_orient node, on the cleanup tab, add module_name as a point attribute to keep.
@@esparafucio 감사합니다. set_orient 노드에 연결 되있는 switch 노드 쪽에 attribcopy 로 module_name 가지고 오니깐 잘 작동 됨니다. 감사합니다
Hi! Thanks for the tutorial, but the resolution is just at 360p, or is just me having this problem? @Houdini Element
Hi! Sometimes it takes a long time for YT to encode in HD.
RUclips takes long time to encode long videos. Should be fine in few hours.
@@viktors_anfimovs That great! thank you so much!
Does anyone else have problems with the HDA? I don't know why but it keeps crushing my Unreal, and when I create or save the HDA in houdini an error shows up telling me that I have references to nodes outside the subnet or references that use absolute paths to operators inside the subnet.
Excellent Tutorial dude, thanks a lot. Just two questions or problems I'm having right now:
1. How would you implement the convex corner here?.
2. To be honest I badly made my concave corners work, in fact I had even to scale them to make them match with the rest of the walls/windows and I don't know why exactly, if you have any idea why would that happen I would love to know.
Thanks again for your work man :D
Concave corners would basically also be done with identifying concave points from building node point cloud.
I have made concave corners for other buildings, and at the basis it would converting each floor into a polyline and putting down a labs node, I'm not sure what its called, but its takes polyline and figures out convex and concave points.
After that you would transfer the concave group to the building point cloud and you can rename those points to concave module names.
For the corners, i remember someone else asked me about corners not lining. I don't exactly remember the solution.
I know it was something about module scaling.
To help you out, write me an email, you can send me a file so I can take a look.
My email should be in my channel description.
ive had the same problem, what fixed it for me was to double check that my transform node inside the for-loop does not have any pivot or pre transforms and to set the match size - justify X to None. the other two are set to Min. Recache the for-loop as well if that doesn't work. might simply be a bug.
@@viktors_anfimovs Hey I am having the same issue and also another one, where I am using a more difficult blockout geometry, and when I have more than 4 sides the whole roof don't work as well as some of the corners, I guess because it cannot select half of the geometry for the procedural module selection and other issues.
Have you tried to use a procedural more complex blockout and still worked? And if so, would you mind sharing what did you have to modify?
Thanks!
are you using houdini 19? i cant seem to install the megascan bridge from their web to houdini 19.5 ..
Im on 19.5.
Try to look where does megascans put its package folder. Make sure houdini picks it up.
I think, bu default it should be in your documents-houdini19.5 folder
Had same problem, Bridge simply didn't create the necessary folder.
Here is the solution: Create "packages" folder in your Houdini installation folder
c:\Users\YOURNAME\Documents\houdini19.5\packages\
Manually create there a text file MegascansPlugin.json
Edit the file to put there the path to your Megascans (using my path here):
{
"path": "d:\\MEGASCANS_LIB\\support\\plugins\\houdini\\4.6\\MSLiveLink"
}
Save this and run Houdini, you should be fine.
Tnx for the video!
This is an excellent tutorial. Really nicely done. Clears up a lot of information on the megascans. For some reason I am having trouble at 1:11:25, I am using 19.5 bu it says the syntax is incorrect for 0-`npoints`(0)/2. Any ideas? I have set the group type to points, it is the base group and I can see the group name appearing in the spreadsheet. this is the message:
Warning
Bad pattern specified 0-npoints(0)/2.
Possible problems: Number out of range or a syntax error.
Valid Syntax: [!]start[-end][:step][,increment]
examples: !1-10:2,3 1-10:2 * 0-5 1
thake out the second `, secont tick means you are ending expression, and houdini reads everything after as a string, 0-`npoints(0)/2 should do fine.
@@viktors_anfimovs Thank you so much for coming back to me. Very much appreciated.
I have hit another issue, on the attribute wrangle at 1:17:15 I get an error saying ;
Invalid source /obj/megascans_building/attribwrangle2/attribvop1
Error: Read-only expression on left side of assignment (2,37).
I have checked the code as it was done in the tutorial but not sure what is causing the issue
int gable_tp_num = npoints(1);
for (int i = 0; i < gable_tp_num; ++1){
vector gable_pt_pos = point(1, "P", i);
vector gable_scale = point(0, "scale", i);
float offset;
int new_pt;
if(v@N.x ==0){
offset = gable_pt_pos.x;
new_pt = addpoint(0, set(offset, v@P.y, v@P.z));
}
}
You have a number in incrementing ++1, it must be the variable we increment, witch is ++i
@@viktors_anfimovs Thank you. That solved everything and I now have a complete HDA. The only thing I am seeing in the viewport is a normal problem with the edge of one roof. Is that just the viewport or should I be putting in a normal node along the way somewhere?
@@DonquijoteDC You can try to turn on flat shaded geometry in viewport.
Also maybe viewport is acting up, from labs tools you can from main toolbar, go Labs-Reset Viewport.
Look at geometry that you are importing, if the single piece looks correct. Normals should be correct for the megascans assets. Sometimes they do not look right.
Hope this helps!
The corners meshes for me aren't aligning at all. In match size I made sure to have X none and Y & Z to min. I don't understand what I am doing wrong here.
sent me a hip file. i can take a look. houdinielement@gmail.com
When multiple boxes are merged together, there will definitely be problems. Does anyone have any solutions?
You can write me an email. With your problem and hip file. I can taka a look and help
@@viktors_anfimovs Thank you for your adoption. Your email has been sent to you.
@@gradinlau hey did you fixed it? I am trying to do the same atm without any luck
Does anyone know how to use the variation parameter in the building utility node in the floor description? I would like to have different expanded forms per facade face basically. Anything I add there takes too long to compute and make me abort whatever its trying to do.
If I remember correctly, create new modules without variation and then reference them in a new utility node as a variation and control its weight.
In a pattern reference the module with variations on it, and it should randomly select the variations.
@@viktors_anfimovs No luck. I think I have to come up with facade side variations on my own, this video is the only documentation that exists about how the node works.
I made a quick hip file to show a little bit of using variations. Maybe this will set you on the right track.
drive.google.com/file/d/1-0SPnwAPRmkO8AkJVwzFC60FhFiapeGo/view?usp=sharing
@@viktors_anfimovs That helped making sense of the variations, thx
corner system is not working with different modular version after deleting and replacing its not filling in the deleted corner.
is there any way to fix this?
If you still cant get it fixed, send me a hip file with your setup, i will gladly help you.
sent it to your email tell me if it works never sent a hip file before😅
also forgot to add that the modules are exported from unreal to houdini so i changed scaling to 0.01 and rotated them
@@deadshot-re9ic sent you an email
My program freezes at 16:47
This usually means the pattern was not recognised. You can write me an email, i will be glad to help you!
my building red😢😢😢
Don't worry, just shoot me an email, and I will send you this tutorial's hip file.
@@viktors_anfimovs Solved a problem. Thank you