Jump to content
The simFlight Network Forums

SimmerCanuck

Members
  • Posts

    6
  • Joined

  • Last visited

  • Days Won

    1

SimmerCanuck last won the day on September 3 2018

SimmerCanuck had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

SimmerCanuck's Achievements

Newbie

Newbie (1/14)

  • One Year In Rare
  • Week One Done Rare
  • One Month Later Rare

Recent Badges

1

Reputation

  1. That's a good nugget. I went simpler and changed the first departure time to 00:00 and that works great. Thanks for that, no point in questioning the logic, it's good to know how it works.
  2. Yes, I said as much in my post, in fact this is the post I was referring to that I'd seen in the forum. That only refers to the not crossing midnight issue, not the strange behavior starting at midnight with the 2 hour delay on arrivals. It this issue that most affects the playability of KMEM as there is much traffic in that 2 hour period.
  3. I've seen this before at other airports. The problem is that if you issue a hold short of a taxiway, it cancels all holds past that, including the implied holds at the runways. Using hold position followed by continue taxi doesn't do this.
  4. I've seen this before and know it's been mentioned on the forums - it doesn't seem that traffic rolls over midnight. With KMEM with RT being very busy for arrivals up until about 0100 this makes playing that first hour a bit odd. I started a game at 2100 and played around to 0100 - It got quiet around 0030 and all traffic after midnight showed a before midnight time on the strip. So then I tried a game starting at 0000 and the midnight hour arrivals showed up - however, the game clock jumps straight to 0208 with a departure. The midnight hour arrivals showed up after that. In fact the 40 arrivals scheduled between 0000 and 0137 all called in between 0208 and 0241. This of course overlaps with the beginning of the many departures that start at 0208. Made for some challenging game play and worked out okay, but it's a significant deviation from the real world (and the RT schedule) where there are nearly no movements for an hour or so while the freight is sorted to the outgoing aircraft. I've got a game log, but it's too large to upload here. I think if you try the same start parameters as I have, you'll find similar results.
  5. This side effect has burned me a number of times for a -1000 penalty. For example at KLAX, I'm doing departures from 25R@F, most of my planes are coming up Bravo but I have one coming up C. I issued a hold short of taxiway bravo to prevent a collision at that intersection. I give the plane coming off of bravo a line up and wait, then I give the one holding short of bravo a continue taxi. A few seconds later - bang, the second plane has driven straight into the side of the one lined up and waiting on 25R. I think to avoid this I'd have to first tell the second plane to hold short of runway 25R and then tell it to continue taxi. Of course after the collision I end up having to delete one or both of the involved planes and do 100 takeoffs and landings to make up the penalty points.
  6. Just discovered Tower!3D Pro this week and have already spent lots of time that I didn't have and controlled airplanes in my sleep. I'm fairly comfortable controlling KPHL at 100% traffic with a westerly flow, arrivals on 27L, departures on 27R. I have encountered one specific problem 3 or 4 times so far. I suspect that this is planned behaviour and I just need to learn to avoid the situation - but thought I'd ask here. If I have a departure on 27R take off at the same time an arrival on 27L is landing, I get an Air Collision Alert (and -500 pts) between the 2 airplanes. Here's what the logs show. 10:35:11 alt: 0 takeoff: True/False/-1 OWNER_GROUND r: 27R * DAL1478 => STATE CHANGE from STATE_TAKEOFFUP to STATE_FLYAWAY 10:35:16 * DAL1478 => ADD HISTORY: Air Collision Alert! ( DAL1478 - PDT4821 ) -500 pts 10:35:17 alt: 99 takeoff: False/False/-2 OWNER_TOWER r: 27L * PDT4821 => STATE CHANGE from STATE_INCOMING to STATE_LAND With the runways being about 1400' apart and the threshold for 27L about 4500' past the 27R threshold, I can see that these 2 airplanes are in fact airborne and probably only have <2500' horizontal separation. They are however travelling in the same direction and there are no options for diverging headings. I think I've answered my own question, but if someone could confirm that I just need to avoid starting takeoff rolls while parallel traffic is on short final that would help. Of course I could switch runways, but that gets really messy trying to get your outbound taxis across the runway with the landing traffic. I think that in the real world, 27R is used for landings while 27L is used for takeoffs during segregated operations - maybe that's for the same reasons as I'm getting this error. Thanks. This is a great sim, my biggest complaint about it is that my headset is not comfortable enough to make it though a good 3 hour session. 😎
×
×
  • 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.