There is some news here. Looks like we are screwed for now as far as AI Aircraft is concerned.
Lights and draw distance as well. At 4K ultra settings, you can’t see any planes or lights until they are very close.
So proprietary now? Then fix your bloody lights!
It looks like they nuked something on the [ELECTRICAL] side of things. I use 3rd party models for AI and the ones with old pre-MSFS values seem to have working lights while the models with modern settings don’t.
Can you share the [ELECTRICAL] settings before the update? I’d like to try them on current AI aircraft to see if it would fix it…
These are old prehistoric values from a 3rd party model but the lights are working. Don’t forget to disable the modern stuff in your system file.
[ELECTRICAL]
; LEGACY
max_battery_voltage = 24 ; ###
generator_alternator_voltage = 28 ; ###
max_generator_alternator_amps = 60 ; ###
electric_always_available = 1 ; ###
flap_motor = 0, 5, 17 ; ###
gear_motor = 0, 5, 17 ; ###
autopilot = 0, 5, 17 ; ###
avionics_bus = 0, 5, 17 ; ###
avionics = 1, 5, 17 ; ###
pitot_heat = 0, 2, 17 ; ###
additional_system = 0, 2, 17 ; ###
marker_beacon = 1, 2, 17 ; ###
gear_warning = 0, 2, 17 ; ###
fuel_pump = 0, 5, 17 ; ###
starter1 = 0, 20, 17 ; ###
light_nav = 0, 5, 17 ; ###
light_beacon = 0, 5, 17 ; ###
light_landing = 0, 5, 17 ; ###
light_taxi = 0, 5, 17 ; ###
light_strobe = 0, 5, 17 ; ###
light_panel = 0, 5, 17 ; ###
So should I take out everything under [ELECTRICAL] and replace it with what you mentioned? Or should I just add on what you mentioned without deleting stuff?
You can create a back up file and just replace the stuff or you disable every line with a ; in front of it.
Please elaborate on the “modern” stuff in the “system file” please.
Every aircraft folder has a systems.cfg
Make a back up of that file, replace the [ELECTRICAL] and see if it works.
I’ll take a run at it tomorrow and advise.
Using IVAO for traffic so should be interesting.
I see in system.cfg there is also a [LIGHTS] section. Do you have legacy data for that?
Just tried changing the systems.cfg
in the Asobo_Generic_Airliner_TwinEngines
aircraft. Logged into VatSim at KSLC and it didn’t seem to fix the issue.
That is a A320 and not a generic twin engine.
I believe that is what is displayed now, in Volanta it was displaying the aircraft was a B739. vPilot the no suitable model setting is set to Generic Airliner Twin Engines Asobo 00
Now you have a workaround until Asobo has figured it out.
I noticed the lack of AI plane lighting but wasn’t sure if SU5 or the hot-fix was to blame.
Hopefully Asobo can get this fixed in the next hot-fix (among a few other items…)
@ Chaezaa - You are a hero! This works perfectly with the IVAO AI aircraft and to be honest I think they look better than the lights that the simulator borked with SU5.
My sincere thanks to you.