Jump to content

Sign in to follow this  
alcanallen

Contrails and Wing Vortices

Recommended Posts

Could you post the lights section here so I can see what could be trimmed down?

Hi,

 

here it is:

 

[Lights]

light.0 = 3, -94.20, -53.50, -1.16, fx_df727_navredh,

light.1 = 3, -94.20, 53.50, -1.16, fx_df727_navgreh,

light.2 = 1, -45.63, 0.00, 8.30, fx_beaconh,

light.3 = 3,-101.90, -53.15, -1.25, fx_df727_navwhi,

light.4 = 3,-101.90, 53.15, -1.25, fx_df727_navwhi,

light.5 = 1, -67.49, 0.00, -6.20, fx_beaconb,

light.6 = 2, -95.38, -53.75, -1.12, fx_df727_strobe,

light.7 = 2, -96.00, -53.75, -1.12, fx_df727_strobe,

light.8 = 2, -95.38, 53.75, -1.12, fx_df727_strobe,

light.9 = 2, -96.00, 53.75, -1.12, fx_df727_strobe,

light.10 = 10,-19.50, 0.00, 2.05, fx_df727_vclight,

light.11 = 5, -58.20, 6.10, -2.20, fx_df727_land,

light.12 = 5, -58.20, -6.10, -2.20, fx_df727_land,

light.13 = 8, -62.40, -6.50, 0.50, fx_df727_wingl2,

light.14 = 8, -62.40, 6.50, 0.50, fx_df727_wingl2,

light.15 = 7, -58.40, -5.80, -2.30, fx_landing,

light.16 = 5, -58.40, 5.80, -2.30, fx_landing,

light.17 = 8, -54.70, -6.30, 1.18, fx_df727_wingl1,

light.18 = 8, -54.70, 6.30, 1.18, fx_df727_wingl1,

light.19 = 2,-144.40, 0.00, 20.75, fx_strobe_df727,

 

I have to confess that I can't identify every single light regarding its function.

Furthermore, I have no imagination what light.19 may be. A strobe light at the tailfin? After looking at many pictures at airplane.net I saw no such light.

 

By the way, can't get the vortices get to work on the SSJ-100 (it only works with RJ's original .xml file which defines only the airspeed). I believe that this is rather a problem of the plane itself, which generally behaves very beta-ish, than of the .xml file.

 

Harald


   Harald Geyer
   Gründer der Messerschmitt Freunde Dresden v. V.

lYI9iQV.jpg

Share this post


Link to post
Share on other sites

Hi,

 

here it is:

 

[Lights]

light.0 = 3, -94.20, -53.50, -1.16, fx_df727_navredh,

light.1 = 3, -94.20, 53.50, -1.16, fx_df727_navgreh,

light.2 = 1, -45.63, 0.00, 8.30, fx_beaconh,

light.3 = 3,-101.90, -53.15, -1.25, fx_df727_navwhi,

light.4 = 3,-101.90, 53.15, -1.25, fx_df727_navwhi,

light.5 = 1, -67.49, 0.00, -6.20, fx_beaconb,

light.6 = 2, -95.38, -53.75, -1.12, fx_df727_strobe,

light.7 = 2, -96.00, -53.75, -1.12, fx_df727_strobe,

light.8 = 2, -95.38, 53.75, -1.12, fx_df727_strobe,

light.9 = 2, -96.00, 53.75, -1.12, fx_df727_strobe,

light.10 = 10,-19.50, 0.00, 2.05, fx_df727_vclight,

light.11 = 5, -58.20, 6.10, -2.20, fx_df727_land,

light.12 = 5, -58.20, -6.10, -2.20, fx_df727_land,

light.13 = 8, -62.40, -6.50, 0.50, fx_df727_wingl2,

light.14 = 8, -62.40, 6.50, 0.50, fx_df727_wingl2,

light.15 = 7, -58.40, -5.80, -2.30, fx_landing,

light.16 = 5, -58.40, 5.80, -2.30, fx_landing,

light.17 = 8, -54.70, -6.30, 1.18, fx_df727_wingl1,

light.18 = 8, -54.70, 6.30, 1.18, fx_df727_wingl1,

light.19 = 2,-144.40, 0.00, 20.75, fx_strobe_df727,

 

I have to confess that I can't identify every single light regarding its function.

