Jump to content
The simFlight Network Forums

coyotedelmar

Members
  • Posts

    12
  • Joined

  • Last visited

Everything posted by coyotedelmar

  1. For PHX, had to dig through noise abatement reports so lack arrivals but iirc EAST FLOW: Departures: 7L, some 8 Arrivals: 7R, probably 8 (guessing on that though) WEST FLOW: Departures: 25R, some 8 Arrivals: 25L, again probably 8 but guessing Primarily takeoffs happen on 7L/25R but there was some off 8/26 just far less. As to which to use, it switches about evenly between the two. I think they said the winds tend to favor East Flow in the morning and West flow in the evening. Oh and found a video for GA, which should take H, H7, F for 25R at least (the video used west flow), and should not cross at F9 or F10. LAX is Outer takeoffs, inner landings. Primarly 25R/24L for takeoffs, 24R/25L for landings. In rare cases, will the 6/7s be used. If they are though, it's 6R/7L for takeoffs, 6L/7R for landings. I'll have to find my chart again for the common ground traffic routes though.
  2. I'd probably rank them, roughly: Atlanta -- It's just so damn busy, there are some nice ways of managing it, depending on the configuration but even still you just have tons of planes moving around and it's really easy to screw up. LaGuardia -- It's smaller but I struggle quite a bit with LGA compared to some of the bigger places, the crossing runways and pretty heavy traffic (despite being smaller and only 2 runways) makes for a good challenge. Add having to watch the taxi routes with the terminal layouts and yeah. Boston -- Another I feel I never get a good hold on, no matter how hard I try =p. The crossing runways and some of the setups can make it tough to keep pushing tin . I have less issues moving traffic around on the ground here, just getting everyone out in a timely matter usually becomes the challenge. JFK -- With a good schedule, JFK can jump up a bit but generally I find it easy to manage the ground traffic, a bit more difficult getting people out but not as bad as Boston. Pushbacks, for me, is where it usually gets the messiest and trying to not keep arrivals waiting a week to get to their gate =p. Phoenix -- PHX I've at least been pissed at a couple times, a lot of it is some bugs though. Most part it isn't too bad, the layout is very LAX like, minus a runway, but also with less traffic so it isn't too bad to manage. San Diego -- It was between SAN and LAS, SAN ends up slightly tougher since you have to remember your exit at commands, and have to be on the ball with getting departures out in a tight window when it's busy. When it isn't busy though, it can be a snore. If you get in a good flow it can be pretty easy, it's mostly just staying on the ball and making sure to make use of exit at. Las Vegas -- Vegas can be fun, I haven't ran into the traffic jams like I did in 2011 at Vegas, but for the most part it isn't too complicated. watch your crossings and your main taxiway drags and you should be fine. I didn't include SFO just because I've only played a bit of it, but it'd probably be 2nd right now if I did. Just in my experience with it (a whole hour granted) it is hell to get anything leaving that place during the rush.
  3. You can basically create two Republic's though in the airline files e.g. RPA, RW, BRICKYARD, Republic Airlines (American) RPA, YX, BRICKYARD, Republic Airlines (Delta) Since the terminal file only takes ICAO, it makes it useless for placement though. But it was the way to quick fix for mergers without having to change every flight in every schedule (meant I used to have SWA flying 717s and such sometimes but still =p).
  4. The biggest issue, well imo, is the terminal file since it uses ICAO. If it was IATA, you could get the game to take it fairly well, just use a different IATA code for the different codeshares (e.g. Brickyard Delta flights could use RW, American use YX, etc.). in 2011 used that after someone mentioned it on the forums here, to take AirTran and US Airways flights in SC and turn them into Southwest/American. Of course, no idea how it works with the liveries though, and how much of a rewrite it'd take to change terminal assignments to using IATA instead of ICAO.
  5. Found one for KBOS, at least the runway configurations KBOS Link to presentation (from June 2017; pdf file): http://massportcac.org/wp-content/uploads/2017/06/Final-BOS-Update-MCAC-Logan-101-060817.pdf Northwest Flow (31%) Arrivals: 27, 33L, 33R (limited), 32 (limited) Departures: 27, 33L Northeast Flow (34%) Arrivals: 4R. 4L used for non-jets only Departures: 4R, 9. 4L used for non-jets only Southwest Flow (31%) Arrivals: 22L, 27 Departures: 22L. 22R for non-jets only Southeast Flow (4%) Arrivals: 15R. 15L (limited) for non-jets only Departures: 9, 15R, 14 (limited) 4L/22R is restricted to non-jets for noise abatement, likewise flights from 22L are supposed to turn to heading 140 after takeoff (again for noise). It didn't specify if there is a preferred layout choice when winds are calm so if anyone knows or anyone knows the usual taxi routes, feel free to correct (likewise if I mistyped/misread something).
  6. Did a bit on schedules on a recent stream, only posting it as it's easier then typing it out (I tried that once, it was a pain haha). Should do one on GA sometime, something definitely needs work on as it's lacking outside of TIST. https://youtu.be/eDHc8LS4CZ0?t=40m27s Bunch of credit to dickparker, schedule creator is what got me into digging into the files, and mostly how I figured things out if I recall.
  7. I can try to find it and make sure to throw it in there, Thomas Cook is in the database, though don't know if they have a livery or not. Yeah, they like to vacate left, which gets annoying. Going to attach a slightly modified schedule, I changed the Frontier 319s to 320s which should get rid of the white Frontiers (didn't know it was only 320s and 321s with liveries on the PHL real color). Oh and forgot to quote it, but there should be cargo departures, it's just not very many outside of early morning/late night. Digging through have a FedEx departure in the 0800 area, 0900 area, 2100 area, then a few FedEx/UPS around 2200. 4 or so UPS around 0800 (well closer to 0900 but in the 0800 range). kphl_schedule_alt.rar
  8. Yep, I started using that a lot at PHL to get planes to not stop at 35 (when it wasn't in use). Just tell them to hold short of something out of the way. Downside is it does the same with taxiways, so can't give the complicated hold instructions like in 2011, they'll just hold at one and blow through everything else.
  9. Hello all, been meaning to post this. I've been working on making some schedules for the different airports in Tower 3D from influence of Schedule Creator but wanting a bit more updated file. Anyways, right now got Philly done and play tested for the full run, and working on finishing San Diego and LAX (while play testing them as well). Should be very limited, if any, issues and real color compatible (at least for PHL). Feel free to give it a try, and leave some feedback. Again, right now it's just PHL but have SAN and LAX mostly finished, just need to add a couple hours then finish the test on them. Going to add the terminal file for PHL as well, but shouldn't need to update the airline file. LAX will, and I'll probably just make a new one for that (as I have for SAN). kphl_schedule.zip
  10. Just looked, and I'm getting the same. On the Store page it doesn't show ATL under DLC as well, but it shows up in the Tower!3D Pro Deluxe Bundle.
  11. You can, but I haven't figured out how to do it with voice commands. If you type it, it works though, how I get some of the planes at LAX that pushback on D to face how I want. e.g. SWA PUSHBACK APPROVED, EXPECT RUNWAY 24L TAXI VIA D D9 E
  12. Just took a look (I don't usually use the realtraffic schedule but was curious), and think I found the issue. Do you have PDT at Terminal 4 as well? When I did that, I went from no planes on the US/American side to mostly full (and got a PDT in the first seconds). The issue with PDT is in the Airlines file, PDT has the IATA code of US. Which either is causing the game to split flights between them, or just give all the US flights to Piedmont, not really sure. Anyways either changing Piedmont's IATA code in the airlines file, or just killing them (// in front of their listing) should fix the issue.
×
×
  • 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.