Hi,I am getting this error message in the main screen dialogue screen and the weather is not appearing in FSX... E"ror during element identification for ---: Object reference not set to an instance of an object."....any ideas ?Thnx

Hi Gabe,That is a strange one. First try a uninstall/reinstall cycle.Please let us know.Thanks,Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/

I would like to second this error.It occurs every once in a while, starting immediately when the line items are parsed.It also happens regardless of whether it is connected to FSX or not.I tried setting up some whether manually, and it seems to display in FSX ok.I wonder if it is just a bug in the newest downloaded weather file?

Hi,What build of ASX are you using?Thanks,Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/

B1106Networked using simconnect.The issue occurs even if I don't have FSX running at the time.It used to work fine, and actually just started the other day.

Hi Jim,I'm now seeing this as well on my ASXsp3 report window as well:13:16:24: Route data processed...13:16:25: 7687 stations were scanned13:16:25: Weather stream fully populated with new data13:16:28: Problem receiving SimConnect data: Exception from HRESULT: 0xC000013C(Error) Source = 13:16:28: Virtual station generation flags have been reset13:16:32: Error during element identification for ---: Object reference not set to an instance of an object.13:16:52: Problem receiving SimConnect data: Exception from HRESULT: 0xC000013C(Error) Source = 13:16:52: FSX connection closedIt seems to now show-up after I load the same flight-plan that I've been using over the past week or so to help Pete trouble-shoot the super-fog issue. I've also done a fresh reboot of both my machines. It occurs before I even attempt to start FSX on the server, but after I load the FP in ASX.

I have been getting this error message as well since yesterday. No problems with the weather in FSX, though. Using SP2.Kylehttp://www.precisionmanuals.com/images/forum/747400.jpg

Hi All,Still looking into this. I got the error once this morning, but then I can't get it again. All I did is close and restart ASX.Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/

Jim,I wonder if it has something to do with the leap-day yesterday. As you know, I've been using the 2200 metar from Feb 25 for working with Pete. I set the desired date and time on the ASX main-page, let it download the metar, then loaded the same 'old Green Bay, WI flight-plan, then I would see it in the ASX report windows. I wonder if it's the fact that I'm downloading a metar from prior to the leap-day that made this error so consistenlty appear today? Just a thought.(UPDATE 5:41pm) Just realised that ASX was running on my simconnect-client all afternoon. I went back through the log after closing ASX, and the "Element" error was not recorded since 2:14pm EST this afternoon. Could it have cleared itself of the issue?Regards,

Hi,It could be, but the others were getting this before the 29th.Is anyone else still getting this error?Thanks!Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/

Hi Jim,I decided to check if I was still getting the error this morning and indeed, I did. This time, I loaded a FP with the current weather. A few moments later, I set the active weather to 20080225:1700 and noted the following my ASX.log:05:09:01: 7687 stations were scanned05:09:01: Weather stream fully populated with new data05:09:08: Error during element identification for ---: Object reference not set to an instance of an object.05:09:18: Problem receiving SimConnect data: Exception from HRESULT: 0xC000013C(Error) Source = 05:09:18: FSX connection closed05:09:19: Virtual station generation flags have been reset

I am not seeing the error message today. Maybe it was due to the leap day...Kylehttp://www.precisionmanuals.com/images/forum/747400.jpg

Hi all,This is a fairly standard 'warning' indicating that something in the data wasn't readable. It affects only one station. Will look into this to try and read it but it may simply be some bad data that can't be parsed.Best,