I don't know if it's me but every time I turn on the landing light. The plane then develops a white smoke trail. Anyone else seen this?
I don't know if it's me but every time I turn on the landing light. The plane then develops a white smoke trail. Anyone else seen this?
You can't take the sky from me...
I just checked mine for you and I am not seeing that problem. Does it only happen with the Paris jet?
Larry
it did for me too...
You can find most of my repaints for FSX/P3D in the library here on the outhouse.
For MFS paints go to flightsim.to
I have this problem with Vertigo f8f and f6f too ...
Donīt know what might be ...
Flavio - P3D v4.5 - MSFS 2020 - Win 11 Pro 64
i912900KF 5.2ghz - ASUS TUFZ690 - AIO Cooler Master PL360 Flux Masterliquid - 32gb Kingston Fury 3600mhz - Asus RTX 2080 Super - AGON 32'' AG323FCXE 165mhz - MCP 737R 2015 Virtual Avionics - SSDs M2 2Tb+1Tb XPG
I have the Vertigo F8F and I am not seeing the issue with that aircraft either. I wonder if you folks with problems have somehow suffered a change in 'key mapping' in some way and the key for the smoke (by default the 'I' key) has been assigned to the lights key (either 'L', 'CTRL+L' or 'SHIFT+L').
I know I have had issues with 'key mapping' in the past, usually when I have updated controller drivers or added a new controller or if I have deleted the FSX.cfg file to cure a problem (all settings have to be remade if you do that). For some reason FSX insists on applying a slew of keys to the joystick, yoke, pedals and/or throttles that I don't want. As I use the Saitek profile editor to assign all my functions I make sure that ALL FSX key assignments for the controllers are deleted in the control settings panel, I just leave the key settings assigned to the keyboard and only assign axis functions to the controllers.
Larry
Sounds like it could be a FX that another plane had that is using that same name for the LL and you are getting that effect..
Humble Poly bender and warrior of Vertices
Alienware Console i7 3770 CPU 3.40 GHz / 16 Gigs of RAM / GTX660 GC w/2 Gigs of VRAM / Windows 7 64 Ultimate
Running 3X Samsung 840 SSD HD's, 200 Gig each, 500/500 Read/Write
I've only seen it with the Paris Jet and it's not the default smoke effect. Seems to be a very small trail that trails aft from the light itself. I'll crank up FSX and see if I can get a screenshot.
You can't take the sky from me...
Flavio - P3D v4.5 - MSFS 2020 - Win 11 Pro 64
i912900KF 5.2ghz - ASUS TUFZ690 - AIO Cooler Master PL360 Flux Masterliquid - 32gb Kingston Fury 3600mhz - Asus RTX 2080 Super - AGON 32'' AG323FCXE 165mhz - MCP 737R 2015 Virtual Avionics - SSDs M2 2Tb+1Tb XPG
Here's what I get....
I don't know what the problem might be except for possibly Video Card drivers. I have an old Radion X1050 and the last set of drivers I installed messed up my text display. ATI no longer supports this card so I might try and see what guru 3d has....
Attachment 20916
You can't take the sky from me...
Brian,
Do you have A2A 3d Lights? If you have, try this new lights set:
[lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0 =1, -17.990000, 0.000000, 4.930000, fx_shockwave_beaconh //fx_beacon
light.1 =1, 1.150000, 0.000000, -1.750000, fx_shockwave_beaconb_nl //fx_beacon
light.2 =3, -18.820000, 0.000000, 0.452000, fx_shockwave_navwhi //fx_navwhi
light.3 =3, 3.300000, -15.820000, 0.938000, fx_shockwave_navred //fx_navred
light.4 =3, 3.300000, 15.820000, 0.938000, fx_shockwave_navgre //fx_navgre
light.5 =5, 13.55, 0.00, -0.1250, fx_shockwave_landing_light_narrow_old
Itīs using different .fx than the default package and because the problem has to do with the lights it might work.
Flavio - P3D v4.5 - MSFS 2020 - Win 11 Pro 64
i912900KF 5.2ghz - ASUS TUFZ690 - AIO Cooler Master PL360 Flux Masterliquid - 32gb Kingston Fury 3600mhz - Asus RTX 2080 Super - AGON 32'' AG323FCXE 165mhz - MCP 737R 2015 Virtual Avionics - SSDs M2 2Tb+1Tb XPG
Bookmarks