Furthermore, I have no imagination what light.19 may be. A strobe light at the tailfin? After looking at many pictures at airplane.net I saw no such light.

 

By the way, can't get the vortices get to work on the SSJ-100 (it only works with RJ's original .xml file which defines only the airspeed). I believe that this is rather a problem of the plane itself, which generally behaves very beta-ish, than of the .xml file.

 

Harald

 

Hello Harald, Light.19 would be a strobe at the tail but it may not display anyway as there are two too many lines in the LIGHTS section.

The nav lights, strobes light etc could all be one line each if you can be bother to edit the effects file. (A bit laborious admittedly)

 

You could actually end up with only seven lines used.

 

As for the SSJ-100.....how many flaps settings does it have.? 

Share this post


Link to post
Share on other sites

 

 


Hello Harald, Light.19 would be a strobe at the tail but it may not display anyway as there are two too many lines in the LIGHTS section.

 

I wonder how this nearly perfect plane shows such a "simple" mistake... Nevertheless, I like it. I think that I don't change it further because while I try to understand the .xml code to edit it useful, editing the effects themselves is far too difficult for me. Thanks, though!

 

 

 


As for the SSJ-100.....how many flaps settings does it have.?

 

Has four: 3, 9, 15 and 30 degrees. (I tried to change the flaps degrees value in your .xml into "9".) From the aircraft.cfg:

 

[flaps.0]       //Trailing Edge Flaps
type             = 1                                    // 1 - tail, 2 - lead
span-outboard    = 0.8                                  // 0.0 .. 1.0
extending-time   = 20                                   // seconds
flaps-position.0 = 0                                    // degrees
flaps-position.1 = 3                                    // degrees
flaps-position.2 = 9                                    // degrees
flaps-position.3 = 15                                    // degrees
flaps-position.4 = 30                                   // degrees
damaging-speed   = 250                                  // KIAS
blowout-speed    = 300                                  // KIAS
lift_scalar = 1.1
drag_scalar = 1.0
pitch_scalar= 1.0
system_type = 1                                         //Hydraulic
 


   Harald Geyer
   Gründer der Messerschmitt Freunde Dresden v. V.

lYI9iQV.jpg

Share this post


Link to post
Share on other sites

I wonder how this nearly perfect plane shows such a "simple" mistake... Nevertheless, I like it. I think that I don't change it further because while I try to understand the .xml code to edit it useful, editing the effects themselves is far too difficult for me. Thanks, though!

 

 

 

 

Has four: 3, 9, 15 and 30 degrees. (I tried to change the flaps degrees value in your .xml into "9".) From the aircraft.cfg:

 

[flaps.0]       //Trailing Edge Flaps

type             = 1                                    // 1 - tail, 2 - lead

span-outboard    = 0.8                                  // 0.0 .. 1.0

extending-time   = 20                                   // seconds

flaps-position.0 = 0                                    // degrees

flaps-position.1 = 3                                    // degrees

flaps-position.2 = 9                                    // degrees

flaps-position.3 = 15                                    // degrees

flaps-position.4 = 30                                   // degrees

damaging-speed   = 250                                  // KIAS

blowout-speed    = 300                                  // KIAS

lift_scalar = 1.1

drag_scalar = 1.0

pitch_scalar= 1.0

system_type = 1                                         //Hydraulic

 

 

Ok in my vortex code you will see (A:FLAPS HANDLE INDEX,number) 4 >

 

Which means flap position 4 and greater than.....the SSJ only goes up to flap position 4 so the votices will not show.

 

Open the XML gauge with notepad and change the 4 to 3  so..(A:FLAPS HANDLE INDEX,number) 3 >

 

Then the vortices will appear after you set flaps 30. Change it to a 2 if you would like to see the vortices after flaps 15. 

Share this post


Link to post
Share on other sites

Oh, I thought this was the flap value in degrees... Will try!


   Harald Geyer
   Gründer der Messerschmitt Freunde Dresden v. V.

lYI9iQV.jpg

Share this post


Link to post
Share on other sites

Hello Harald,

 

If you get the vortex working on the SSJ you will notice that the width between the vortices need adjusting....and the height. Only the forward/back position is changed by the aircraft cfg.

 

This is because both vortices are written in the same effects file. I will try to show which bits to adjust.

 

 

<copyright>©2013 Edward Cox</copyright>
 
