Arma2NET

[Scott_NZ]

Nlog.dll.nlog stores the configuration for logging, including where to log to. At the moment it should be ${specialfolder:LocalApplicationData}/ArmA 2 OA/Arma2NET Logs/Arma2NET.log (e.g. C:\Users\Scott\AppData\Local\ArmA 2 OA\Arma2NET Logs\Arma2NET.log)

[[KH]Jman]

Our server runs Windows server 2003

The closest directory path to your example on our server is:

C:\Documents and Settings\Administrator\Local Settings\Application Data

There is no "Arma2NET Logs" directory at that location or any other.

Arma2server does not create or save any data to that "ArmA 2 OA" folder path since all server logs are stored at the paths specified in the server's startup switches.

i.e in our server arma2oaserver.RPT, ArmA2-Public.cfg, Server-Public.cfg, Server-Public.log, mpStatistics.log are all stored in C:\Server-Public

[Scott_NZ]

Try "Arma2Net.Unmanaged" callExtension "" with BaseFunctionsPlugin loaded, it should return a string saying the version. If it does, it means Arma2NET probably loaded fine but the logging is failing.

[[KH]Jman]

I'll give it a go thx Scott.

---------- Post added at 11:06 ---------- Previous post was at 11:05 ----------

It's returning an empty string which indicates to me that Arma2NET is not loading on the dedicated. Any ideas?

On my local non dedicated i've got @Arma2NET loaded from Arma2 root folder (which works)
On the dedicated it's the same. Should I try moving it to expansions\beta ?

Edit. Tried that. No go.

.NET Framework 4 Client Profile is installed on the server.
A serverside "Arma2Net.Unmanaged" callExtension call results in an empty string.

[HeliJunkie]

@[KH]Jman:

Check if link points to "..\ArmA 2\Expansion\beta\arma2oa.exe" or "...\ArmA 2\Expansion\beta\arma2oaserver.exe"
AND the working dir points to "...\ArmA 2" (NOT to "...\ArmA 2\Expansion\beta).


Another hint is to copy it into both directorys.
* "Arma 2\@Arma2Net"
and
* "ArmA 2\Expansion\beta\@Arma2Net"

I love this mod. Infinite possibilities...

Regards
HeliJunkie

[[KH]Jman]

@[KH]Jman:

Check if link points to "..\ArmA 2\Expansion\beta\arma2oa.exe" or "...\ArmA 2\Expansion\beta\arma2oaserver.exe"
AND the working dir points to "...\ArmA 2" (NOT to "...\ArmA 2\Expansion\beta).

Our server is setup correctly.

Another hint is to copy it into both directorys.
* "Arma 2\@Arma2Net"
and
* "ArmA 2\Expansion\beta\@Arma2Net

Like I said I have tried both.

I believe the problem lies in the Arma2NET dlls somewhere when working off dedicated.

[Scott_NZ]

Well, I've run out of ideas. I haven't had a chance to test this on a dedicated server but Arma2NET shouldn't care about how it's being run.

[GossamerSolid]

Maybe callExtension functionality on dedicated servers is broken?

Somebody should test with another extension and see.

[[KH]Jman]

No callExtension is not broken on dedicated since as I've said jayarmalib works just fine on the serverside.
If someone else could do a test with Arma2NET on dedicated making sure its the __SERVER__ thats doing the "Arma2Net.Unmanaged" callExtension call that would be most helpful.

[.kju [PvPscene]]

What about creating a simple test package, so that other server owners can give it a go and report back.