I tried to make a module according to the instructions, and generated the dll file and placed it under the file. It can be pulled out in the gui, but the run failed and the server listing module did not have my module.
Sometimes the DLL does not get copied automatically. Find where the DLL was actually copied to and then copy the DLL to the AWE Server folder. Check the Build output window in Visual Studio. It looks like your file is there though.
After this, restart AWE Server. Confirm that the new module shows up in the list. If so, proceed to use it in Audio Weaver Designer.
I am sorry to hear you are having issues. I can see you have transferred the Dll file to the correct location. Can you please try closing the AWE Server and reopening again? It might happen that the server was unable to pull the Dll file of the new module.
I am sorry to hear that. As my colleague mentioned, I am sure you must have checked but to be certain if the output file path in Visual Studio also points to the same folder? Can you please close the server, rebuild the project in Visual Studio , verify the Build is Release and Win32. After rebuilding the project in VS, reopen the AWE Server again. You can also press the button "Refresh Target Info" on Designer as it pulls the latest module information from the AWE Server.
Hope this helps. If you are still having issues please let us know.
11:51am
Hi @HaoXiang.Xu,
Sometimes the DLL does not get copied automatically. Find where the DLL was actually copied to and then copy the DLL to the AWE Server folder. Check the Build output window in Visual Studio. It looks like your file is there though.
After this, restart AWE Server. Confirm that the new module shows up in the list. If so, proceed to use it in Audio Weaver Designer.
Let me know if you continue to face any issue.
Thanks,
Gary
11:53am
Hi Xu,
I am sorry to hear you are having issues. I can see you have transferred the Dll file to the correct location. Can you please try closing the AWE Server and reopening again? It might happen that the server was unable to pull the Dll file of the new module.
Thanks,
Karishma
8:54pm
I restarted the server and computer many times but still have this problem
1:56am
Hi Xu,
I am sorry to hear that. As my colleague mentioned, I am sure you must have checked but to be certain if the output file path in Visual Studio also points to the same folder? Can you please close the server, rebuild the project in Visual Studio , verify the Build is Release and Win32. After rebuilding the project in VS, reopen the AWE Server again. You can also press the button "Refresh Target Info" on Designer as it pulls the latest module information from the AWE Server.
Hope this helps. If you are still having issues please let us know.
2:15am
'The files I generated are placed here
D:\AWE Designer 8.D.2.3 Pro\CustomModules\test_new_module\x64\Debug\TestNewDll.dll' 不同，因此已忽略指示詞
1>TestNewDll.vcxproj -> D:\AWE Designer 8.D.2.3 Pro\CustomModules\test_new_module\x64\Debug\TestNewDll.dll
1>..\..\..\x64\Debug\TestNewDll.dll
It looks different from the file generation location you mentioned. How can I correct it?
2:15am
'The files I generated are placed here
D:\AWE Designer 8.D.2.3 Pro\CustomModules\test_new_module\x64\Debug\TestNewDll.dll' 不同，因此已忽略指示詞
1>TestNewDll.vcxproj -> D:\AWE Designer 8.D.2.3 Pro\CustomModules\test_new_module\x64\Debug\TestNewDll.dll
1>..\..\..\x64\Debug\TestNewDll.dll
It looks different from the file generation location you mentioned. How can I correct it?
2:23am
Thanks I changed my compilation mode to Release and Win32