[Library Effect]
Lifetime=5
Version=1.00
 
[Properties]
Cockpit=1
VirtualCockpit=1
Spot=1
Tower=1
Map=1
 
[Emitter.0]
Lifetime=0.00, 0.00
Delay=0.00, 0.00
Bounce=0.00
Rate=8.00, 8.01
X Emitter Velocity=0.00, 0.00
Y Emitter Velocity=0.00, 0.00
Z Particle Velocity=0.00, 0.00
Drag=0.00, 0.0
X Particle Velocity=0.00, 0.00
Y Particle Velocity=-70.00, -70.00
Z Particle Velocity=0.00, 0.00
X Rotation=0.00, 0.00
Y Rotation=0.00, 0.00
Z Rotation=5.00, 6.00
X Offset=20.90, 20.90
Y Offset=0.90, 0.90
Z Offset=0.00, 0.00
 
[Particle.0]
Lifetime=1.10, 1.20
Type=21
X Scale=0.70, 0.70
Y Scale=0.70, 0.70
Z Scale=0.00, 0.00
X Scale Rate=0.25, 0.30
Y Scale Rate=0.25, 0.30
Z Scale Rate=0.00, 0.00
Drag=-1.00, -0.90
Color Rate=0.00, 0.00
X Offset=20.90, 20.90
Y Offset=0.90, 0.90
Z Offset=0.00, 0.00
Fade In=0.05, 0.05
Fade Out=0.30, 0.30
Shade=1
Face=1,1,1
 
[ParticleAttributes.0]
Blend Mode=1
Texture=fx_smoke.bmp
Bounce=0.00
Color Start=244, 244, 247, 180
Color End=249, 249, 249, 255
Jitter Distance=3.00
Jitter Time=2.10
TempK=0.00
TempRate=-70.01
uv1=0.00, 0.00
uv2=1.00, 1.00
X Scale Goal=5.00
Y Scale Goal=5.00
Z Scale Goal=0.00
Extrude Length=10.00
Extrude Pitch Max=5.00
Extrude Heading Max=5.00
 
[Emitter.1]
Lifetime=0.00, 0.00
Delay=0.00, 0.00
Bounce=0.00
Rate=8.00, 8.01
X Emitter Velocity=0.00, 0.00
Y Emitter Velocity=0.00, 0.00
Z Particle Velocity=0.00, 0.00
Drag=0.00, 0.0
X Particle Velocity=0.00, 0.00
Y Particle Velocity=-70.00, -70.00
Z Particle Velocity=0.00, 0.00
X Rotation=0.00, 0.00
Y Rotation=0.00, 0.00
Z Rotation=5.00, 6.00
X Offset=-20.90, -20.90
Y Offset=0.90, 0.90
Z Offset=0.00, 0.00
 
[Particle.1]
Lifetime=1.10, 1.20
Type=21
X Scale=0.70, 0.70
Y Scale=0.70, 0.70
Z Scale=0.00, 0.00
X Scale Rate=0.25, 0.30
Y Scale Rate=0.25, 0.30
Z Scale Rate=0.00, 0.00
Drag=-1.00, -0.90
Color Rate=0.00, 0.00
X Offset=-20.90, -20.90
Y Offset=0.90, 0.90
Z Offset=0.00, 0.00
Fade In=0.05, 0.05
Fade Out=0.30, 0.30
Shade=1
Face=1,1,1
 
[ParticleAttributes.1]
Blend Mode=1
Texture=fx_smoke.bmp
Bounce=0.00
Color Start=244, 244, 247, 180
Color End=249, 249, 249, 255
Jitter Distance=3.00
Jitter Time=2.10
TempK=0.00
TempRate=-70.01
uv1=0.00, 0.00
uv2=1.00, 1.00
X Scale Goal=5.00
Y Scale Goal=5.00
Z Scale Goal=0.00
Extrude Length=10.00
Extrude Pitch Max=5.00
Extrude Heading Max=5.00
 
---------------------------------------------------------------------------------------------------------------
 
Red letters= effect height
Blue letters= effect width left
Green letters= effect width right
 
Everthing below [Emitter.1] is a copy of below [Emitter.0] which is the other vortex...just the green letters are different from the blue.
 
And so it follows if the same was to be done with the beacons for example (positioning written within the effects file) only one line need be used in the aircraft cfg.

