I'm having a problem with this useful utility when running via WideFS. This is what the display shows:-

 

 

 

But installing in on my FS9 PC it shows all the information correctly...

 

 

 

I will write to the author but I wondered if anyone else had experienced the same problem.

I'm having a problem with this useful utility when running via WideFS. This is what the display shows:-

 

 

 

But installing in on my FS9 PC it shows all the information correctly...

 

 

 

I will write to the author but I wondered if anyone else had experienced the same problem.

Hi to all, thanks for this issue: I'll investigate if there is a speedy w/a or is better to integrate widefs. Thanks for your patience!

 

geniX

Hi Genix,

 

Thanks for replying. Is it possible for the entry in FSUIPC.ini to be different? Tail means other programs such as FS Flight Keeper can't identify aircraft by their liveries, only reg number.

 

I would like AITT2 but only if the entry in fsuipc.ini can be different.

genix,

 

I changed the entry in fsuipc.ini from Tail to Flight. AiTT2 still continued to display Ai flight details correctly. Just thought you and others might be interested.

 

If you can get it working via WideFS it would certainly interest me.

Hi Ray. Very well discover!

I used the Tail in order to have a better granularity in flight "cancellation" searching.

So, about WideFs: now I remember the patchwork used some years ago.

The first thing is to share the drive and main path of the running FS (i.e. \\MyrunningFS\Program Files\Microsoft Games\Fs9) on the pc running FS, the second is to put in the aitt2.ini file the row (under the [General] section)

 

 

FSPath=Z:

 

where Z: is the mapped network drive (on the pc running AITT2 through WideFS).

 

The key aspect is that AITT2 get real-time info from FSUIPC but ETA/ETD from the traffic.bgl files; for this reason it needs to understand where these files are.

Anyway, in some days I wish to introduce WideFs facilities in AITT2...

 

P.S. - Send me your e-mail address for a prize ;)

Hey Ray,

Thanks for this post! I was unaware of AITT for FS9 until this post! I am now a proud owner :)

 

Thank you for the information!

-Paul

Hi Ray. Very well discover!

I used the Tail in order to have a better granularity in flight "cancellation" searching.

So, about WideFs: now I remember the patchwork used some years ago.

The first thing is to share the drive and main path of the running FS (i.e. \\MyrunningFS\Program Files\Microsoft Games\Fs9) on the pc running FS, the second is to put in the aitt2.ini file the row (under the [General] section)

 

 

FSPath=Z:

 

where Z: is the mapped network drive (on the pc running AITT2 through WideFS).

 

The key aspect is that AITT2 get real-time info from FSUIPC but ETA/ETD from the traffic.bgl files; for this reason it needs to understand where these files are.

Anyway, in some days I wish to introduce WideFs facilities in AITT2...

 

P.S. - Send me your e-mail address for a prize ;)

Just to clarify...

So Z should be \\XP64FS9\Microsoft Games\FS9 for example if that is where FS9.exe is located?

 

Also Ray, I am using it over WideFS right now and while I am getting some DELAYED like in your pics alot of the flights are also registering correctly but the times are all over the place...

This is with nothing in the Path= line When I try to add my FS9 path to that line AITT pops up and asks where my FS9 is on startup?

Hi Ray. Very well discover!

I used the Tail in order to have a better granularity in flight "cancellation" searching.

 

Okay. I don't fully understand what that means but I think the first priority is to get it running across WideFS.

 

So, about WideFs: now I remember the patchwork used some years ago.

The first thing is to share the drive and main path of the running FS (i.e. \\MyrunningFS\Program Files\Microsoft Games\Fs9) on the pc running FS, the second is to put in the aitt2.ini file the row (under the [General] section)

 

 

FSPath=Z:

 

where Z: is the mapped network drive (on the pc running AITT2 through WideFS).

 

