Hi David,

Thanks for sharing these lightings. Is it possible to use these for the 737-900s as well and if so, what should I do to accomplish this? (I tried to copy the .ini file to the appropriate -900 folder tbut this doesn't seem to do the trick  )

 

Edited November 12, 20187 yr by hvw

Hans there is no trick it will not work with the 600-700 or the 900. The reason why is the Cockpit is in a different place. Sorry.

Just now, Nyxx said:

Hans there is no trick it will not work with the 600-700 or the 900. The reason why is the Cockpit is in a different place. Sorry.

Thanks, David

 

Tried it last night, looks great! Thank you!

3 hours ago, Johnny19 said:

Tried it last night, looks great! Thank you!

Thank you, I updated it late last night Ivan, the FMC bloom is now on its own light not tied to the main panel anymore.

Enjoy!

44 minutes ago, Nyxx said:

Thank you, I updated it late last night Ivan, the FMC bloom is now on its own light not tied to the main panel anymore.

Enjoy!

I'll try it now, dusk flight form EDDK to LICJ with Ryanair :) Thank you!

On 11/12/2018 at 9:48 AM, hvw said:

Hi David,

Thanks for sharing these lightings. Is it possible to use these for the 737-900s as well and if so, what should I do to accomplish this? (I tried to copy the .ini file to the appropriate -900 folder tbut this doesn't seem to do the trick  )

 

 

On 11/12/2018 at 11:25 AM, Nyxx said:

Hans there is no trick it will not work with the 600-700 or the 900. The reason why is the Cockpit is in a different place. Sorry.

There is a „trick“. But considering the amount of lights this is a bit of work, you have to costruct it a bit, but why not?..

please note, I am away from my computer so this comes out of my head, handle with care. And make backups first.

Go to your 737-800 aircraft.cfg. Look for the [views] section, there are 3 values seperated by commas. Those are the location of the point of view. I don‘t recall which one is the value for the „forward/backward“ position (sry, my english has suffered since school). 

Now also open the aircraft.cfg of the 737 version you want to use (let’s assume the -700) with the spotlights and also go down to views. Compare the values, 2 of them should be the same, one should be different. That‘s your value. The difference between the two values of the -800 and -700 is the important value you need to modify the spotlights.ini. Write it down.

 

now use a copy (!!) of Nyxx’ spotlights.ini and open it with the spotlights manager. It works interactively so check out which value moves the light balls backwards (as the 737-700 is shorter than the -800. now, from this original -800 value substract the value you calculated before from the cfg files. Do this for every light and you should get the same lighting for the -700. 

Great. Thanks, Marc. I might give it a go sometime in the near future.

 

38 minutes ago, hvw said:

Great. Thanks, Marc. I might give it a go sometime in the near future.

 

sure.. I THINK both the cfg and the manager work with the values as meters but it might be the case that in the cfg it's feet. I am not totally sure about it, but the windows calculator can easily convert it.

Now available here at AVSIM.

https://library.avsim.net/download.php?DLID=207777

4 minutes ago, Nyxx said:

Now available here at AVSIM.

https://library.avsim.net/download.php?DLID=207777

Thanks a lot, David

 

Daivid,

 

Just for your information. The FSlabs 738 WL lights in combination with Aerosoft's Cologne (EDDK) scenery seems to be a not all that happy combination. It so far happened twice to me that while approaching EDDK and using your .ini file, P3D aborted. 

Doing the same approach with the fslights being uninstalled, all went fine.

 

That's very odd my first flight with the new lights was from EGSS to EDDK landing at night, no problem and then a dawn flight from EDDK to EGSS again no problem.

After that EDDK to LIME dusk to night and then LIME to EDDK landing at Dusk, no problem, I don't know how or why FSLSpotlight would cause a problem like that, nothing on their forums from anyone having any problems like your reporting. Sorry. No idea why. 

I've been using spotlight ever since the FSL A320 never had one crash with the spotlight being the problem. All the lighting in the FSL A320/319 is the same lighting system but built to use the switchers.

What did the windows crash report say? 

EDDK has had updates since it came out, are you up to date? New scenery and all that. It's a very nice airport.

Edited November 15, 20187 yr by Nyxx

David,

Thanks. I just tried a night approach to EDDK (P3D's native version) (EDDV-EDDK) with the FSLights (yours) enabled, no problem at all. Later today or tomorrow I will do a full night flight into EDDK using your fsligh.ini again and see what happens.

Hope it goes well just make sure EDDK is up to date. I don't have the airport DL turned ON. I have it and all my airport DL OFF. I always think that's hard on a system on approach. Also with all the landing lights on with DL ON with the NG is asking a lot. Only FSL have found a trick to have almost zero impact with aircraft DL ON.

Edited November 15, 20187 yr by Nyxx