Caldred
Member-
Content Count
6 -
Joined
-
Last visited
-
Medals
Community Reputation
10 GoodAbout Caldred
-
Rank
Rookie
-
I had a question about packing pbo's, do I have to have my addon source directory in the P drive at for example P:\MyServerOnlyAddon? When I pack from other locations (like C:\Workspace\MyServerOnlyAddon) my dedicated server doesn't seem to load the addon pbo's correctly, it can't find the functions/script paths correctly. It's not a big deal as it still works fine when I use PboProject and have my projects at P drive, was just curious if there was a way to build from a separate location as I think I've been able to build other addons from ohter locations besides P drive (maybe my addon config is messed up or something). Also wanted to say thank you for your Arma3P.cmd file, works really good for me and really makes it easy when they update the BI Tools to a new version, so thank you!
-
Loading Server Only Addon
Caldred replied to Caldred's topic in ARMA 3 - MISSION EDITING & SCRIPTING
Thanks, that got rid of the script not found error. So something interesting I found...when I build my addon with the BI Arma 3 Tools addon builder (the one that you download from Steam) it seems to not work, or at least it seems to handle the file paths differently. When I build my addon with the Eliteness pbo tool then everything seems to work properly. For example I was adding functions to my addon using the CfgFunctions {} in the config.cpp, according to the Wiki entry for CfgFunctions as far as directory structure, and when I packed my pbo using the BI addon builder, it was not able to locate any of the function files correctly. But when packed using Eliteness everything worked as according to the Wiki. I probably have my Addon Builder setup wrong or need to get the latest version from Steam, not sure, but maybe this will save some people the headaches I went through. -
I have a function library (addon I guess?) that I just want to be loaded by the dedicated server, not by clients, because it calls to an externall DLL using the RVExtension function. I'm stuck with how to load my addon on the server when the mission file is initially run/processed by the dedicated server. I have this basic code in my mission init.sqf file, so when the server runs this, it is supposed to load my addon init.sqf: X_Server = false; if (isDedicated) then { X_Server = true; }; if (X_Server) then { [] execVM "\ServerLibraryTest\init.sqf"; }; Whenever I test my mission in multiplayer on the dedicated server I get a script error: cannot find script "\ServerLibraryTest\init.sqf". Maybe I'm either not getting the addon loaded onto the server properly, or maybe I am specifying the path wrong in my call to the execVM call? I'm loading the addon pbo (built with the addon builder tool) to the server at Arma3Root\@ServerLibraryTest\addons\ServerLibraryTest.pbo, and the mission file I export to multiplayer and copy to the server MPMissions folder. My addon is really basic it just has a config.cpp and then the init.sqf which just initializes a couple variables. Also I load the addon when I start the server with the -mod=ServerLibraryTest option, and the RPT log file doesn't show any errors when server is starting, it shows that the addon is loaded. Not sure what I am missing, maybe I'm going about this wrong as far as separating the server functions into their own library that is separate from the mission pbo? Thanks for your help!
-
Robin was a legend! He was in so many of my favorite movies. RIP.
-
Looking forward to learn the ways of ArmA modding! Well met.
-
AddonBuilder instantly crashes when i press PACK
Caldred replied to olli_'s topic in ARMA 3 - BI TOOLS - TROUBLESHOOTING
If you click on the "Options" button in AddonBuilder, I had to change my paths to CfgConvert, Binarize, FileBank, DsSignFile. By default they were pointing to the Arma 3 folder, instead of Arma 3 Tools which is where these files are located by default if you install through Steam. Not sure if that's your problem but that's what I got, and I got that same error, just crashed to desktop.