Page MenuHomeFeedback Tracker

Headless Client startup problem
Closed, ResolvedPublic

Description

rpt log:

17:03:39 Strange convex component327 in a3\structures_f\research\dome_big_f.p3d:geometryFire
17:03:39 Error in expression <ffectCreate ["ColorCorrections", 1600];
BIS_TotDesatCC ppEffectAdjust [1,1,0,[0,>
17:03:39 Error position: <BIS_TotDesatCC ppEffectAdjust [1,1,0,[0,>
17:03:39 Error Nicht definierte Variable in Ausdruck: bis_totdesatcc
17:03:39 File A3\functions_f\Feedback\fn_feedbackInit.sqf, line 56
17:03:40 Error in expression <tOxygenRemaining player;

BIS_SuffCC ppEffectAdjust [1,1,0,[0.0090>
17:03:40 Error position: <BIS_SuffCC ppEffectAdjust [1,1,0,[0.0090>
17:03:40 Error Nicht definierte Variable in Ausdruck: bis_suffcc
17:03:47 Client: Object 7:0 (type Type_91) not found.

Details

Legacy ID
4018448294
Severity
None
Resolution
Open
Reproducibility
Always
Category
Server
Steps To Reproduce

Start HC
arma3server.exe -client .....

Event Timeline

shukari edited Steps To Reproduce. (Show Details)May 4 2015, 5:13 PM
shukari set Category to Server.
shukari set Reproducibility to Always.
shukari set Severity to None.
shukari set Resolution to Open.
shukari set Legacy ID to 4018448294.May 8 2016, 12:01 PM
Bohemia added a subscriber: Dwarden.May 4 2015, 5:13 PM

I also have this every single time HC is started

15:47:11 Error in expression <ffectCreate ["ColorCorrections", 1600];
BIS_TotDesatCC ppEffectAdjust [1,1,0,[0,>
15:47:11 Error position: <BIS_TotDesatCC ppEffectAdjust [1,1,0,[0,>
15:47:11 Error Undefined variable in expression: bis_totdesatcc
15:47:11 File A3\functions_f\Feedback\fn_feedbackInit.sqf, line 56
15:47:11 Error in expression <tOxygenRemaining player;

BIS_SuffCC ppEffectAdjust [1,1,0,[0.0090>
15:47:11 Error position: <BIS_SuffCC ppEffectAdjust [1,1,0,[0.0090>
15:47:11 Error Undefined variable in expression: bis_suffcc

Adam added a comment.May 5 2015, 9:22 AM

Hello, i'm unable to reproduce this issue. Could you please provide more info? Thanks.

start arma3server.exe with -client

allready a problem

I get this issue as well on 1.54. It might happen only after connecting to a server with a mission running or when starting a mission. Happens for me on both Linux and Windows servers and headless clients.

Also it seems to be mostly harmless as everything else continues to work normally.

dedmen closed this task as Resolved.May 18 2020, 11:08 AM