FSDreamTeam forum
Products Support => XPOI FSX/P3D => Topic started by: JDLinn on March 02, 2017, 01:12:46 am
-
Hi ... Often when I'm flying, XPOI just stops working and there is nothing about it in the drop down. The addon manager is still there. It doesn't crash or anything, it just disappears. Can't find anything in the events log. Any ideas? I can reload the sim, and it is there and working fine.
Thank you
Doug
-
Enable logging in the Troubleshooting page of the GSX Settings menu and, if it happens again, exit from the sim and check your Couatl.LOG file and, eventually, send it to me ( email is best ), to see if there's anything wrong with it.
-
Hi ... I don't have GSX, Just XPOI ... where can I find the troubleshooting page of the GSX Settings menu?
Doug
-
Hi ... I don't have GSX, Just XPOI ... where can I find the troubleshooting page of the GSX Settings menu?
Sorry, I assumed you had GSX, since it's quite a bit more popular than XPOI (pity, because it's XPOI is a nice little program). There's no user interface to enable logging if you have just XPOI, so you must enable it manually, this way:
open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case l and a capital F )
Save the file as couatl.ini in the %APPDATA%\Virtuali folder, run FSX and then exit after it finished loading. Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content.
-
(No wonder you have 5 stars!) :-)
Made it, pasted it, just ran P3D, and checked it, and there is a log there now. Wonderful! So Now I'll do some flying and wait for it to crash, then grab that log and send it to you. Thank you, sir!
----OFF Topic - As a side note, we fly mostly "bush" planes and routes at Return to Misty Moorings (my web site). So not a huge need for GSX. But XPOI is almost BASIC to what we are doing ... since almost everything is VFR. I also fly on Twitch (mistymoorings) and flying the Alaska back country with XPOI is a real treat with XPOI because it lets people identify what they are seeing out the window. I was surprised to see you say that XPOI is not used much ... for anyone flying as we do, it is a MUST!!! (And thank you for putting the GLACIERS in as a component). I would hope others "discover" XPOI ... so much more fun than looking at a panel and a sky in front of you!
Doug
-
I was flying down the Columbia River broadcasting on Twitch and it happened. You can see it at the 1 hour and 14 second mark of this video: https://www.twitch.tv/videos/125900194 . I stopped the broadcast and grabbed the log. I changed the extension on it from "log" to "txt" to attach it here. Let me know if this is what you needed.
Doug
Update: A friend of mine made a 30 second "clip" of XPOI quitting, here's what it looked like: https://clips.twitch.tv/SpicyElegantSpiderWTRuck
-
Was the log helpful? Should I send another one?
Doug
-
Was the log helpful? Should I send another one?
Yes, the log shows Simconnect returned bogus data, as if it was corrupted somehow, this was the error:
exception UNRECOGNIZED_ID in call SetDataOnSimObject param #3
This one, instead, seems to be a very well known P3D bug of fake exceptions caused by OTHER products, leaking into the wrong client, given the user the wrong impression an addon is faulty, when in fact it's another one.
However, this bug is SUPPOSED to have been fixed in the latest Hotfix 3, have you installed it ?
-
I see the Hotfix 3 ... getting it downloaded now. Thank you. I saw that "error" and wondered about it ... now I know what to look for. Thank you so much. (and I do have NVIDIA 980 TI ... so updating driver too).
Doug
-
OK, got the hotfix 3 "in" and working (I know its in because it wiped out my updated GPS500). So the fix is in. Flew for about an hour and XPOI quit. Sorry, I missed that log, I had fixed some things, went back to check them, they were ok, then realized I'd wiped out the log. So flew another flight and about 1/2 hour in, it quit again and I have that log it is attached (relabeled "txt" to send it).
Let me know what I need to do. I can keep doing this for you or try anything you like. Happy to help.
Doug
-
flew another flight and about 1/2 hour in, it quit again and I have that log it is attached (relabeled "txt" to send it).
That log is not the one coming after a session where Couatl quitted, because it doesn't indicate any issues.
-
That log is not the one coming after a session where Couatl quitted, because it doesn't indicate any issues.
Funny story: "it doesn't indicate any issues" is pretty much what Doug said right after grabbing the log.
The log says: "log started on Wed Mar 08 15:06:12 2017"
This seems to be a perfect match for this Twitch stream:
https://www.twitch.tv/videos/127315530
Interesting time stamps:
00:37:20 - XPOI is still working, after a few seconds, Doug enters IMC
00:42:45 - visibility is back, no XPOI markers visible
00:43:25 - Doug checks the Add-on menu and the Couatl and XPOI entries are gone, then he grabs the log while the sim is paused
00:44:55 - Doug remarks "I don't see the error this time"
So unless Doug grabbed the wrong log file and manipulated the time stamp in the log, I guess that means that either Couatl/XPOI died quietly (or rather, more violently) this time or, for some unknown reason, the error message didn't make it into the log?
Perhaps that in itself provides some valuable information?
Cheers,
Marc
PS: This was not a singular incident. On a previous stream, Couatl/XPOI vanished, but we made the mistake to try to revive Couatl by restarting the exe and the log was overwritten. I asked Doug to show the last page of the log on stream (before restarting Couatl, ie. before it was overwritten) and I distinctly remember commenting on the peculiarity that it did not end with an error message. The last 20-30 lines looked exactly like the ones in the log Doug provided in his last post.
-
Funny story: "it doesn't indicate any issues" is pretty much what Doug said right after grabbing the log.
Which simply confirms what I said. The PREVIOUS log indicated a LOT of issue, which were related to the outdated P3D, since the Hotfix 3 is supposed to fix the UNRECOGNIZED_ID which DID appear in the previous log.
XPOI is still working, after a few seconds, Doug enters IMC
Is REX being used ? We had another unrelated report, where there are problems that seem to kill Simconnect altogether, with no logs, when REX injects the weather.
On a previous stream, Couatl/XPOI vanished, but we made the mistake to try to revive Couatl by restarting the exe and the log was overwritten.
That's probably what happened here again so, we are not looking on a meaningful log.
-
Which simply confirms what I said.
IMHO it doesn't, but since the video proof doesn't count, there's nothing else I could contribute. Back to Doug with the weather.
-
IMHO it doesn't
Yes, it does, and it really seems you are not getting my point. Saying "simply confirms what I said", doesn't mean anything more than what it says: the log doesn't show ANY issues. The previous log DID so, as I've said, something has changed by installing the Hotfix.
Maybe you didn't get the issue clear enough: the Hotfix will only STOP Exceptions caused by other addons to be wrongly reported to other clients! THAT'S IT.
So, by applying the Hotfix, one will stop see errors reported in the wrong client, so he wouldn't mislead thinking the previously affected client was the cause. In this case, Exceptions that used to be reported in the Couatl.LOG.
But the Hotfix won't magically "fix" the issue that CAUSED the Exceptions it will simply start to report them to the CORRECT client, the one that caused them in the first place!
That's why it's normal that exceptions won't appear in the Coautl.LOG anymore now, because there weren't CAUSED by it, they were only mistakenly reported to it, because the Hotfix wasn't installed.
But if the real culprit is still causing exceptions, and these are confusing Simconnect, up to the point to create a problem to XPOI, no Hotfix will fix this.
WHICH IS WHY, I asked if a 3rd party weather engine was used, because the report of "Doug enters IMC 00:42:45 - visibility is back, no XPOI markers visible", LOOKS LIKE a problem caused when the weather changed and THERE IS another report in another thread of REX causing this.
-
Good Morning. Our posts crossed and mine didn't make it, so reposting.
Nope, no REX here. But I do have ACTIVE SKY NEXT with the CLOUD ART installed and that can make weather "happen." Good explanation on the Hotfix and error reporting, very interesting.
Here's my plan for now. I'll fly as I usually do and see if/when it quits again and grab the log (which again probably will show nothing). After that happens, if it does, then I'll fly a long flight without ACTIVE SKY NEXT ... maybe there's a problem there. But this will be a way for us to find out. Is there anything else you want me to do on my end? (I really appreciate the help).
XPOI is the best program of its kind, and perfect for what I'm doing (broadcasting low and slow flights) ... So I'm going to use it whether or not we ever find the problem ... it is that good! I'll keep you posted with what is happening. If you have anything for me to try, let me know.
Doug
-
OK. I flew out of Prince Rupert and set a direct route to Anchorage at 6500 feet and just let it run with "unlimited fuel" activated. ACTIVE SKY NEXT was turned on and working. Everything was working fine. I ran some errands (3 hours) and came back and looked at it, and even though way out over ocean (where no XPOI data points), the XPOI had disappeared from the menu, meaning it had stopped again. The log is attached. I still don't see any error on it. But it did stop working again.
Now I'm going to do the same thing, fly direct from Prince Rupert to Anchorage at 6500 feet with ACTIVE SKY NEXT turned OFF. This will be a good test because if it stops again, we'll know it isn't ACTIVE SKY NEXT. I'll keep you posted. And again, if there is something I can try for you, I don't mind being a beta to help you.
Doug
-
ACTIVE SKY OFF test. Ran the identical scenario. ACTIVE SKY NEXT was "OFF". The same thing happened about an hour into the flight. So it is not ACTIVE SKY NEXT.
I've attached two logs (don't know if it makes a dif for you or not). The 01 is BEFORE I turned off P3D. The 02 log is after P3D was shut down. They look the same to me and I don't see an error.
I'm not running any other active programs that I can think of, except FSUIPC. So I'm out of ideas to try here. From an amateur's point of view, it looks like the log isn't catching the error at all. (Is this because I don't have GSX? Maybe some relationship with logging with that program?).
Another Clue. I have FSUIPC and have it turned on to "save" a flight I'm running every half hour or so. When I reloaded this latest one where XPOI stopped, when it reloaded, XPOI was there and in the menu and working perfectly.
I now also see an error in my event viewer ... and it shows the same for both instances today. Attached is a screen shot of the error.
Hope all of this helps.
Doug
Update: I have the "latest" FSUIPC. I downloaded the latest Version "4.962 found." I downloaded 4.964 but it will not install to the latest version of P3D (HotFix 3). So I think I'm up to date on FSUIPC.
-
Latest Log from 3.10.2017 about 8:30 PM EST
It stopped this time about 15 minutes into the flight. Active Sky was running. Attached is the log (I don't see any errors) and a copy of the event error.
Doug
-
Try to simply lower the POI density, by turning off some categories and/or lowering their visual range in the XPOI Settings.
It's POSSIBLE there's an hard limit on the number of objects that can be created by the sim through Simconnect calls, that we simply are unaware of, since it's not documented in the SDK.
The issue is, XPOI takes all its data from the internet, and it's likely the geonames data base it's bigger than what it used to be in 2009 when XPOI was designed, so it might require some tweaking in some areas, to keep the load manageable.
-
Ok I'll back out some items and see what happens. But did you notice the errors I'm getting with my event manager? Also it whole be nice if we could back off the distance for the items. Backing off the distance for the name wouldn't do anything for this problem. A range of 5 miles, 10, 15 woold be good. If you back off only on the names showing, the calls have still been made. I'll back things off and keep you posted.
Doug
-
Also it whole be nice if we could back off the distance for the items. Backing off the distance for the name wouldn't do anything for this problem. A range of 5 miles, 10, 15 woold be good. If you back off only on the names showing, the calls have still been made.
That's not how XPOI works, and that's why there's no separate option for the xpoi items. The item and each separate letter of the name are entirely separate calls so, controlling the distance of the title is far more effective.
-
OK, cut everything back, more than half. Turned off the POI and Facilities settings ... nothing was showing. It quit after 30 minutes and I was flying over ocean near Hawaii (not much to pop up anyway). Please look at these two errors from my event log for the computer. I've attached the log (shows nothing), and the two Administrative Errors from the Computer's events log.
Doug
-
Again, the error logs do not show anything. Try to XPOI altogether.