FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: garymccl on August 22, 2018, 07:18:58 pm
-
Hi I'm sorry to bring this subject up again, because I have searched for it on your forums and found other people raising it as a problem.
Before today, I have had no problems, but for some reason, now I have loaded up my aircraft in the same position as yesterday, at the same airport, and from CTRL+SHIFT+F12, I - for some reason get the SELECT PARKING FACILITY screen...?
I told P3D what gate I want - the same as yesterday (when GSX didn't bring this screen up - yesterday it gave me the proper loading options, etc...). But for some reasons, today, GSX doesn't think I'm at a gate - and the only thing I can therefore think, is that it's getting it's data from a different place to P3D for gate positions. I have checked out the Scenery Library and it looks no different. I have also rebuilt the airport cache.
What has changed for this airport today? https://photos.app.goo.gl/Nwf4g5ciHE9ZCtRG7
(https://photos.app.goo.gl/Nwf4g5ciHE9ZCtRG7)
-
the only thing I can therefore think, is that it's getting it's data from a different place to P3D for gate positions.
That's why the GSX parking customization page will TELL YOU from which file GSX is taking its data from and, if you read the other similar threads when users said GSX doesn't recognize the parkings, the first reply is always check from which file GSX is taking its data from.
Then, depending on what that page says, we can discuss the reason and the solution.
-
Sorry - but this is rubbish. I have seen plenty of messages on this forum where it looks like the Administrator is getting frustrated over this question, and generally comes back with 'we've already answered your question'...
Because I had a slow reply from you, I went to another forum to try and get help. I did, but it wasn't great. I have sorted the problem, and what I did is what I quoted below. It describes how I fixed it and how annoyed at this software I still am. (Just to note, I have spent most of my life as a software developer, and I would NEVER write a piece of software that relies on the end-user being able to go into the file-system and have to make changes to file names, etc.) If you want your software to use another BGL file - write that into the front end!!! From the other forum:
- I now have this fixed, but I will go into the forum for the GSX software and let them know because I haven't heard from them, despite logging the problem yesterday, and also the fact that I think their software sucks!
I have changed NOTHING on my system. I was using ORBX before, which gave me two files: ADE_FTX_ENG_EGNT_CVX.bgl and ADE_FTX_ENG_EGNT.BGL. I have renamed them with the '.old' file extension, and it has fixed it after I regenerated the airports in P3D.
WHY have I had to use a rubbish piece of software that does not even give me a front-end to do this? I have to go through the back-end of the Windows file system to fix something, and I don't know caused the problem! If it gives you a front end to change the docking/gate positions, I can understand it will want to override the setting in the Scenery Objects library, but surely someone can say why this becomes a read-only area of the airport manager in GSX...? Why can't you browse for another BGL file, or revert to the original???
By the way - I HAD read all of the documentation, and it didn't help...
-
Sorry - but this is rubbish.
It's not.
I have seen plenty of messages on this forum where it looks like the Administrator is getting frustrated over this question, and generally comes back with 'we've already answered your question'...
I usually always include a link to previous messages that discussed and answered the same thing.
Because I had a slow reply from you, I went to another forum to try and get help.
You went on Avsim forum a few *hours* after you posted here, without even realizing it was in the middle of the night HERE! Are you trying to say that, unless we work 24/7, our support can only be flagged as "slow" ?
It describes how I fixed it and how annoyed at this software I still am. (Just to note, I have spent most of my life as a software developer, and I would NEVER write a piece of software that relies on the end-user being able to go into the file-system and have to make changes to file names, etc.) If you want your software to use another BGL file - write that into the front end!!!?
Sorry, but you are so wrong in this reply, that I don't even know where to start.
I'm not sure what kind of software you write but, I would NEVER write a piece of software that would touch any files belonging to OTHER 3RD PARTY PRODUCTS installed alongside the same host.
Because, if you haven't realized it, the simulator is a host, and what you are installing are, essentially, 3rd party plug-ins that CAN have conflicts between each other but, if would be WRONG, WRONG and WRONG AGAIN, if one of them tried to fix conflicts in OTHER files not belonging to itself!
In any case, I can see plenty of replies on Avsim too to the same message you posted here and, guess what, they are all saying the same thing so, maybe, it would be best if you reconsidered what you said.
-
I'm not sure what kind of software you write but, I would NEVER write a piece of software that would touch any files belonging to OTHER 3RD PARTY PRODUCTS installed alongside the same host.
I write software for lawyers! Not that it matters - but it is more than one piece of 3rd party stuff needs to talk to another, and I have to be in the middle. Anyway - not important.
Because, if you haven't realized it, the simulator is a host, and what you are installing are, essentially, 3rd party plug-ins that CAN have conflicts between each other but, if would be WRONG, WRONG and WRONG AGAIN, if one of them tried to fix conflicts in OTHER files not belonging to itself!
Well, I would certainly agree that all pieces of software should say (if applicable) that they are compatible with each other as well as the host. As I said, I've made no changes to the system to have it change the way it is talking to me when I'm at EGNT gate 9... I can't explain the change, which is why I came here.
As far as I'm concerned, for me at least, it's fixed. My only suggestion would be that the software area where you can modify the gates (and make that a higher priority than other 3rd party party) should have an option to say "Returning to using Scenery Library Raw data for this airport"...?
You went on Avsim forum a few *hours* after you posted here, without even realizing it was in the middle of the night HERE! Are you trying to say that, unless we work 24/7, our support can only be flagged as "slow" ?
For that, I'm very sorry - you are very right, I was impatient, and that is completely my fault to go and do that. :-[
Gary
-
BTW, I think you have a fantastic piece of software that has made P3D look so much better from my point of view...
It's true - and I just wanted to let you know!
Gaz
-
I'm not sure what kind of software you write but, I would NEVER wri should have an option to say "Returning to using Scenery Library Raw data for this airport"...?
I don't know what you are referring to "Scenery Library Raw data". The scenery library is, of course, precisely the place where GSX takes its data from, and it obviously respects its layer priority.
It cannot prevent conflicts, it cannot prevent fault AFCADs, and cannot prevent conflict data coming from two airports. No software can, unless it was explicitly sold as a troubleshooting utility, and fact that nobody even tried to do such utility, is quite telling.
-
the only thing I can therefore think, is that it's getting it's data from a different place to P3D for gate positions.
That's why the GSX parking customization page will TELL YOU from which file GSX is taking its data from and, if you read the other similar threads when users said GSX doesn't recognize the parkings, the first reply is always check from which file GSX is taking its data from.
Then, depending on what that page says, we can discuss the reason and the solution.
Ok Umberto, I did what you suggested. First some background information:
I started P3D, selected the PMDG 777 and chose CYVR gate 73. Here's a pic showing the 777 parked at gate 73 at CYVR:
https://1drv.ms/u/s!AkjJbty_NdPA3lwXpnt0OfvomSTA (https://1drv.ms/u/s!AkjJbty_NdPA3lwXpnt0OfvomSTA)
Next, when I select CTRL+SHIFT+F12, I got the "Select parking facility" menu, but what I wanted is ground services menu to select the boarding option. Here's a pic of that:
https://1drv.ms/u/s!AkjJbty_NdPA3l3A4nsaLcDeczlp (https://1drv.ms/u/s!AkjJbty_NdPA3l3A4nsaLcDeczlp)
Next, as per your quote above, I opened the GSX parking customization page and here's a pic of what came up for your troubleshooting pleasure:
https://1drv.ms/u/s!AkjJbty_NdPA3l4uCetB1UzS_Yec (https://1drv.ms/u/s!AkjJbty_NdPA3l4uCetB1UzS_Yec)
Now, as you said, let's discuss the reason and the solution.
As an added note, I hit CTRL+SHIFT+F12 again and selected the same gate 73, followed by "Just warp me there". I thought since I chose the exact same gate that my aircraft would remain in the exact spot. But no such luck. The aircraft was re-positioned at gate 73 with the nose inside the terminal building (see two pics below). However, the good news is that now when I select CTRL+SHIFT+F12, I get the "Activate ground servises" menu. Yayyyyy lucky me! NOT.
https://1drv.ms/u/s!AkjJbty_NdPA3l-DLjR7X3LEeTfN (https://1drv.ms/u/s!AkjJbty_NdPA3l-DLjR7X3LEeTfN)
https://1drv.ms/u/s!AkjJbty_NdPA3mC_npD5nY-dFyug (https://1drv.ms/u/s!AkjJbty_NdPA3mC_npD5nY-dFyug)
So Umberto, I did what you suggested. What's your solution?
Tony
-
Next, as per your quote above, I opened the GSX parking customization page and here's a pic of what came up for your troubleshooting pleasure:
As clearly indicated in that screenshot, the culrprit (as usual) is...
ORBX!!
You have a conflicting AFCAD for CYVR coming with Orbx FTX PNW which you should:
1) Ensure it stays on a LOWER layer than FSDT CYVR, exit the sim and enter it again. GSX should recreate the airport cache and hopefully read the correct AFCAD.
OR
2) Just remove that file. Hopefully, there aren't any *other* conflicting AFCADs for CYVR and/or no installer for OrbX will try to restore it.
-
The idea here to note is that you will have conflicting afcads/airport files at ANY and ALL airports that you have payware scenery in the same areas as any ORBX FTX regions that you will need to fix or address to display correctly.
-
As clearly indicated in that screenshot, the culrprit (as usual) is...
ORBX!!
You have a conflicting AFCAD for CYVR coming with Orbx FTX PNW which you should:
1) Ensure it stays on a LOWER layer than FSDT CYVR, exit the sim and enter it again. GSX should recreate the airport cache and hopefully read the correct AFCAD.
OR
2) Just remove that file. Hopefully, there aren't any *other* conflicting AFCADs for CYVR and/or no installer for OrbX will try to restore it.
It's already at a lower level than CYVR. Unless I'm reading it wrong. Here is a pic of the scenery library:
https://1drv.ms/u/s!AkjJbty_NdPA3mG2Z8WV-0J95eae (https://1drv.ms/u/s!AkjJbty_NdPA3mG2Z8WV-0J95eae)
Also, I renamed the conflicting Orbx file .old and when I restarted P3D and CTRL+SHIFT+F12 I got an error saying it can't find it. I guess your suggestion didn't work. Any other ideas?
-
Also, I renamed the conflicting Orbx file .old and when I restarted P3D and CTRL+SHIFT+F12 I got an error saying it can't find it. I guess your suggestion didn't work. Any other ideas?
There are 4 CYVR files to disable in FTX PNW, but you can get away with leaving FTX_PNW_objects_CYVR_Delta_PLC.bgl intact if you want.
-
As clearly indicated in that screenshot, the culrprit (as usual) is...
ORBX!!
Really? LOL You're hilarious Umberto!!!
ORBX is a high-end scenery developer. One of the best. Are you really that arrogant that you're going to blame ORBX as being the culprit for the problems that your software creates? You really are a piece of work!
I have purchased many airport sceneries from Aerosoft, Fly Tampa, ImagineSim, LatinVFR, Taxi2Gate, TropicalSim and of course ORBX and not one of their airports has any issues with ORBX. Furthermore, I find it strange that we, the end user, have to manually disable some files in order for your software not to conflict with them. ORBX PNW was the first thing I installed. Way before FSDT CYVR or GSX. I would have agreed with you if your software was installed first and then ORBX created the conflict when it was installed. But you expect us to believe ORBX is the culprit when it was installed first before your software? Now, that's hilarious to say the least. If your software was truly as superior as you claim, and especially since you've been aware of the problem for quite sometime now, it would have identified the conflict on its own and renamed the conflicting files, the same way Chase Plane or EzDok automatically rename two files in TrackIR. Other well-written software do the same also. But not yours. Every time I have experienced a problem with any of your products, you always blamed others without exception.
I sincerely hope someone develops a GSX and CYVR alternatives very soon. But for now, I guess I'm stuck with yours.
-
Wow.... lol are you even close to semi-serious FlyingAce? Have you even looked on the ORBX compatibility forum about making their sceneries compatible with other addons? It's fairly clear from your reply that you have little understanding of how it all works, but you really really should go and have a look.
-
ORBX is a high-end scenery developer. One of the best. Are you really that arrogant that you're going to blame ORBX as being the culprit for the problems that your software creates? You really are a piece of work!
I sincerely hope someone develops a GSX and CYVR alternatives very soon. But for now, I guess I'm stuck with yours.
And apparently we with you. ;D ORBX is indeed high end but also rather arrogant in messing with other developers scenery. ::)
Clayton
-
Really? LOL You're hilarious Umberto!!!
I only presented with the facts.
ORBX is a high-end scenery developer. One of the best. Are you really that arrogant that you're going to blame ORBX as being the culprit for the problems that your software creates? You really are a piece of work!
The file comes is made by OrbX and comes with an Orbx scenery. Removing that file from the OrbX folder will fix the problem. How you can possibly say it's a problem "created" by GSX ?
Assume you found a file in an FSDT folder that created a problem TO an OrbX scenery (is there such thing ? I would like to know), and you found that removing that FSDT file from the FSDT folder fixes the problem. Who's to blame ? OrbX ? Obviously not so, why the reverse is valid, according to your own twisted logic ?
I have purchased many airport sceneries from Aerosoft, Fly Tampa, ImagineSim, LatinVFR, Taxi2Gate, TropicalSim and of course ORBX and not one of their airports has any issues with ORBX.
Let's see:
Crash at FlyTampa CYYZ, wrongly attributed to FlyTampa, the user eventually found it was caused by ORBX OpenLC NA
http://flytampa.org/forum/viewtopic.php?f=1&t=10318&hilit=orbx&start=28
Elevation problem at FlyTampa EHAM, solution unknown, but I'm sure FlyTampa didn't do EHAM like that:
http://flytampa.org/forum/viewtopic.php?f=32&t=12211&hilit=orbx
Elevation problem at FlyTampa St.Marteen, user decided to uninstall Vector, to keep using FlyTampa:
http://flytampa.org/forum/viewtopic.php?f=14&t=12167&hilit=orbx
FlyTampa EHAM not displaying correctly after installing OrbX True Earth NL:
http://flytampa.org/forum/viewtopic.php?f=32&t=12116&hilit=orbx
http://flytampa.org/forum/viewtopic.php?f=32&t=12050&hilit=orbx
For the 2nd issue, OrbX made a fix.
Another problem at St. Marteen, which has been fixed by removing an OrbX file:
http://flytampa.org/forum/viewtopic.php?f=14&t=10637&hilit=orbx
Should I continue ? There a 50 pages of search result in FlyTampa's forum about OrbX. It's so common that, some users even start their post by saying "I'm not using any OrbX products", obviously because they might have *searched* the forum and found how common these issues are.
Furthermore, I find it strange that we, the end user, have to manually disable some files in order for your software not to conflict with them.
You got it backwards. You don't have to remove ANYTHING from "our software", which obviously works perfectly as it is. What you MUST remove, instead, are conflicting files from OTHER products, regardless who made them.
It's common knowledge that, when you buy an add-on airport, you should remove any duplicates files for the SAME airport you have, and this is valid in any case, regardless if the conflicting file came with OrbX, with an AI Traffic product, with another freeware scenery of the same airport: in ALL cases you want to find duplicates and remove them and, of course, if you bought an add-on airport, the file you want to keep is the one that comes with that airport.
ORBX PNW was the first thing I installed. Way before FSDT CYVR or GSX. I would have agreed with you if your software was installed first and then ORBX created the conflict when it was installed. But you expect us to believe ORBX is the culprit when it was installed first before your software? Now, that's hilarious to say the least.
It might sound "hilarious" to you, only because you have no idea how the simulator works, how exclusion files works, why they are made in a certain way, and why respecting the layer priority doesn't ALWAYS guarantee two sceneries from the same airport will never go into conflict.
Yes, in a perfect world, the scenery installed last should always get an higher priority, and thus exclude everything below.
But there are bugs in the .BGL exclude system, which forces developers to not use large exclude areas, because they cause issues with autogen, jetways and special effects, so add-on airports usually have many small exclude files, which precisely exclude all objects for the default scenery, so autogen, jetways and effects will always work, but at the cost that a file for the same airport CAN cause conflicts, even if it stays on a lower layer in the Scenery Library.
Why you think ADE does excludes that way ? Why you think there are TOOLS made precisely to find AFCAD duplicates ? If your theory of "the scenery installed last should fix everything belows" was valid, there wouldn't be any need of such tools to begin with.
If your software was truly as superior as you claim, and especially since you've been aware of the problem for quite sometime now, it would have identified the conflict on its own and renamed the conflicting files, the same way Chase Plane or EzDok automatically rename two files in TrackIR. Other well-written software do the same also. But not yours. Every time I have experienced a problem with any of your products, you always blamed others without exception.
I hope this wrong sentence of yours has been based on your wrong assumption that the conflicting files came from OUR files. I really hope you don't seriously think we should remove conflicting files in OTHER products! That would be WRONG, totally wrong. We would NEVER, EVER touch anything that came with another developer product.
There was one thing we did: in case of KLAS, which was also a victim of some OrbX files that caused elevation issues to it, since OrbX HAS made a fix for the problem THEY caused TO KLAS, our Live Update *recognize* the OrbX fix and will not consider it extraneous which is, basically, the same as what I said before: NEVER touch any files not belonging to you, which includes the OrbX fix, which IS a file made by OrbX.
I sincerely hope someone develops a GSX and CYVR alternatives very soon. But for now, I guess I'm stuck with yours.
I'll excuse this comment of yours, which was clearly based on wrong assumptions. But I'm sure you understood my explanation, and I hope you changed your mind about this. Several other users, here and on other forums, have stressed the importance of knowing what you are installing, and maintaining your simulator free of conflicting files.
-
Also, I renamed the conflicting Orbx file .old and when I restarted P3D and CTRL+SHIFT+F12 I got an error saying it can't find it.
This has been explained elsewhere on the forum.
In order to speed up the cache regeneration time and the simulator startup time, GSX will not check each and every .BGL installed to see if it has been changed (there might be ten of thousands) but, instead, it only checks the FOLDER last modification date, for a speedup of at least 10x (or more, depending how many .BGL a folder contains).
When you RENAME a file, SOMETIMES the folder last modification date doesn't change, so GSX cannot detect a cache rebuild is required. Which is why, there's an option in the Couatl menu to "Restart and rebuild the airport cache", which should be used in these cases, which will refresh the cache and that error will go away.