August 11, 20187 yr Hey, I have the issue that my F/O doesn't set the flood lights anymore. It worked some versions of the MD before, but now the lights are set during the cockpit preparation flow, but not in flight. Here is what the INI file looks like.. maybe there's a hickup in there? [FS2CrewData] Accent=8 Volume=2 USBDevice=0 AES=1 Doors=1 GateDep=1 GateArr=1 PbUnits=1 PbDist=25 TA=100 TL=100 ArrElev=0 UGCX=1 VOICE=1 Lights10K=1 The last entry was added by me, however it makes no difference.. Best, Matthias Edited August 11, 20187 yr by MatzeH84 Regards. Matthias Hanel MilViz Beta Team
August 12, 20187 yr Commercial Member Hi Matthias, You can't add entries to the ini file. Are you saying the flood lights are not consistent with the manual and any subsequent change log? B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
August 12, 20187 yr Author The flood lights are set by the FO on ground, but are not touched while in the air. So he/she won't turn them off passing 20k, or back on in the descend. I added he entry because you stated: Quote -As per a user request, if you want the flood lights to come on/off at 10,000 feet instead of 20,000 feet, do this: C:\Users\****YOUR USER NAME****\AppData\Roaming\FS2Crew2010\Versions\MadDogRB\SavedData\FS2CrewData.ini Open FS2CrewData.ini with notepad. Make Lights10K=1 Then Save. However, as there was no Lights10K entry before, I added it. Version installed is latest Maddog and your 1.5. Regards. Matthias Hanel MilViz Beta Team
August 12, 20187 yr Commercial Member Hi Matthias, Oh I remember that now. I'm getting old 🙂 I'll check it out and and add it to the list of things to check for the next update. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
August 12, 20187 yr Author Funny enough, once I posted it, it currently works again, and the FO switched off the floods at 10k with the entry added. The last 5 flights when it didn't work I tried the F/O takeoff, but took control before finishing the climb check, maybe something got stuck there.. maybe there could be an internal reset logic once you state 'my controls'. I guess this was the culprit. Regards. Matthias Hanel MilViz Beta Team
Archived
This topic is now archived and is closed to further replies.