You are probably right about the link being still intact, because
although FSX went, the IVAO panel stayed open, until I closed it with
Task Manager.
The lockups, sometimes preceded by ground to stratosphere spikes,
baffle me. They have to be linked to IVAO because I can't reproduce
them off line. Also they occur after landing, never before takeoff,
when at the same airfield. Usually they are preceded by an FSX error
message about being out of memory and advising a change in FSX
settings. Last night there were no messages and it was just FSX that
was affected, whereas often it's the system that goes; occasionally to
the blue screen.
Which server were you on last night Mike, if you can remember that far
back? I think mine usually offers the same server, which I normally
just accept. Is there a preferred server, from recent experience?
The only other thing that has changed on my FSX is that for some time,
because of the early morning flights, the joining panel has been set
to "No Voice". Since I was flying VFR and no ATC at Belfast, I left it
at that setting when I joined last night.
Another factor I'd thought might have a bearing is AutoGen. I don't
recall having the Lockup in the area covered by the Horizon scenery.
That area is free from Default AG, although I have lots of third party
AG present, in the main it doesn't include buildings and is certainly
not blanket coverage. I'd reduced my AG slider from max to Dense,
before last night's flight. Is there any mileage in AG as a cause?
I spoke too soon! I launched IVAP, just, to check what the no voice
option was called. I did this by triggering the IVAP panel, pressing
the Join panel to look at the option, then pressing the Cancel button.
Then On the FSX screen, I went to the top and opted to Stop IVAP. At
that point I FSX locked and, untypically, I got the message about FSX
having to close, Restart, Phone Message etc.
So, it's happened off line, though with IVAP still a possible factor.
The plit thockens...
Gerry Winskill
Fossil wrote:
Just to add to that I saw you all the way from EGNC to EGAC and then
you sat
on the ground for ages. Although your target dropped off screen once or
twice it was still there when I finally logged off at 2200. It
suggests that
even though your FS had locked up your connection to IVAO was still
intact.
bones
bones@xxxxxxx
-----Original Message-----
From: jhb-bounce@xxxxxxxxxxxxx [mailto:jhb-bounce@xxxxxxxxxxxxx] On
Behalf
Of Mike Lucas
Sent: 16 July 2009 22:49
To: jhb@xxxxxxxxxxxxx
Subject: [jhb] Re: IVAO Tonight
Gerry
Both Bones and I watched your approach at EGAC - Bones on his radar
display, me on TCAS. You disappeared from my TCAS just before
landing, although Bones reported you still on radar. After I landed
there myself, I gather you disappeared from radar briefly but when
you reappeared you were once again visible to me so I taxied and
parked alongside you for about 5 minutes before taking off again and
returning to EGNS. I suspect we were on different IVAO servers, and
one of them may have thrown a wobbly.
Unfortunately there was very little other traffic tonight to get any
sort of accurate picture of whether there were other disappearances.
Mike L
Gerry Winskill wrote:
Tonight I flew, IVAO, Kirkbride to Belfast City; the latter being
the latest ARM project. He's reacted to my suggestion and is
spending hours using GE to create photoscenery for the EGAC circuit
area. I wonder if Mally's ears are burning?
Anyway, I spotted Mike leaving EGNS, also bound for EGAC. I saw him
on finals, before he disappeared from FSX and Servinfo. Shortly
after that I had another FSX lockup. Thinking back, I don't recall
having one when not on line. I've even re flown problem flights, off
line, without problems. Tonight's lockup was whilst I was parked on
the GA apron, in Spot View, looking round for Mike. Off line I've
done this until dizzy, without getting it to lock up.
Anyone have any ideas on cause and effect?
Gerry Winskill
__________ Information from ESET NOD32 Antivirus, version of virus
signature
database 4251 (20090716) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
