|
Post by Travis on Jan 19, 2015 23:36:14 GMT -5
Otherwise LOVIN' it Thanks for the nice thoughts! Mas, Funny enough I was working in this area just today, so tell me what you think of this: CASTLE AIR AND CARGO DISPATCH RELEASE FSCAPTAIN 1.6.2
FLIGHT 9521 KMER-KRDD 20-JAN-15 04:23Z
AIRCRAFT (TBA) OUT: _______ OFF: _______ TYPE C208 ON: _______ IN: _______
CREW INFORMATION: DISP: T J GUY / ____________________________ (SIGNED) PIC : RUFUS T. FIREFLY / ____________________________ (SIGNED)
FUEL CALCULATION WEIGHT/FUEL BREAKDOWN MIN 0LB ZFW 6375LB TAXI 21LB 21MIN T/O FOB 590LB KRDD 242LB 86MIN PLANNED TOW 6965LB KCIC 57LB 19MIN ENROUTE BURN 242LB RSV 135LB 45MIN PLANNED LDW 6723LB HOLD 45LB 15MIN ARRIVAL FOB 338LB *************** TOTAL 600LB
Please note that the Reserve & Holding times will generally be the same. There are new Options to change the minutes of holding fuel time & reserve fuel time.
"Trip time" (here to KRDD) is the ETE minus the "Taxi Time." The time calculation to the alternate airport (KCIC) is made from the destination.
|
|
|
Post by ludwig1976 on Jan 20, 2015 5:14:26 GMT -5
My suggestion: Checklist management using FSCaptain's voicekits. It's quite annoying to listen different voices when using an aircraft built-in checklist manager (like Calls! on Feelthere Embraer Regional Jets) and FSC.
|
|
|
Post by Travis on Jan 21, 2015 1:35:51 GMT -5
Our first sprint in this area won't be "voice based," but we do have plans for a checklist feature. Oops... cat's out of the bag....
|
|
|
Post by mas618 on Jan 27, 2015 13:10:50 GMT -5
Otherwise LOVIN' it Thanks for the nice thoughts! Mas, Funny enough I was working in this area just today, so tell me what you think of this: CASTLE AIR AND CARGO DISPATCH RELEASE FSCAPTAIN 1.6.2
FLIGHT 9521 KMER-KRDD 20-JAN-15 04:23Z
AIRCRAFT (TBA) OUT: _______ OFF: _______ TYPE C208 ON: _______ IN: _______
CREW INFORMATION: DISP: T J GUY / ____________________________ (SIGNED) PIC : RUFUS T. FIREFLY / ____________________________ (SIGNED)
FUEL CALCULATION WEIGHT/FUEL BREAKDOWN MIN 0LB ZFW 6375LB TAXI 21LB 21MIN T/O FOB 590LB KRDD 242LB 86MIN PLANNED TOW 6965LB KCIC 57LB 19MIN ENROUTE BURN 242LB RSV 135LB 45MIN PLANNED LDW 6723LB HOLD 45LB 15MIN ARRIVAL FOB 338LB *************** TOTAL 600LB
Please note that the Reserve & Holding times will generally be the same. There are new Options to change the minutes of holding fuel time & reserve fuel time.
"Trip time" (here to KRDD) is the ETE minus the "Taxi Time." The time calculation to the alternate airport (KCIC) is made from the destination.
Cool stuff! Thanks - looking forward!
|
|
|
Post by ralf9636 on Feb 6, 2015 16:48:02 GMT -5
As you asked for ideas for further enhancements for 1.6.3 (hope this hasn't been discussed before):
I miss situations with rejected takeoffs. It would be nice if there was a failure area with its own adjustable percentage for failures/birdstrikes occuring randomly at any time during the takeoff roll - if that is at all possible.
Thanks
Ralf
|
|
|
Post by nickatc on Feb 6, 2015 18:45:05 GMT -5
+1 to ralf9636 suggestions.
It also would be nice, to have an option to simulate runway obstructions... or something like that, things that would make delays before landing.
It'd be nice to have this option (completely enabled or disabled by user) in case someone flies online.
V 1.6.3 looks very promising. I hope to have the time to fly and help with the beta testing phase...
|
|
|
Post by DirkDP on Feb 13, 2015 21:05:37 GMT -5
Hey guys. I think I mentioned this in another thread about a year ago. Would it be possible to add a center of gravity readout on one of the info screens. Like on the FMC of PMDG 737, or Feelthere 737 & Airbus.
|
|
|
Post by Travis on Feb 14, 2015 15:05:43 GMT -5
As you asked for ideas for further enhancements for 1.6.3 (hope this hasn't been discussed before): I miss situations with rejected takeoffs. It would be nice if there was a failure area with its own adjustable percentage for failures/birdstrikes occuring randomly at any time during the takeoff roll - if that is at all possible. Ralf, I do not recall this being discussed before. It's a nice idea - certainly something that should be under each Captain's control as far as percentages go. We would have to balance at least three types of calculations, so it's not a simple add of a new type of failure... rather a new condition of a failure type to check against. I'll discuss it with the team and maybe something could come together by 1.7.0.
|
|
|
Post by Travis on Feb 14, 2015 15:14:56 GMT -5
+1 to ralf9636 suggestions. It also would be nice, to have an option to simulate runway obstructions... or something like that, things that would make delays before landing. It'd be nice to have this option (completely enabled or disabled by user) in case someone flies online. V 1.6.3 looks very promising. I hope to have the time to fly and help with the beta testing phase... Of course any such option would be at the Captain's discretion... just as long as the choice is made before the flight. I've long wanted the ability for airports (facilities) to have dynamic abilities. For instance to be able to command SimConnect to close a segment of taxiway for AI & ATC use, and then to put some construction vehicles in that area. A little thing that may or may not make you change your normal route when you visit an airport. We could present such to a Captain before a flight, etc. The trick is to get the AI & ATC to cooperate. That's one thing about the Ground De-Icing system that we have... as well as GSX & AES. No other aircraft asks for de-icing! To obstruct a runway would be even more difficult. (Or to even mark an airport as closed due to snow or a crash, etc.) But it would be very cool to do! And it's an idea that I won't ever give up thinking about....
|
|
|
Post by Travis on Feb 14, 2015 15:19:55 GMT -5
Hey guys. I think I mentioned this in another thread about a year ago. Would it be possible to add a center of gravity readout on one of the info screens. Like on the FMC of PMDG 737, or Feelthere 737 & Airbus. I think the only problem would be in finding a place for it. Those screens are fairly crowded as it is. I'm certain that I could add it to the load screen... only in cases of auto-loading naturally. But that's a good idea, so I will start thinking on it!!
|
|
|
Post by peter on Feb 21, 2015 13:24:48 GMT -5
|
|
|
Post by nickatc on Feb 22, 2015 13:55:44 GMT -5
hahaha... almost! My idea is for dispatch to deny the approach clearance because (here it comes imagination) there is a loose dog on the RWY, maybe because there is FOD, perhaps because there is a runway inspection on course or because there is a problem in ATC communication facilities... The idea would be to create a small delay so that we captains would have to deal with it. Just an idea...
|
|
|
Post by bjratchf on Feb 22, 2015 13:59:07 GMT -5
This winter a few things have come to mind (and may have been mentioned in the last 7 pages of this thread I haven't read)-
Temporary runway closures for plowing and deicing: during periods of active snow/precip, runways sometimes are closed for 15 minutes at a time to facilitate the cleanup- leaving aircraft to hold on a STAR or fix for a predetermined amount of time. Could throw a cog in the wheel of someone's fuel calculations, and lead to the potential, but realistic diversion option...
Ground delay programs: could be simulated by gate holds before departure, or getting a takeoff time that must be complied with after push (go and hold in the pad for 5 minutes, then takeoff), speed requests during cruise... For example during the last hour of cruise, we could get a " maintain a speed at or below 280 knots in your descent" - which might change someone's planning for their top of descent point, but is realistic.
Gate area closures/cleaning: during winter ops, sometimes aircraft are asked to hold in a pad or on a taxiway, in order for ramp crews to finish clearing a gate.
MELs/CDLs: while it might be out of fscaptain's scope to simulate the more advanced failures of addons- fscaptain could store a basic MEL list and randomly, during preflight throw an error- (for example, in the 767, you can dispatch with an air conditioning pack inop, however the flight must remain within 60 minutes of an airport). Fscaptain would of course have to leave it up to us for compliance, as we'd have to just pretend the pack is failed- but you see where I'm going.
Oceanic requests: since oceanic airspace is usually uncontrolled by vatsim/ivao, the opportunity opens up for a rudimentary datalink/CPDLC use within the fscaptain ACARS. The ACARS can request the simpilot to "reduce to Mach .80" or the simpilot can request a step climb to fl350- and either be granted or denied, just like in the real world. Of course, "unable requested climb due to traffic" would be simulated, since fscaptain wouldn't be aware of other simulated or vatsim traffic.
Company gates: I don't simulated the "assigned parking" in fscaptain because I find that it usually assigns me parking in a random place where my airline doesn't park. It would be cool during the dispatch phase in the administrator to insert a few "favorite" gates at each airport so that when you get your in range message from the ACARS, it's not some random place.
|
|
|
Post by nickatc on Feb 22, 2015 14:07:20 GMT -5
... Company gates: I don't simulated the "assigned parking" in fscaptain because I find that it usually assigns me parking in a random place where my airline doesn't park. It would be cool during the dispatch phase in the administrator to insert a few "favorite" gates at each airport so that when you get your in range message from the ACARS, it's not some random place. As far as I know, you can change the gate at the destinations airport. Right before comminting for a flight. Not sure if this is what you are talking about... but I do it all the time. I select the parking gate on arrival airport. As for the rest of ideas, it would be nice to have them implemented.
|
|
|
Post by peter on Feb 22, 2015 17:17:09 GMT -5
As far as I know, you can change the gate at the destinations airport. True, but only within limits. FSCaptain filters the available gates and sometimes (!) it gets it really wrong. For instance, it insists to put my 777 on obscure cargo ramps at CYVR and my Beech 1900D on a military spot at PHNL that is about 3 km away from the actual terminal. I think allowing to assign any gate is the best improvement idea. Direly needed Peter
|
|