The UDF library you are trying to load (libudf) is not compiled for 3D on the current
 

Hello Everyone,
As i am New to UDF Scheme coding and Compiling option.SO i need you guys to help me out as i have tried almost every post related to my problem but i did not get it.Thanks
My problem is to Link the C compiler with Fluent.
My system parameters are,
Windows 7 (64 Bit)
Fluent 14.5 (64 Bit)
Fluent 15.0.7 64 Bit

About the compilers i have checked almost every version of the Microsoft visual studio and Windows SDk but every time i got the same problem which pictures i have posted.I have set the path inside the environment variables also i have started fluent from VS command prompts and SDK command promts.I also Run fluent in serial and parallel mode but results were same.
Can any body can suggest me as i am totally exhausted with this process again and again.
I have used VS 2008 SP1,VS 2010 Express and Ultimate,VS 2012 Ultimate with SDK 7.1 and 2.0 Net framwork SDK 2.0 for 64 Bit.
I have also kept my case and data file and Source code file in same folder that is working director but results are same.

PLEASE GUYS HELP ME OUT I NEED YOUR HELP.
Error is as following:
Error: The UDF library you are trying to load (libudf) is not compiled for parallel use on the current platform (win64).

The operation completed successfully.

C:\working\libudf\win64\3d_host\libudf.dll
Error Object: #f

same here!

See here for more info.

Hi, I face the same problem too. Could I know how you solve it?

I solved it by changing serial to parallel when I started fluent

hahaha, nice joke. Happy New Year

No.It is not a joke.I really made that mistake.
Your Happy New Year is the first one I heard.
Anyway,Happy New Year!:D:D:D

switching between parallel and single solver will NOT solve problems with compiling.

Author of thread is trying to LOAD precompiled library instead of compiling it.

What you did is just LOAD precompiled for parallel solver library using parallel.

However, usually you can compile that library for single solver to without any changes in source code.

Your comment may confuse users in future.

Best regards

Sorry, I didn't make my point clear.
I ran a case and compiled library successfully using parallel on my laptop.
Then I copy that case/dat/c files, all of them, to my computer and then I started fluent using serial, it failed. At last switching between parallel and single solver solved my problem.:(

The original post dates back to 2015, but obviously it shows up in some searches, so I might as well spell out the steps you need to get a UDF to run in Fluent:
(1) Set up the compiler.
(2) Start Fluent in the correct working directory.
(3) If the libudf is not already compiled for the current Fluent session, make Fluent compile it.
(4) Make Fluent load the libudf.
(5) Hook in the UDF to wherever it is intended to go.

Some comments on each step:
(1) This can be a complicated process, but you only need to do it once for a specific system. (Actually, the last few times I have done it on Windows, it was not complicated at all. I used "Visual Studio 2012 Express", and the installation set up all the environment variables for me. No need to launch from SDK prompts etc.)
(2) Selecting the correct working directory at launch time is much easier than trying to navigate to it later. (You would not think that Fluent would be so inflexible, but it really is. See also the important advice to avoid spaces in the whole path to your working directory.)
(3) As Jennifer Von has pointed out, if you have compiled it on one operating system for Fluent in parallel and single-precision, then that does not mean that you have compiled it for any other combination (operating system, parallel/serial, single/double).
(4) Compilation and loading generally happens automatically when you re-open a working case. Because of this, I would not recommend having more than one libudf in a directory. (This used to be OK, but not any more.) Also, there is a nasty trap here: if you have an already-compiled libudf, and then you try to re-compile but fail (for example, due to compilation errors), then you might still be able to load the old libudf. So, whenever you compile, you *must* scroll back through the messages to check whether it has worked. This is tedious and error-prone.
(5) Note a small distinction between the libudf (possibly more than one UDF, defined by a collection of source files) and a UDF inside it.

For each of those steps, consult the help files -- but maybe it helps to know that these are the steps to follow.

Change Encoding
 

Change your format to .c with an encoding of Western Euro (ISO) - Codepage 28591.

That worked for me with version 17.1

I have tried，but it does not work.It has the same problem.
 

I have tried，but it does not work.It has the same problem.

Error: The UDF library you are trying to load (libudf) is not compiled for parallel use on the current platform (win64).\n\n???????????
\n\nC:\CFD\libudf\win64\2ddp_host\libudf.dll
Error Object: #f

See here for answers. Seriously.

Take care for the name of your file
 

Please, NAME your c file WITHOUT any spacing

EX: Good file.c (wrong ) ...... Good_file.c (correct )

It may help you guys

Yes，got it，thank you