Share this post


Link to post
Share on other sites

O.K., the correction of the flap setting worked fine.

Editing the effect itself will be the next step to learn. Particularly for the DF B727 this will be a work for some more free time!

 

Just one question left: How is the code for the .xml gauge if it switches a light instead of the smoke system?

 

EDIT: All fine with the SSJ-100, as the pictures show. If only the plane itself was a little bit more mature...

 

 

 

 

 

 


   Harald Geyer
   Gründer der Messerschmitt Freunde Dresden v. V.

lYI9iQV.jpg

Share this post


Link to post
Share on other sites

Ed, I installed your gauge and effects and was delighted to see when and where it works.

Great stuff!

 

 

I am transplanting this into "my" panel.

If I were to try moving the vortices outward:

Am I correct in thinking the position is fixed by

X Offset in the fx file, and

[smokesystem] entry in a/c.cfg file

Share this post


Link to post
Share on other sites

Ed, I installed your gauge and effects and was delighted to see when and where it works.

Great stuff!

 

 

I am transplanting this into "my" panel.

If I were to try moving the vortices outward:

Am I correct in thinking the position is fixed by

X Offset in the fx file, and

[smokesystem] entry in a/c.cfg file

 

Yes you are correct WingZ.

 

Only the purple entry in the [smoke system] affects the effect position (Z axis (forward/back)) 

 

smoke.0 = 0.000,  -33.0,   0.000000,    TDS787_flap

 

To move the vortices out towards the wingtip increase the X offset figures in the fx file. (blue and green lines....green is simply a negative of the blue as it is measured from the reference_datum_position)

 

What I do is alter only one side first so I can see the difference between left/ right vortices ...when happy you know what figures to enter for the other side.

 

The real buttsky pain with fx is one has to shut down the sim and restart it to see the results of any changes. :angry:

Share this post


Link to post
Share on other sites

O.K., the correction of the flap setting worked fine.

Editing the effect itself will be the next step to learn. Particularly for the DF B727 this will be a work for some more free time!

 

 

 

 

Looking good there Harald. For me your vortices look a tad high...you can lower them by decreasing the figures I highlighted in red in the fx file (Y offset)

Remember one has to shutdown the sim and reboot it to see any changes.

 

Editing effects will take you to new heights. Take the single flash wingtip strobes on boeing aircraft....both tip strobes should flash at the same time....have them as separate lines in your aircraft cfg and they will slowly go out of sync. Put both left/right strobes in the SAME effects file and they should stay in sync. :wink:

 

Just one question left: How is the code for the .xml gauge if it switches a light instead of the smoke system?

 

 

 

First one has to ascertain what light effects are free to use on your particular aircraft.

 

Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=taxi, 7=recog, 8=wing, 9=logo, 10=cabin

 

Usually 7=recog or 10=cabin is free.

 

I will write and test the code before uploading here.

Share this post


Link to post
Share on other sites

 

 


