DllBind and Packaging ...

[OneGoodCop]

I have made heavy use of DLLBind for a project but the Unreal Frontend doesn't seem to run the functions. It works fine on PlayOnPC, but the Frontend doesn't find them. I have found a few threads on this but they are older and wondered what the current state of this problem is and how others have worked around this.

[Chosker]

I'm not even sure if the UnrealFrontent uses the same directory structure for DLLBind-related stuff, but is there a chance that the dll's are not being included? if you edit the UDKGame/Build/CookerSync_Game.xml you can make the packaging/installer include extra files

[OneGoodCop]

Thanks ... I will try that.

[TechElv]

Nice information @chosker thanks.

[OneGoodCop]

Darn ... I tried a few different entries in a few different sections but couldn't get it to work .. anyone else have success with it?

[OneGoodCop]

Seems as though the dllBind .dll's do need to be copied into the Win32/UserCode folder in order for them to function. Am still having a problem getting all of my my StaticMeshes to show up in my final packaged and installed distributable though. I spawn many meshes at runtime ... some appear as normal, but some simply are not there. Is there anything that would prevent certain meshes from being packaged by the Unreal frontend even though they work fine during PlayOnPC??

[Chosker]

well I might be wrong but if those meshes are not directly saved into a level that's cooked, or used directly by some class (ie. the Pawn), or flagged as AlwaysCook, they might not be included in the package at all

[OneGoodCop]

Thanks Chosker ... Am at work now but will look into your suggestions. I think the missing meshes are in a package all by themselves. They are neither saved in the level nor directly referenced by a class. I am not sure what the AlwaysCook flag is or where to find it but I will look into it. It sounds like a promising lead. Thanks for your help.

[Chosker]

there's a category inside one of the .inis that's called PackagesToAlwaysCook (probably DefaultEngine.ini), and there you can put the names of the packages you want. every time you do some changes to that package and save in the editor though, you'll get a warning saying how it takes up memory and blah blah
either that, or make a test level, place all of your meshes on it, and include it in the cooked levels list

[OneGoodCop]

Thanks Chosker. I will do that and post the results. I have a feeling it will solve my problem. Thanks again.