Can't create a appearance material

#4

and copying default…gives a NULL as well

0 Likes

#6

Which version of Revit do you use ?
It will work only in Revit 2018.1 and later.

0 Likes

#7

2019.2 dynamo 1.3.4.6666

0 Likes

#8

Can you upload your graph and a sample Revit file ?

0 Likes

#9

kozijn_generator.rfa (2.9 MB)
kozijngenerator.dyn (327.5 KB)

It is a work in progress…making windows from lines…

0 Likes

#10

I just made a very simple test with your kozijn_generator.rfa file and the Genius Loci custom nodes work fine.

I can’t speak for your python script that creates the materials.
Try first with the existing materials in your family.

0 Likes

#11

strange if i setup a new test, same as you it works… will investigate some more…nodes work

thank you

0 Likes

#12

the problem was that i was making a material…and Revit was probably still writing the data at the moment that i wanted to adress that data to make the appearance material…
So i made a wait for…then read all the materials again en select the newly made material…then it works fine.

0 Likes

#13

I have just released a beta version of Orchid dealing with Materials and Assets, would you mind testing it?

0 Likes

#14

will have a look this week

0 Likes

#15

Thanks, that would be great… building those nodes is not that easy. I have had a maniac time figuring all the internal Revit units for material values… some of them are really crazy :slight_smile:

0 Likes

#16

Agreed. I went through a similar struggle with a Revit plugin for a client. This AU2017 class was very helpful to me,

0 Likes

#17

It was not the Visual Appearance I was struggling with.

Just to inform you, the shown example concerning Visual Appearance is being deprecated from Revit 2019… new ways of using Visual Appearance is being introduced from Revit 2019.
Thats why I am in a limbo. Either code something for Revit 2018.1 up to Revit 2019 or from 2019 and forward… In writing do I not know which way I will go.

0 Likes

#18

always move forward…

1 Like

#19

The exe from the github, are not installing the dyf files…do you also have a normal zip…

in 2.0 it makes the folder but no data, there are files in the bin and extra folder…

for 1.3 it isn’t even creating the dyf folder

0 Likes

#20

Zerotouch means no dyf’s, just dll

1 Like

#21

As @Marcel_Rijsmus writes, I have no Custom Nodes using python. All my nodes are coded as ZeroTouch nodes in C#… you cant see the code behind the work being processed!

0 Likes

#22

got it…wasn’t looking carefull enough…
first impressing is very good…

0 Likes

#23

The AU Class I linked to is an overall demonstration of the new materials API introduced in Revit 2018.1, not just the visual appearance. :slight_smile:

Oh wow. That stinks. This was released with Revit 2018.1 and they are deprecating it? Do you have a link to something that discusses this?

This is what I had found: https://thebuildingcoder.typepad.com/blog/2017/08/revit-20181-and-the-visual-materials-api.html

0 Likes

#24

Always keep an eye on @Jeremy_Tammik :slight_smile:

0 Likes