My FS9 install is located in F:\Fs2004. However despite mapping the entire F drive and entering the path into aitt2.ini I am prompted for the path to FS9 when AiTT2 launches. I don't know how you can map to a drive letter on another PC without using the full network path such as \\flying\fs2004. By mapping as you suggest the path becomes \\flying\F\fs2004 which is even longer. Is it not possible for you to accept a full network path to the location of fs9.exe?

 

The key aspect is that AITT2 get real-time info from FSUIPC but ETA/ETD from the traffic.bgl files; for this reason it needs to understand where these files are.

Anyway, in some days I wish to introduce WideFs facilities in AITT2...

 

Okay, I understand that. But I think you need to allow a full network path in the ini file unless I am totally misunderstanding what you're asking me.

 

P.S. - Send me your e-mail address for a prize ;)

Thanks. I've sent you a PM.

 

Just to clarify...

So Z should be \\XP64FS9\Microsoft Games\FS9 for example if that is where FS9.exe is located?

 

I think you'll find that a full network path will not work and you'll get the popup prompting you for the location of FS9.EXE.

 

Also Ray, I am using it over WideFS right now and while I am getting some DELAYED like in your pics alot of the flights are also registering correctly but the times are all over the place...

 

If you check the two tables Paul they are completely different flights even though both programs are running at the same time. It looks to me as if AiTT2 is getting different times when run via WideFS.

 

Hey Ray,

Thanks for this post! I was unaware of AITT for FS9 until this post! I am now a proud owner :)

 

Thank you for the information!

-Paul

 

You're welcome Paul. I was a bit surprised more people hadn't noticed this as it's a nice utility.

Hi Ray,

I get the exact same thing when I enter the full path in that field... All of a sudden a pop-up asks for my FS Path but there is no way to browse to my FS9 machine from that popup and I have to cancel out. If I then leave that field empty "some" flights seem to work but the times are all over the place...

Hi Paul,

 

The problem is that dialogue box has no option for pointing to a network location and it needs to have one.

 

If that can be changed then we're making good progress. But as geniX said there may be good reasons why he's done it the way he has.

 

I think the aesthetics could be improved but that's secondary to getting it to work across WideFs. There's no way I can run it on my FS PC as I only have the one display.

 

All my flights via WideFS are non-existent.

I am with you there Ray... I run everything over WideFS... I would also love to see re-sizable windows but like you I just want to make sure it is working properly first. I already had both my FS9 (/userdata folder) as well as full FS9 directory shared for other apps so perhaps that is why some flights are working on my end?

Hi Paul,

 

I've turned everything off now so will check later but I'm pretty sure I have the same permissions setup as you.

 

I admire people who have the skills to write programs like this. I wish I knew how it was done and I'm sure it's a lot harder that I imagine. Hopefully we can get a useable version running across widefs and the author can watch as the cash rolls in!

Hi to all. First thank you for this chatting...

Now, AITT2 when find a blank FSPath, it tries to search into the registry and...if the PC doesn't have FS2004 installed...it start the annoying dialogbox to find the path.

AITT2 is not to test if fs2004.exe is in the main directory, nor checks the FSPath length.

What it needs is a successful path to main fs2004 folder maybe with a drive letter first.

I confirm I am going to take in charge WideFS users, too.

 

Thanks for all kind of comments!

Hi geniX Soft,

 

You do need to allow for a network path to be selected rather than just a drive letter. Drive letters cannot be accessed directly across a network.

 

When the dialogue box is presented it needs to include an option to My Network Places like this...

 

 

 

Sorry if you already know this.

 

The PC I'm running this on did have FS9 installed on it a few years ago but I was sure I had removed all entries in the Registry. Perhaps some remain which is why I'm getting such odd data compared to Paul.

 

Is there a particular registry entry I can check for?

Hi Ray, I was about to suggest a registry search for FLIGHT that is what I did... I did a search this morning and all of the registry references to FS9 I have on the box I have AITT installed on actually point to my network share on my other FS box... Incidentally, just thinking out loud now; what about running the F1 registry fixer and pointing THAT to your networked FS drive... I believe I have done that in the past as well.