Page 1 of 1

Flightplans

Posted: 07 Dec 2008, 07:29
by Jumpshot724
So, I got a little sick and tired of AFCADs, my eyes are starting to not like them lol and decided to write some flightplans of a non-military nature. I just wanted to know if the following code would work correctly as it's a mix:

AC#3,N620FE,60%,WEEK,IFR,1/11:00:00,1/12:00:00,360,F,19,RJBB,1/12:19:00,2/08:30:00,350,F,18,KMEM,2/10:00:00,2/12:00:00,360,F,19,RJBB,2/12:19:00,3/08:30:00,350,F,18,KMEM,3/10:00:00,3/12:00:00,360,F,19,RJBB,3/12:19:00,4/08:30:00,350,F,18,KMEM,4/10:00:00,4/12:00:00,360,F,19,RJBB,4/12:19:00,5/08:30:00,350,F,18,KMEM
AC#4,N578FE,60%,24HR,IFR,01:00:00,04:00:00,360,F,1432,KJFK,07:22:00,10:17:00,350,F,1431,KMEM

Posted: 07 Dec 2008, 07:37
by Flyin Illini
This:

AC#4,N578FE,60%,24HR,IFR,01:00:00

Needs to be this:



AC#4,N578FE,60%,24HR,IFR,0/1:00:00

Posted: 07 Dec 2008, 07:56
by MACC
Flyin Illini wrote:This:

AC#4,N578FE,60%,24HR,IFR,01:00:00

Needs to be this:



AC#4,N578FE,60%,24HR,IFR,0/1:00:00
No it dosen't, because it's a 24HR flightplan so it's just xx:xx:xx, but it would need a 2nd leg i thought.

Macc

Posted: 07 Dec 2008, 08:29
by swp53
Why not use Rips utiiity RPP_FPGen_v1.0 and let it do the work for you

Posted: 07 Dec 2008, 08:57
by Flyin Illini
yea youre right macc, i dont do 24hr cause they are boring i think at least. My fault.

Posted: 07 Dec 2008, 11:08
by MACC
Flyin Illini wrote:yea youre right macc, i dont do 24hr cause they are boring i think at least. My fault.
No probs, thanks for making the effort to help anyway :)

Posted: 07 Dec 2008, 16:06
by Jumpshot724
There will be more legs. I'm using 24hr because it's set flightplans for FedEx (I still can't believe FedEx wasn't included in UT after all these years :shock: )

I just wanted to know if the "WEEK" and "24HR" variables could be used together

Posted: 07 Dec 2008, 16:20
by campbeme
Hey Jumpshot,

Why not download the WOAI pack? It's upto there usual high
standard and will save you a heap of time.

Mark

Posted: 07 Dec 2008, 16:49
by Ford Friendly
Jumpshot724 wrote:I just wanted to know if the "WEEK" and "24HR" variables could be used together
The answer to that question is fairly simple. Since the repetition time indicators relate to different flightplans which in turn relate to different aircraft, there's no conflict.

Expanding on that, even IF the beginning of the two lines was as follows:
AC#3,N620FE,60%,WEEK,IFR,...
AC#3,N620FE,60%,24HR,IFR,...
these lines actually refer to 2 separate and distinct aircraft which just happen to be using the same texture and flight data (the AC# part which is the link to the aircraft.txt file and that, in turn points to the aircraft.cfg files/data) and are coincidentally using the same flight identifier (the N620FE part - something only the ATC cares about). Both aircraft would fly with no problem.

The only one who might notice is you/the user if both aircraft are in the same ATC area at the same time that you are.

At least that's my understanding.

Posted: 07 Dec 2008, 22:58
by Jumpshot724
Hey Jumpshot,

Why not download the WOAI pack? It's upto there usual high
standard and will save you a heap of time.

Mark
Because I just spent 3 days free time researching ~1000 flightplans from the past week lol


The answer to that question is fairly simple. Since the repetition time indicators relate to different flightplans which in turn relate to different aircraft, there's no conflict.

Expanding on that, even IF the beginning of the two lines was as follows:
AC#3,N620FE,60%,WEEK,IFR,...
AC#3,N620FE,60%,24HR,IFR,...
these lines actually refer to 2 separate and distinct aircraft which just happen to be using the same texture and flight data (the AC# part which is the link to the aircraft.txt file and that, in turn points to the aircraft.cfg files/data) and are coincidentally using the same flight identifier (the N620FE part - something only the ATC cares about). Both aircraft would fly with no problem.

The only one who might notice is you/the user if both aircraft are in the same ATC area at the same time that you are.

At least that's my understanding.
Yea, that's what I figured I just wanted to make sure. Thanks!!