Managed to get a flight plan together, get clearance, taxi and depart
MIA in a Delta jet for Atlanta, but it was an ordeal. MIA_TWR previously
reported only 1/5 and 3/5 `voice read� using FSInn, so there I was
SHOUTING into the Mic and frantic. SB was loud and clear. FSInn
settings do not save well. It's very frustrating.
Made a decision when entering ATL CTR airspace to disconnect.. the
reason being it was so busy, plus I was unprepared to enter that `space�
with no charts, planning (except for some scribble-notes) or a view of
the traffic (ServInfo was shut down because it caused stutters when
updating.)
Didn't want to sound like a frantic doofus in front of all those guys!!
Vatsim is going to be fun but it may require a close-in, active Mic
where there'll be no shouting over the engine sounds.
-G
There were problems with a number of the VATSIM voice servers yesterday.
Some are still having problems today, but not as bad.
I'll add a feature to test the voice servers to the FSInn/VATSIM FAQ as it
does the data servers. The facility will work equally well with Squawkbox.
I'm sure it doesn't matter which client you use, the key is live ATC -
[V]irtual [A]ir [T]raffic [SIM]ulation... VATSIM.
-- L. James
--
L. D. James
lja...@apollo3.com
www.apollo3.com/~ljames
-- L. James
--
L. D. James
lja...@apollo3.com
www.apollo3.com/~ljames
>> Vatsim is going to be fun but it may require a close-in, active Mic
>> where there'll be no shouting over the engine sounds.
>>
>> -G
>
>There were problems with a number of the VATSIM voice servers yesterday.
>Some are still having problems today, but not as bad.
>
>I'll add a feature to test the voice servers to the FSInn/VATSIM FAQ.
>The facility will work equally well with Squawkbox.
>
>I'm sure it doesn't matter which client you use, the key is live ATC -
>[V]irtual [A]ir [T]raffic [SIM]ulation... VATSIM.
>
>-- L. James
L.J.. To answer your other question about the fsx.exe `compatibility�
tab, everything is either blank or grayed out on that tab.
I need FSInn and FSFDT to be able to SAVE changes I make in their
control panels and menus. It's really a pain to go back and change five
settings each time you start it. Have looked at the FSFDT folder for
`read only� attributes, etc. but it looks ok.
Also.. those AC that were causing INVALID code errors.. I looked at
the error log and cannot tell what CODE or ID is invalid, so to solve..
the AC folders were Zipped or Rar'd so the Aircraft.CFGs are no longer
a problem. Can I email that error log to you? and perhaps you can point
out the problems?
One other thing -- S.B. installed CELP codecs which are used in
commercial digital voice communications. How does FSInn handle
coherent digital audio?
-G
What's the best way to import a Flight Plan into Squawkbox?
Can it open FSX flight plan files? If so.. I could not find which
folder to look in.. everything being so rushed. If not.. what other
file can S.B. open?
Further.. what do you use to create a S.B. FP?
-G
Hi, Gregory. I'm self-conscientious about giving FSInn support in a
Squawkbox thread. I've already mentioned in the thread that Squawkbox works
as a great alternative client to FSInn. I had offered the support in your
other thread that was discussing FSInn.
I'll mention, however, that in most of the messages about support or
problems with FSInn I mention the importance of two messages... the
Installation sticky that you linked in your original message about FSInn and
the linked FSInn/VATSIM FAQ. Since you're saying you don't have a check
mark on the compatibility tab, this is indicating that you missed one of the
important steps. It might have saved you a lot of aggravation had you
mentioned earlier that you didn't (or couldn't) do that step. Most Vista
users would have been able to assist you with it... especially the users who
experiment with making changes to their OS.
You can access that box by turning on UAC. If for someone reason you prefer
to have your Vista's protection turned off, you can turn it back off after
you've configured that check mark as referenced in the FSInn installation
sticky.
By the UAC protection is a great addition for computer users. Many of my
customers who would inherent problems with their computers in months and
have to call me to fix it has gone for years without developing computer
problems with I attribute to the UAC protection. It helps even me to avoid
inadvertently installation something or allowing programs to make changes to
my OS.
I can't speak directly about technical implementation of the VATSIM Voice
Library the two applications use, but they use the same Library. I will say
that in the past when people reported problems with communicating with FSInn
I advised them to go over the steps presented in the two messages, more
specifically the FSInn/VATSIM FAQ and report to me the results. The ones
who actually report the steps report success. Some people won't do the
test. They look at the steps and say they are having a different issue.
Those are the only ones that appear not to have their issues resolved.
>> L.J.. To answer your other question about the fsx.exe `compatibility�
>> tab, everything is either blank or grayed out on that tab.
>>
>> I need FSInn and FSFDT to be able to SAVE changes I make in their
>> control panels and menus. It's really a pain to go back and change five
>> settings each time you start it. Have looked at the FSFDT folder for
>> `read only� attributes, etc. but it looks ok.
>>
>> Also.. those AC that were causing INVALID code errors.. I looked at
>> the error log and cannot tell what CODE or ID is invalid, so to solve..
>> the AC folders were Zipped or Rar'd so the Aircraft.CFGs are no longer
>> a problem. Can I email that error log to you? and perhaps you can point
>> out the problems?
>>
>> One other thing -- S.B. installed CELP codecs which are used in
>> commercial digital voice communications. How does FSInn handle
>> coherent digital audio?
>
>
>Hi, Gregory. I'm self-conscientious about giving FSInn support in a
>Squawkbox thread. I've already mentioned in the thread that Squawkbox
>works as a great alternative client to FSInn. I had offered the support in
>your other thread that was discussing FSInn.
With all due respect L.D., what the blazes are you talking about? Have
you received emails from me over the weekend? I've already read your
Installation link about two weeks ago and pointed out some ambiguous
parts, and that the app doesn't run as expected after reading the docs.
Also the OS here is Xp Pro SP3 and there's no Administrator setting in
the Compatibility tab.
I've spent some four evenings and one afternoon sitting in parking spots
at various FSX airfields trying to verify proper comms operations. FSInn
IMO in a good client with lots of features, and I'm willing to work at
solving the issues, but PLEASE don't advise me to read over your
Installation notes again. :-]]
-G
You did mention parts that you pointed out as ambiguous. I thought I had
clarified those parts you pointed out as having been direct and specific.
>
> Also the OS here is Xp Pro SP3 and there's no Administrator setting in
> the Compatibility tab.
I'm sorry. I reviewed the thread, but guess I didn't review it far enough.
In the messages I was reviewing I couldn't tell which OS you were running.
While the question is consistent, to specify no such tab for me is a good
answer. I really didn't mean to impose extra work.
>
> I've spent some four evenings and one afternoon sitting in parking spots
> at various FSX airfields trying to verify proper comms operations. FSInn
> IMO in a good client with lots of features, and I'm willing to work at
> solving the issues, but PLEASE don't advise me to read over your
> Installation notes again. :-]]
I guess you're right. It was fairly against my better judgment to offer
support for FSInn in a topic specific to Squawbox. When you asked what was
wrong I should have suggested that you start another topic with FSInn as the
subject matter. I should have just let my input stop on the reference that
there were substantial voice server outage on the day you described as
having voice connection issues.
I always use the "Installation notes" as reference. But of course I can
resist imposing support where it's not wanted.
> -G
>
>>I'll mention, however, that in most of the messages about support or
>>problems with FSInn I mention the importance of two messages... the
>>Installation sticky that you linked in your original message about FSInn
>>and
>>the linked FSInn/VATSIM FAQ. Since you're saying you don't have a check
>>mark on the compatibility tab, this is indicating that you missed one of
>>the
>>important steps. It might have saved you a lot of aggravation had you
>>mentioned earlier that you didn't (or couldn't) do that step. Most Vista
>>users would have been able to assist you with it... especially the users
>>who
>>experiment with making changes to their OS.
-- L. James
"Gregory" <flights...@bkwds.comcast.net> wrote in message
news:ltvif59ftemnp78r4...@4ax.com...
> On Tue, 10 Nov 2009 01:13:26 -0500, "L. D. James" <lja...@apollo3.com>
> brought the following to our attention:
> With all due respect L.D., what the blazes are you talking about? Have
> you received emails from me over the weekend?
I hadn't noticed email from you. I get a lot of email and start out with
expected email and work my way up. If I'm not expecting something specific,
don't recognize the name or the subject matter, it might be weeks before I
see it, if it see it.
I will check, however, out of respect. If I had saw it in the past, I would
have respectfully replied to it.
>It was fairly against my better judgment to offer support for FSInn
>in a topic specific to Squawbox. When you asked what was wrong
>I should have suggested that you start another topic with FSInn as
>the subject matter. I should have just let my input stop on the
>reference that there were substantial voice server outage on the
>day you described as having voice connection issues.
L.D.
How about If I start another topic on FSInn.. because it has lots of
good features and I'm interested in getting it to work. Only condition
is that you don't mention the installation notes aGaiN. :))) We're
way past that stage now. BTW there's a 69-page FSInn doc here in
PDF format that I've read nearly end-to-end.
-G
"Gregory" <flights...@bkwds.comcast.net> schrieb im Newsbeitrag
news:ll6gf51psjoe14hqm...@4ax.com...
"Gregory" <flights...@bkwds.comcast.net> wrote in message
news:409jf5petga2626oo...@4ax.com...
Hi, Gregory. I'd gladly work with anyone interested in my assistance. Many
times when trying to help the users give me the impression that I'm
imposing, and I ease up.
As far as not mentioning the installation notes, I'm sorry. But that's not
possible. Even though I wrote them, when someone described a problem, I
look thought their description and compare it with two messages, the
installation sticky that you originally linked to and the linked FAQ find
out how the steps deviated or what is missing. Then I suggest then I
suggest what to do from the same information I'm looking at. I find it very
convenient.
Also, I find it important, for others and validation, to know if it
continues to work. While people often become angry at me and interpret the
procedure as a callous concern, I know that many people appreciate that type
of effort because I receive lots of emails and PM's from people that never
post a single message telling expressing thanks for having helped them.
This is something I learned from the Usenet group long ago. Most of the
Usenet groups that I read have a FAQ. Most of the people that gives the
best assistance in that group will hardly retype something that is already
written in the Usenet group FAQ. They will point to the Usenet group FAQ.
They'll also update the Usenet group FAQ if it becomes necessary, based on
something they the user applying what in the FAQ, if it fails and they have
to look for a different resolution.
I really hope the installation sticky and the linked FAQ will help dispel
the notion that using FSInn is a haphazard venture where a person will have
the fiddle until they get lucky.
By the way, I found email from you. I'll reply to it soon. I won't retype
what you posted in the email. But I will tell you that the question you
asked is spelled out clearly in the linked FAQ of the installation sticky
that you originally linked.
I wouldn't retype the information in the FAQ. I'd give you the FAQ question
as a reply. If you were having problems with the wording of the FAQ entry,
I'd then try to find different words to explain the information. At
present, I've spent a four years trying to find the best words to explain
each entry. I don't think I could do it better initially without some
reference to which part might be confusing.
James.. you are wasting your time and everyone else's typing six or
seven paragraphs below, each of which says READ THE FAQ. And yes
you are pissing me off by not providing a single concise answer to a
specific question. Do NOT reply to my emails with READ THE FAQ!!
I expect you to provide TECHNICAL answers!!!! not BS.
The original FSInn issue was posted on 10-22-09 and went on for some
nine days.. where in each reply you typed six, eight, ten paragraphs of
bullshit defending your FAQ and Installation Notes. Are you a technical
guy or some book writer?
You know.. I must have 10 or 15 printed docs on my desk, trying to
digest them all, and dealing with multiple FSX technical issues all at
the same time.. and that doesn't include my `day job.� Things are going
well with FSX, but for now I'm going to use Squawkbox until all is
working smoothly.
Maybe then I'll go back and try to diagnose FSInn by digging through the
docs. You really have not been ANY help. Recall I was the one who posted
the Install Note in the first place! (see link above) Danny has provided
10 times more information that you and your 100 paragraphs of FAQ and
Installation Sticky harping.
Ok? Thank you and good bye.
-G
>Guten Morgen Gregory,
>concerning VATSIM FSInn (ATC voice contact) I am exactly in the same state
>of progress then you.
>I can only say KEEP ON Bei� die Z�hne zusammen.
>FSInn is a little challenging sometimes. But there is benefit against SB.
>Regards G�nter
Guten morning Herr Gunter.. The teeth bite together? :)))
I've been on the ground with FSInn, and in the air several times with
SquawkBox. The one time with FSInn was on a short hop from Orlando
to Daytona Beach with comms and text chat at the departure end.
Of the VATSIM flights in the past 2 or 3 weeks, I'm finding that once in
the air, being very much unprepared to make the flight. That is.. a lack
of planning, information, charts, diagrams, frequencies, etc. It's a new
and exciting aspect of FS.. and FSX specifically.
Last night I install.. http://www.vroute.net/ which is also exciting.
It keeps getting better and better.
As for FSInn.. will get to is before long, but right now I need to
GET IN THE AIR!! q:]]
-G
>Guten Morgen Gregory,
>concerning VATSIM FSInn (ATC voice contact) I am exactly in the same state
>of progress then you.
>I can only say KEEP ON Bei� die Z�hne zusammen.
>FSInn is a little challenging sometimes. But there is benefit against SB.
>Regards G�nter
Ausger�umt Morgen Herr Gunter. Die Z�hne bei�en zusammen? :)))
Ich bin auf dem Boden mit FSInn, und in der Luft mehrere Zeiten mit
Squawkbox gewesen. Die eine Zeit mit FSInn war auf einem kurzen Sprung
von Orlando zu Daytona Strand mit comms und Textplauderei am
Abfahrtende.
Von den VATSIM Fl�gen in den vergangenen 2 oder 3 Wochen, finde ich dass
einmal in der Luft, ist sehr viel unvorbereitetes, den Flug zu machen.
Jener is. ein Mangel der Planung, Informationen, Diagramme, Zeichnungen,
Frequenzen usw. Es ist ein neuer und aufregender Aspekt von FS. und FSX
ausdr�cklich.
Gestern Abend installiere ich.. http://www.vroute.net/, der auch
aufregt. Es beh�lt, sich zu erholen, und besser.
Als f�r FSInn. wird erhalten zu bald ist, aber jetzt ich muss IN DIE
LUFT ERHALTEN!! q:]]
-G
I won't. I'll just point to the FAQ question that answers the question in
your email:
----- Question -----
How can I change the CALLSIGN from my default `ED-WNN� to something like
DAL171 for Delta 171? and also create a pulldown list of 3 - 5 frequently
used callsigns?
----------
----- Answer -----
FSInn/VATSIM FAQ question #10 ("How can I change my Default Callsign?")
----------
>
> I expect you to provide TECHNICAL answers!!!! not BS.
Actually I expected some appreciation for my attention to your questions.
But again, if you had the question, there's a chance someone else has it
also. Maybe someone else will read the entry and give you the resolution.
And of course, it'll help others with the same or similar question.
>
> The original FSInn issue was posted on 10-22-09 and went on for some
> nine days.. where in each reply you typed six, eight, ten paragraphs of
> bullshit defending your FAQ and Installation Notes. Are you a technical
> guy or some book writer?
>
> http://groups.google.com/group/alt.games.microsoft.flight-sim/browse_thread/thread/23b71a02cb252ba0/ec4136c04d2efdcb
>
Looking at the link you posted. It's with the picture of your error. It's
in the Original Linked sticky. While you might bash it. It could have
saved you a lot of time if you had at least looked at the list of questions
in the FSInn/VATSIM FAQ that is highlighted in red.
The answer to that is very simple. It's FSInn/VATSIIM FAQ question #17 (out
of the only 17 FAQ questions). "Why is FSInn Failing to install (Error
writing file)?".
This, just like any other issue you might have could save you days.
I'm very sorry for your "pissed off". But if you post the question, I'll
point to the resolution that is listed in a short list. I know it helps
lots of people. Because they express their appreciation.
Of course you can go to a private forum and bash FSInn as being haphazard
and not working. But for the general public that might stumble on the
question writing in this forum, they will be able to see the resolutions are
consolidated in two short messages.
> You know.. I must have 10 or 15 printed docs on my desk, trying to
> digest them all, and dealing with multiple FSX technical issues all at
> the same time.. and that doesn't include my `day job.� Things are going
> well with FSX, but for now I'm going to use Squawkbox until all is
> working smoothly.
It issues related to FSInn could have been contained in two printed docs.
If I were in your place, I'd appreciate being able to replace the 15 pages
with two.
>
> Maybe then I'll go back and try to diagnose FSInn by digging through the
> docs. You really have not been ANY help. Recall I was the one who posted
> the Install Note in the first place! (see link above) Danny has provided
> 10 times more information that you and your 100 paragraphs of FAQ and
> Installation Sticky harping.
>
> Ok? Thank you and good bye.
You're very welcome. Good Bye.
-- L. James
You don't answer my emails.. then plaster my callsign on the newsgroup!!
I've already figured that out.. you bozo.
>----- Question -----
>How can I change the CALLSIGN from my default `ED-WNN� to something like
>DAL171 for Delta 171? and also create a pulldown list of 3 - 5 frequently
>used callsigns?
>----------
>----- Answer -----
>FSInn/VATSIM FAQ question #10 ("How can I change my Default Callsign?")
>----------
Why don't you guys `ring me up� when flying.. but of course trolls will
also doing that now.
-G
Hi, Gregory. VATSIM, with programs such as Servinfo, VATSpy, and a number
of other server browser tools that has been presented to you in this news
group, isn't the place for anonymity.
>
> I've already figured that out. you bozo.
I didn't know you had figured it out. Because it appeared to have been so
clear in the original message I gave you for using FSInn with VATSIM, I didn't
know it really took figuring. But I tried to help anyways.
The word "bozo" may have a different connotation or meaning for me than for
you. To me it would closer resemble someone spending weeks discovering
resolutions that are already presented in two messages. It might closer
resemble someone developing hatred for someone trying to help. I would
still consider it a harsh word for someone just being a bit confused and
having problems.
>
>>----- Question -----
>>How can I change the CALLSIGN from my default `ED-WNN� to something like
>>DAL171 for Delta 171? and also create a pulldown list of 3 - 5 frequently
>>used callsigns?
>>----------
>>----- Answer -----
>>FSInn/VATSIM FAQ question #10 ("How can I change my Default Callsign?")
>>----------
>
> Why don't you guys `ring me up� when flying.. but of course trolls will
> also doing that now.
Thanks for the invitation. By the way, you'd hardly have trolls on VATSIM.
People that don't respect the rules and spirit of the network will not stick
around. There is a strict requirement for ATC control and separation. If
you're harassed in the least when on VATSIM, just use the .wallop command
and a network supervisor will be there to help you, even if you're being
harassed by a controller. The offending troll will drift somewhere else.
VATSIM is a great network. You don't need FSInn to use it. Squawkbox will
work very well.
By the way, I welcome the traffic when I'm flying. You can easy find me by
my name or LWA2237 callsign. VATSpy has a feature to notify you when your
favorite person is flying.
>
>
> -G
>
> Last night I install.. http://www.vroute.net/ which is also exciting.
> It keeps getting better and better.
>
> As for FSInn.. will get to is before long, but right now I need to
> GET IN THE AIR!! q:]]
>
>
> -G
Let me guess... you bought the premium version. I just installed the
free version and I finds a route for me but to do anything it says
"available in vroute premium" It does look nice though.
--
==============
==============
boB-Copter_Six
==============
==============
Regarding Vatsim, you can click the ATC tab and see the probabilities of
when Vatsim might be staffing those locations. It will also show if any
Controller has already 'booked', in advance, his time at the scope. I don't
find that feature being used very much, although I have seen several KLAX
controllers shown here when they 'pre-booked' their time slot.
Danny
"boB-Copter6" <cop...@xxxyahooxxx.vom> wrote in message
news:hdo0rc$loq$1...@news.albasani.net...