[Amarant]

I write UDF, interpret it, hook it, everything works fine.

Than i interpret another UDF in the same case and 1st one disappear.

They can be same type or different type, it always does that. When I interpret an UDF, the one i had interpreted disappear.

Which is pretty problematic since i need UDF to set my boundary conditions and to initialize my flow field.

Is that a problem with FLUENT or am I doing something wrong?

[Amir]

Hi,

Store all of them in one file then interpret it.

Bests,

[Amarant]

Originally Posted by Amir

Hi,

Store all of them in one file then interpret it.

Bests,

It is a must to do so or a solution to my problem?

I find it easier to create individual UDF, especially for boundary, interior, initialization and so on.

Thank you for your fast response.

[Amir]

Originally Posted by Amarant

It is a must to do so or a solution to my problem?

I find it easier to create individual UDF, especially for boundary, interior, initialization and so on.

Thank you for your fast response.

If you want to interpret your UDFs, you have to use this procedure but if you compile these UDFs, you could use different files. (I recommend compile mode, its faster and doesn't have any restriction, but you need extra compiler)

Bests,

[Amarant]

Originally Posted by Amir

If you want to interpret your UDFs, you have to use this procedure but if you compile these UDFs, you could use different files. (I recommend compile mode, its faster and doesn't have any restriction, but you need extra compiler)

Bests,

Didn't know that.

By compiler you mean that i cannot write them in .txt but I need complier such as QT?

[Amir]

Originally Posted by Amarant

Didn't know that.

By compiler you mean that i cannot write them in .txt but I need complier such as QT?

There isn't any different in developing UDFs in both methods in which you need ".c" extension; in interpret mode, you can use internal compiler of FLUENT which has some restrictions in definitions of few classes; indeed, it reduces speed of implementation; on the other hand, there aren't these restrictions with compile method which require visual c++ compiler linked with FLUENT. For this purpose, it's better refer here.

Bests,

[Amarant]

Thank you very much, you helped me a lot !