iopad.blogg.se - Arma 3 debug commands

#Arma 3 debug commands code#

you can open the debug console by invoking the function DT_fnc_openDialog yourself or by default just press the minus key on the numpad to open it if you are in-game (key can be changed with DT_openKey variable in the debug.sqf file).

execute the debug.sqf from your init.sqf (at the very bottom it needs to be executed on the client and server).

open your description.ext file and include the debug dialog at the end of the file like this:.

copy the files RscDebugDialog.hpp and debug.sqf to your MPMission folder/PBO.

This is called in my service point refuel script, just as an example how it can be used (keep in mind the refuel script is client side and the log window on the server).

#Arma 3 debug commands code#

The code to log something in this example is pretty simple: format call DT_fnc_log

This ain't pretty but might help with script debugging a lot. The number in the bottom right cornor means 9 log entries filters out of 26 log entries overall. I've just added a simple log filter at the bottom, so you are able to filter the log entries to match a specified text in real time. You can enter any valid SQF script code in the large text field and then execute it locally on the client or via remote execution on the server, the result of the code is displayed in the lower text field (also the result of remote exec), just to simplify it so you won't have to add a log call or "hint str (1+2+3)" instead of just call "1+2+3" or whatever (and yes you can use this as a calculator lol) Here a simple screenshot what the debug dialog looks like atm: Is there any interest in tools like this? I can publish my stuff if any admin or script/mod developer may need something like this. That logging extension is optional of course but i use it for debgging myself, not on the live server. Also I have added my own little extension (DLL) for remote logging to a separate window on the server, so essentially if you want to log some debug info it pops up in that window and not in the RPT file. Using the same variables you can also clear or change the fields.I could not find any ArmA2 debug tool that worked with Epoch so I developed my own little script and dialog to do just some simple things like execute SQF code on the fly (client and server side via custom remote execution). ProfileNamespace getVariable "rscdebugconsole_watch4" ProfileNamespace getVariable "rscdebugconsole_watch3" ProfileNamespace getVariable "rscdebugconsole_watch2"

ProfileNamespace getVariable "rscdebugconsole_watch1" ProfileNamespace getVariable "rscdebugconsole_expression" These can also be access using profileNamespace getVariable with the following code: The debug console automatically saves each field as you go, Even after game restart.

Buttons (all of the close the pause menu and open some another window).

When code is taking too long to evaluate (>0.003s), the background turns orange and the value is not saved.

Performance Test - See: BIS_fnc_codePerformance.

Server - execute on server only using BIS_fnc_MP.

Global - execute on all computers using BIS_fnc_MP.

Local - execute on player's computer using execVM.

The expression can be executed by one of the following buttons:.

Value is saved when console is closed and restored again upon return.

The parameter has priority over the description.ext attribute.

1: Available in SP and for hosts / logged in adminsĪlternatively, you can add "\a3\functions_f\Params\paramDebugConsole.hpp" mission parameter, where server host / admin can set whether he'll allow debug console.

0: Default behavior, available only in editor.

If mission designer wishes to enable it elsewhere, he can achieve it using following Description.ext param:

The console is automatically available in missions running from editor. In editor map screen, you can open in by clicking on "Debug Console" button or using Ctrl+D shortcut.

While playing a mission from the editor, the console is immediately available in pause menu.