Jump to content
The simFlight Network Forums


  • Posts

  • Joined

  • Last visited

Posts posted by gel

  1.  ok .. thanks vic,


    i can't find the purchase info for tracon! ... i guess it was erased some where along the way ... i have pretty much every other

    receipt from the end of 2013 on ... that's what i was sending to you ... i'm thinking that doesn't satisfy your request of proof of purchase..


    @ stuall ...sorry..i didn't mean to hy-jack your thread ...

  2. @kevin ... updates?  as in: correcting the inability to create one's own air space?... the editor is really just a means

                    for the customer to correct the mistakes one invariably finds... such as: wrong altitudes upon STAR entry, etc....

                    feelthere really do need to 'freshen' things up a tad ...

  3. When you say " editing the code was necessary at some points." Do you mean you had to manually code for the runways .... that's the 'achilles heel'

    with the editor ... and i've tried w/ notepad++ ... no can do ...


    too bad ... i suspect the majority of those attempting to create their local sectors have hit this wall and as a result

    it's made for a less robust community imo ...


    ..continued success!

  4.   It's not you ...it's the program.


     There are some (very few) that have managed to create their own sectors ..they are the exceptions...you are the rule.

    There appears to be no support for this.

     So unless you care to devote most of your waking hours to programming... (apparently via notepad++)

    you must be content to edit the product that is shipped ... regardless of the advertisement. You know ...the part where they suggest you can create your own sector... etc. (One of the main reasons I personally purchased this product.)


    Be assured... you will find plenty to edit with the finished product you already have.


    This is a missed opportunity to be sure.

  5. I've added a few more waypoints to my scenario to help with vectoring for the final...

    I choose to have everything coming in from the east (se,ne) come down the "chute" ..

    so.. RIIVR 2 I treat as a straight in arrival and I will feed the oldee and seavu arrivals into that..

    those last two arrivals are flying on an intercept route that's nice to take advantage of...I'll turn them in (250deg)

    just as they are approaching the line between RIIVR and LUVYN...

    I do keep them higher though..@ 10,000...then I'll clear them for an ILS approach around FUELR...

    the extra altitude allows for easier handling of the north and west arrivals destined for 24R ...IOW, I can bring them in a bit tighter

    knowing I have vertical separation.

    Similar to you, anything coming in from SLI  I'll clear them for BASET  but give a "..turn left heading 250"

    well before BASET to intercept GAATE at 7000...maybe lower...

    With the SADDE arrivals..I'll usually clear them direct to SMO and resume the arrival ... that seems to be a help

    when overseas flights from Asia are making their way in... 


  6. Hey Japhus... I went looking for the same thing after finding these two traffic flow images (

    some time ago) for Toronto's Pearson Int'l .... very cool and representative of a typical day

    (or in this case I think 4 hours) 

    The arrivals are in red ... note the 4 arrival streams ...

    I can't locate the same imagery for LAX.


    Alas..I've tried everything I know to create the Pearson Tracon through Tracon2012! sector creator

    but to no avail...I just can't get around the 'runway problem'.





  7. One thing I wanted to add regarding SP is sometimes my inability to understand what it's saying.

    Some of it's pronunciations are creative to say the least.

    One way around that for me is to open a couple of google tabs ....on one page I open wikipedia world airline codes

    ....on the other i open wikipedia airport by iaco codes.

    While I have a few minutes I look up the various dep/arr airports and find any airline calls that I'm unable to pickup

    from SP.

    It adds a little more depth to my game play.



  8. Hey Japhus ... I do use SP and I don't experience any problems other than sometimes I release the 'TAB' button too soon...

    Obviously the busier it gets the more taxing on the system (and on me!)...I find it does need to catch up at times...I just try to leave myself

    plenty of room. It has never been 'stuck' though.


    To operate multiple airports you need only toggle on/off each (active) runway at whatever airport(s) you choose to control...

  9. Yes, I know what you mean about Fillmore. The other one that can be 'interesting' is the traffic from oldee2 and seavu2....the oldee2 arrivals are well

    w/i the sector boundary before the center handoff is initiated and if it's busy one can be too late to catch the conflict coming in from seavu.


    I'm getting into the habit of slowing the arrivals down as they approach, certainly w/i a 15mi final and absolutely for the 

    north arrivals through sadde and kimmo... as an example, the sadde arrivals maintain a 070 heading past SMO and it allows

    for better timing for me if I slow them down to 180kts before vectoring them to 220 @ 4000 for the loc intercept ... this allows a tighter turn

    in which I don't need to be right on them as they find the 220 hdg...


    Another note: Sometimes I will handle arrivals for santa monica and longbeach as well as lax. (I'll do that over taking on the roll of both arr/dep)



  10. Well ... probably not what you're looking for but I don't take on both roles at the same time.

    Don't think they do in real life either.

    Having said that I think there are certain fundamentals one would have to address: If they are arriving and descending don't climb them...

    if they are departing and climbing don't hold them @ altitude too far away from the airport (think of ground objects, noise and the like) ...

    'Handle' as little as possible and hand them off as soon as possible...

    I think maintaining separation through vectoring and speed are the preferred methods.

    But I'm pretty new at this... it is fun though!

  11. Yes ... excellent vids and very helpful to a noob like me. I do seem to recall though, that Mark thought the Sadde arrivals were coming in too low,

    yet when I pull-up the Sadde SID it is as you described above (SMO at or above 5000) The trouble is, of course, departures heading north

    may not climb fast enough (CRJ?) to be @6000 or above by the time they reach SMO. So the choice may be (as per Mark?) keep the arrivals @ or above 7000 or vector arr/dep to maintain separation. I prefer keeping the arr's at 7000..if I can catch them in time...not easy to do when things get busy.


    Two other comments that come to mind: I find I don't need to vector the arrivals "off the localizer" in order to clear them for an ILS arrival.

    An example of that would be the BASET3 SID that is essentially a straight in approach. I don't need to vector those arrivals at all.

    The other comment is more about a scenario that repeats: flights arriving from seavu and oldee ...it becomes a real challenge to maintain

    separation. The arrival on oldee2 does not become controllable until well inside the sector boundary and usually right on top

    off the arrival coming in from seavu2.

  12. wow... my hat's off to you Satch... in my desperate attempts to create a sector (Pearson Int'l) all have crashed.

    Just can't get around the 'runway problem'. Too bad; I suspect most that have tried have found themselves up against

    the same challenge. That's probably why we don't see a lot of activity in  that area.

    Unfortunate... the community would certainly benefit by the ability to develop and share their creations...

    I think it would go a long way in tapping into and growing the enthusiasm for the product.



  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.