Interior Lamp

[DeputyLOL]

How to get lamp to illuminate area around it when it is activated.

[Alexustas]

in my Knobs used "CUSTOM_ALCOR_BACKLIGHT_ON"

// Backlight -------------------------------------------------------------------------------

MODULE { name = JSIVariableAnimator refreshRate = 10

VARIABLESET 
{   
    coloredObject = LabelObj
    passiveColor = 0,0,0,255
    activeColor = 180,180,180,255
    variableName = CUSTOM_ALCOR_BACKLIGHT_ON
    scale = 0,1
    threshold = 0.1,1.1

}   
VARIABLESET 
{
    coloredObject = MarkObj
    passiveColor = 0,0,0,255
    activeColor = 180,180,180,255
    variableName = CUSTOM_ALCOR_BACKLIGHT_ON
    scale = 0,1
    threshold = 0.1,1.1
}   

}

[Alexustas]

do you have any other "B-Knob" props in your scene and are they workig properly?

[DeputyLOL]

yup. I have the 3 point one and that's working.

[DeputyLOL]

I found this in the log. Is this unrelated? [WRN 18:10:04.652] HighlightingSystem : Multiple Highlighter components on a single GameObject is not allowed! Highlighter has been disabled on a GameObject with name 'model'.

[Alexustas]

"would that affect it?"

I'm not sure. but it can be

[Alexustas]

 I found this in the log. Is this unrelated?

no, it's kind of stock bag, i suppose.

part are highlighted when the mouse cursor over them. and squad have some problems with this effect

[Alexustas]

i think, it will be better temporary to remove whole "Backlight" block from dimmer cfg

[DeputyLOL]

ok..

[Alexustas]

and when your monitors come alive, displays the value of variables "PERSISTENT_LD_FLOODInput", "CUSTOM_POWERTOGGLE" and "MATH_FLOODLIGHT_BRIGHTNESS"

[DeputyLOL]

I just did. MATH_FLOODLIGHT_BRIGHTNESS stayed at 0. That's the problem!

[Alexustas]

and values of PERSISTENT_LD_FLOODInput and CUSTOM_POWERTOGGLE ?

[DeputyLOL]

they worked correctly. CUSTOM_POWERTOGGLE went from 0 to 1. PERSISTENT_LD_FLOODInput went from 0 to 10.

[DeputyLOL]

I'm going to check the log for any mention of it.

[DeputyLOL]

log didn't have anything. But it says that RPM recognised and accepted MATH_FLOODLIGHT_BRIGHTNESS.

I'm out of ideas.

[Alexustas]

so, your "CUSTOM_POWERTOGGLE" is "1", "PERSISTENT_LD_FLOODInput" is more then zero, but the result of multiplying this two numbers is always zero?

[DeputyLOL]

yup

[DeputyLOL]

I think i know what is wrong. there are multiple MATH_FLOODLIGHT_BRIGHTNESS in other switches. I think its reading it from one of them.

[Alexustas]

can you upload your dimmer config?

[Alexustas]

"I think i know what is wrong. there are multiple MATH_FLOODLIGHT_BRIGHTNESS in other switches."

Yes, maybe it's not quite right, but I have it still works

[DeputyLOL]

i only used one. The problem is that there are more than one MATH_FLOODLIGHT_BRIGHTNESS. The game reads the first one it sees and uses that. That's why it stays at 0. I got to go for a minute.

[Alexustas]

I will collect all MATH_ variables in a separate file, but I do not think that is what is causing the problem. Because MATH_FLOODLIGHT_BRIGHTNESS is the same in all file and uses the same sources, and there no matter in what config this variable will be calculated. result always will be the same

[Alexustas]

i've collect all five MATH variables in one cfg and remove all MATH blocks from Knobs config DL: https://www.dropbox.com/s/zn7gxk6hhbwt5wy/ASET_B-Knob-LightDimmer.zip?dl=0

[Alexustas]

if only, you has edit only one knob config and MATH setup and do not edit all other ... quite possible the LAST MATH setup was used by RPM and not the fact that it was the one you were editing

[Alexustas]

... and now I'm pretty sure that's how it happened

[Alexustas]

oh .. I found another mistake, sorry

[Alexustas]

DL: https://www.dropbox.com/s/zn7gxk6hhbwt5wy/ASET_B-Knob-LightDimmer.zip?dl=0

[DeputyLOL]

testing now

[Alexustas]

finaly, i make test of ALL dimmers and lights

[Alexustas]

i found yet another typo (( in the CUSTOMs config file PERSISTENT_LD_ENGINEERInputt - delete last "t", please

All works propperly

[DeputyLOL]

ok

[DeputyLOL]

it works. but it doesn't look like what I was intending. I assume there is no way to make light not pass through the cockpit model.

Could you make a light that has a very short range and is designed to light up the MCP.

[Alexustas]

in ksp only sun cast shadow

[Alexustas]

all other lights shine through any meshes

[DeputyLOL]

oh well... i can use the lights for other things.

[Alexustas]

to illuminate a wide and a narrow part, it is desirable to use something like LED-strips, ie many small dim lights

[Alexustas]

I would advise you to use one or two spotlights to illuminate the entire dashboard, including MCP

[Alexustas]

using a lot of lights for one panel only - it's too unaffordable luxury for KSP ((

[DeputyLOL]

yeah... my computer does have a reputation of not being fast.

[Alexustas]

in my version of MK-1-2 i'm using only 3 lights at all. in the ALCOR - 5 lights

[Alexustas]

yeah... my computer does have a reputation of not being fast.

My "main" computer is 3770K, overclocked to 4.5 Ghz and i have some lags too (((

[DeputyLOL]

O_O

[Alexustas]

blame squad ))

[DeputyLOL]

Is it possible to use the brightness switch with the screens? So they have an adjustable brightness.

[Alexustas]

Why not ) You can replace "power-on" variable to some "display brightness" persistent variable and change variable range.

something like that:

MODULE 
{
    name = JSIVariableAnimator
    refreshRate = 10
    VARIABLESET
    {
        coloredObject = ScreenObj
        passiveColor = 0,0,0,255
        activeColor = 255,255,255,255
        variableName = PERSISTENT_CMD_MIP_DISP_BRGT
        scale = 0,10
    }
}

[DeputyLOL]

Beautiful!