Modeler 1.0

[Howitzer99]

Does anyone know where we actually go for support with Modeler?  Was hoping Alexey would be more active here.  Needing to get some of the setup issues resolved.

[mald]

modinstr.txt

Hi Fred.  Try reading these instructions and see if they help.  Any queries please ask.

Mal

[Fred Maher]

Thank You Mal!

That worked! Just one last mystery:

Should this "Just Work" or should be I invoking it in a particular context.

 

Cheers - Fred

Edited March 14, 2020 by Fred Maher
Update

[mald]

Hi Fred

Glad you have made some progress.

Alexey has mentioned elsewhere that some of the tools are not working correctly with the current version of houdini 18(eg.set flow).  He has indicated he will be releasing a new version of modeler in a few weeks which should correct the bugs.

Mal

[Fred Maher]

Mal - Hang on. I just did what that error message said to do.

I created a new Pane Tab looked around and found it.

F 

[Howitzer99]

Yup, that's the method.  You need to have an existing pane for KitBash to spawn into.  I haven't played around with it too much, but does look pretty useful.

[Houdini7]

the zone menu is called with the Z key. with the new version, there is a smaller zone menu. it is now splitted. press P, J, Q and so on for the others. press space for a list of the most commands. (but of course you must press "Edit Mesh" button in the modeler menu.

[Howitzer99]

Thanks Andy, I'll try the smaller Edit Mesh menus.

I guess what I'm looking for is the older style with the Zone Menu setup (page 20 in the Modeler manual).  Maybe the manual was just pasted from an earlier version, since there is no menu on the shelf to hotkey to, per the instructions.

 

 

 

[Houdini7]

15 hours ago, Howitzer99 said:

Thanks Andy, I'll try the smaller Edit Mesh menus.

I guess what I'm looking for is the older style with the Zone Menu setup (page 20 in the Modeler manual).  Maybe the manual was just pasted from an earlier version, since there is no menu on the shelf to hotkey to, per the instructions.

 

 

 

this must be from the old version. by the way, you can extend the menus yourself, which is handy.

[Howitzer99]

It's actually from the Modeler 1.0.4 manual, must be included by mistake.

Thanks, I'll see if I can create my own menus.  I like the idea of having a larger subset of the tools in a single menu, instead of my full-screen menu invoked with the space bar.

Overall, the tools are quite handy, a bit cryptic, but has helped with some modeling tasks I've had recently.  Hopefully the menus will be enhanced in future releases, as well as the documentation, and updated tutorials.

[Isleofgough]

Unfortunately it looks like this is $100 for users like me who bought DM1 and upgraded to DM2. There is no discount. Is it actually a new product or just renamed DM2?

[Howitzer99]

On the surface, it's not much different.  Looking at the update info, there are more refined toolsets underneath.  Like 2.0 versions of existing tools, and that it's working in H18.

[Isleofgough]

It looks like any upgrade from DM2 still costs $100. 

Edit: Thank you Alexey for giving me the link. It is great.

Edited April 3, 2020 by Isleofgough

[Alexey Vanzhula]

7 hours ago, Isleofgough said:

It looks like any upgrade from DM2 still costs $100. Too bad. I guess that was why there was an asterix next to "free for DM2 owners".

you are wrong. update from DM1.0 and DM 1.5 to Modeler 1.0 costs $70. But now, during quarantine, it costs $30

[bobc4d]

On 3/13/2020 at 1:06 AM, mald said:

modinstr.txt

Hi Fred.  Try reading these instructions and see if they help.  Any queries please ask.

Mal

I followed your install instruction (thanks for typing them out) but I get error on Houdini startup. I have attached screen shots of the error and my Houdini.env file.  I get the error if I have quotes or not around each statement

Edited April 4, 2020 by bobc4d

[bobc4d]

here is my Houdini file structure

[MostHated]

***********  Edit - I didn't realize that his instructions in the txt file specifically had you format the env file like this: HOUDINI_PATH = "$HOUDINI_PATH;&;$MODELER_PATH". Iif what I said is incorrect for this particular addon, my bad, I apologize. If so, just disregard and do as the instructions said. I have yet to even try this addon out since I bought it. I will test it on my end.

If that is the case, in the file I added below, change it to this instead:

{
	"env": [
		{
			"MODELER": "C:/Users/PATH/TO/modeler/"
		},
		{
			"HOUDINI_PATH" : 
			{
				"value": "$MODELER/",
				"method": "append"
			}
		},
	]
}

 

------------------------------------------------------------------------------------------

 

Remove the $HOUDINI_PATH from the HOUDINI_PATH and have the & at the end.

HOUDINI_PATH=$MODELER_PATH;&

PYTHONPATH is (I believe) the only one in which you want to have PTPATH = $PYPATH;$OTHERSTUFF;

 

Even better yet, don't modify the houdini.env file at all. In your Documents\houdini18.0\  create a folder called "packages" if it does not exist, and in there add the modeler.json file I have attached. Then open it and change "C:/Users/PATH/TO/modeler/" to the actual path to your modeler folder. This allows you to put the modeler folder somewhere else, remove it from your houdini.env and saves a lot of trouble and confusion.

Modeler.json

 

Edited April 4, 2020 by MostHated

[bobc4d]

removing $houdini_path took care of it, it is working fine now.  thank you very much.  

[MostHated]

7 minutes ago, bobc4d said:

removing $houdini_path took care of it, it is working fine now.  thank you very much.  

Very good. I just tested out my other recommendation using packages to make sure it worked as well. I expected it would, but I wanted to be sure. Using the modeler.json I attached above, and putting the actual modeler files in a different location (I keep them all in a separate addons folder on a faster drive) works just fine as well as you can see the modeler shelf in the image below.

So it just comes down to personal preference. I like to keep everything separated out in to their own packages and keep my env file clean.

 

Edited April 4, 2020 by MostHated

[Midphase]

I can't get your .json file to work whatsoever and I am not sure why.

 

Here's what my file looks like:  

 

{
	"env": [
		{
			"MODELER": "/Users/kays/Library/Preferences/houdini/18.0/MODELER"
		},
		{
			"HOUDINI_PATH": "$MODELER/"
		}
	]
}

 

And yet I am getting this error when trying to access Modeler from within Houdini:

 

 

 

Any help would be most appreciated!