The real buttsky pain with fx is one has to shut down the sim and restart it to see the results
Well I did eventually figure this out... but only after I'd figured out that editing the fx outside the sim wasn't going to bring a result either! (You know, saving to the place you'd opened the zip to? Doh)

 

Anyway I'm quite enjoying this thread, thanks to all!

Share this post


Link to post
Share on other sites

Hello Harald, here is an example of using the LIGHTS section for the flap vortices effect (on the TDS 787)

 

 

[lights]
Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=taxi, 7=recog, 8=wing, 9=logo, 10=cabin
light.0 = 8, 7.7, -27, -1, tdsb8_wing_light
light.1 = 8, 7.7, 27, -1, tdsb8_wing_light
light.2 = 6, 54.787, 0, -8.5, tdsnose_gearwell
light.3 = 1, 43.88, 0, 9.00, fx_beaconh ,
light.4 = 1, 16.00, 0, -10.83, fx_beaconb ,
light.5 = 10, -33.00, 0,  0, TDS787_flap ,
 
Here is the code. (Tested)
 
<Gauge Name="vortex" Build="1.0">
<Update Frequency="2"/>
  <Element>
    <Select>
      <Value> 
(A:AIRSPEED INDICATED,knot) 180 < (A:Radio height, feet) 20 > 
(A:SEA LEVEL PRESSURE,inHg) 30.12 < (A:FLAPS HANDLE INDEX,number) 4 > 
(A:AMBIENT TEMPERATURE,celsius) 0 > and and and and 
if{ (A:LIGHT CABIN,bool) ! if{ 0 (>K:TOGGLE_CABIN_LIGHTS) } } els{ (A:LIGHT CABIN,bool) if{ 0 (>K:TOGGLE_CABIN_LIGHTS) } } 
      </Value>
    </Select>
  </Element>

</Gauge>

 

Share this post


Link to post
Share on other sites

you can lower them by decreasing the figures I highlighted in red in the fx file (Y offset)

 

Yes, I did this already but obviously not enough (ran out of patience with restarting the sim again and again as I posted the pictures long after midnight).

 

 

 

Take the single flash wingtip strobes on boeing aircraft....both tip strobes should flash at the same time....have them as separate lines in your aircraft cfg and they will slowly go out of sync. Put both left/right strobes in the SAME effects file and they should stay in sync.

 

I already thought about if the strobes should flash synchronized or not - yes they should (is this also valid for the 727 which obviously has two strobes at every wing?). Now with this information I can "merge" the wings strobes, the white position lights, the landing lights and so I have won one free light to insert the flap vortices. I can go until light.17, can't I?

 

 

 

Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=taxi, 7=recog, 8=wing, 9=logo, 10=cabin

 

Usually 7=recog or 10=cabin is free.

 

In the case of the DF 727, the "9" seems to be unused. "7" is used be one (really: only one) landing light:

 

light.15 = 7, -58.40,  -5.80, -2.30, fx_landing,

light.16 = 5, -58.40,   5.80, -2.30, fx_landing,

 

Maybe that's another thing to be fixed, or could these different types make any sense?

 

This is one of the most useful threads of the recent time!

 

Harald

 

EDIT: I see that our posts have crossed... If I chose the light type "9" - am I right that I have to replace the term "cabin" with "logo" within the xml code?


   Harald Geyer
   Gründer der Messerschmitt Freunde Dresden v. V.

lYI9iQV.jpg

Share this post


Link to post
Share on other sites

 

I already thought about if the strobes should flash synchronized or not - yes they should (is this also valid for the 727 which obviously has two strobes at every wing?). Now with this information I can "merge" the wings strobes, the white position lights, the landing lights and so I have won one free light to insert the flap vortices. I can go until light.17, can't I?

 

 

Way to go Harald! You are correct.

 

 

 

 

 

In the case of the DF 727, the "9" seems to be unused. "7" is used be one (really: only one) landing light:

 

light.15 = 7, -58.40,  -5.80, -2.30, fx_landing,

light.16 = 5, -58.40,   5.80, -2.30, fx_landing,

 

Maybe that's another thing to be fixed, or could these different types make any sense?

 

This is one of the most useful threads of the recent time!

 

Harald

 

EDIT: I see that our posts have crossed... If I chose the light type "9" - am I right that I have to replace the term "cabin" with "logo" within the xml code?

 

 

 

If "9" is unused use that. Note that if an aircraft uses C+ gauges (I presume the DF727 does), The XML code cannot override it....so if there is an active switch for anyone of those light switches the xml code will not work....if the gauges were written with XML no problem. (I love XML gauges!) 

 

Again you are correct...if your replace precisely "cabin" with "logo" you can choose type "9"

 

I say precise because Reverse Polish Notation is very unforgiving if even a space is wrong.

 

Edit* afterthought....if the overhead panel (I presume that is where the light switches are) is not written as one gauge it may be possible to comment out in the panel cfg any C+ gauge that you do not wish to use. 

Share this post


Link to post
Share on other sites

Thanks Sir!

 

Now I know what to do at the next weekend.

 

What do you think about one landing light being type "5" and the other one being type "7"? Shouldn't they better both be type "5"?

 

In the meantime I watched some 727 night videos. Some of them seem to have no strobes at all (or not to use them), at others I believe to recognize that the leading edge strobes left and right are synchronized with each other, but not with the trailing edge strobes, which themselves are synchronized with each other (left and right) though. Strange.

 

Greetings from Dresden!

Harald


   Harald Geyer
   Gründer der Messerschmitt Freunde Dresden v. V.

lYI9iQV.jpg

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    34%
    $8,560.00 of $25,000.00 Donate Now
×
×
  • Create New...