FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: fnav77 on August 23, 2022, 03:49:57 pm
-
Hi,
How come a new version of GSX for MSFS messes up P3D's GSX so badly?
When releasing new software, are you guys not testing it, because surely the problems would have been spotted straight away? Everybody now has a broken version of GSX for P3D.
Are you in such a rush to release a broken product to make money at the detriment of quality and customer satisfaction? This is extremely poor practice!
When I update a piece of software I expect it to work, I am not supposed to be a beta tester or spend my life on this forum to find out it actually is broken.
I know P3D is not your priority anymore but as your customer I expect the product I purchased from you to be working.
I don't appreciate you always put the blame on users for getting things wrong, not knowing what to do, etc...In this particular case YOU are the ones who got it awfully wrong....What a disaster!
So... please fix this ASAP and in a way that it is easy to update/correct via the Live Updater for example (not by having to follow 50 dodgy DIY steps requiring a computing technology degree).
Thank you.
-
Agreed wholeheartedly,
Since purchasing GSX for FSX and now using it on P3Dv5.
I have seen nothing but arrogance, combativeness, and a complete disregard for the customer by the developer. I find the responses on here along the lines of bullying and it's unacceptable!
-
Agreed wholeheartedly,
Since purchasing GSX for FSX and now using it on P3Dv5.
I have seen nothing but arrogance, combativeness, and a complete disregard for the customer by the developer. I find the responses on here along the lines of bullying and it's unacceptable!
You obviously live in a different world to me. How rude. And wrong.
-
Agreed wholeheartedly,
Since purchasing GSX for FSX and now using it on P3Dv5.
I have seen nothing but arrogance, combativeness, and a complete disregard for the customer by the developer. I find the responses on here along the lines of bullying and it's unacceptable!
You obviously live in a different world to me. How rude. And wrong.
No actually I don't... go take a look at how condescending the developer is to people on this forum... I personally got the brunt of it a while ago when asking a simple question when I upgraded to v5.
-
Hi,
How come a new version of GSX for MSFS messes up P3D's GSX so badly?
When releasing new software, are you guys not testing it, because surely the problems would have been spotted straight away? Everybody now has a broken version of GSX for P3D.
Are you in such a rush to release a broken product to make money at the detriment of quality and customer satisfaction? This is extremely poor practice!
When I update a piece of software I expect it to work, I am not supposed to be a beta tester or spend my life on this forum to find out it actually is broken.
I know P3D is not your priority anymore but as your customer I expect the product I purchased from you to be working.
I don't appreciate you always put the blame on users for getting things wrong, not knowing what to do, etc...In this particular case YOU are the ones who got it awfully wrong....What a disaster!
So... please fix this ASAP and in a way that it is easy to update/correct via the Live Updater for example (not by having to follow 50 dodgy DIY steps requiring a computing technology degree).
Thank you.
Hello,
I fully agree with this message.
I myself had many problems with GSX during my transition from Prepar3D v4 to v5. As a customer, I expected understanding, help and above all respect. I got yelled at as if I was responsible.
When I asked a question about missing features on P3D v5, I was told that P3D was not their priority anymore.
Today, like many people, I find myself handicapped on P3D without this add-on which is (we're not going to hide it) essential. The dozens of open topics, all less clear than the other, do not allow the slightest understanding of a possible resolution to this problem.
GSX was released for MSFS, that's good, but it's even more problematic for P3D. So please have the decency to quickly fix the problem for P3D and don't just excuse that the problem doesn't exist because P3D is no longer current enough in your opinion.
You are selling GSX for P3D v5 (at least that is what is stated on your website). So if you're charging that much for this add-on, please be kind to make it work.
Thanks in advance.
-
Lots of replies in the MSFS thread, nothing useful here.
At minimum a working rollback is actual needed.
-
At minimum a working rollback is actual needed.
Instructions how to download and install the latest full P3D installer have been already provided.
-
At minimum a working rollback is actual needed.
Instructions how to download and install the latest full P3D installer have been already provided.
As I already told you (http://www.fsdreamteam.com/forum/index.php/topic,26761.msg175732.html#msg175732), I installed the download you provided. This does not solve my problem with P3D v5. Still waiting for a fix.
-
At minimum a working rollback is actual needed.
Instructions how to download and install the latest full P3D installer have been already provided.
It does not work. Here's an entire thread with people replying that following your instructions does not fix the issue: http://www.fsdreamteam.com/forum/index.php/topic,26834.0.html
-
It does not work. Here's an entire thread with people replying that following your instructions does not fix the issue
There isn't an "entire thread", after my last post with more clear and revised instructions, only two replied, one that didn't want to remove the Addon Manager, another saying it doesn't work, without proving extra information.
Proving a log when something doesn't work, is always helpful.
-
It does not work. Here's an entire thread with people replying that following your instructions does not fix the issue
There isn't an "entire thread", after my last post with more clear and revised instructions, only two replied, one that didn't want to remove the Addon Manager, another saying it doesn't work, without proving extra information.
Proving a log when something doesn't work, is always helpful.
Solve this ----> see attachment
-
Tried the new installer twice yesterday - both times with problems including the “coatl not started” error which I had not seen before. Does seem that the current install is not compatible with P3D.
-
Tried the new installer twice yesterday - both times with problems including the “coatl not started” error which I had not seen before. Does seem that the current install is not compatible with P3D.
The process coatl.exe opens ok here (i can see the icon in systray), BUT as soon as i click in "OK" to fly, the process crashes. And there is a crash error message in windows events monitor saying that coatl.exe process crashed but it not says why (at least in my low TI knowledge)
After that, there is no GSX option in "Addons menu", only the "Addon Manager" saying that all my FSDT products are in TRIAL mode (Even if they all were activated ok before this gsx issue)
-
Assuming you installed the offline installer and nothing else, a crash like that seems to be caused by the antivirus, be sure it's configured to have the whole Addon Manager folder in the Exclusions, then run the offline installer again.
-
Thanks Umberto, but my antivirus (Kaspersky) is the same as allways as before. I didnt change anything and it was working perfetly before.
Anyway, i did another try just now to verify and this time i created a exclusion in kaspersky antivirus:
(https://imagizer.imageshack.com/v2/1280x1024q90/922/Zx9Dfa.jpg) (https://imageshack.com/i/pmZx9Dfaj)
When P3D is opened it appears to be working ok:
(https://imagizer.imageshack.com/v2/1280x1024q90/923/oTu5jh.jpg) (https://imageshack.com/i/pnoTu5jhj)
As soon as i click in "fly" the coatl.exe process closes:
(https://imagizer.imageshack.com/v2/1280x1024q90/922/OFN4dP.jpg) (https://imageshack.com/i/pmOFN4dPj)
No GSX options in addon menu, just "addon manager":
(https://imagizer.imageshack.com/v2/1280x1024q90/923/r0YZVk.jpg) (https://imageshack.com/i/pnr0YZVkj)
The error message in windows event viewer:
(https://imagizer.imageshack.com/v2/1280x1024q90/924/tVKXaP.jpg) (https://imageshack.com/i/potVKXaPj)
This is the file i ran before start the simulator (Ran just this one):
(https://imagizer.imageshack.com/v2/1280x1024q90/922/aDwCmO.jpg) (https://imageshack.com/i/pmaDwCmOj)
If i run coatl.exe by hand, it shows all my addon in TRIAL mode. If i try to register my products again, this happens:
(https://imagizer.imageshack.com/v2/1280x1024q90/924/PHSf7A.jpg) (https://imageshack.com/i/poPHSf7Aj)
This situation happened just AFTER the fatidic update. Before, it was working perfeclty (even with antivirus on, etc)
As said before, im not complaining, just trying to add more information. The log is attached below. (I waited in the sim for the time to recreat a new DB as instructions, wich is fast here in my end) But if there is no coatl.exe process running i doubt it was creating anything.
I think ill stop trying correct this for now and wait for a final correction. It´s better.
Thanks and good luck.
-
Your log shows the program crashed while rebuilding the airport cache in D:\Prepar3D v4, try to add this folder too to the antivirus Exclusions.
-
Hi! As can be seen in the first image of my post in the previous page "1" of this topic, i have already "D:\Prepar3D v4" in the exclude list.
BUT, i tried again with antivirus completely OFF with the same results. (Coatl.exe process crashes)
Your post suggests that the issue is when recreating the scenery cache file. Is there a way to force NOT to recreate the scenery cache just to see if GSX opens?
I saw this in the log:
Airport cache not valid: file meta.txt not found or malformed (Is this an issue?)
I have already tried to delete the whole "C:\ProgramData\Virtuali\Couatl" folder. It was recreated ok in the first time i opened p3d after. But coatl.exe process still crashes.
And a question: if i completely unistall GSX/GSX2 from my p3dv4 install and installs it from zero, can this issue be resolved? Remembering that this issue started at the same time of situation we´re currently facing.
Thanks again for your time.
-
I see all those crashes are with P3D 4, and in fact I now can crash it too. I've been using only V5 for all tests, not sure what's the difference, since the Couatl64 exe is the same, but we now at least know where to look for.
-
Hello, try this guys:
http://www.fsdreamteam.com/forum/index.php/topic,26999.msg177358.html#msg177358
It corrected the couatl.exe process crash for me. Good luck!
-
In any case, I suggest trying the Live Update now, I realized we uploaded a version of the P3D V4 Addon Manager ( bglmanx64.dll ) which had logging enabled, and this would slow it down the startup.
-
Will do. Thanks Umberto!