altransam Posted October 21, 2011 Share Posted October 21, 2011 These are the files that report errors when flying near KSEA: 1st batch are when Vashon is actived: D1A6009E-4DFC-104E-5B12-008A1AEBD112 D1A6009E-4DFC-104E-5B12-008A0FEBD112 2D5914EA-C73D-9D75-E7B6-A464C1039EFA 2D5914EA-C73D-9D75-E7B6-A464C0039EFA A60255B9-508F-4920-9941-BFFB775E49C4 ED7359B9-1F03-47E2-A239-EA9EDE2C292E B066FD23-4286-42AC-80CB-54EDE24EB4AF DA38729E-2824-C2CD-2B40-DE43C0A98A51 ECFC514A-EED1-45D4-9D5D-709566E9FF65 AE5CF9BF-BF9A-44B3-8E09-676ACD31F810 Then, when i deleted Vashon: 214EB039-2677-4FC1-99CF-83F9D30E793D DFED50C0-A47B-4B8E-88EC-A2138B7F9DFC 91EC56E4-A729-44DB-8A10-4EE02841A901 15E5E15A-ABC5-4E4F-AE0A-B369281979F7 966EE4A7-2F81-469F-A19C-918AFB4BC759 DFEA5A78-7EA4-4F92-A23C-FB765B4C0550 145C9036-7495-4A23-A446-CD3A5597CFD8 76FE2F0B-A355-4C2F-80C0-8EBB65DAFDB7 059EF9B0-1257-43DD-9374-E3E5DECA634A 61F2BC07-E105-4033-9818-64830E990332 1C454F43-EF18-4BF6-92AA-D8A1385999B8 8F6E16A7-9AE1-4BBE-A047-4FE975D83D2A do these files belong to ORBX or default FSX and, could they be responsible for G3D.dll crashes ? Thank you.... Link to comment Share on other sites More sharing options...
altransam Posted October 23, 2011 Author Share Posted October 23, 2011 36 hours + and no response.... Forgot to mention the first batch of files come up when you choose KSEA as a starting point...and when FTX central switch to default, there is no error... Link to comment Share on other sites More sharing options...
Wolter van der Spoel Posted October 23, 2011 Share Posted October 23, 2011 sorry I'm not always around did you install the latest Library files from the support page ? Link to comment Share on other sites More sharing options...
altransam Posted October 23, 2011 Author Share Posted October 23, 2011 Yes, no change.... Link to comment Share on other sites More sharing options...
Ian Routley Posted October 23, 2011 Share Posted October 23, 2011 So .... these are missing GUIDs ? No doubt the team members looking at missing library objects will take a look at them, but there is no list of "missing" library objects with which to compare them. Known library objects have already been incorporated into recent libs. So the only way to troubleshoot such a problem is to Vanilla install FSX and test for missing GUIDs, (and there are many!) Then, install ONLY FTX regions, and airports and test sequentially. Unfortunately, a list of GUIDs of itself is not easily sought out. Logic would suggest, however, that if there were new entries that only occur with Vashon installed, then they are indeed called from Vashon. Bearing in mind that FSX can call objects from a large distance away in line of sight however, this is NOT a given. Do they cause g3d.dll errors? Unknown. On the 36 hours bit, your initial post falls at 8:26am Saturday morning AU, and the most recent one at 11:17pm. I did see your query yesterday, but wasn't aware it required urgent support over the weekend! One of the team will take a look early in the week no doubt. Thanks for the troubleshooting. Link to comment Share on other sites More sharing options...
altransam Posted October 23, 2011 Author Share Posted October 23, 2011 Ian thank you for responding; There was no emergency on my account, I would have expected an acknowledgement sooner, not a resolution these guid files appear only when FTX is switched to NA, when default FSX, no guid and no g3d.dll in KSEA area; I've spent a couple of weeks so far trying to find a solution, as much for myself as for the benefit of other users; I am not able to enjoy flying in PNW, with all the money invested in ORBX's airports in the area so it is a little frustrating. What I would like is an answer to those questions : 1:do these files belong to ORBX or default FSX and, could they be responsible for G3D.dll crashes ? 2: What can I do on my end, re-install just PNW or FSX completely ? Just say the word... I am not blaming anybody but since I have no clue as what to do and these problems only occur when PNW is activated, this is why i asked for you guys help. I had a g3d.dll before over Washington DC that i was able to point towards KIAD from Imaginesim but this time, i'm lost as even with all addons from library deactivated except ORBX, G3D.dll error comes back 99% of the time... Have a nice week end Link to comment Share on other sites More sharing options...
Ian Routley Posted October 24, 2011 Share Posted October 24, 2011 These are library entries that are called but not present. They are not "files" as such. All known ORBX GUIDs have been patched into ORBXLIB updates (but of course there may be others) With regard to your specific questions: 1. As explained above. Not known. 2. I doubt a reinstall will necessarily fix these, unless you think the install has been corrupted in some way. Finding GUIDs that are referenced but not present is an ongoing issue. There is no master list of them, apart from those that have been patched. If you are running the latest ORBXLibs then these should not be flagging. We can only look at your list as a report and see if there are instances of these in scenery placement. Link to comment Share on other sites More sharing options...
altransam Posted October 24, 2011 Author Share Posted October 24, 2011 Fair enough, I"ll be waiting.... Yesterday I deleted and reinstalled PNW, then the PNW.004 patch, then the library 111014; same guid missing, same G3D.dll 5 minutes later... :'( Link to comment Share on other sites More sharing options...
altransam Posted November 5, 2011 Author Share Posted November 5, 2011 Well, I finally found why I had missing GUID in KSEA area, we know they come from Vashon which I deleted but other GUID appears (the second batch) so to get rid of them, I renamed my FSX install, made a repair option on both FSX and acceleration, reinstall PNW with patch only, test flight from KORS to KPDX ok; install PFJ and patch, test ok, Install NRM, test ok, install CRM, same; then I installed airports one at a time, test between each install, ok, no GUID and NO G3D.dll CRASHES !!!! Then I compared ORBX/ FTX_NA folders of my new install and my original and noticed something: WA69 (I guess it is installed at the same time as 2S1) ! I deleted it of my original install, re-tested and Voilà ! no more GUID or crashes..... Finally !!!! Hope this will help you guys.. Alain from Montreal Link to comment Share on other sites More sharing options...
Ian Routley Posted November 5, 2011 Share Posted November 5, 2011 Thanks Alain, So just to confirm ... you've reinstalled WA69, but not Vashon, and the problems are gone? We have been doing some work on Vashon, and have eliminated (I think) all the errant objects. It may d=form part of a patch, when some other things are sorted. Thanks for the input. Link to comment Share on other sites More sharing options...
Rob Abernathy Posted November 5, 2011 Share Posted November 5, 2011 Thanks Alain, So just to confirm ... you've reinstalled WA69, but not Vashon, and the problems are gone? We have been doing some work on Vashon, and have eliminated (I think) all the errant objects. It may d=form part of a patch, when some other things are sorted. Thanks for the input. Hi Ian, WA69, Wax Orchards, is part of the Vashon install isn't it? Not a separate install. Link to comment Share on other sites More sharing options...
Ian Routley Posted November 5, 2011 Share Posted November 5, 2011 TBH, I can't remember! So many airfields you have over there. I believe you are correct. Link to comment Share on other sites More sharing options...
altransam Posted November 5, 2011 Author Share Posted November 5, 2011 Since i did not find a separate installer for WA69, I supposed it came with 2S1 installer, I was hoping you would confirm Ian LOL... I did not reinstall Vashon, please take a look at WA69 also ? thanks Alain from Montreal Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.