jpc55

Just finished running 1.1.15, and all went flawlessly! :excl: Took it for a short burger run and a flight over Sac; and all is good. Will post if I find anything. Awesome Steve, thanks ever so mush. B)

This is what I found with Sacramento, Ca. and the brown spots are associated with parks. :o

I re-ran the ContentConverter but had to leave just about the time it was going to complete, so I did not get see that. My computer crashed after it had completed, and no, it did not cause it to crash. This time there was no ContentErrors and I fired it up and all is well. B) I really need to rebuild this old computer!

@ winjimon “BTW, I don't use Norton if you were suggesting it could be interfering” No, in toolkit 1.1.12 and early versions I had to turn off my Norton 360 to install/uninstall the toolkit because it was detecting a false bug. Shortly after toolkit 1.1.12 came out, I had to re-download my Norton 360 and what I downloaded was what they are replacing 360 with. My wife’s computer has the latest version of “Norton Security” and when you open it, that its name. My Norton is the same as hers, but mine is still named Norton 360. :o I will try running it again and will let you know happens. :smile:

Well when I went into the Avsim Flight forum today, I saw that Toolkit 1.1.13 became available from stonelance. I downloaded it, installed it, and ran the ContentConverter. (It took between 35 and 40 mins. to run) It seems to have a problem: Here is how it ended, and a copy of the ContentErrors. Hope this is helpful Steve? I would like to add that a short time back I had a problem with my Norton 360, and had to re-download it. Before, I had to temporarily turn off Norton to install/uninstall the toolkit, however now it no longer has that problem.

Ah, still another victim of FSX in FLIGHT! B)

Thanks Kavinda J.D As always, greatly appreciated. That is like 100% better. A great day to you and yours, and to all!

There was a thread started back on 4/27/13 that might help you a little. It is on page 31 at present, and I hope this link will work to get you there. Wishing you good luck! B) http://forum.avsim.net/topic/406364-the-white-cross-hairs-and-x-when-using-a-mouse-and-keyboard/

Thanks majuh for your response, maybe someone will be able to come up with a way to convert it to the small o. :o

@ majuh, in your #11 post you have a SS that indicates (correct me if I am wrong) you are flying in mouse mode. Lately I have had to start flying in mouse mode more because my yoke and throttles are due to be replaced. What I would like to know is how to change the mouse mode monstrosity indicator to the little “ o “ like you have. Greatly appreciate any, and all help, and a great flight day to all. :o :smile:

Here was another CE, but it only lasted a few seconds. This was a clandestine flight from Blue Canyon-Nyack (KBLU) to Kingdom (O20) a distance of 77.5nm. I was about 25nm from my destination when I got this hit. :ph34r: I continued on only to be hit with this on final. I thought I was going to have to go on instruments and execute a missed approach, but being able to see the ground and with the 41kts wind I slowed the plane down to a crawl and made my way to the runway, and it was a really a short roll on landing. Until next time, a good day to all! B)

Thanks Dick, I really do appreciate your time and effort with this. I added your taxiway sign fix for KPVU and this was the results. Thank you again, and to all who are helping to keep Flight alive! :excl:

Just wondered what you make of this stonelance? I was flying a mission from Delta Mun. (KDTA) to Provo Mun. (KPVU) Dis. 62.3nm. When on approach to land, this popped up. I took a number of SS of this anomaly, trying different scenery setting, and then my computer crashed. This crash happens from time to time, so I don't think that this caused the crash. After it rebooted I went back to the location and it now came up like this. I played around with different scenery setting again, and the only common thing with all of them was this one runway sign. Here is a verity of SS. Just curious. :wink: :smile:

Ah, still another encounter! This time I had a clandestine run from Blue Canyon-Nyack (KBLU) to Auburn Mun. (XAUN) and it was a distance of 26.1nm; so I knew that LE (Law Enforcement) would probably be on me at takeoff or shortly thereafter. I got my first hit as I was taxing for takeoff. I proceeded with takeoff and dove down the first canyon on the south side of Interstate 80 that would take me to my destination, when I got my second hit, and he locked on to me at this time. These sets of SS were of my run down to canyon trying and make it to my destination. :o Well on the first attempt, I was busted, so I restarted the mission. Being familiar with the area, I decided to try flying down the canyon on the north side of Interstate 80. I took off and did a 180 headed for the other canyon. Just after I crossed over I-80 I had this hit from LE, but no lock. I continued on into the canyon, and this time I completed the mission. :ph34r:

Another Close Encounter! I thought you might like to see some SS of my latest encounter. This took place in the state of Nevada. It is a clandestine flight from Fallon Mun. (KFLX) to Derby (LOL) and the distance was 34.9nm. About 26.8nm from my destination, JAFO said he spotted another plane close by, but it only lasted a second. Then at about 24.5nm out, I had a second hit, and this time he got a lock on me. These are SS along the way. After landing I went to the overhead view and watched as he circled above me, never coming closer then .5nm from me. I remember someone asking a short time back, can law enforcement be beaten; well this is not my first time. :ph34r: