Thread: Compiling From Source

Hi,

sorry, the google code page is outdated

You need GCC 4.7 for compiling (C++11 features). You can pick it up for MinGW here: https://code.google.com/p/mingw-builds/downloads/list

Please initialize the iniparser submodule in the main vaultmp repository; it points to this commit: https://github.com/Foxtacles/inipars...bfa6ce8d28c95c

That should fix the linker errors.

(https://www.kernel.org/pub/software/s...submodule.html)

Yep, it's because of name mangling. The git submodule points to a commit of a branch in my iniparser repository which exports the functions as C functions.

You can follow the GitHub link I had in my last post. It is the correct commit; download it as ZIP or git clone / checkout, that will work

Success! I had messed up with which iniparser branch (or whatever they're called) I had put in the VaultMP source tree. Got it all working (well, short of vaultgui, but I don't want to mess with that yet).

Thank you for patiently working me through that.

Edit - D'oh, forgot I'd need vaultgui.dll to be able to try the new version.

Queue

For vaultgui, you'll need Microsoft Visual Studio Express 2010 (at least the MSVC compiler) and the DirectX SDK files.

However it should be no problem to change the meaning of:

https://github.com/Foxtacles/vaultmp...ultmp.cpp#L576

to not set DLLerror to true. Then, as long as you don't use server-side script functions to send chat messages, everything should still work fine.

That's actually the first thing I tried (commenting out the vaultgui.dll loading code), but I'm getting the following error when I try and run New Vegas (through VaultMP):
Could not enter CriticalSection object 0051E330, timeout of 5000ms reached (15CriticalSection)
and then New Vegas crashes after I click OK. I have no idea if this is due to other vaultgui.dll code that needs to be disabled, or if it's some other problem. I'm just starting to poke around the code in earnest.

VaultMP works (well, aside from known issues) if I use the Gary 1 binaries, for what that's worth.

Also, I think there might be a problem with Utils::FileOnly. When I synchronize with the server, it cuts off the first character of file names, so ''The Mod Configuration Menu.esp'' becomes ''he Mod Configuration Menu.esp'' and so on.

Edit - Yeah, I peeked inside the vaultgui suo file and saw it was VS2010. I'd prefer to avoid installing that, or I may set up a virtual machine just to host that so I don't pollute my pretty optimized Windows install with all the baggage VS2010 includes.

Queue

The CriticalSection error is (likely) due to me having introduced some nasty concurrency problem in one of my commits in the last 1-2 weeks. I believe I fixed it (it works fine for me), but you never know with this kind of error. Do you have the up-to-date sources from the repository?

I've been struggling with CriticalSection errors for long times. It's extremely hard to track down that bugs (mostly, deadlocks => lock timeouts)

Yep, Utils::FileOnly has that bug. I always forget to fix it Thanks.

Oh, and I also have to mention that there is a bug with the EquipItem function in New Vegas.
https://github.com/Foxtacles/vaultmp/issues/56

So if you are using the default vaultscript, which equips the PipBoy on startup, the game might just silently "close" itself. That's the stack overflow. I wasn't able to find the cause for it yet - it's a side effect of the engine function and occurs in some other thread of the executable. The stack overflow does not occur if the player is in any in-game menu; EquipItem works fine then. In Fallout 3, this problem doesn't exist at all.