Piglet's Paris Jet

[Brian_Gladden]

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?

[Tako_Kichi]

I just checked mine for you and I am not seeing that problem. Does it only happen with the Paris jet?

[jankees]

it did for me too...

[flaviossa]

I have this problem with Vertigo f8f and f6f too ...
Don´t know what might be ...

[Tako_Kichi]

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.

[Lionheart]

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..

[Brian_Gladden]

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.

[flaviossa]

Here´s what i´m talking about:


And my key mapping is the default one. I´ll investigate the .fx thing that might be overwrited by another aircraft (Have so many installed!!).

But, please, don´t want to highjack the topic created by Brian. So, let´s keep talking about the Paris Jet :salute:

[Brian_Gladden]

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

[flaviossa]

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.