c0ff

That's a client-side log. We need the server's one.

it would be nice to see the log from the server

user mods should be installed into Saved Games/DCS/Mods/... in this case that is : Saved Games/DCS/Mods/tech/farpmod/

1.5.4.54596.121 is live now

1.5.4 can't normally work on Steam because of a bug, that's why it was delayed.

Just FYI, internal version now supports IPv6 for LAN servers. In order to support IPv6 over the Internet there is still work to do with logins and the master server.

Due to a build configuration oversight the campaigns were not signed in the build.

A bug. Thanks for the report.

Very important.

Not yet.

Да.

IPv6 is being worked on. No ETA, however.

The math for calculation of position of remote aircraft was completely rewritten. No more teleportations/crazy oscillations. Object should move much more predictably.

Yaw = [0, 2*Pi)

positions are 64-bit double float.

Mostly C++, with UI logic and other non-performance-critical stuff in Lua. Internal tools - mostly Python with some C#.

Wow, what a find! Thank you for posting this, I'll try to make a workaround in the updater itself.

Yes. (Technically, they return nothing, which in most cases is the same as nil).

From the updated docs: In multiplayer the availability of the API on clients depends on the server setting. The calls to check export capabilities: Export.LoIsObjectExportAllowed() -- returns the value of server.advanced.allow_object_export Export.LoIsSensorExportAllowed() -- returns the value of server.advanced.allow_sensor_export Export.LoIsOwnshipExportAllowed() -- returns the value of server.advanced.allow_ownship_export These calls are only available on clients when LoIsObjectExportAllowed() is true: Export.LoGetObjectById Export.LoGetWorldObjects These calls are only available on clients when LoIsSensorExportAllowed() is true: Export.LoGetTWSInfo Export.LoGetTargetInformation Export.LoGetLockedTargetInformation Export.LoGetF15_TWS_Contacts Export.LoGetSightingSystemInfo Export.LoGetWingTargets These calls are only available on clients when LoIsOwnshipExportAllowed() is true: Export.LoGetPlayerPlaneId Export.LoGetIndicatedAirSpeed Export.LoGetAngleOfAttack Export.LoGetAngleOfSideSlip Export.LoGetAccelerationUnits Export.LoGetVerticalVelocity Export.LoGetADIPitchBankYaw Export.LoGetTrueAirSpeed Export.LoGetAltitudeAboveSeaLevel Export.LoGetAltitudeAboveGroundLevel Export.LoGetMachNumber Export.LoGetRadarAltimeter Export.LoGetMagneticYaw Export.LoGetGlideDeviation Export.LoGetSideDeviation Export.LoGetSlipBallPosition Export.LoGetBasicAtmospherePressure Export.LoGetControlPanel_HSI Export.LoGetEngineInfo Export.LoGetSelfData Export.LoGetCameraPosition Export.LoSetCameraPosition Export.LoSetCommand Export.LoGetMCPState Export.LoGetRoute Export.LoGetNavigationInfo Export.LoGetPayloadInfo Export.LoGetWingInfo Export.LoGetMechInfo Export.LoGetRadioBeaconsStatus Export.LoGetVectorVelocity Export.LoGetVectorWindVelocity Export.LoGetSnares Export.LoGetAngularVelocity Export.LoGetHeightWithObjects Export.LoGetFMData These functions are always available: Export.LoGetPilotName Export.LoGetAltitude Export.LoGetNameByType Export.LoGeoCoordinatesToLoCoordinates Export.LoCoordinatesToGeoCoordinates Export.LoGetVersionInfo Export.LoGetWindAtPoint Export.LoGetModelTime Export.LoGetMissionStartTime These are not available in the *GameGUI state: -- Export.LoSetSharedTexture -- Export.LoRemoveSharedTexture -- Export.LoUpdateSharedTexture

1. Yes 2. Yes. 3. allow_object_export=false, allow_sensor_export=false, allow_ownship_export=true

You've nearly hit the YAML notation :) Unfortunately, it does not work this way. For the unit database, for example, it makes no sense to check one or several files, you have to check all of them. Currently, only ED can generate manifest files. At this time I can't add anything to what I've said earlier on the subject. As for Export-mods, the current internal implementation has 3 on/off options regulating the Export API: allow_object_export -- getting info about world objects allow_sensor_export -- getting radar/targeting info allow_ownship_export -- getting instruments/fm-data for the ownship.

I've thought about allow_ownship_export breaking the homecockpits... It is possible to split this option into several ones with finer granularity. Any ideas?

Sure. Current policy is that server has the same freedom as the single-player mode. The present allow_object_export option does affect only clients. allow_ownship_export will work the same way.

Guys, please, calm down. One of the points of the new IC is to make MP a fair play. This mod, which I was unaware of before, runs outside of the scope of the IC. It uses the Export API. We have a server-side option to allow/forbid world objects export, but no option to control the ownship export, just because it was assumed to be safe. So, talking about LEAVU-style mods, this is a simple question of adding a server-side option to allow/forbid ownship export. If I understand you correctly and this is what you want - the option will be added soon - it is relatively simple to implement.

Err, not yet. The wording is not correct. The tool is not yet available, mostly because the game still needs some changes for the tool to be useful. I fixed the post. Thanks.