hreich

Thank you deeleyer !!!

Thanks, just like you said, job done...

I found a file -clickabledata.lua in cockpit/scripts folder with this...How to modify default.lua file so i can assign those switches to my TM Warthog HOTAS? elements["PNT_402"] = default_3_positiontumb(("Anti-Collision/Strobe Lights, BOTH/OFF/A-COLL"), devices.LIGHTS, EFM_commands.strobeLight, 402) elements["PNT_404"] = default_3_positiontumb(("Tail Lights, BRIGHT/OFF/DIM"), devices.LIGHTS, EFM_commands.tailLights, 404) elements["PNT_405"] = default_3_positiontumb(("Wing Lights, BRIGHT/OFF/DIM"), devices.LIGHTS, EFM_commands.wingLights, 405) elements["PNT_406"] = default_3_positiontumb(("Formation Lights, BRIGHT/OFF/DIM"), devices.LIGHTS, EFM_commands.formationLights, 406) elements["PNT_401"] = default_2_positiontumb(("Landing/Taxi Light, ON/OFF"), devices.LIGHTS, EFM_commands.landingLight, 401) elements["PNT_403"] = default_2_positiontumb(("Nav Lights, FLASH/STEADY"), devices.LIGHTS, EFM_commands.navLights, 403) elements["PNT_400"] = default_springloadedswitch(("Exterior Lights Master Switch"), devices.LIGHTS, EFM_commands.lightsMaster, -1,0,1, 400)

Ta Taxi light/ landing light, exteenal nav light, anti collision light..and also master switch if it's not implemented

Does somebody know how to add option to map lights switch to HOTAS throttle, i dont see any light switch in options inside DCS?

ok, thanks

Does anybody know if is it safe to cutoff MJX plate - i found it a bit too long...https://winwingsim.com/view/goods-details.html?id=1125. It is made of high-pressure precision-cast aluminum alloy and i don't know if i can use metal saw to cut it around half of it's length?

Does it break MP?

Is there a simple tutorial how to setup WhisperAttack?

Does anybody know how to fix problems with bat1, bat2 and launch bar extend/retract not working when assigned to hotas? If i click switchews in cockpit it works,but when i map them to hotas it doesn't?null Also how to map hud brightness dial to rotary on hotas?

Strange one indeed

And here's a fix that works for me, so that fonts are readable in cockpit and on mfd export...you can change thickness and fuziness, but also set this to TRUE -- dbg_drawStrokesAsWire = true I have now clear fonts on mfd export and in game!! -------FONTS---------- fontdescription = {} dbg_drawStrokesAsWire = true HUD_thickness = 1.5 HUD_fuzziness = 0.5 MFD_thickness = 0.2 MFD_fuzziness = 4.1 null

Thanks, you are the live saver...I need them readable on my exported mfd for now

I had to change name of export screens - T-45 mod export names are:- MFDL MFDR So you need to put entries in your monitor config file Alternatively, you could change those names to LEFT_MFCD and RIGHT_MFCD and then they will export into the same positions as the A10, F18 etc. In the files VNAO_T45\Cockpit\Scripts\Displays\MFDL\Indicator\init.lua ----> try_find_assigned_viewport("MFDL") to try_find_assigned_viewport("LEFT_MFCD") and VNAO_T45\Cockpit\Scripts\Displays\MFDR\Indicator\init.lua ----> try_find_assigned_viewport("MFDR") to try_find_assigned_viewport("RIGHT_MFCD") I got it to export but fonts are unraeadable...

Managed export now, but fonts not readable